Administration Considerations

This section provides general information about the following topics:

Space Management

Database Locations

In order to use the physical storage on a node, the Tamino Manager uses the concept of database locations. Database locations are where the Tamino database spaces are stored. The Tamino Manager maps these database locations (which can also be thought of as logical names) to physical location paths.

Let us suppose that a database administrator has a directory called C:\Myfiles\Tamino\mydbbackup, in which she/he plans to store backup copies of his database mydb. Using the Database Location Manager, she/he can assign the database location name of mydbBackup to this directory. Once this has been done, she/he can administrate the files via the location name without having to remember where they are physically located.

Database Spaces

Database spaces are the physical components that comprise the database. They are stored in and administrated via database locations.

Types of database spaces

The following types of database spaces exist for each database:

Space Type File Extension Purpose
Index Space 1I0 Contains the database's meta data, e.g. indexes
Data Space 1D0 Contains the database's data
Log Space 1L0 Contains the information required to recover updates after restoring a database
Backup Space 1B0 Contains database backups
Tamino CD Database Info File 1R0 Contains the information required to register a CD database with the Tamino Manager
Journal Space 1J0 Contains the information required for transaction rollback
Journal Overflow Space 1O0 Journal overflow spaces are used to save pending global transactions and the logging records of long running transactions. Journal overflow is automatically created or extended if it is necessary, and it will also be automatically removed or decreased during server shutdown.
Temporary Sort Space 1S0, 1T0, 1F0, 1W0 Contains temporary data
Utility Recovery Space 1C0, 1C1 Contains log information from calls to the Data Loader
Tamino dump file 0M0, 1M0 Contains information for error analysis by Software AG support

Do not directly manipulate these files, but use the inoadmin command line tool for all operations. These files are deleted when a database is deleted, with the exception of the dump files. Dump files can be deleted manually if they are no longer needed for error analysis by Software AG support. Backup files can be kept with a corresponding option in the Delete Database dialog box.

Problem Reporting

How to prepare Problem Information

If a problem occurs at a customer's site, Software AG's support team will attempt to provide a solution as fast as possible (in some cases, software is also distributed via partners, who are responsible for support themselves). To minimize the time required to analyze a problem and deliver a solution, the support team requires detailed information about the problem.

The problem information should contain:

  • Problem description:

    • Tamino component or function used

    • Error messages (message IDs) and texts

    • A short description of the problem

  • Environment description:

    • Tamino version

    • Operating system version

    • Hardware environment (CPU type, disk device types, etc.)

  • Can the problem be reproduced?

    • What are the steps to reproduce it

    • Which data is needed to reproduce it (schemas, XML instances, queries)

If the problem is not reproducible, the problem information should contain additionally:

  • Where does the problem occur?

    • On all databases, or on a single database only

    • On databases within a specific environment only

    • Environments where the problem does or does not occur

  • When does the problem occur?

    • Always or only sporadically

    • In parallel with other events

    • Periods of time when the problem does not occur

    • When the problem first occurred

    • Changes of the environment around this date

    • Last changes of the environment before this date

If Tamino creates crash dumps that are associated with a problem, they can also be sent to the support team. The files in question have the suffix 0M0 or 1M0 and can be found in the database's reserve location. The files should be compressed using a ZIP utility before sending them in order to save space.