Messages and Codes: General Messages - Set 2

The last server session of the database was terminated abnormally. Before the database can be used, the data consistency will be re-established, changes which had not been written to disk will be redone, and transactions which were open at the time of the abnormal server session termination will be reset.

Wait for the end of the autorepair processing before using your database.

The server has encountered an error situation which causes a crash. In order to enable error analysis, the server writes status information to a file in the reserved location.

Report the crash to your software supplier, together with the dump files in the reserved location.

This is a generic message that is used for identification of an activity.

No action required.

The database recovery processing is starting. After restoring a database, the recovery processing re-applies all updates that were done since the database backup was created.

Wait for the end of the recovery processing before using your database.

The database restore is being performed without recovery processing. Log space information will be marked as skipped.

Wait for the end of the recovery skipping before using your database.

The database recovery processing is starting. After restoring a database, the recovery processing re-applies all updates that were done between the database backup creation and the specified time.

Wait for the end of the recovery processing before using your database.

This is a generic message that is used for identification of an activity.

No action required.

The allowed database size is limited by the amount allowed in your license file. The attempted expansion of the database would have exceeded the allowed size.

Please contact your software supplier for an enhanced license which allows a larger database size.

Source and destination of a copy operation must not specify the same object.

Please specify another source or destination for the copy operation.

The copy operation was incomplete due to a system error.

Please consult your manufacturer's manual.

There was an operating system error while performing the specified operation on the specified file.

Please consult your manufacturer's manual.

The given path does not specify a valid raw section.

Specify a valid raw section.

The size of the given raw section could not be determined.

Please contact your software supplier.

The specified raw section is not empty and must not be reset.

Specify another raw section or deallocate all entries from the specified one.

The specified container is still in use and must not be changed.

Ensure that the container is not in use before trying to change it.

The specified database space is currently in use and must not be deallocated.

No action required.

The specified database space is in use and must not be reallocated.

No action required.

The log space was generated by a previous Tamino version.

Use the previous Tamino version for restore/recovery and then switch again to the current version.

An internal error has occurred. The database can still be used.

Please contact your software supplier and provide the message text.

The server has terminated due to shortage of journal space. This has caused a situation in which the autorestart processing that will run automatically at the start of the next server session cannot be guaranteed to resolve internal data inconsistencies from the current terminated session. Therefore, the next server session will start with an emergency restart.

Restart the server. If the emergency restart completes without error, the database is in a consistent state and can be used normally. If the emergency start fails, you must recover your data using the latest backup.

There was an error in an operation on an index during the database restart processing. All indexes on the affected doctype have been dropped, but the doctype still is available.

After the restart has finished, recreate all indexes by choosing the "Check and Repair" function for the database in the Tamino Manager.

There was an error in an operation on the doctype during the database restart processing. The doctype has been destroyed.

After the restart has finished, restore the doctype.

The database's internal database key is corrupt.

Please contact your software supplier.

The specified raw section does not contain enough contiguous space to allocate the specified database space.

Specify another raw section for this database space or free space in the given raw section.

The required database space is already present.

Remove the database space from the specified raw section.

Raw sections must not overlap with file systems since this can result in data corruption.

Define the raw section so that it does not overlap with a mounted file system.

The operating system's mount table could not be processed.

Please contact your software supplier.

An attempt to decrease the size of the specified raw section failed because the required new size is too small. Only free space at the end of a raw section can be removed.

Specify a raw section partition with a larger size.

An attempt was made to initialize a raw section that is already initialized. A raw section can be initialized only once.

No action required.

At the specified position in the raw section there is not enough contiguous space to allocate the specified database space.

Specify another raw section or another position.

The raw section contains too many database spaces in the management area.

Choose another raw section or remove obsolete database spaces.

An error occurred while trying to allocate space on the specified raw section.

Please contact your software supplier.

There was an operating system error while performing the specified operation on the specified raw section.

Please consult the manufacturer's manual.

The data on the specified raw section is corrupted.

Please contact your software supplier if the section had been initialized.

An attempt was made to define a raw device on a block device. Raw sections must not be block devices.

No action required.

There has been an I/O error during an operation (initialization of a database space). This does not, however, lead to a loss of data.

Check the affected device: is it on-line, are the permissions correct, can operating system tools access the device? If you cannot find the reason for the read error by yourself, please contact your software supplier.

The system could not write the specified database space.

Check the attributes (e.g. permissions) of the database space.

The database space could not be opened.

Check the affected device: is it on-line, are the permissions correct, can operating system tools access the device? If you cannot find the reason for the read error by yourself, please contact your software supplier.

The specified operating system error has occurred.

Please consult the manufacturer's manual.

The given block size is not allowed.

