This section provides general information about the following topics:
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 are the physical components that comprise the database. They are stored in and administrated via database locations.
The following types of database spaces exist for each database:
Note:
Do not directly manipulate these files, but use the Tamino Manager
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.
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.