Provide a valid block size.

There is not enough space on the device.

Specify another device or free some space.

The specified tape device cannot be written because the blocking factor is not supported.

Change the blocking factor of the tape device. It must be either variable or a multiple of 1024.

The file structure of the specified file does not match the expectations of the system.

Check the file's content and the defined structure.

During any given server session, there is a limit on how much the database can grow. This limit has been reached in the current server session.

Stop the current server session and restart the database. In the new server session, the database can be extended.

A tape device is required, but the specified path does not point to a tape device.

Correct the path.

An asynchronous I/O operation has failed due to an operating system error.

Check for problems with the device. Check whether the device is off-line or read-only. In the case of a logical volume, try to access all of its physical devices by using operating system commands. Check the system log file for appropriate error messages.

The input does not uniquely identify a keyword.

Please specify an unambiguous keyword.

There was an error in an operation on a doctype. The doctype has been excluded from further recovery processing.

Please contact your software supplier.

A text index has encountered an error.

Please contact your support center and provide them with the information given in the error message and with a backup copy of your database.

A text index has encountered an error.

Please contact your support center and provide them with the information given in the error message and with a backup copy of your database.

This message indicates an installation error.

Please consult the manufacturer's manual. If you cannot fix the error, contact your software supplier.

The journal space was insufficient. Recovery processing was terminated.

Provide more journal space. Restart the terminated activity.

The log space does not contain correct log information.

Check if files have been moved or copied to the log space location.

A doctype required for recovery processing was not found. The doctype has been excluded from further recovery processing.

If the previous recovery processing aborted, restart the restore and recovery.

A doctype required for recovery processing was locked. The doctype has been excluded from further recovery processing.

The doctype may be locked due to an abort of previous recovery processing. Restart the restore and recovery.

There was an error in an operation on an index of a doctype. The index of the doctype has been disabled.

After the recovery has finished, recreate the index by choosing the "Check and Repair" function for the database in the Tamino Manager.

The index remains in a disabled state from a previous abort during recovery processing.

After the recovery has finished, recreate the index by choosing the "Check and Repair" function for the database in the Tamino Manager.

Although the sub-function is a valid function request, it has not yet been implemented for the utility. This is an internal message.

Please contact your software supplier.

This is an internal message.

Please contact your software supplier.

A utility issued a request to allocate temporary memory, but this request failed. The utility will now terminate, and the administration agent will carry out any necessary recovery tasks.

No action required. Please contact your system administrator for further information.

An internal configuration error has occurred. The utility will now terminate, and the administration agent will carry out any necessary recovery tasks.

No action required. Please contact your system administrator for further information.

A sub-function was specified that is not valid for the utility.

Specify a valid sub-function for the utility.

The virtual operating system could not open the requested file.

Make sure that the file is available.

An attempt was made to start a utility against a database that had not terminated correctly.

Start the database, and let the autorepair processing complete. Then rerun the utility.

A syntax error was detected in the parameters of a utility.

Correct the syntax error and rerun the utility.

A file synchronization operation has failed at the operating system level.

Check the manufacturer's manual.

An error has occurred while an operation on a semaphore was requested from the operating system.

Check the manufacturer's manual.

The log space does not contain correct log information.

Check if files have been moved or copied to the log space location.

The log space does not contain correct log information.

Check if files have been moved or copied to the log space location.

The log space could not be opened. The recovery function has been stopped.

Check if files have been moved or copied to the log space location.

A transaction has been aborted. All changes of this transaction have been undone.

Check whether a higher transaction timeout value would make sense in your environment. Restart the transaction.

A transaction has been aborted. All changes of this transaction have been undone.

Check the reason for the transaction abort. Restart the transaction.

A server session was explicitly stopped by the administrator. All changes of this transaction have been undone.

No action required.

A transaction has been aborted because there was not enough space to log all the changes of the transaction or because too many transactions were active at the same time. All changes of this transaction have been undone.

Consider enlarging the journal space. Restart the transaction.

A transaction has been aborted. All changes of this transaction have been undone.

No action required.

A transaction has been aborted because its locking requirements caused a deadlock with other transactions. All changes of this transaction have been undone.

Restart the transaction.

A transaction has been aborted. All changes of this transaction have been undone.

Please contact your software supplier.

The specified database error has occurred.

Please contact your software supplier.

The doctype may be locked or may have been corrupted by a previous action (e.g. failed server restart).

If the doctype is locked, wait until it is unlocked, then retry. If the doctype was corrupted by a previous action, the system administrator must rebuild the doctype from backups.

The indexes may have been corrupted by a previous action (e.g. failed server restart).

Wait for a short while, then retry. If the problem persists, this might indicate that the indexes have to be rebuilt. To rebuild the indexes, choose the "Check and Repair" function for the database in the Tamino Manager.

The operating system has signalled an I/O error. This is typically caused by a hardware error.

Check whether any disk devices have gone offline. Check the error log for hardware errors.

An internal inconsistency has been found in the indexes.

The indexes have to be rebuilt. To rebuild the indexes, choose the "Check and Repair" function for the database in the Tamino Manager.

An internal error occurred. This could result in incorrect data.

Please contact your software supplier.

An error in an I/O related function has occurred.

Please contact your software supplier.

The specified length value is invalid.

Correct the length specification.

The FI option is only allowed if a non-zero standard length is given.

Correct the input line.

The wrong input file has been used for the utility.

Ensure that the correct input file is being used by the utility.

The database could not be completely repaired.

Please contact your software supplier.

The structure of the data to be loaded is invalid.

Ensure that the correct input file is being used. Send the load files (extension 1C0/1C1) to your software supplier.

It is not possible to attach the process to the shared memory.

Ensure that there is enough available memory, and contact your software supplier if required.

The specified response has been returned by the server.

Determine the reason for the response, or contact your support center.

It is not possible to access the database server.

Determine the reason why the database server is not accessible and retry the operation.

The size of an internal buffer has caused a record to overflow.

Please contact your software supplier.

The recovery function was started without supplying an event token.

Check the usage of the administration tool.

When the recovery function is started, logging must be disabled. In this case, the recovery function was started with logging enabled.

Check the usage of the administration tool.

The specified database name is too long. If the database name consists of ASCII characters, it can be up to 16 characters long. If the database name consists of multibyte characters, the total number of bytes required to store the database name must not exceed 16.

Please specify a shorter database name.

A database name cannot contain a comma.

Please modify the database name.

A database name cannot contain certain characters, such as # " . [ ] .

Please modify the database name.

A database name cannot contain a backslash.

Please modify the database name.

The maximum allowed number of data/index files has been reached.

Please contact your software supplier.

The size of the file to be created exceeds the limits of the operating system or of the underlying storage medium. For example, you want to create a file with a size greater than 2GB, but the operating system does not support this.

Select a smaller file size.

An unexpected free space management error occurred when adding a new database file.

Please contact your software supplier.

The information for a log space or a savepoint entry could not be retrieved or set up.

Check the reasons for errors accessing and updating the internal configuration store (for example permissions or low disk space).

The error is caused by an attempt to create a unique index on data that contains non-unique values.

No action required.

A database name cannot contain a space.

Please modify the database name.

The database file has the compressed attribute, which is not permitted, because write errors should be avoided if the device is getting full.

Remove the compressed attribute from the database file.

The information for a savepoint entry could not be retrieved.

Contact your software supplier.

A backup file or a file for recovery purpose could not be moved or removed.

Contact your software supplier.

A log space entry for the given savepoint and session number could not be found.

Contact your software supplier.

A backup space for the given savepoint could not be found.

Contact your software supplier.

The internal information for the file type associated with a savepoint is set up incorrectly.

Contact your software supplier.

An internal error occurred.

Please contact your software supplier.

The autorepair from the crash of the previous server session was not completely successfully.

Check the detailed error messages and repair the affected data.

The database space specified for the current operation is too large.

Retry the operation specifying a smaller database space.

No more extents of the specified space type can be created because the maximum number has been reached.

Retry the operation with a smaller number of extents specified.

The backup file needed for error analysis could not be created due to the given reason.

Please consult the manufacturer's manual.

An error occurred during recovery skipping. This message indicates an internal inconsistency.

Please contact your software supplier.

The system has tried to allocate a new database space, probably because the existing database spaces did not contain enough free space. The allocation has failed.

Check which database space was affected by checking the free space. Allocate another database space manually.

The log information which is needed to recover the database is corrupt, so the database recovery was stopped when the corruption was detected.

Send the log space to your software supplier for analysis.

The specified keyword must not be abbreviated.

Please specify the keyword in full length.

The specified keyword is not recognized or invalid.

Please specify a correct keyword.

An internal syntax error occurred.

Please contact your software supplier to analyze the problem.

The given value has to be in a numeric format.

Please specify a numeric value.

The number of allowed list elements is exceeded.

Please limit the number of list elements to the maximum allowed.

The specified value is too low.

Please enter a value greater than or equal to the required minimum.

The specified value is too high.

Please specify a value less than or equal to the allowed maximum.

The range specified is invalid.

Please specify a range within the allowed limits.

The specified number of characters was too low.

Please specify a sufficient number of characters.

The maximum allowed number of characters was exceeded.

Please specify no more than the maximum allowed number of characters.

The displayed mandatory parameter could not be found and a default value is not available.

Supply the displayed mandatory parameter.

The specified parameter value is invalid.

Correct the input.

The crash dump file is from a different platform.

Go to the proper platform.

The option specified is unknown.

Correct the input line.

The supplied option is not permitted for this function.

Check the input parameters.

The specified level number is not allowed in this context.

Correct the input line.

The specified field name is reserved.

Correct the field name.

The Tamino server cannot be started in read-only mode because the previous session was abnormally terminated.

Start the Tamino server in normal mode to do an autorepair for the abnormal termination. Restart the Tamino server in read-only mode.

The Tamino server cannot be started in read-only mode because of pending global transactions.

Start the Tamino server in normal mode and close the pending global transactions.

An unexpected error occurred while adding a container.

Check the device and the environment variable relating to the new container.

The maximum number of created database spaces within one session has been reached.

Shut down and restart the database server and retry the operation.

There is no more space on the disk for extending the current database space.

Check the disk size where the latest database space is located. Think about creating a new database space on another disk where space is available.

The request to remove a database space failed because the file space at the end of the file is in use.

Ensure that the database space is not in use and retry the operation.

An error occurred during database recovery.

Check for additional error messages in the event log.

A database root block linkage is invalid.

Perform a restore/recover of the database.

It is not possible to access the specified doctype.

Check that the correct doctype name has been specified, and that it is currently available for use.

The file with the given number could not be loaded

Check whether the file exists or is not accessible.

The given function is invalid with an active server.

Shut down the server.

While processing a log space, re-applying updates resulted in an error.

Check if the database was in a different state than it was when the original command was executed. This may be caused by using a backup copy and log spaces inconsistently.

The maximum size of the given database space has been reached. This means the database cannot be extended any more.

A database redesign is necessary. Either delete doctypes from the database or create a second database.

The database space (data) cannot be enlarged. The new database space requires allocations in the index space, but the index space allocation failed due to the internal reason displayed.

Investigate why the index database space cannot be enlarged.

A database space extension failed, so the database could not be enlarged.

View the subsequent error message for information about why the database could not be enlarged.

An internal error occurred while accessing a database container file.

Contact your software supplier and report the number displayed in the message.

The backup with the given representation could not be determined in the database configuration.

Contact your software supplier to analyze the problem.

The database is in an inconsistent state that cannot be handled by the autorepair process. The database must be restored.

The reason for an inconsistent database can be re-applying a mass load during recovery. If no abort timestamp is shown in the event log of the aborted session, perhaps due to a power failure, restart with restore/recover. For any other reasons that will cause the error to re-occur, set up the restore/recover until a timestamp shortly before the recovery abort shown in the event log of the aborted session.

While processing a log space, re-applying the updates resulted in an error.

Check if the database is in a different state than it was when the original command was executed. This may be caused by using a backup copy and log spaces inconsistently.

Replication processing could not be started.

Check for for additional related messages in the event log.

An error during the previous replication processing prevents the continuation of the replication.

If the master database is lost, the Reset Replication function can be used to convert the database for usage as a substitution. In any other case, the replication database has to be recreated using a new backup from the master database.

Replication cannot be continued because a function (e.g. restore without full recover) was executed on the master database which is not yet supported for replication

A backup from the master database after the operation in question should be used to recreate the replication database.

The database identification supplied is already in use.

Repeat the process using an unused database identification.

An internal call has failed to enumerate the defined database names.

Please contact your software supplier.

The master database could not find the log space to return the required log space data.

Check the database properties for the number of backup generations and increase the value if set too low.

The rename function is not allowed for a database which is to be used as a master database for replication purposes.

Remove replication databases first before renaming the database. New replication databases can be created from a backup created after the rename operation.

The name of the replication database was not found in the master database's list of permitted databases.

Add the replication database name to the list of permitted replication databases of the master database.

The replication database does not match the contents of the master database.

Check whether the replication database was created using a backup from another database than the one specified as master database or check whether another database was renamed using the same database name as the master database's name.

An internal parameter error has caused the utility to fail.

Please contact your software supplier.

An internal error occurred.

Please contact your software supplier and provide the message text.

An internal error occurred.

Please contact your software supplier and provide the message text.

An internal error occurred.

Please contact your software supplier and provide the message text.

An unexpected error was returned by the server communication interface.

Please contact your software supplier and provide the message text.

The directory specified does not exist.

Specify a valid directory name.

There is not enough space in the given directory to complete the operation.

Free some disk space or specify another directory.

The file cannot be created in the destination directory because another file with the same name already exists.

Change the destination directory parameter.

The infofile path is too long.

Please specify another directory for the CD database.

An invalid path was specified.

Specify a valid path.

The CD database infofile could not be parsed.

Please contact your software supplier.

A new database cannot be created because there are too many databases already.

Check if you still need all the databases you created and if possible delete some of them.

The server must be offline to perform the requested operation.

Shut down the database.

The work pool used is too small.

Ensure that a sufficiently large work pool is available.

The CD database information file has an invalid format.

This error should not occur unless the file was modified manually. Avoid manual modification in the information file.

The CD database cannot be created because the database is incompatible with the target platform.

Create the CD database on the same platform as the original database.

The required operation cannot be performed on a CD database or read-only database.

Switch the "read only" server parameter to "no". This does not apply to databases on CD.

A location with the same name already exists.

Choose another location name.

There was an attempt to delete the default location or default backup location. Delete operations on these locations are not allowed.

No action required.

A location with the same path settings already exists

Choose another location path.

The specified location was not found.

Correct the location name parameter and try again.

An internal error occurred.

Please contact your software supplier and provide the message text.

An internal error occurred.

Please contact your software supplier and provide the message text.

Unexpected response received while trying to lock the port allocation lock.

Please contact your software supplier.

An invalid port value was detected.

Please specify a valid port value.

A port range has to contain a minimum number of ports.

Please specify a valid port range.

Static and dynamic port range overlap, which is not allowed.

Please specify valid port ranges.

An error occurred while retrieving the static and dynamic port range.

Please contact your software supplier.

At least one port in the given dynamic port range is already in use by another server.

Please specify a dynamic port range where no ports are used by other servers.

An internal error occurred.

Please contact your software supplier and provide the message text.

The given web server is not registered.

Specify a registered web server.

The web server is not correctly registered. Either the IP address or the port number is missing.

Correct the web server registration.

The web server is not assigned to the database.

Check your web server registrations.

The environment extension is not registered in the Tamino configuration.

No action required.

No environment extension registered for Tamino version or server.

No action required.

No extension point definitions were found for the specified version.

Check your configuration.

An invalid port range was detected.

Specify a valid port range.

The component already exists for the extension point in the specified version.

No action required.

The component already exists in the extension section of the specified version.

No action required.

The specified component is not defined for the given extension point and version.

No action required.

The specified component does not exist in the extensions for the given version.

No action required.

The extension point function was not found in the specified extension point library.

Check library name, path and entry points of the extension point library.

The specified extension point does not exist in the given version.

No action required.

The extension point library could not be loaded via the specified path.

Check the library name and path of the extension point definitions.

No port could be allocated in the static port range, because it is full.

Extend the static port range, use a port from outside the static port range or force reusage of a port from the static range.

An error occurred while retrieving the static and dynamic port range.

Please contact your software supplier.

Unexpected response received while trying to lock the raw section lock.

Please contact your software supplier.

The web server specified is already registered. Therefore the rename is not allowed.

Choose another name for the web server or delete the existing web server.

An internal error occurred.

Please contact your software supplier and provide the message text.

The specified web server is already present.

Update the web server.

The specified database spaces are in use and must not be reallocated.

No action required.

The specified database space(s) could not be found in the raw section.

Please contact your software supplier.

The given path does not specify a regular file.

Specify a regular file.

The specified database spaces are in use and must not be deallocated.

No action required.

This item has no data records, therefore a reinvert cannot be performed.

Use the X-Machine programming command "admin" to recreate the index.

The specified database space could not be found.

Correct the database space specification and try again.

The specified database space is in use and must not be changed.

Ensure that the database space is not in use before changing it.

The database is active. Therefore database spaces must not be moved.

Stop the database before moving any database spaces.

An unexpected response was received while trying to grant the container move lock.

Please contact your software supplier.

An unexpected error occurred while reading a data reference block into the internal cache.

Please contact your software supplier.

The input file for a data load operation has a structure level mismatch, or the file is corrupted.

Check if the input file has the wrong structure level or is corrupted.

An internal error occurred.

Please contact your software supplier and provide the message text.

A server parameter was requested in an invalid context.

Please contact your software supplier.

The given server parameter name is invalid.

Specify a valid server parameter name.

Static server parameters must not be changed while the server is active.

Stop the server before changing a static parameter.

The license file does not contain the permission to access raw sections.

Use the file system instead or obtain the required license from your software supplier.

An upgrade is not allowed for a replication database.

If the master database has been upgraded, the replication database must be newly created from the master backup.

The management of physical database spaces has an empty counter.

The database seems to be physically corrupted. Perform a restore/recover.

The blocksize field of first index space does not match the real blocksize.

No action required.

The physical management of the database is corrupted.

Perform a restore/recover.

It was no possible to verify that the specified path points to a tape device.

Make sure that the path is correct, that the tape is in the drive, that the tape device is online and the tape device is properly connected to the system.

This error can occur during 'Add Location', if the requested location type does not match the actual file type.

Specify the correct location type.

Stopping the server failed.

Please contact your software supplier.

An internal server call failed with given error string.

Please look into the server job log if there is additional error information. If not, contact your software supplier.

An internal server call failed with given error string.

Please look into the server job log to see if there is additional error information. If not, contact your software supplier.

The doctype has a lock conflict with a running action of another user.

Investigate which user is active and what activity is causing the lock.

The required database conversion between the stated versions is not supported.

Consult the documentation about possible upgrade options.

An unexpected error occurred while Tamino tried to determine the file type of the displayed location.

Check if the displayed location is accessible. If the location is accessible please contact your software supplier.

The current parameter configuration does not allow the creation of all necessary threads to start and manage the Tamino server.

Either the system defined maximum number of threads per process is too low and should be increased, or the Tamino parameter configuration should be changed to decrease the number of threads to be created.

There are not enough system resources available to create a new thread.

There are not enough system resources available to create a new thread. The reason for that is either that the system defined maximum number of threads per process is exceeded, or that there is not enough memory available to allocate the necessary thread resources.

A backup made in the old version cannot be used, e.g. because this old version is not supported any more. This only applies for databases that are already in a higher version than the backup.

Use a more recent backup to restore the database.

An attempt was made to execute a replication command that requires the master database to be active.

Start the master database and retry the command.

An attempt was made to execute a replication command that requires the replication database to be offline.

Stop the replication database and retry the command.

A restart of the master database is necessary.

Restart the master database and try to set up the replication database again.

The database already has update sessions so it cannot be used to replicate another database.

Use a newly created database and retry this operation.

Permission to replicate the master database was denied.

Ask the administrator to permit replication access to the master database.

This database is not suitable to be set as the replication database of the specified master database. Perhaps the versions are not identical or this one was not created from the backup of the master. Also possible is that this database has its own updates after the creation.

Use another database to replicate the master.

To change the type of a database to a replication database or to set it back to a normal one, the user needs to have administrator rights. Other possible reason: The database is not allowed to replicate the master database.

Log in as administrator and try the operation again and check whether this database is in the permission list of the master database.

An internal error occurred. The server will be stopped.

Please contact your software supplier and provide the message text.

Identical names have been supplied for the master and a replication database, but this is not allowed.

Supply different names.

After a replication database has been reset by 'Set Type to Normal Database', it cannot become a replication database any more.

Delete the database, recreate it from a non-initial backup of the master and execute 'Set Type to Replication'.

The data field layout block with the given number is corrupted.

No action required.

This error may occur when the server is in the starting or stopping phase. During these phases the server is neither online nor offline. The other reason for this error is when the server is offline and there are some activities on the database in parallel, e.g. adding some index space.

Wait until the server is definitely online or offline and than retry.

The operation cannot run in parallel with another operation that requires the server to be running in standby mode.

A standby session is used for the restore/recover operation. Wait until this operation is finished and the server is shut down.

An external backup is an invalid object for this operation.

Some database operations are not allowed for external backups.

A recovery input file must not be moved because it is used by the server.

Try to perform the operation later. A log space will be unlocked after a session switch. Other recovery input files will be unlocked after the termination of a mass load.

Necessary configuration information was not found.

Please contact your software supplier.

A registered backup or recovery file to be moved or deleted does not exist.

Check the locations used for the database whether files have been lost due to unintended removal or restore operations.

A registered backup or recovery file to be moved already exists.

Check the locations used for the database whether files are present due to restore operations or files remaining from a deleted database.

Moving a backup or recovery file failed.

Check access control settings of the location where the file is to be moved.

Removing a backup or recovery file failed.

Check access control settings of the file to be deleted or of the source file to be moved.

An earlier backup was used for a restore not using the recover all option. Due to new modifications done on this base, the newer backup must not be used for restore/recover.

Use another backup for restore/recover. The selected backup can only be used to create new database.

This error can appear during database creation. There are a number of reasons why the creation of the initial backup might fail e.g. a file with the same name already exists in the backup location, a tape is not ready (if the backup medium is tape) or no reading process is attached to a pipe (if backup medium is pipe). The root cause of the error will be given in the job log.

Read the job log to find the root cause of the error. If there is the file with the same name as the initial backup name in the backup location on the file system, remove this file or move it to another place. If the backup medium is tape , ensure that the tape is ready. If the backup medium is a named pipe, ensure that there is a process reading from this pipe.

If native TCP/IP is used as a communication method for the Tamino server the TCP/IP port used must not be set to zero.

Use a valid port number for TCP/IP communication.

The database must be started for this operation.

Start the database.

In specific situations it is not possible to shut down the database with rolling back open transactions. This is: 1. a mass load is active 2. an external backup is active 3. there is a LOG file full situation.

Wait until a mass load or external backup operation is finished and try again. If the log file is full, supply space for the LOG and try again.

There is another modifying job or process active or the server is within startup. Those actions must be serialized.

Check your database state and wait until the server is up or check other modifying database actions.

This is an internal error message.

Please contact your software supplier.

An attempt was made to remove a replication database from the permission list, but the replication database is not present in the permission list.

Retry the command with a correct name.

An attempt was made to add a replication database to the permission list, but the replication database is already present in the permission list.

Retry the command with a correct name.

The database file has been divided among more than one physical file extents. Now while processing this file the given extent is not specified.

Specify all physical file extents.

The support of multiple physical file extents requires that the current file is completely written. However with network file systems (e.g. NFS) if getting full, the current file is less in size than expected. Therefore the switch to the next location is impossible in this case. A local file system should not have those problems.

Be sure that you have enough space at your file system because this one can only support one single file extent. Or take locally attached file systems.

Multiple physical file extents specified by the user are not consistent. Either the extent is missing, unexpected or specified twice or the file does not come from the same database.

Enter all required file extents and verify if they are from the same database.

If the backup consists of multiple file extents it is not possible to (re)move single extents when another database has a reference to it.

Check which database references the backup.

An administration function could not be executed because it must not be used for a replication database.

Check whether the function is to be executed for the master database.

During migration or restore/recover, the database is in an undefined state which cannot be solved. The database cannot be started anymore.

Recover from the latest valid backup or if not possible contact your software supplier.

During migration the database cannot be started because of an internal error.

View the server's startup text file (inosrv.txt) for more information.

The server died during the startup phase.

Inspect the server output file and correct the error.

The operation mode of the database is not suited for changes in this property. Changing it would jeopardize the database consistency.

For a read only database, if you really want to change the parameter, set the "read only" property to "no", modify the parameter, start the database, stop the database, set "read only" property to "yes".

There is no conversion utility of the most recent version found.

Upgrade the conversion only to the current one.

The file specified cannot be opened due to an internal operating system error.

Consult the manufacturer's manual.

An I/O error has occurred on the given database space.

Analyse the internal operating system error.

A database space could not be created because of an operating system error.

Analyse the system error and consult the manufacturer's manual.

Your license does not permit usage of replication databases.

Contact your software supplier for an upgrade of your license.

Your license does not permit usage of replication databases.

Contact your software supplier for an upgrade of your license.

Your license does not permit usage of replication databases.

Contact your software supplier for an upgrade of your license.

Your license does not permit usage of replication databases.

Remove all databases from the master database's replication database table or contact your software supplier for an upgrade of your license.

The utility cannot connect the server which is assumed to be online. Note that the communication goes over XTS.

Check if the database is reachable over the XTS directory service. If you cannot find the reason switch on the XTS tracing facility.

An error was returned from the communication interface when trying to contact the server.

Check whether the communication component is set up correctly and the communication process (e.g. Software AG XTS Directory Server) is running.

The last backup available must not be deleted because in the case of a database crash no restore is possible.

No action required.

To create a backup, either a valid location or directory must be specified.

Specify a valid location or directory.

A block size mismatch has been detected on the specified database space.

Ensure that the block size of the database space to be restored is the same as that in the backup copy.

The storage for database space is exhausted.

Try to allocate more storage; if this is not possible contact your software supplier.

Tamino could not start external backup processing.

Check that the third party hardware and drivers are installed and working correctly. If the symptoms persist, contact your software supplier.

There is possibly a corruption of the internal configuration store.

If the symptoms persist, contact your software supplier.

There is possibly a corruption of the internal configuration store.

If the symptoms persist, contact your software supplier.

There is possibly a corruption of the internal configuration store.

If the symptoms persist, contact your software supplier.

There is possibly a corruption of the internal configuration store.

If the symptoms persist, contact your software supplier.

There is a problem with the database downgrade utility.

If the symptoms persist, contact your software supplier.

The Create/Backup/Restore utility cannot be executed, possibly due to a corruption in the internal configuration store.

If the symptoms persist, contact your software supplier.

Tamino could not start external restore processing.

Check that the third party hardware and drivers are installed and working correctly. If the symptoms persist, contact your software supplier.

There is possibly a corruption of the internal configuration store.

If the symptoms persist, contact your software supplier.

Within parallel backup a client process of the dump utility terminated unexpectedly.

The error value defines the exit code of the client process. There are generally additional error messages describing the situation in detail. Ask your software supplier for the reason of the given error.

The specified character set is not supported by the current software version.

Check for possible typing errors in character set name.

The Tamino software components that you are using are not compatible.

Please request a new version of Tamino from your software supplier.

The database server failed to register with the Software AG XTS Directory Server. The error returned from the XTS layer is displayed as part of the message.

Fix the error situation described by the XTS message or contact your software supplier.

The server failed to create the necessary Software AG XTS Directory Server entries and the server startup failed. The reason for the failure is returned by the XTS layer.

Please check that the service "Software AG XTS Directory Server" is running. If not, please start it. On Windows this can be done using the Control Panel. On UNIX please use the scripts provided (which are normally executed at system start). If the service was running when the error occurred, and the XTS message does not specify enough details to fix the problem, please contact your software supplier.

The server failed to do the necessary parameter setting for the Software AG XTS Directory Server and the server startup failed. The reason for the failure is returned by the XTS layer.

Fix the error situation described by the XTS message or contact your software supplier.

The format for the parent field of a collation descriptor is invalid. The only allowed parent formats are "wide" and "alphanumeric".

Check the collation descriptor definition.

The locale name is misspelled or the locale is not supported.

Check the spelling.

An internal error occurred changing a key value in the internal configuration store.

Please contact your software supplier.

Because of an internal error the internal configuration could not be changed.

Please contact your software supplier.

Internal error, while requesting database ID information.

Contact your software supplier.

Internal error, while requesting database name information.

Please contact your software supplier.

This is an internal error.

Please contact your software supplier.

Most probably, a newer version of the ICU library has been installed and old data is not available In this case, all collating indexes must be rebuilt.

Rebuild the collating index.

This is an internal error.

Please contact your software supplier.

This is an internal error.

Please contact your software supplier.

This error can occur during database creation, or when trying to rename an existing database and a database with the same name already exists.

Specify another name.

The attempt to perform an external database backup failed due to the reason specified in the message.

Correct the error indicated and retry the operation.

A database restore with a connected external system failed due to the reason specified in the message.

Correct the error indicated and retry the operation.

The call to delete an external backup failed due to the reason given.

Correct the error indicated and retry the operation.

A call of EMC's SYMAPI failed for the given reason.

Correct the error indicated and retry the operation.

Configuring the environment for an external backup failed.

Correct the error indicated and retry the operation.

The "Set version" operation is already running on this database.

Wait for the "set version" operation to complete.

The function cannot be processed because of pending global transactions.

Start the Tamino server in normal mode and close the pending global transactions.

The function cannot be processed because the previous session was abnormally terminated.

Start the Tamino server in normal mode to do an autorepair from the abnormal termination.

This message can appear when trying to convert a database to a previous version, but the requested downgrade is not supported.

No action required.

A new user was rejected due to internal reasons.

You can force a memory dump with "inodba database=name trap=9228" for further analysis after reproducing the error.

The temporary work space was too small to execute the requested function.

Consider increasing the temporary workspace by adding locations with free space to the temporary working location.

The temporary work space was too small to execute the requested function.

Consider increasing the temporary workspace.

A transaction has been aborted due to internal reasons. All changes of this transaction have been undone.

You can force a memory dump with "inodba database=name trap=9291" for further analysis after reproducing the error.

There are structural inconsistencies in the database. The database should not be used any longer.

Restore the database from a backup copy and apply the log files. You can force a memory dump with "inodba database=name trap=9130" for further analysis after reproducing the error.

The current load could not be processed because the buffer pool is too small.

Consider increasing the buffer pool size or force a memory dump with "inodba database=name trap=9138" for further analysis after reproducing the error.

There are structural inconsistencies in the database. The database should not be used any longer.

Restore the database from a backup copy and apply the log files. You can force a memory dump with "inodba database=name trap=9127" for further analysis after reproducing the error.

There are structural inconsistencies in the database. The database should not be used any longer.

Restore the database from a backup copy and apply the log files. You can force a memory dump with "inodba database=name trap=9123" for further analysis after reproducing the error.

There are structural inconsistencies in the database. The database should not be used any longer.

Restore the database from a backup copy and apply the log files. You can force a memory dump with "inodba database=name trap=9057" for further analysis after reproducing the error.

There are structural inconsistencies in the database. The database should not be used any longer.

Restore the database from a backup copy and apply the log files. You can force a memory dump with "inodba database=name trap=9058" for further analysis after reproducing the error.

The Tamino Server requires a valid license file. The location of the license file could not be determined.

Contact your software supplier.

The licensing period of Tamino has expired.

Please contact your software supplier for a renewal of your license.