INODSA1000 | Starting autorepair after abnormal termination |
Explanation |
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. |
Action |
Wait for the end of the autorepair processing before using your database. |
INODSA1001 | Start writing crash dump of database, writing to file filename |
Explanation |
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. |
Action |
Report the crash to your software supplier, together with the dump files in the reserved location. |
INODSA1002 | name textversiontext on system information |
Explanation |
This is a generic message that is used for identification of an activity. |
Action |
No action required. |
INODSA1003 | Starting recovery |
Explanation |
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. |
Action |
Wait for the end of the recovery processing before using your database. |
INODSA1006 | Skipping database recovery during restore |
Explanation |
The database restore is being performed without recovery processing. Log space information will be marked as skipped. |
Action |
Wait for the end of the recovery skipping before using your database. |
INODSA1007 | Starting recovery until time |
Explanation |
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. |
Action |
Wait for the end of the recovery processing before using your database. |
INODSA2278 | Tamino name modifierversionmodifier2 on system information |
Explanation |
This is a generic message that is used for identification of an activity. |
Action |
No action required. |
INODSE1015 | Expanding the database has failed, because the licensed database size would have been exceeded |
Explanation |
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. |
Action |
Please contact your software supplier for an enhanced license which allows a larger database size. |
INODSE1025 | Source and destination of the copy operation specify the same object (source) |
Explanation |
Source and destination of a copy operation must not specify the same object. |
Action |
Please specify another source or destination for the copy operation. |
INODSE1026 | Copy operation (location to location) incomplete, copied done of expect bytes |
Explanation |
The copy operation was incomplete due to a system error. |
Action |
Please consult your manufacturer's manual. |
INODSE1027 | System error text during operation call on file file |
Explanation |
There was an operating system error while performing the specified operation on the specified file. |
Action |
Please consult your manufacturer's manual. |
INODSE1028 | pathname does not specify a valid raw section (returned type error) |
Explanation |
The given path does not specify a valid raw section. |
Action |
Specify a valid raw section. |
INODSE1029 | Size of raw section section was computed as 0 |
Explanation |
The size of the given raw section could not be determined. |
Action |
Please contact your software supplier. |
INODSE1030 | Raw section section is not empty and must not be reset |
Explanation |
The specified raw section is not empty and must not be reset. |
Action |
Specify another raw section or deallocate all entries from the specified one. |
INODSE1031 | database space space number of database server in raw section section is in use and must not be changed |
Explanation |
The specified container is still in use and must not be changed. |
Action |
Ensure that the container is not in use before trying to change it. |
INODSE1036 | database space space number of database server in raw section section is in use and must not be deallocated |
Explanation |
The specified database space is currently in use and must not be deallocated. |
Action |
No action required. |
INODSE1037 | database space space number of database server in raw section section is in use and must not be reallocated |
Explanation |
The specified database space is in use and must not be reallocated. |
Action |
No action required. |
INODSE1051 | Structure level mismatch on log space from session session number |
Explanation |
The log space was generated by a previous Tamino version. |
Action |
Use the previous Tamino version for restore/recovery and then switch again to the current version. |
INODSE1052 | Internal error occurred: error string, location location |
Explanation |
An internal error has occurred. The database can still be used. |
Action |
Please contact your software supplier and provide the message text. |
INODSE1055 | Preparing for an emergency restart |
Explanation |
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. |
Action |
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. |
INODSE1056 | During database restart, an error has occurred in an index on doctype doctype (ID). All indexes on this doctype have been dropped. |
Explanation |
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. |
Action |
After the restart has finished, recreate all indexes by choosing the "Check and Repair" function for the database in the Tamino Manager. |
INODSE1057 | During database restart, an error has occurred on doctype doctype (ID). The doctype is no longer accessible. |
Explanation |
There was an error in an operation on the doctype during the database restart processing. The doctype has been destroyed. |
Action |
After the restart has finished, restore the doctype. |
INODSE1060 | Invalid internal database key found |
Explanation |
The database's internal database key is corrupt. |
Action |
Please contact your software supplier. |
INODSE1061 | No space left in raw section pathname for database space space number of database server |
Explanation |
The specified raw section does not contain enough contiguous space to allocate the specified database space. |
Action |
Specify another raw section for this database space or free space in the given raw section. |
INODSE1063 | database space space number of database server already present in raw section section |
Explanation |
The required database space is already present. |
Action |
Remove the database space from the specified raw section. |
INODSE1068 | The raw section section overlaps with a mounted file system |
Explanation |
Raw sections must not overlap with file systems since this can result in data corruption. |
Action |
Define the raw section so that it does not overlap with a mounted file system. |
INODSE1069 | Error accessing the mount table |
Explanation |
The operating system's mount table could not be processed. |
Action |
Please contact your software supplier. |
INODSE1070 | Decreasing the size of the raw section section failed |
Explanation |
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. |
Action |
Specify a raw section partition with a larger size. |
INODSE1071 | Raw section section is already initialized |
Explanation |
An attempt was made to initialize a raw section that is already initialized. A raw section can be initialized only once. |
Action |
No action required. |
INODSE1072 | No space for database space space number of database server at specified position in raw section pathname |
Explanation |
At the specified position in the raw section there is not enough contiguous space to allocate the specified database space. |
Action |
Specify another raw section or another position. |
INODSE1073 | Overflow on raw section section |
Explanation |
The raw section contains too many database spaces in the management area. |
Action |
Choose another raw section or remove obsolete database spaces. |
INODSE1074 | Error allocating database space space number of database server on raw section section |
Explanation |
An error occurred while trying to allocate space on the specified raw section. |
Action |
Please contact your software supplier. |
INODSE1076 | System error text during operation call on raw section section |
Explanation |
There was an operating system error while performing the specified operation on the specified raw section. |
Action |
Please consult the manufacturer's manual. |
INODSE1077 | Raw section section is corrupted or not initialized |
Explanation |
The data on the specified raw section is corrupted. |
Action |
Please contact your software supplier if the section had been initialized. |
INODSE1079 | path is a block device and cannot be used for raw sections |
Explanation |
An attempt was made to define a raw device on a block device. Raw sections must not be block devices. |
Action |
No action required. |
INODSE1080 | I/O error on block number in database space space number (operating system error text) |
Explanation |
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. |
Action |
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. |
INODSE1081 | Journal space must be writable |
Explanation |
The system could not write the specified database space. |
Action |
Check the attributes (e.g. permissions) of the database space. |
INODSE1082 | Error when opening database space space number (at path) |
Explanation |
The database space could not be opened. |
Action |
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. |
INODSE1083 | System error text when opening database space space number (path) |
Explanation |
The specified operating system error has occurred. |
Action |
Please consult the manufacturer's manual. |
INODSE1084 | Invalid block size block size |
Explanation |
The given block size is not allowed. |
Action |
Provide a valid block size. |
INODSE1085 | No space for source left on path |
Explanation |
There is not enough space on the device. |
Action |
Specify another device or free some space. |
INODSE1086 | Tape handling error: blocking factor not supported |
Explanation |
The specified tape device cannot be written because the blocking factor is not supported. |
Action |
Change the blocking factor of the tape device. It must be either variable or a multiple of 1024. |
INODSE1087 | Data error on source |
Explanation |
The file structure of the specified file does not match the expectations of the system. |
Action |
Check the file's content and the defined structure. |
INODSE1088 | A further extent of source cannot be created (reason reason, error text, errtxt) |
Explanation |
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. |
Action |
Stop the current server session and restart the database. In the new server session, the database can be extended. |
INODSE1094 | Tape device required |
Explanation |
A tape device is required, but the specified path does not point to a tape device. |
Action |
Correct the path. |
INODSE1096 | Error text has been signalled in the execution of an asynchronous I/O for id |
Explanation |
An asynchronous I/O operation has failed due to an operating system error. |
Action |
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. |
INODSE1099 | Ambiguous keyword |
Explanation |
The input does not uniquely identify a keyword. |
Action |
Please specify an unambiguous keyword. |
INODSE1100 | Internal database error error on doctype doctype (ID). No further recovery on this doctype. |
Explanation |
There was an error in an operation on a doctype. The doctype has been excluded from further recovery processing. |
Action |
Please contact your software supplier. |
INODSE1101 | Internal error n f g h r in text index |
Explanation |
A text index has encountered an error. |
Action |
Please contact your support center and provide them with the information given in the error message and with a backup copy of your database. |
INODSE1102 | Internal error n f g h x in text index |
Explanation |
A text index has encountered an error. |
Action |
Please contact your support center and provide them with the information given in the error message and with a backup copy of your database. |
INODSE1103 | Loading of text index failed due to operating system error text |
Explanation |
This message indicates an installation error. |
Action |
Please consult the manufacturer's manual. If you cannot fix the error, contact your software supplier. |
INODSE1104 | Journal overflow during recovery processing |
Explanation |
The journal space was insufficient. Recovery processing was terminated. |
Action |
Provide more journal space. Restart the terminated activity. |
INODSE1105 | Invalid structure for log space from session session number |
Explanation |
The log space does not contain correct log information. |
Action |
Check if files have been moved or copied to the log space location. |
INODSE1106 | Doctype doctype not found, no further recovery on this doctype |
Explanation |
A doctype required for recovery processing was not found. The doctype has been excluded from further recovery processing. |
Action |
If the previous recovery processing aborted, restart the restore and recovery. |
INODSE1107 | Doctype doctype locked, no further recovery on this doctype |
Explanation |
A doctype required for recovery processing was locked. The doctype has been excluded from further recovery processing. |
Action |
The doctype may be locked due to an abort of previous recovery processing. Restart the restore and recovery. |
INODSE1108 | Internal database error error on index index name of doctype doctype (ID). All indexes on this doctype have been dropped. |
Explanation |
There was an error in an operation on an index of a doctype. The index of the doctype has been disabled. |
Action |
After the recovery has finished, recreate the index by choosing the "Check and Repair" function for the database in the Tamino Manager. |
INODSE1109 | The index of doctype doctype is not accessible, recovery of this doctype will not include index |
Explanation |
The index remains in a disabled state from a previous abort during recovery processing. |
Action |
After the recovery has finished, recreate the index by choosing the "Check and Repair" function for the database in the Tamino Manager. |
INODSE1111 | Utility sub-function has not yet been implemented |
Explanation |
Although the sub-function is a valid function request, it has not yet been implemented for the utility. This is an internal message. |
Action |
Please contact your software supplier. |
INODSE1112 | Utility handling not implemented |
Explanation |
This is an internal message. |
Action |
Please contact your software supplier. |
INODSE1117 | No more memory can be allocated |
Explanation |
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. |
Action |
No action required. Please contact your system administrator for further information. |
INODSE1118 | Internal configuration error |
Explanation |
An internal configuration error has occurred. The utility will now terminate, and the administration agent will carry out any necessary recovery tasks. |
Action |
No action required. Please contact your system administrator for further information. |
INODSE1120 | Sub-function is not valid for utility |
Explanation |
A sub-function was specified that is not valid for the utility. |
Action |
Specify a valid sub-function for the utility. |
INODSE1121 | Open of file path has failed due to operating system error text |
Explanation |
The virtual operating system could not open the requested file. |
Action |
Make sure that the file is available. |
INODSE1124 | Utility cannot run because of a pending autorepair on the database |
Explanation |
An attempt was made to start a utility against a database that had not terminated correctly. |
Action |
Start the database, and let the autorepair processing complete. Then rerun the utility. |
INODSE1125 | A syntax error has occurred in a utility |
Explanation |
A syntax error was detected in the parameters of a utility. |
Action |
Correct the syntax error and rerun the utility. |
INODSE1128 | System error text occurred during file synchronization |
Explanation |
A file synchronization operation has failed at the operating system level. |
Action |
Check the manufacturer's manual. |
INODSE1130 | System error text occurred during semaphore operation |
Explanation |
An error has occurred while an operation on a semaphore was requested from the operating system. |
Action |
Check the manufacturer's manual. |
INODSE1131 | Invalid server session number session number found in log space block block number |
Explanation |
The log space does not contain correct log information. |
Action |
Check if files have been moved or copied to the log space location. |
INODSE1132 | Invalid block sequence found in log space - expected block number, current is block number |
Explanation |
The log space does not contain correct log information. |
Action |
Check if files have been moved or copied to the log space location. |
INODSE1133 | Error opening log space: error message |
Explanation |
The log space could not be opened. The recovery function has been stopped. |
Action |
Check if files have been moved or copied to the log space location. |
INODSE1136 | Transaction aborted due to transaction timeout |
Explanation |
A transaction has been aborted. All changes of this transaction have been undone. |
Action |
Check whether a higher transaction timeout value would make sense in your environment. Restart the transaction. |
INODSE1137 | Transaction aborted due to non-active connection |
Explanation |
A transaction has been aborted. All changes of this transaction have been undone. |
Action |
Check the reason for the transaction abort. Restart the transaction. |
INODSE1138 | Transaction aborted because server session had been stopped by administrator |
Explanation |
A server session was explicitly stopped by the administrator. All changes of this transaction have been undone. |
Action |
No action required. |
INODSE1139 | Transaction aborted due to overflow in journal space journal space |
Explanation |
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. |
Action |
Consider enlarging the journal space. Restart the transaction. |
INODSE1140 | Transaction aborted due to security violation |
Explanation |
A transaction has been aborted. All changes of this transaction have been undone. |
Action |
No action required. |
INODSE1141 | Transaction aborted due to deadlock |
Explanation |
A transaction has been aborted because its locking requirements caused a deadlock with other transactions. All changes of this transaction have been undone. |
Action |
Restart the transaction. |
INODSE1142 | Transaction aborted due to internal error reason |
Explanation |
A transaction has been aborted. All changes of this transaction have been undone. |
Action |
Please contact your software supplier. |
INODSE1143 | Internal database error error has occurred |
Explanation |
The specified database error has occurred. |
Action |
Please contact your software supplier. |
INODSE1144 | The data of doctype doctype is not accessible |
Explanation |
The doctype may be locked or may have been corrupted by a previous action (e.g. failed server restart). |
Action |
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. |
INODSE1145 | The indexes of doctype doctype are not accessible |
Explanation |
The indexes may have been corrupted by a previous action (e.g. failed server restart). |
Action |
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. |
INODSE1148 | I/O error on database space number |
Explanation |
The operating system has signalled an I/O error. This is typically caused by a hardware error. |
Action |
Check whether any disk devices have gone offline. Check the error log for hardware errors. |
INODSE1150 | The indexes of doctype doctype are corrupt, reason error text |
Explanation |
An internal inconsistency has been found in the indexes. |
Action |
The indexes have to be rebuilt. To rebuild the indexes, choose the "Check and Repair" function for the database in the Tamino Manager. |
INODSE1154 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INODSE1158 | I/O subsystem error (error text/error text): error text |
Explanation |
An error in an I/O related function has occurred. |
Action |
Please contact your software supplier. |
INODSE1167 | standard length out of range |
Explanation |
The specified length value is invalid. |
Action |
Correct the length specification. |
INODSE1171 | FI only allowed if standard-length is given |
Explanation |
The FI option is only allowed if a non-zero standard length is given. |
Action |
Correct the input line. |
INODSE1172 | Wrong input file assigned |
Explanation |
The wrong input file has been used for the utility. |
Action |
Ensure that the correct input file is being used by the utility. |
INODSE1173 | Checked and repaired database. Number of corrupted indexes was number. Of these, repairing failed for failed. |
Explanation |
The database could not be completely repaired. |
Action |
Please contact your software supplier. |
INODSE1175 | Invalid load data structure at file (ID id, length length) |
Explanation |
The structure of the data to be loaded is invalid. |
Action |
Ensure that the correct input file is being used. Send the load files (extension 1C0/1C1) to your software supplier. |
INODSE1176 | Unable to attach to shared memory |
Explanation |
It is not possible to attach the process to the shared memory. |
Action |
Ensure that there is enough available memory, and contact your software supplier if required. |
INODSE1181 | An unexpected server response (response) has occurred |
Explanation |
The specified response has been returned by the server. |
Action |
Determine the reason for the response, or contact your support center. |
INODSE1182 | Database server is not accessible |
Explanation |
It is not possible to access the database server. |
Action |
Determine the reason why the database server is not accessible and retry the operation. |
INODSE1194 | An internal buffer is too large (size) |
Explanation |
The size of an internal buffer has caused a record to overflow. |
Action |
Please contact your software supplier. |
INODSE1198 | Event token not supplied |
Explanation |
The recovery function was started without supplying an event token. |
Action |
Check the usage of the administration tool. |
INODSE1199 | Logging not disabled |
Explanation |
When the recovery function is started, logging must be disabled. In this case, the recovery function was started with logging enabled. |
Action |
Check the usage of the administration tool. |
INODSE1200 | Database name is too long |
Explanation |
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. |
Action |
Please specify a shorter database name. |
INODSE1201 | Database name contains invalid character "," (comma) |
Explanation |
A database name cannot contain a comma. |
Action |
Please modify the database name. |
INODSE1202 | Database name contains an invalid character |
Explanation |
A database name cannot contain certain characters, such as # " . [ ] . |
Action |
Please modify the database name. |
INODSE1203 | Database name contains invalid character "\" (backslash) |
Explanation |
A database name cannot contain a backslash. |
Action |
Please modify the database name. |
INODSE1209 | Maximum number of space files reached |
Explanation |
The maximum allowed number of data/index files has been reached. |
Action |
Please contact your software supplier. |
INODSE1210 | Size of space file too large |
Explanation |
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. |
Action |
Select a smaller file size. |
INODSE1212 | Internal free space error |
Explanation |
An unexpected free space management error occurred when adding a new database file. |
Action |
Please contact your software supplier. |
INODSE1213 | Error error accessing or modifying information in the internal configuration store |
Explanation |
The information for a log space or a savepoint entry could not be retrieved or set up. |
Action |
Check the reasons for errors accessing and updating the internal configuration store (for example permissions or low disk space). |
INODSE1214 | An error occurred during a create index process on doctype doctype |
Explanation |
The error is caused by an attempt to create a unique index on data that contains non-unique values. |
Action |
No action required. |
INODSE1215 | Database name contains a space |
Explanation |
A database name cannot contain a space. |
Action |
Please modify the database name. |
INODSE1217 | Error when opening database space, compressed state is not permitted (at path) |
Explanation |
The database file has the compressed attribute, which is not permitted, because write errors should be avoided if the device is getting full. |
Action |
Remove the compressed attribute from the database file. |
INODSE1221 | Error error when accessing internal information for savepoint savepoint |
Explanation |
The information for a savepoint entry could not be retrieved. |
Action |
Contact your software supplier. |
INODSE1222 | Error error when trying to move or delete file name |
Explanation |
A backup file or a file for recovery purpose could not be moved or removed. |
Action |
Contact your software supplier. |
INODSE1223 | Log space not found for savepoint savepoint, session number session number |
Explanation |
A log space entry for the given savepoint and session number could not be found. |
Action |
Contact your software supplier. |
INODSE1224 | Backup space not found for savepoint savepoint |
Explanation |
A backup space for the given savepoint could not be found. |
Action |
Contact your software supplier. |
INODSE1225 | Backup file type file type is invalid for savepoint savepoint |
Explanation |
The internal information for the file type associated with a savepoint is set up incorrectly. |
Action |
Contact your software supplier. |
INODSE1226 | Unexpected return code error when executing function function |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier. |
INODSE1231 | Errors have occurred during autorepair |
Explanation |
The autorepair from the crash of the previous server session was not completely successfully. |
Action |
Check the detailed error messages and repair the affected data. |
INODSE1232 | Database space is too large |
Explanation |
The database space specified for the current operation is too large. |
Action |
Retry the operation specifying a smaller database space. |
INODSE1233 | The limit of extents for container name has been reached |
Explanation |
No more extents of the specified space type can be created because the maximum number has been reached. |
Action |
Retry the operation with a smaller number of extents specified. |
INODSE1235 | Crash dump file filename could not be created due to operating system error error text (errtxt) |
Explanation |
The backup file needed for error analysis could not be created due to the given reason. |
Action |
Please consult the manufacturer's manual. |
INODSE1236 | Recovery skipping has terminated with an error |
Explanation |
An error occurred during recovery skipping. This message indicates an internal inconsistency. |
Action |
Please contact your software supplier. |
INODSE1318 | Internal server error during database creation, reason: reason |
Explanation |
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. |
Action |
Check which database space was affected by checking the free space. Allocate another database space manually. |
INODSE1320 | Log space structure error error number |
Explanation |
The log information which is needed to recover the database is corrupt, so the database recovery was stopped when the corruption was detected. |
Action |
Send the log space to your software supplier for analysis. |
INODSE1374 | No abbreviation allowed for this keyword |
Explanation |
The specified keyword must not be abbreviated. |
Action |
Please specify the keyword in full length. |
INODSE1375 | Invalid keyword |
Explanation |
The specified keyword is not recognized or invalid. |
Action |
Please specify a correct keyword. |
INODSE1376 | Syntax error |
Explanation |
An internal syntax error occurred. |
Action |
Please contact your software supplier to analyze the problem. |
INODSE1380 | Given value not numeric |
Explanation |
The given value has to be in a numeric format. |
Action |
Please specify a numeric value. |
INODSE1381 | Only number value(s) allowed |
Explanation |
The number of allowed list elements is exceeded. |
Action |
Please limit the number of list elements to the maximum allowed. |
INODSE1382 | Value has to be greater than or equal to value |
Explanation |
The specified value is too low. |
Action |
Please enter a value greater than or equal to the required minimum. |
INODSE1383 | Value has to be less than or equal to value |
Explanation |
The specified value is too high. |
Action |
Please specify a value less than or equal to the allowed maximum. |
INODSE1385 | Invalid range specified |
Explanation |
The range specified is invalid. |
Action |
Please specify a range within the allowed limits. |
INODSE1386 | At least number character(s) required |
Explanation |
The specified number of characters was too low. |
Action |
Please specify a sufficient number of characters. |
INODSE1387 | Only number character(s) allowed |
Explanation |
The maximum allowed number of characters was exceeded. |
Action |
Please specify no more than the maximum allowed number of characters. |
INODSE1390 | Missing mandatory parameter value |
Explanation |
The displayed mandatory parameter could not be found and a default value is not available. |
Action |
Supply the displayed mandatory parameter. |
INODSE1391 | Invalid parameter value |
Explanation |
The specified parameter value is invalid. |
Action |
Correct the input. |
INODSE1416 | architecture mismatch detected, file from platform |
Explanation |
The crash dump file is from a different platform. |
Action |
Go to the proper platform. |
INODSE1498 | unknown option |
Explanation |
The option specified is unknown. |
Action |
Correct the input line. |
INODSE1506 | option not permitted |
Explanation |
The supplied option is not permitted for this function. |
Action |
Check the input parameters. |
INODSE1512 | transition to this level not allowed |
Explanation |
The specified level number is not allowed in this context. |
Action |
Correct the input line. |
INODSE1523 | reserved field name |
Explanation |
The specified field name is reserved. |
Action |
Correct the field name. |
INODSE1538 | Read-only mode is not permitted because the previous session was abnormally terminated |
Explanation |
The Tamino server cannot be started in read-only mode because the previous session was abnormally terminated. |
Action |
Start the Tamino server in normal mode to do an autorepair for the abnormal termination. Restart the Tamino server in read-only mode. |
INODSE1539 | Read-only mode is not permitted because of pending transactions |
Explanation |
The Tamino server cannot be started in read-only mode because of pending global transactions. |
Action |
Start the Tamino server in normal mode and close the pending global transactions. |
INODSE1603 | Error when adding a new type |
Explanation |
An unexpected error occurred while adding a container. |
Action |
Check the device and the environment variable relating to the new container. |
INODSE1604 | Number of additional name extents currently exhausted |
Explanation |
The maximum number of created database spaces within one session has been reached. |
Action |
Shut down and restart the database server and retry the operation. |
INODSE1605 | No space for extending database space |
Explanation |
There is no more space on the disk for extending the current database space. |
Action |
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. |
INODSE1606 | Database space to be removed is in use |
Explanation |
The request to remove a database space failed because the file space at the end of the file is in use. |
Action |
Ensure that the database space is not in use and retry the operation. |
INODSE1633 | Recovery terminated with error |
Explanation |
An error occurred during database recovery. |
Action |
Check for additional error messages in the event log. |
INODSE1769 | Invalid database root block header (size block size / next block) |
Explanation |
A database root block linkage is invalid. |
Action |
Perform a restore/recover of the database. |
INODSE1898 | The specified doctype is not available. |
Explanation |
It is not possible to access the specified doctype. |
Action |
Check that the correct doctype name has been specified, and that it is currently available for use. |
INODSE1913 | File file not loaded |
Explanation |
The file with the given number could not be loaded |
Action |
Check whether the file exists or is not accessible. |
INODSE1945 | Function not permitted while server is running |
Explanation |
The given function is invalid with an active server. |
Action |
Shut down the server. |
INODSE1976 | Internal database error error during recovery processing |
Explanation |
While processing a log space, re-applying updates resulted in an error. |
Action |
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. |
INODSE1979 | Database space space has reached the upper limit |
Explanation |
The maximum size of the given database space has been reached. This means the database cannot be extended any more. |
Action |
A database redesign is necessary. Either delete doctypes from the database or create a second database. |
INODSE1984 | Allocation of a new data space failed on required index allocation (reason) |
Explanation |
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. |
Action |
Investigate why the index database space cannot be enlarged. |
INODSE1987 | Error when extending type |
Explanation |
A database space extension failed, so the database could not be enlarged. |
Action |
View the subsequent error message for information about why the database could not be enlarged. |
INODSE1992 | Invalid container request type |
Explanation |
An internal error occurred while accessing a database container file. |
Action |
Contact your software supplier and report the number displayed in the message. |
INODSE1995 | Access to configuration information for savepoint 'name' failed: message |
Explanation |
The backup with the given representation could not be determined in the database configuration. |
Action |
Contact your software supplier to analyze the problem. |
INODSE1996 | Database is inconsistent, restore required |
Explanation |
The database is in an inconsistent state that cannot be handled by the autorepair process. The database must be restored. |
Action |
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. |
INODSE1999 | Internal database error error during recovery processing on doctype doctype |
Explanation |
While processing a log space, re-applying the updates resulted in an error. |
Action |
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. |
INODSE2000 | Starting replication failed |
Explanation |
Replication processing could not be started. |
Action |
Check for for additional related messages in the event log. |
INODSE2001 | Replication processing cannot be continued due to previous replication error |
Explanation |
An error during the previous replication processing prevents the continuation of the replication. |
Action |
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. |
INODSE2004 | Invalid operation detected |
Explanation |
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 |
Action |
A backup from the master database after the operation in question should be used to recreate the replication database. |
INODSE2013 | Database identification already in use |
Explanation |
The database identification supplied is already in use. |
Action |
Repeat the process using an unused database identification. |
INODSE2014 | Failed to enumerate databases |
Explanation |
An internal call has failed to enumerate the defined database names. |
Action |
Please contact your software supplier. |
INODSE2019 | No log space data found for session session number |
Explanation |
The master database could not find the log space to return the required log space data. |
Action |
Check the database properties for the number of backup generations and increase the value if set too low. |
INODSE2020 | Replication database(s) defined, rename not allowed |
Explanation |
The rename function is not allowed for a database which is to be used as a master database for replication purposes. |
Action |
Remove replication databases first before renaming the database. New replication databases can be created from a backup created after the rename operation. |
INODSE2022 | Replication permission denied by master database |
Explanation |
The name of the replication database was not found in the master database's list of permitted databases. |
Action |
Add the replication database name to the list of permitted replication databases of the master database. |
INODSE2023 | Replication database origin mismatch |
Explanation |
The replication database does not match the contents of the master database. |
Action |
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. |
INODSE2024 | An internal utility parameter error (location) has occurred |
Explanation |
An internal parameter error has caused the utility to fail. |
Action |
Please contact your software supplier. |
INODSE2031 | Internal error occurred: DSIF name [name - line] text parameter value |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2033 | Internal error occurred: OVO function [name - line] error |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2034 | Internal error occurred: SMP function [name - line] error |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2035 | Server communication interface [name - line] error error |
Explanation |
An unexpected error was returned by the server communication interface. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2036 | path is not a valid directory |
Explanation |
The directory specified does not exist. |
Action |
Specify a valid directory name. |
INODSE2037 | Insufficient free disk space on path - available size MB, needed needed MB |
Explanation |
There is not enough space in the given directory to complete the operation. |
Action |
Free some disk space or specify another directory. |
INODSE2042 | File name already exists in the destination directory name |
Explanation |
The file cannot be created in the destination directory because another file with the same name already exists. |
Action |
Change the destination directory parameter. |
INODSE2043 | Infofile cannot be created, because otherwise the full path name of the info file would exceed operating system limit |
Explanation |
The infofile path is too long. |
Action |
Please specify another directory for the CD database. |
INODSE2045 | File path does not exist |
Explanation |
An invalid path was specified. |
Action |
Specify a valid path. |
INODSE2046 | Failed to parse infofile , line 'line' |
Explanation |
The CD database infofile could not be parsed. |
Action |
Please contact your software supplier. |
INODSE2048 | Cannot create database, because there are too many databases already |
Explanation |
A new database cannot be created because there are too many databases already. |
Action |
Check if you still need all the databases you created and if possible delete some of them. |
INODSE2050 | Requested operation not permitted in online mode |
Explanation |
The server must be offline to perform the requested operation. |
Action |
Shut down the database. |
INODSE2061 | Work pool too small |
Explanation |
The work pool used is too small. |
Action |
Ensure that a sufficiently large work pool is available. |
INODSE2064 | Invalid infofile format |
Explanation |
The CD database information file has an invalid format. |
Action |
This error should not occur unless the file was modified manually. Avoid manual modification in the information file. |
INODSE2065 | Incompatible operating system (original database was created on operating system) |
Explanation |
The CD database cannot be created because the database is incompatible with the target platform. |
Action |
Create the CD database on the same platform as the original database. |
INODSE2067 | Operation not allowed on read-only or CD databases |
Explanation |
The required operation cannot be performed on a CD database or read-only database. |
Action |
Switch the "read only" server parameter to "no". This does not apply to databases on CD. |
INODSE2069 | Location with the same name already exists |
Explanation |
A location with the same name already exists. |
Action |
Choose another location name. |
INODSE2070 | Cannot delete default location or default backup location |
Explanation |
There was an attempt to delete the default location or default backup location. Delete operations on these locations are not allowed. |
Action |
No action required. |
INODSE2071 | Location with the same path settings already exists |
Explanation |
A location with the same path settings already exists |
Action |
Choose another location path. |
INODSE2072 | Location name not found |
Explanation |
The specified location was not found. |
Action |
Correct the location name parameter and try again. |
INODSE2080 | Internal error occurred: DSIF function [name - line] not allowed in this context |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2081 | Internal error occurred: OVO memory text(bytes) [name - line] error |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2082 | Granting port allocation lock failed with response text - error text |
Explanation |
Unexpected response received while trying to lock the port allocation lock. |
Action |
Please contact your software supplier. |
INODSE2084 | Invalid port value port detected, valid port values are between minimum and maximum |
Explanation |
An invalid port value was detected. |
Action |
Please specify a valid port value. |
INODSE2085 | Invalid port range from - to detected, minimum minimum ports required in range |
Explanation |
A port range has to contain a minimum number of ports. |
Action |
Please specify a valid port range. |
INODSE2086 | Static port range from - to and dynamic port range from - to overlap |
Explanation |
Static and dynamic port range overlap, which is not allowed. |
Action |
Please specify valid port ranges. |
INODSE2087 | Port check function could not read static and / or dynamic port range |
Explanation |
An error occurred while retrieving the static and dynamic port range. |
Action |
Please contact your software supplier. |
INODSE2088 | The given dynamic port range from - to is not free |
Explanation |
At least one port in the given dynamic port range is already in use by another server. |
Action |
Please specify a dynamic port range where no ports are used by other servers. |
INODSE2092 | Internal error occurred: DSIF function [name - line] invalid combination of parameters |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2093 | Web server webserver not registered |
Explanation |
The given web server is not registered. |
Action |
Specify a registered web server. |
INODSE2094 | Web server webserver not correctly registered |
Explanation |
The web server is not correctly registered. Either the IP address or the port number is missing. |
Action |
Correct the web server registration. |
INODSE2095 | Web server webserver not assigned to database database name |
Explanation |
The web server is not assigned to the database. |
Action |
Check your web server registrations. |
INODSE2096 | Environment extension name not registered for Tamino text text |
Explanation |
The environment extension is not registered in the Tamino configuration. |
Action |
No action required. |
INODSE2097 | No environment extension registered for Tamino text text |
Explanation |
No environment extension registered for Tamino version or server. |
Action |
No action required. |
INODSE2099 | No extension point definitions found for version version |
Explanation |
No extension point definitions were found for the specified version. |
Action |
Check your configuration. |
INODSE2103 | Invalid port range from - to detected |
Explanation |
An invalid port range was detected. |
Action |
Specify a valid port range. |
INODSE2104 | Component name already exists for extension point name in version text |
Explanation |
The component already exists for the extension point in the specified version. |
Action |
No action required. |
INODSE2105 | Component name already exists for extensions in version text |
Explanation |
The component already exists in the extension section of the specified version. |
Action |
No action required. |
INODSE2106 | Component name does not exist for extension point name in version text |
Explanation |
The specified component is not defined for the given extension point and version. |
Action |
No action required. |
INODSE2107 | Component name does not exist in extensions for version text |
Explanation |
The specified component does not exist in the extensions for the given version. |
Action |
No action required. |
INODSE2108 | Could not find function name for extension point name, version text, component name |
Explanation |
The extension point function was not found in the specified extension point library. |
Action |
Check library name, path and entry points of the extension point library. |
INODSE2109 | Extension point name does not exist in version text |
Explanation |
The specified extension point does not exist in the given version. |
Action |
No action required. |
INODSE2110 | Could not load library name for extension point name, version text, component name |
Explanation |
The extension point library could not be loaded via the specified path. |
Action |
Check the library name and path of the extension point definitions. |
INODSE2111 | Could not allocate a port, because the static port range is full |
Explanation |
No port could be allocated in the static port range, because it is full. |
Action |
Extend the static port range, use a port from outside the static port range or force reusage of a port from the static range. |
INODSE2114 | Port allocation function could not read static and / or dynamic port range |
Explanation |
An error occurred while retrieving the static and dynamic port range. |
Action |
Please contact your software supplier. |
INODSE2117 | Granting raw section lock failed with response text - error text |
Explanation |
Unexpected response received while trying to lock the raw section lock. |
Action |
Please contact your software supplier. |
INODSE2121 | Web server webserver is already registered, rename is not allowed |
Explanation |
The web server specified is already registered. Therefore the rename is not allowed. |
Action |
Choose another name for the web server or delete the existing web server. |
INODSE2124 | Internal error occurred: function [name - line] text parameter value |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2125 | Web server webserver is already registered |
Explanation |
The specified web server is already present. |
Action |
Update the web server. |
INODSE2126 | database space of database server in raw section section is in use and must not be reallocated |
Explanation |
The specified database spaces are in use and must not be reallocated. |
Action |
No action required. |
INODSE2127 | database space of database server not present in raw section section |
Explanation |
The specified database space(s) could not be found in the raw section. |
Action |
Please contact your software supplier. |
INODSE2129 | pathname does not specify a regular file (returned type error) |
Explanation |
The given path does not specify a regular file. |
Action |
Specify a regular file. |
INODSE2130 | database space of database server in raw section section is in use and must not be deallocated |
Explanation |
The specified database spaces are in use and must not be deallocated. |
Action |
No action required. |
INODSE2134 | Index recreation not permitted at this item |
Explanation |
This item has no data records, therefore a reinvert cannot be performed. |
Action |
Use the X-Machine programming command "admin" to recreate the index. |
INODSE2135 | database space space number of server server not found |
Explanation |
The specified database space could not be found. |
Action |
Correct the database space specification and try again. |
INODSE2136 | database space of database server in raw section section is in use and must not be changed |
Explanation |
The specified database space is in use and must not be changed. |
Action |
Ensure that the database space is not in use before changing it. |
INODSE2137 | Database server is active, database spaces must not be moved |
Explanation |
The database is active. Therefore database spaces must not be moved. |
Action |
Stop the database before moving any database spaces. |
INODSE2138 | Granting container move lock failed with response text - error text |
Explanation |
An unexpected response was received while trying to grant the container move lock. |
Action |
Please contact your software supplier. |
INODSE2140 | Error while reading data reference block block into internal pool |
Explanation |
An unexpected error occurred while reading a data reference block into the internal cache. |
Action |
Please contact your software supplier. |
INODSE2141 | Load file has unexpected structure level number (compatibility name) |
Explanation |
The input file for a data load operation has a structure level mismatch, or the file is corrupted. |
Action |
Check if the input file has the wrong structure level or is corrupted. |
INODSE2142 | Internal error occurred: DSIF function [name - line] invalid parameter handle (name) supplied |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2143 | Server parameter "value" not available in current context |
Explanation |
A server parameter was requested in an invalid context. |
Action |
Please contact your software supplier. |
INODSE2144 | Invalid server parameter name "value" supplied |
Explanation |
The given server parameter name is invalid. |
Action |
Specify a valid server parameter name. |
INODSE2145 | Static server parameter "value" must not be changed online |
Explanation |
Static server parameters must not be changed while the server is active. |
Action |
Stop the server before changing a static parameter. |
INODSE2157 | Due to license restrictions, raw section access is not allowed |
Explanation |
The license file does not contain the permission to access raw sections. |
Action |
Use the file system instead or obtain the required license from your software supplier. |
INODSE2160 | Upgrade is not allowed for replication database |
Explanation |
An upgrade is not allowed for a replication database. |
Action |
If the master database has been upgraded, the replication database must be newly created from the master backup. |
INODSE2162 | Physical extent count 0 detected at type |
Explanation |
The management of physical database spaces has an empty counter. |
Action |
The database seems to be physically corrupted. Perform a restore/recover. |
INODSE2163 | First Index blocksize incompatible (size) |
Explanation |
The blocksize field of first index space does not match the real blocksize. |
Action |
No action required. |
INODSE2164 | Physical extent entry error (type first - last) |
Explanation |
The physical management of the database is corrupted. |
Action |
Perform a restore/recover. |
INODSE2167 | Check for tape device failed on path. Check that the path is correct and whether tape is in drive. |
Explanation |
It was no possible to verify that the specified path points to a tape device. |
Action |
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. |
INODSE2168 | Location type mismatch - expected 'type' , found 'type' |
Explanation |
This error can occur during 'Add Location', if the requested location type does not match the actual file type. |
Action |
Specify the correct location type. |
INODSE2170 | Received response error text (text) while stopping server |
Explanation |
Stopping the server failed. |
Action |
Please contact your software supplier. |
INODSE2173 | Unexpected internal server error: text |
Explanation |
An internal server call failed with given error string. |
Action |
Please look into the server job log if there is additional error information. If not, contact your software supplier. |
INODSE2175 | Unexpected internal server error: text, location location |
Explanation |
An internal server call failed with given error string. |
Action |
Please look into the server job log to see if there is additional error information. If not, contact your software supplier. |
INODSE2178 | Doctype doctype is locked by another user |
Explanation |
The doctype has a lock conflict with a running action of another user. |
Action |
Investigate which user is active and what activity is causing the lock. |
INODSE2179 | Upgrade from version text to version text not supported |
Explanation |
The required database conversion between the stated versions is not supported. |
Action |
Consult the documentation about possible upgrade options. |
INODSE2187 | Cannot determine file type from path |
Explanation |
An unexpected error occurred while Tamino tried to determine the file type of the displayed location. |
Action |
Check if the displayed location is accessible. If the location is accessible please contact your software supplier. |
INODSE2192 | The maximum number of threads allowed per process (max_threads) is too low to start and manage the Tamino server |
Explanation |
The current parameter configuration does not allow the creation of all necessary threads to start and manage the Tamino server. |
Action |
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. |
INODSE2193 | Insufficient system resources to create thread: thread 'name', error error returned by thread create function |
Explanation |
There are not enough system resources available to create a new thread. |
Action |
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. |
INODSE2194 | Restore from backup made in version version not supported to upgrade to version |
Explanation |
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. |
Action |
Use a more recent backup to restore the database. |
INODSE2200 | Master database database name is not active |
Explanation |
An attempt was made to execute a replication command that requires the master database to be active. |
Action |
Start the master database and retry the command. |
INODSE2201 | Replication database name is active |
Explanation |
An attempt was made to execute a replication command that requires the replication database to be offline. |
Action |
Stop the replication database and retry the command. |
INODSE2202 | Master database must be restarted before a replication database can be set up |
Explanation |
A restart of the master database is necessary. |
Action |
Restart the master database and try to set up the replication database again. |
INODSE2203 | Update server sessions exist |
Explanation |
The database already has update sessions so it cannot be used to replicate another database. |
Action |
Use a newly created database and retry this operation. |
INODSE2204 | Replicate master database database name not permitted |
Explanation |
Permission to replicate the master database was denied. |
Action |
Ask the administrator to permit replication access to the master database. |
INODSE2205 | Inconsistency detected while setting the database to replication type |
Explanation |
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. |
Action |
Use another database to replicate the master. |
INODSE2206 | No permission to modify the type of the database |
Explanation |
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. |
Action |
Log in as administrator and try the operation again and check whether this database is in the permission list of the master database. |
INODSE2208 | Internal error occurred: modification not allowed for replication database. |
Explanation |
An internal error occurred. The server will be stopped. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2212 | The names of master and replication databases cannot be identical |
Explanation |
Identical names have been supplied for the master and a replication database, but this is not allowed. |
Action |
Supply different names. |
INODSE2213 | A former replication database cannot be set to replication type |
Explanation |
After a replication database has been reset by 'Set Type to Normal Database', it cannot become a replication database any more. |
Action |
Delete the database, recreate it from a non-initial backup of the master and execute 'Set Type to Replication'. |
INODSE2214 | Data field layout block number, invalid periodic group count count for name |
Explanation |
The data field layout block with the given number is corrupted. |
Action |
No action required. |
INODSE2215 | Activity currently not permitted |
Explanation |
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. |
Action |
Wait until the server is definitely online or offline and than retry. |
INODSE2216 | Operation is not permitted during a standby server session |
Explanation |
The operation cannot run in parallel with another operation that requires the server to be running in standby mode. |
Action |
A standby session is used for the restore/recover operation. Wait until this operation is finished and the server is shut down. |
INODSE2217 | Operation not allowed for external backup |
Explanation |
An external backup is an invalid object for this operation. |
Action |
Some database operations are not allowed for external backups. |
INODSE2218 | File currently locked |
Explanation |
A recovery input file must not be moved because it is used by the server. |
Action |
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. |
INODSE2219 | Savepoint not found for internal key key |
Explanation |
Necessary configuration information was not found. |
Action |
Please contact your software supplier. |
INODSE2220 | File filename does not exist |
Explanation |
A registered backup or recovery file to be moved or deleted does not exist. |
Action |
Check the locations used for the database whether files have been lost due to unintended removal or restore operations. |
INODSE2221 | File filename already exists |
Explanation |
A registered backup or recovery file to be moved already exists. |
Action |
Check the locations used for the database whether files are present due to restore operations or files remaining from a deleted database. |
INODSE2222 | File filename could not be moved |
Explanation |
Moving a backup or recovery file failed. |
Action |
Check access control settings of the location where the file is to be moved. |
INODSE2223 | File filename could not be removed |
Explanation |
Removing a backup or recovery file failed. |
Action |
Check access control settings of the file to be deleted or of the source file to be moved. |
INODSE2229 | Backup time has become invalid |
Explanation |
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. |
Action |
Use another backup for restore/recover. The selected backup can only be used to create new database. |
INODSE2231 | Cannot create initial backup |
Explanation |
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. |
Action |
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. |
INODSE2232 | XML port must not be set to zero if the communication method includes native TCP/IP |
Explanation |
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. |
Action |
Use a valid port number for TCP/IP communication. |
INODSE2233 | The database database name must be online |
Explanation |
The database must be started for this operation. |
Action |
Start the database. |
INODSE2236 | Stopping database failed, reason: reason |
Explanation |
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. |
Action |
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. |
INODSE2237 | No privilege to modify database, concurrent modifying process is currently active |
Explanation |
There is another modifying job or process active or the server is within startup. Those actions must be serialized. |
Action |
Check your database state and wait until the server is up or check other modifying database actions. |
INODSE2241 | Internal error occurred: DSIF function returncode value error error |
Explanation |
This is an internal error message. |
Action |
Please contact your software supplier. |
INODSE2242 | Replication instance name not found in the permission list |
Explanation |
An attempt was made to remove a replication instance from the permission list which does not exist. |
Action |
Retry the command with a correct name. |
INODSE2243 | Replication instance name already present in the permission list |
Explanation |
An attempt was made to add a replication instance to the permission list which already exists . |
Action |
Retry the command with a correct name. |
INODSE2249 | Physical file extent (extent) missing |
Explanation |
The database file has been divided among more than one physical file extents. Now while processing this file the given extent is not specified. |
Action |
Specify all physical file extents. |
INODSE2250 | A further extent of source cannot be created, because current file is incomplete |
Explanation |
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. |
Action |
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. |
INODSE2258 | Inconsistent usage or missing type file extent during processing extent extent |
Explanation |
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. |
Action |
Enter all required file extents and verify if they are from the same database. |
INODSE2263 | (Re)Move of a single file extent is not possible because there is a reference from another database |
Explanation |
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. |
Action |
Check which database references the backup. |
INODSE2264 | Function not permitted for a replication database |
Explanation |
An administration function could not be executed because it must not be used for a replication database. |
Action |
Check whether the function is to be executed for the master database. |
INODSE2265 | Database is inconsistent and cannot be used |
Explanation |
During migration or restore/recover, the database is in an undefined state which cannot be solved. The database cannot be started anymore. |
Action |
Recover from the latest valid backup or if not possible contact your software supplier. |
INODSE2268 | Database refused startup after conversion |
Explanation |
During migration the database cannot be started because of an internal error. |
Action |
View the server's startup text file (inosrv.txt) for more information. |
INODSE2274 | Server died during startup |
Explanation |
The server died during the startup phase. |
Action |
Inspect the server output file and correct the error. |
INODSE2275 | Property name must not be changed for read only / replication database |
Explanation |
The operation mode of the database is not suited for changes in this property. Changing it would jeopardize the database consistency. |
Action |
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". |
INODSE2279 | Invalid version version of the conversion component |
Explanation |
There is no conversion utility of the most recent version found. |
Action |
Upgrade the conversion only to the current one. |
INODSE2282 | Open of source (path) has failed due to operating system error text (errtxt) |
Explanation |
The file specified cannot be opened due to an internal operating system error. |
Action |
Consult the manufacturer's manual. |
INODSE2283 | type error error (errtxt) on block block number in database space space number |
Explanation |
An I/O error has occurred on the given database space. |
Action |
Analyse the internal operating system error. |
INODSE2285 | Creation of database space space number (path) has failed due to system error text (errtxt) |
Explanation |
A database space could not be created because of an operating system error. |
Action |
Analyse the system error and consult the manufacturer's manual. |
INODSE2289 | Due to license restrictions, usage of replication management functions is not permitted |
Explanation |
Your license does not permit usage of replication databases. |
Action |
Contact your software supplier for an upgrade of your license. |
INODSE2290 | Due to license restrictions, server startup for replication database database name is not permitted |
Explanation |
Your license does not permit usage of replication databases. |
Action |
Contact your software supplier for an upgrade of your license. |
INODSE2291 | Due to license restrictions, server startup of database name as a master for replication databases is not permitted |
Explanation |
Your license does not permit usage of replication databases. |
Action |
Contact your software supplier for an upgrade of your license. |
INODSE2293 | Due to license restrictions, set version for replication master database database name is not permitted |
Explanation |
Your license does not permit usage of replication databases. |
Action |
Remove all databases from the master database's replication database table or contact your software supplier for an upgrade of your license. |
INODSE2298 | Cannot establish connection to server |
Explanation |
The utility cannot connect the server which is assumed to be online. Note that the communication goes over XTS. |
Action |
Check if the database is reachable over the XTS directory service. If you cannot find the reason switch on the XTS tracing facility. |
INODSE2340 | Communication error when trying to contact server name |
Explanation |
An error was returned from the communication interface when trying to contact the server. |
Action |
Check whether the communication component is set up correctly and the communication process (e.g. Software AG XTS Directory Server) is running. |
INODSE2341 | The last backup available must not be deleted |
Explanation |
The last backup available must not be deleted because in the case of a database crash no restore is possible. |
Action |
No action required. |
INODSE2342 | No valid location or directory specified |
Explanation |
To create a backup, either a valid location or directory must be specified. |
Action |
Specify a valid location or directory. |
INODSE4055 | Block size mismatch detected on database space |
Explanation |
A block size mismatch has been detected on the specified database space. |
Action |
Ensure that the block size of the database space to be restored is the same as that in the backup copy. |
INODSE4058 | Database space storage (container) exhausted |
Explanation |
The storage for database space is exhausted. |
Action |
Try to allocate more storage; if this is not possible contact your software supplier. |
INODSE4109 | Failure calling external backup |
Explanation |
Tamino could not start external backup processing. |
Action |
Check that the third party hardware and drivers are installed and working correctly. If the symptoms persist, contact your software supplier. |
INODSE4110 | Failed to retrieve number of backup generations from internal configuration store |
Explanation |
There is possibly a corruption of the internal configuration store. |
Action |
If the symptoms persist, contact your software supplier. |
INODSE4111 | Failed to remove oldest savepoint information from internal configuration store. |
Explanation |
There is possibly a corruption of the internal configuration store. |
Action |
If the symptoms persist, contact your software supplier. |
INODSE4113 | Failed to retrieve server version |
Explanation |
There is possibly a corruption of the internal configuration store. |
Action |
If the symptoms persist, contact your software supplier. |
INODSE4114 | Failed to enumerate savepoint information |
Explanation |
There is possibly a corruption of the internal configuration store. |
Action |
If the symptoms persist, contact your software supplier. |
INODSE4118 | Failed to downgrade database |
Explanation |
There is a problem with the database downgrade utility. |
Action |
If the symptoms persist, contact your software supplier. |
INODSE4120 | Failed to execute inodmp utility |
Explanation |
The Create/Backup/Restore utility cannot be executed, possibly due to a corruption in the internal configuration store. |
Action |
If the symptoms persist, contact your software supplier. |
INODSE4121 | External Restore failed |
Explanation |
Tamino could not start external restore processing. |
Action |
Check that the third party hardware and drivers are installed and working correctly. If the symptoms persist, contact your software supplier. |
INODSE4122 | Failed to retrieve database identity |
Explanation |
There is possibly a corruption of the internal configuration store. |
Action |
If the symptoms persist, contact your software supplier. |
INODSE5251 | An inodmp client terminated with unexpected error text |
Explanation |
Within parallel backup a client process of the dump utility terminated unexpectedly. |
Action |
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. |
INODSE5261 | Invalid or unsupported character set charset |
Explanation |
The specified character set is not supported by the current software version. |
Action |
Check for possible typing errors in character set name. |
INODSE5267 | Software configuration error |
Explanation |
The Tamino software components that you are using are not compatible. |
Action |
Please request a new version of Tamino from your software supplier. |
INODSE5268 | Failed to register server with the Software AG XTS Directory Server: error text |
Explanation |
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. |
Action |
Fix the error situation described by the XTS message or contact your software supplier. |
INODSE5271 | Failed to create the Software AG XTS Directory Server entries: error text |
Explanation |
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. |
Action |
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. |
INODSE5272 | Parameter setting for the Software AG XTS Directory Server failed: error text |
Explanation |
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. |
Action |
Fix the error situation described by the XTS message or contact your software supplier. |
INODSE5283 | Invalid parent field format for collation descriptor |
Explanation |
The format for the parent field of a collation descriptor is invalid. The only allowed parent formats are "wide" and "alphanumeric". |
Action |
Check the collation descriptor definition. |
INODSE5287 | Invalid collation locale s |
Explanation |
The locale name is misspelled or the locale is not supported. |
Action |
Check the spelling. |
INODSE5309 | Key id could not be changed, message |
Explanation |
An internal error occurred changing a key value in the internal configuration store. |
Action |
Please contact your software supplier. |
INODSE5310 | Database name name could not be changed in the internal configuration store, message |
Explanation |
Because of an internal error the internal configuration could not be changed. |
Action |
Please contact your software supplier. |
INODSE5320 | Database ID could not be determined, message |
Explanation |
Internal error, while requesting database ID information. |
Action |
Contact your software supplier. |
INODSE5321 | Database name could not be determined, message |
Explanation |
Internal error, while requesting database name information. |
Action |
Please contact your software supplier. |
INODSE5334 | Unable to get collator version for locale locale |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INODSE5335 | Collation version does not match |
Explanation |
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. |
Action |
Rebuild the collating index. |
INODSE5336 | Internal ICU error (error text) occurred while producing collation key |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INODSE5337 | Unable to determine server state |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INODSE5341 | Database database name already exists |
Explanation |
This error can occur during database creation, or when trying to rename an existing database and a database with the same name already exists. |
Action |
Specify another name. |
INODSE5343 | External backup failed, reason: reason text |
Explanation |
The attempt to perform an external database backup failed due to the reason specified in the message. |
Action |
Correct the error indicated and retry the operation. |
INODSE5344 | External restore failed, reason: reason text |
Explanation |
A database restore with a connected external system failed due to the reason specified in the message. |
Action |
Correct the error indicated and retry the operation. |
INODSE5345 | External delete failed, reason: reason text |
Explanation |
The call to delete an external backup failed due to the reason given. |
Action |
Correct the error indicated and retry the operation. |
INODSE5346 | EMC request failed: text |
Explanation |
A call of EMC's SYMAPI failed for the given reason. |
Action |
Correct the error indicated and retry the operation. |
INODSE5354 | External backup configuration error, reason: reason |
Explanation |
Configuring the environment for an external backup failed. |
Action |
Correct the error indicated and retry the operation. |
INODSE5358 | Set version already running on this database |
Explanation |
The "Set version" operation is already running on this database. |
Action |
Wait for the "set version" operation to complete. |
INODSE5359 | Function is not permitted because of pending transactions |
Explanation |
The function cannot be processed because of pending global transactions. |
Action |
Start the Tamino server in normal mode and close the pending global transactions. |
INODSE5360 | Function is not permitted because the previous session was abnormally terminated |
Explanation |
The function cannot be processed because the previous session was abnormally terminated. |
Action |
Start the Tamino server in normal mode to do an autorepair from the abnormal termination. |
INODSE5361 | Downgrade to version version not supported |
Explanation |
This message can appear when trying to convert a database to a previous version, but the requested downgrade is not supported. |
Action |
No action required. |
INODSE5402 | Maximum number of users exceeded |
Explanation |
A new user was rejected due to internal reasons. |
Action |
You can force a memory dump with "inodba database=name trap=9228" for further analysis after reproducing the error. |
INODSE5404 | Insufficient temporary work space |
Explanation |
The temporary work space was too small to execute the requested function. |
Action |
Consider increasing the temporary workspace by adding locations with free space to the temporary working location. |
INODSE5405 | Insufficient temporary work space |
Explanation |
The temporary work space was too small to execute the requested function. |
Action |
Consider increasing the temporary workspace. |
INODSE5406 | Transaction internally aborted |
Explanation |
A transaction has been aborted due to internal reasons. All changes of this transaction have been undone. |
Action |
You can force a memory dump with "inodba database=name trap=9291" for further analysis after reproducing the error. |
INODSE5407 | Database is corrupt, invalid block block |
Explanation |
There are structural inconsistencies in the database. The database should not be used any longer. |
Action |
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. |
INODSE5408 | buffer pool overflow |
Explanation |
The current load could not be processed because the buffer pool is too small. |
Action |
Consider increasing the buffer pool size or force a memory dump with "inodba database=name trap=9138" for further analysis after reproducing the error. |
INODSE5410 | Database is corrupt, data block damaged |
Explanation |
There are structural inconsistencies in the database. The database should not be used any longer. |
Action |
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. |
INODSE5411 | Database is corrupt |
Explanation |
There are structural inconsistencies in the database. The database should not be used any longer. |
Action |
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. |
INODSE5416 | Database is corrupt, physical structures damaged |
Explanation |
There are structural inconsistencies in the database. The database should not be used any longer. |
Action |
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. |
INODSE5417 | Database is corrupt, allocation error detected |
Explanation |
There are structural inconsistencies in the database. The database should not be used any longer. |
Action |
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. |
INODSF1008 | The location of the license file could not be found |
Explanation |
The Tamino Server requires a valid license file. The location of the license file could not be determined. |
Action |
Contact your software supplier. |
INODSF1011 | The license of Tamino has expired |
Explanation |
The licensing period of Tamino has expired. |
Action |
Please contact your software supplier for a renewal of your license. |
INODSF1012 | The version of Tamino and the version used in the license file do not match |
Explanation |
The Tamino product version and the version used in the license file must match. |
Action |
Use the license file that has been shipped with your product version. |
INODSF1018 | Database creation has failed due to license restrictions. Licensed database size is size MB, attempted dataspace container size is size MB. |
Explanation |
The dataspace size of a database is limited by the amount given in your current license. |
Action |
Create a database with a smaller dataspace size. |
INODSF1020 | Error error accessing the raw section section via mode |
Explanation |
Accessing the raw section failed due to an unexpected system response. |
Action |
Please consult your manufacturer's manual. |
INODSF1021 | Verification error on raw section section (structure level mismatch) |
Explanation |
An error occurred while verifying the structure level in the raw section management structure. |
Action |
Please contact your software supplier. |
INODSF1022 | Verification error on raw section section (wrong architecture byte) |
Explanation |
An error occurred while verifying the architecture byte in the raw section management structure. |
Action |
Please contact your software supplier. |
INODSF1023 | Verification error on raw section section (section management header) |
Explanation |
An error occurred while verifying the management header in the raw section management structure. |
Action |
Please contact your software supplier. |
INODSF1024 | Raw section section is not initialized |
Explanation |
The raw section is not initialized. |
Action |
Please initialize the raw section. |
INODSF1250 | Open of source (path) has failed due to an incompatible file or a compatibility mismatch |
Explanation |
The file could not be opened because it either does not have the expected compatibility level or a subsequent file extent does not match the previously opened one. |
Action |
Check that the correct file has been specified for the operation or if 2 physical file extents belong to each other. |
INODSF1251 | Internal error error occurred |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1254 | Unexpected signal signal received in text index procedure call from thread thread |
Explanation |
An unexpected exception or signal has occurred. |
Action |
If the exception or the signal was asynchronous (i.e. no access violation etc.), repeat the operation. |
INODSF1255 | Index too deep |
Explanation |
The index structure exceeds the maximum levels of indexing supported. |
Action |
Please contact your software supplier. |
INODSF1256 | Internal error on doctype doctype: second error caused by failed recovery due to the following error: first error |
Explanation |
An error occurred on the specified doctype. While trying to undo the changes on the doctype, another error has occurred. The server must terminate in order to prevent the database from being corrupted. |
Action |
Restart the server. |
INODSF1257 | Log space full |
Explanation |
The server session has been abnormally terminated because there is no space left for logging. |
Action |
Provide space for logging and restart the server. |
INODSF1259 | Error closing a log space: error message |
Explanation |
The log space could not be closed properly. The server session is aborting. |
Action |
Try to fix the reason for the error. It is recommended to back up the database. Restart the server. |
INODSF1260 | Error on doctype doctype during rollback transaction: error text |
Explanation |
An error occurred during the rollback of a transaction. The server must terminate in order to prevent the database from being corrupted. |
Action |
Restart the server. |
INODSF1261 | Assertion failed: assertion |
Explanation |
A coding error has occurred. |
Action |
Please inform your software supplier. Restart the server. |
INODSF1262 | Open of source (path) has failed due to an incorrect file type |
Explanation |
The file could not be opened because it does not have the expected type. It is possible that the file is internally corrupted. For example there is an index space with entirely binary zeroes in it. |
Action |
Check that the correct file has been specified for the operation. |
INODSF1263 | Error error number has occurred in SMP initialization. |
Explanation |
An internal error has occurred. The server has stopped. |
Action |
Please contact your software supplier. |
INODSF1264 | Setting the maximum number of resources to value has failed. Server stopped. |
Explanation |
The requested system resources were not available. |
Action |
Check your system configuration. |
INODSF1265 | Server already active |
Explanation |
There is another server running for the current database. |
Action |
Please contact your software supplier. |
INODSF1266 | Error error number during synchronization call in line line (address address) |
Explanation |
An internal error has occurred. The server has been stopped. |
Action |
Please contact your software supplier. |
INODSF1267 | SMP resource allocation failed with response error text at line line |
Explanation |
An internal error has occurred. The server has been stopped. |
Action |
Please contact your software supplier. |
INODSF1268 | Error error number during synchronization call in line line |
Explanation |
An internal error has occurred. The server has been stopped. |
Action |
Please contact your software supplier. |
INODSF1269 | Increasing the number of resources by value has failed. Server stopped. |
Explanation |
The requested system resources were not available. |
Action |
Check your system configuration. |
INODSF1270 | Invalid value (value) found at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1271 | Invalid pointer (value) found at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1272 | Internal error error string occurred at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1273 | Invalid value (value) found at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1274 | Internal error in block block number occurred at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1275 | Invalid value (value) found on address address at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1276 | Invalid values (value 1, value 2) found on address address at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1277 | Invalid values (value, value) found at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1278 | Invalid value (value) found in block block number at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1279 | Invalid value (value) found on address address at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1280 | Internal error location-text-text occurred |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1282 | Received response error text (text) while loading function(s) for extension point name |
Explanation |
Loading a function for an extension point failed. |
Action |
Please contact your software supplier. |
INODSF1283 | Internal communication initialization failed |
Explanation |
The server's internal communication could not be activated. |
Action |
Please contact your software supplier. |
INODSF1284 | Internal memory management could not be initialized |
Explanation |
The initialization of the server's memory management has failed. |
Action |
Please contact your software supplier. |
INODSF1285 | Temporary working space could not be allocated |
Explanation |
The allocation of the working space needed for server operation has failed. |
Action |
Please contact your software supplier. |
INODSF1286 | Buffer pool too small. At least minimum value bytes required. |
Explanation |
The defined buffer pool is too small for the server to start. |
Action |
Increase the buffer pool parameter and restart the server. |
INODSF1287 | Buffer pool too small to start the server (internal reason reason) |
Explanation |
The defined buffer pool is too small for the server to start. |
Action |
Increase the buffer pool parameter and restart the server. |
INODSF1288 | Server for this database already active |
Explanation |
There is already an active server for the same database or at least some resources of the previous server run have not been released yet. |
Action |
If there is no active server and you cannot determine which resources may cause the conflict, contact your software supplier. |
INODSE1289 | Error when opening database space space number (at path): size mismatch |
Explanation |
The size of the database space is not equal to the size expected by the server. |
Action |
Please contact your software supplier. |
INODSE1290 | I/O error occurred on database space space number. System error text caused by operation operation on block block number. |
Explanation |
The operating system has signalled that the specified I/O operation has failed. |
Action |
Please consult the manufacturer's manual. |
INODSF1291 | Not enough memory available to execute process |
Explanation |
The operating system did not have enough resources to run another process. Possible reasons are too many concurrently active processes or a too small swap/paging space. |
Action |
Please check the resource usage and the configuration of your computer. |
INODSE1292 | Creation of database space space number (path) has failed |
Explanation |
The database space could not be created at the specified location. |
Action |
Look for other error messages to find the reason for the failure. |
INODSE1293 | Creation of database space space number (path) has failed due to system error text |
Explanation |
The database space could not be created at the specified location because of an error signalled by the operating system. |
Action |
Please consult the manufacturer's manual. |
INODSE1295 | Creation of journal space 1 (path) has failed |
Explanation |
The database space could not be created at the specified location. |
Action |
Look for other error messages to find the reason for the failure. |
INODSF1296 | source (path) is corrupted at offset |
Explanation |
The data cannot be used. |
Action |
Please contact your software supplier. |
INODSF1297 | Creation of source (path) has failed |
Explanation |
The file could not be created at the specified location. |
Action |
Look for other error messages to find the reason for the failure. |
INODSF1298 | source (path) could not be opened: device type not supported |
Explanation |
An invalid device type was chosen. |
Action |
Choose a valid device type. |
INODSF1299 | Open of source (path) has failed due to operating system error text |
Explanation |
The file could not be opened. |
Action |
Please consult the manufacturer's manual. |
INODSF1300 | Open of source (path) has failed due to an invalid structure |
Explanation |
The file could not be opened because it does not have the expected structure. |
Action |
Check if the file origin is the same machine architecture. If you cannot detect the error, please contact your software supplier. |
INODSF1301 | Open of source (path) has failed. Missing extents or wrong sequence of extents. Please check and retry. |
Explanation |
The file could not be opened because the sequence in which devices are given (e.g. tapes) is not correct or not all sequences required were specified. |
Action |
Specify all extents in the correct sequence. |
INODSF1302 | Open of log space (path) has failed because sequence of log spaces is incorrect |
Explanation |
The file could not be opened because the sequence in which log spaces are given (e.g. tapes) is not correct. |
Action |
Use the correct sequence. |
INODSF1303 | Open of source (path) has failed due to an incorrect file type |
Explanation |
The file could not be opened because it does not have the expected type. |
Action |
Check that the correct file has been specified for the operation. |
INODSF1305 | Open of source has failed due to invalid or missing internal information |
Explanation |
The file could not be opened because its location was not specified. |
Action |
Check the database parameters. |
INODSF1306 | Internal error location occurred: Please report r t h c |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier and report the values given with the message. Restart the server. |
INODSF1307 | Database database name not registered |
Explanation |
The specified database has not been properly created or the internal entries of this database have been destroyed. |
Action |
Create the database again. |
INODSF1308 | Executable name not found |
Explanation |
The system could not find the executable object specified. |
Action |
Please check your installation. |
INODSF1309 | System error text occurred during the creation of another process |
Explanation |
The system could not create another process. You might have exceeded the amount of available memory or the maximum number of processes. |
Action |
Please increase the amount of virtual memory available, or increase the number of possible processes. Please refer to the manual of your operating system for details. |
INODSF1310 | Invalid value (value) found at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1311 | Error text has been signalled during the execution of an asynchronous I/O on log space for id |
Explanation |
An asynchronous I/O has failed due to an operating system error. |
Action |
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 operating system commands. Check the system log file for appropriate error messages. |
INODSF1312 | Error text has been signalled during the execution of an asynchronous I/O on journal space for id |
Explanation |
An asynchronous I/O has failed due to an operating system error. |
Action |
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 operating system commands. Check the system log file for appropriate error messages. |
INODSF1313 | Error text has been signalled during the execution of an asynchronous I/O for id |
Explanation |
An asynchronous I/O has failed due to an operating system error. |
Action |
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 operating system commands. Check the system log file for appropriate error messages. |
INODSF1317 | Semaphore could not be created because system limit was reached |
Explanation |
The system limit for semaphores was reached. |
Action |
Increase the number of semaphores supported by the operating system. |
INODSF1319 | Unexpected signal signal received |
Explanation |
An unexpected exception or signal has occurred. |
Action |
If the exception or the signal was asynchronous (i.e. no access violation etc.), repeat the operation. |
INODSF1321 | Error opening sequential file: error |
Explanation |
An error occurred when opening a sequential file. |
Action |
Correct the reason for the sequential file open failure and retry the operation. |
INODSF1322 | Latest savepoint not found |
Explanation |
Internal information about the latest savepoint could not be found. |
Action |
Contact your software supplier. |
INODSF1323 | Path or type of log location not found |
Explanation |
The internal information for the log location, path or type could not be found. |
Action |
Contact your software supplier. |
INODSF1324 | Processing information for a log space is undefined |
Explanation |
A previous server session process was killed during restore/recover. |
Action |
Use a later backup if possible or use a recover until a timestamp that is less than the creation date of the log space in question. |
INODSF1325 | Signal signal number caught. Termination initiated. |
Explanation |
An unexpected signal was caught. This leads to an immediate termination. |
Action |
If the signal cannot be explained by the environment (operator initiated or operating system initiated signal), please contact your software supplier. |
INODSF1326 | database creation not completed |
Explanation |
The database creation is not finished, or terminated unexpectedly, leaving the database files on disk. |
Action |
Check if the creation is still in progress. If so, wait until completed. If not, clean up and restart the database creation. |
INODSF1328 | Unexpected buffer pool error |
Explanation |
An unexpected error has occurred when trying to access the buffer pool. |
Action |
Repeat the action. If it still fails, contact your support center. |
INODSF1329 | Unexpected error getting a page from the buffer pool |
Explanation |
An unexpected error has occurred when trying to get a page from the buffer pool. The operation was cancelled. |
Action |
Contact your software supplier. |
INODSF1330 | An unexpected I/O error has occurred |
Explanation |
An unexpected I/O error has occurred. The operation was cancelled. |
Action |
Contact your software supplier. |
INODSF1331 | Unable to extend database space. Reason: ret_code. |
Explanation |
The specified error has occurred while trying to extend a database space. |
Action |
Determine the reason for the error code, and retry the operation. |
INODSF1332 | Index chain is corrupt |
Explanation |
Corruption has been found for an index on a doctype. |
Action |
The indexes have to be rebuilt. To rebuild the indexes, choose the "Check and Repair" function for the database in the Tamino Manager, then retry the operation. |
INODSF1334 | No index summary in input file |
Explanation |
The input file does not have the required index definitions. |
Action |
Ensure that the correct input file has been specified. |
INODSF1335 | No streams available |
Explanation |
Multi-file mode is being used but no streams are available. |
Action |
Please contact your software supplier. |
INODSF1336 | Cannot handle given extent type |
Explanation |
It is not possible to handle the type of extent specified. |
Action |
This is an internal error. Please contact your software supplier. |
INODSF1337 | Shared memory segment of server exists |
Explanation |
At least one shared memory segment of the server already exists. |
Action |
Check if the server is already active. If not retry the operation. If the error persists remove the existing shared memory segment and retry. |
INODSF1341 | Error on temporary storage space |
Explanation |
An error has occurred when trying to write to a temporary storage space. |
Action |
Ensure that there are no errors on the device where temporary space is to be used and retry the operation. |
INODSF1342 | No space for index space |
Explanation |
There are not enough system resources available for the index space. |
Action |
Allocate sufficient resources to allow the operation to succeed. |
INODSF1343 | Error opening data space |
Explanation |
An error has occurred while opening the data space. |
Action |
Correct the error and retry the operation. |
INODSF1344 | Error opening journal space |
Explanation |
An error has occurred while opening the journal space. |
Action |
Correct the error and retry the operation. |
INODSF1345 | Internal error: Provided memory not sufficient |
Explanation |
An area in memory used as working space was defined too small. |
Action |
Please contact your software supplier. |
INODSF1346 | No input slot could be allocated |
Explanation |
An internal error occurred preventing an input slot being allocated for an index. |
Action |
Please contact your software supplier. |
INODSF1347 | No space for preserved slot |
Explanation |
An internal error occurred preventing a preserved slot being allocated for an index. |
Action |
Please contact your software supplier. |
INODSF1348 | Invalid database space |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier. |
INODSF1349 | Error while reading index |
Explanation |
An internal error occurred while reading the index. |
Action |
Please contact your software supplier. |
INODSF1350 | No more temporary space |
Explanation |
Temporary space has been exhausted. |
Action |
Ensure that there is enough free space to allocate the required temporary space. |
INODSF1351 | No slot available |
Explanation |
An internal error occurred when trying to write to a slot. |
Action |
Please contact your software supplier. |
INODSF1353 | More than one block to be written (number) |
Explanation |
A disk write failed because more than one block was requested to be written. This is an internal error. |
Action |
Please contact your software supplier. |
INODSF1354 | Utility not permitted to run |
Explanation |
This utility is currently not permitted to run. |
Action |
Wait until the database is available again. |
INODSF1355 | Internal sort error |
Explanation |
An internal sort error has occurred. |
Action |
Please contact your software supplier. |
INODSF1356 | Internal error occurred: utility entry not found |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier. |
INODSE1358 | Creation of database space space number (path) has failed because the file already exists |
Explanation |
The database space could not be created at the specified location because the file is already present. |
Action |
Remove or move the file to another location before repeating the action. |
INODSF1359 | Invalid value (long value) found on address address at location location |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1360 | The tape device is not responding, please ensure that a tape is mounted |
Explanation |
Response EINVAL was returned by the operating system. The most likely cause is that no tape has been mounted. |
Action |
Ensure that a tape is mounted and the device is switched on. |
INODSF1362 | Journal space too small (minimum required size is size MBytes) |
Explanation |
The journal space is not sufficient for the Tamino server. |
Action |
Create a database with a larger journal space. |
INODSF1363 | Journal overflow. Server cannot proceed. |
Explanation |
The journal space was insufficient. The current server session has to be terminated. |
Action |
Check if more journal space can be provided. Restart the server. |
INODSF1364 | Log space not found for savepoint savepoint |
Explanation |
A log space entry for the given savepoint could not be found. |
Action |
Contact your software supplier. |
INODSF1366 | License file not found at path |
Explanation |
Your license is not at the expected place. |
Action |
Please move the license file to the place indicated. |
INODSF1367 | License file not valid (error error) |
Explanation |
Your license is not valid. It is incomplete or has been edited. |
Action |
Please acquire a correct license file from your software supplier. |
INODSF1369 | Internal licensing error error |
Explanation |
There was an internal error in the processing of the licensing information. |
Action |
Please contact your software supplier. |
INODSF1373 | Database database name not registered |
Explanation |
The specified database has not been properly created or the internal entries of this database have been destroyed. |
Action |
Create the database again. |
INODSE1413 | System error text when opening database space space number (path) |
Explanation |
The specified operating system error has occurred. |
Action |
Please consult the manufacturer's manual. |
INODSF1431 | Error during autorepair. The database is inconsistent. |
Explanation |
The last server session terminated abnormally. The database autorepair has failed. The database cannot be used. |
Action |
Send the journal space and all other error information to your software supplier. Then recover your database from the last backup. |
INODSF1432 | Start of autorepair information cannot be determined |
Explanation |
The last server session terminated abnormally. The database autorepair has failed. The database cannot be used. |
Action |
Send the journal space and all other error information to your software supplier. Then recover your database from the last backup. |
INODSF1433 | Journal overflow during database autorepair. The database is inconsistent. |
Explanation |
The last server session terminated abnormally. The database autorepair has failed. The database cannot be used. |
Action |
Send the journal space and all other error information to your software supplier. Then recover your database from the last backup. |
INODSF1436 | Terminated with errors |
Explanation |
A previous error has caused the termination of the process. |
Action |
Please check the event log for detailed information about previous errors that have caused the process to terminate. |
INODSF1454 | Internal error occurred: location thread module function. Server stopped. |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSF1688 | Shared memory of size size MB is not available (internal error text) |
Explanation |
The server needs a shared memory of the specified size. However, this shared memory could not be created. |
Action |
View the previous message which describes the operating system error in detail. Check the manufacturer's manual. Consider increasing the operating system limits on shared memory size or decreasing the needs of the server by decreasing parameters such as buffer pool size. |
INODSF2002 | Error during replication processing, replication stopped |
Explanation |
Replication cannot be continued due to a previous error during replication processing |
Action |
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 a new backup from the master database should be used to recreate the replication database. |
INODSF2005 | Internal replication error error/error information detected when processing data of server session session number - block block number, location record number |
Explanation |
The data required for replication processing could not be supplied by the master database. |
Action |
Please check that the log space has not yet been deleted by creating new backups of the master database. If the log space still exists keep the error information and contact your software supplier. |
INODSF2075 | Failure writing to tape device, please ensure that a tape is loaded |
Explanation |
The response EFAULT was returned by the operating system. The most likely cause is that no tape is loaded in the device. |
Action |
Ensure that a tape is loaded and the device is switched on. |
INODSF2116 | Internal command recovery failure (response) on doctype doctype, caused by: response |
Explanation |
A internal recovery failed and therefore the server cannot resolve a rollback. The server must terminate in order to prevent the database from being corrupted. |
Action |
Restart the server. |
INODSF2119 | Invalid compatibility level: DBMS level, backup file level (filename) |
Explanation |
An invalid compatibility level of DBMS and backup file has been detected. |
Action |
Please use a DBMS version with the same compatibility level as the backup file, or use a backup file with the compatibility of the DBMS. |
INODSF2120 | IO [name-line] error error |
Explanation |
An unexpected error occurred in an I/O function. |
Action |
Please contact your software supplier and provide the message text. |
INODSF2122 | Invalid compatibility level: DBMS level, database level |
Explanation |
An invalid compatibility level has been detected. |
Action |
Please contact your software supplier. |
INODSF2123 | CF [name-line] error error |
Explanation |
An internal configuration error occurred. |
Action |
Please contact your software supplier and provide the error message text. |
INODSF2128 | Invalid data block detected at block number (doc doc, cont name) |
Explanation |
An invalid data block was detected which refused a database backup. At least one collection has a data fault. |
Action |
Repair the database with restore/recover from the latest good backup. |
INODSF2188 | Failed to enter the new compatibility level in the internal configuration store |
Explanation |
The new compatibility level could not be entered in the internal configuration store. |
Action |
Please contact your software supplier and provide the message text. |
INODSF2227 | Internal error error during flush operation |
Explanation |
The write operation of the internal buffer cache to disk failed. A detailed error message precedes this message. |
Action |
Analyse the error code, maybe check your disks and restart server. |
INODSF2234 | SMP resource allocation failed at module[line] because of a lack of available memory |
Explanation |
The allocation of memory failed. The reason for that is either that the pagefile is too small or that the available virtual memory is exhausted. |
Action |
Increase the size of the pagefile. If that doesn't help contact your software supplier. |
INODSF2235 | Database key mismatch, required text, present text |
Explanation |
The index space has an unexpected key within the first index space. The database space obviously comes from another database. |
Action |
Check the index container spaces. |
INODSF2266 | Cannot start Tamino utility of version due to system error text |
Explanation |
Submitting a Tamino utility as a subprocess failed due to an operating system error. |
Action |
Analyze the system error and check the installed version. |
INODSF2280 | Unexpected I/O error (io operation) on database space |
Explanation |
An I/O failed and the process cannot continue. |
Action |
View any previous or related system error messages and analyse why the I/O operation on the given database space could have failed. |
INODSF2284 | Error text (errtxt) has been signalled during the execution of an asynchronous I/O on database space for id |
Explanation |
A severe read/write error has occurred. |
Action |
Analyse the operating system error. |
INODSF2286 | Internal replication error error/error information detected when processing data of mass load recovery input filename |
Explanation |
The mass load input required for replication processing could not be supplied by the master database. |
Action |
Please check that the recovery input file has not yet been deleted by creating new backups of the master database. If the log space still exists, keep the error information and contact your software supplier. |
INODSF2287 | Internal error error detected when processing mass load recovery input with key key |
Explanation |
The recovery of a mass load activity failed. |
Action |
Please contact your software supplier. |
INODSF2288 | Cannot grant server synchronization semaphore |
Explanation |
The server synchronization semaphore cannot be granted. |
Action |
Check if the semaphore already exists and another process has granted it, or if the permission settings of the semaphore do not allow access. |
INODSF2294 | Filename for database space container could not be determined |
Explanation |
It was not possible to determine the full filename for the specified database space. It was obviously missing in the internal configuration store. |
Action |
This is an internal error. Please contact your software supplier. |
INODSF2296 | Internal error text on database space (reason) |
Explanation |
The writing of relevant information to the given database space (Log, Journal) failed due to an internal error. |
Action |
Check the location where the database space resides and also analyse the previously given operating system error message. |
INODSF2299 | Internal error number reading database space at block number |
Explanation |
Reading the given database block resulted in an internal I/O error. |
Action |
No action required. |
INODSF2308 | Product usage found in the license file is not allowed for an unlimited license |
Explanation |
The product usage found in the license file is only allowed for a time-limited license. |
Action |
Please contact your software supplier to correct your license. |
INODSF2309 | Server abort because of license expiration |
Explanation |
The grace period after license termination has expired. The server did an abort. |
Action |
Please contact your software supplier to extend your license. |
INODSF2334 | The license for name with ID id has expired, server aborts now |
Explanation |
The license has expired. The server has stopped operation (abort). Operation can be continued upon restart with a renewed license key. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager, then restart the server. |
INODSF2335 | The license for name sub-licensed by name with ID id has expired, server aborts now |
Explanation |
The license has expired. The server has stopped operation (abort). Operation can be continued upon restart with a renewed license key. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager, then restart the server. |
INODSF2336 | The license for name with ID text sub-licensed by name has expired, server aborts now |
Explanation |
The license has expired. The server has stopped operation (abort). Operation can be continued upon restart with a renewed license key. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager, then restart the server. |
INODSF2337 | The license for name with ID text sub-licensed by name with ID id has expired, server aborts now |
Explanation |
The license has expired. The server has stopped operation (abort). Operation can be continued upon restart with a renewed license key. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager, then restart the server. |
INODSF2338 | Internal error number writing database space at block number |
Explanation |
Cannot write database block due to an internal I/O error. |
Action |
Analyse the error number and check the database. |
INODSF2339 | XTS refuses database connection, reason reason_code |
Explanation |
It is not possible to reach the database via XTS. |
Action |
Switch on XTS_TRACE, repeat the function and check the trace file. |
INODSF4256 | Structure level mismatch on database |
Explanation |
The version of the server differs from the version of the utility. |
Action |
Run the correct version of the utility or server, or convert the database. |
INODSF4258 | The database type and/or version does not match the backup |
Explanation |
This operation can only be performed against a database of the same type and/or version as the backup. |
Action |
Ensure that the utility is being run against the correct type and version of database. |
INODSF4262 | Database server mismatch: present database name |
Explanation |
A mismatch occurred between the database server parameter and the database server name of the assigned index space. |
Action |
Ensure that the correct database name is supplied. |
INODSE5300 | Filename for database space container could not be determined |
Explanation |
It was not possible to determine the full filename for the specified database space. |
Action |
This is an internal error. Please contact your software supplier. |
INODSF5331 | Version version is not installed |
Explanation |
The required software version is not installed. |
Action |
please contact your software supplier. |
INODSF5332 | Invalid structure level value |
Explanation |
An invalid structure level has been detected. |
Action |
Please contact your software supplier. |
INODSI1004 | Stop of database successfully initiated - server is going down now |
Explanation |
All database activities are terminated - the server process is about to terminate. |
Action |
No action required. |
INODSI1013 | Read-only database, word fragment index cannot be created |
Explanation |
Read-only database, no database update permitted. |
Action |
Ensure that the database upon which you wish to carry out the operation is write-enabled. |
INODSI1016 | Initializing journal space |
Explanation |
When the database first starts, the entire journal space must be formatted with binary zeroes. |
Action |
Wait until the operation finished: This could take several seconds or even several minutes if the file is very large. |
INODSI1034 | The Tamino Server that is provided with this Tamino Developer Edition may be used for educational purposes only. For production purposes, you must use the Tamino Server that is included in the Tamino Server Edition. |
Explanation |
This is an informational message |
Action |
None |
INODSI1039 | Function function executed |
Explanation |
The specified function was executed. |
Action |
Information only, no action required. |
INODSI1246 | Read-only database, word fragment index cannot be removed |
Explanation |
The database is readonly, so no database update is permitted. |
Action |
Ensure that the database upon which you wish to carry out this operation is write-enabled. |
INODSI1327 | Database stopped |
Explanation |
The database has been stopped. |
Action |
No action required. |
INODSI1371 | sufficient space in locations, continue |
Explanation |
Now there is sufficient space on the location where the file was waiting for, the operation now continues |
Action |
Now there is a subsequent file extent |
INODSW1372 | Waiting for space on space location |
Explanation |
The location where the file wants to grow has no more free space and the current request will wait until space is available. |
Action |
Either delete unused files from the location that has insufficient space or define a new location with enough space for that file. |
INODSI1384 | Setting of parameter name=value |
Explanation |
no description available |
Action |
no action required |
INODSI1417 | database database name at structure level for version version |
Explanation |
This informational message states the structure level of the database. |
Action |
No action required. |
INODSI1420 | Dump file at version: text, level level |
Explanation |
This informational message states the version and level of the dump file. |
Action |
Select the version displayed. |
INODSI1451 | Creation of word fragment index started |
Explanation |
The creation of the word fragment index has started. |
Action |
No action required. |
INODSI1452 | Server session session number started |
Explanation |
The server started successfully. |
Action |
No action required. |
INODSI1453 | Internal event event has occurred |
Explanation |
This message indicates a certain event in the server processing. It is not relevant to the user. |
Action |
No action required. |
INODSI1456 | The Tamino Server that is provided with the Tamino Developer Edition may be used for test purposes only. For production purposes, you must use the Tamino Server that is included in the Tamino Server Edition. |
Explanation |
This is an informational message. |
Action |
Use the correct Tamino Server. |
INODSI1457 | End of tape tape - rewinding |
Explanation |
The tape is being rewound. |
Action |
No action required. |
INODSI1458 | End of diskette path |
Explanation |
The diskette is full. |
Action |
No action required. |
INODSI1459 | Log space of server session session number from time opened |
Explanation |
The log space of the specified server session has been opened. |
Action |
No action required. |
INODSI1460 | Log space of server session session number completed |
Explanation |
The log space of the specified server session has been completed. |
Action |
No action required. |
INODSI1463 | Database 'database name' accessed online |
Explanation |
The specified database has been accessed online. |
Action |
No action required. |
INODSI1464 | Database 'database name' accessed offline |
Explanation |
The specified database has been accessed offline. |
Action |
No action required. |
INODSI1466 | Creation of database space space number (location name) has successfully finished |
Explanation |
The specified database space has been created. |
Action |
No action required. |
INODSI1467 | Tamino name modifierversion on system information |
Explanation |
This is a generic message used to identify an activity. |
Action |
No action required. |
INODSI1468 | No index found |
Explanation |
No index found. |
Action |
No action required. |
INODSI1469 | The database server is active on a remote node |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSI1470 | Database spaces for database database name have been created |
Explanation |
The database spaces for a database server have been successfully created. The next step of database creation will be restoring the initial contents of the database. |
Action |
Restore the initial contents of the database. |
INODSI1471 | Database database name has been deleted |
Explanation |
The database with the given name has been successfully deleted. |
Action |
No action required. |
INODSI1474 | Read-only database database name , startup at startup |
Explanation |
This message shows the time at which the database was started in read-only mode. |
Action |
No action required. |
INODSI1475 | Database database name, startup at startup |
Explanation |
This message shows the time at which the database was started. |
Action |
No action required. |
INODSI1480 | Log space of server session session number processed until time |
Explanation |
All information generated before the given end timestamp of the log space of the specified server session was processed. |
Action |
No action required. |
INODSI1481 | Log space of server session session number skipped |
Explanation |
The log space of the specified server session was not processed because it contains only information generated after the given end timestamp. |
Action |
No action required. |
INODSI1484 | No log space information found |
Explanation |
The initial backup was used for restore, and no log space of another session exists. |
Action |
No action required. |
INODSI1485 | Checking finished. No inconsistencies found. |
Explanation |
The check and repair database action has finished. |
Action |
No action required. |
INODSI1486 | Log space of server session session number extent extent number archived |
Explanation |
A log space extent has been copied to the archive location. |
Action |
No action required. |
INODSI1487 | The backup tape from time has been unregistered |
Explanation |
The information about the availability of the given backup tape has been removed. |
Action |
The tape may be removed from the archive. |
INODSI1488 | Previous server session aborted when recovering session session number |
Explanation |
A previously started restore/recovery run did not complete the recovery phase. |
Action |
See the instructions within subsequent messages. |
INODSI1489 | Log space data processing end time stamp is time |
Explanation |
This is a progress message about the aborted recovery run or an abort of replication processing. |
Action |
In the case of a recovery run, the information can be used to start a recover until. |
INODSI1490 | Continuing server startup will disable subsequent backups |
Explanation |
When the server startup is continued, backups done later than the used one will become invalid. |
Action |
No action required. |
INODSI1491 | Due to an unexpected problem, Restore and/or Recover was not successful. Please re-execute the Restore and/or Recover now to ensure data integrity. |
Explanation |
For reasons stated in the job log, the Restore and/or Recover failed to execute properly. Depending on the reason for the abort, either "restore without recover" or "recover until" can be used to recover your data. |
Action |
If the reason for the initial recovery abort was a missing or corrupted log space, use "restore without recover" or "recover until". |
INODSI1492 | Subsequent backups disabled |
Explanation |
Backups older than the one used for the aborted recovery run are invalid now. |
Action |
No action possible. |
INODSI1493 | Tamino server successfully started in read-only mode |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSI1494 | Destruction of word fragment index started |
Explanation |
Destruction of word fragment index started |
Action |
No action required |
INODSI1495 | Creation of word fragment index successfully finished |
Explanation |
Creation of the word fragment index successfully finished. |
Action |
No action required |
INODSI1496 | Destruction of word fragment index successfully finished |
Explanation |
Destruction of the word fragment index successfully finished |
Action |
No action required |
INODSI1532 | referential constraint name dropped (primary primary, foreign foreign) |
Explanation |
The specified referential integrity constraint has been dropped. |
Action |
None. |
INODSI1535 | file file refreshed |
Explanation |
The specified file has been refreshed. |
Action |
None. |
INODSI1550 | function not permitted, referential constraint defined |
Explanation |
The function not permitted because a referential constraint is defined. |
Action |
None. |
INODSI1631 | Autorepair completed without errors |
Explanation |
The autorepair from the crash of the previous server session was successful. |
Action |
The database can now be used. |
INODSI1632 | Recovery terminated successfully |
Explanation |
The recovery has processed all log spaces. All updates have been re-applied. |
Action |
The server can now be restarted. |
INODSI1634 | Successful completion |
Explanation |
The action has completed without errors. |
Action |
No action required. |
INODSI1635 | Crash dump of database finished |
Explanation |
The crash dump is complete. |
Action |
No action required. |
INODSI1636 | Tamino server successfully started |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSI1637 | Skipping recovery terminated successfully |
Explanation |
The operation of skipping the recovery has terminated successfully. The update of the log space information has been completed. |
Action |
The server can now be restarted. |
INODSI1691 | Mass load recovery files archived |
Explanation |
The mass load recovery files have been copied to the archive location. |
Action |
No action required. |
INODSI1732 | Calculated RESTART point - BLOCK=block,CHECKPOINT=name |
Explanation |
Recovery has restarted from the position shown. |
Action |
No action required. |
INODSI1986 | no file protection enabled |
Explanation |
File protection is not enabled |
Action |
No action required. |
INODSI1988 | PID pid |
Explanation |
Process ID. |
Action |
None. |
INODSI2003 | Replication of server session session number suspended replication data processed until timestamp |
Explanation |
Replication processing is suspended due to a server shutdown request of the replication database. |
Action |
No action required. |
INODSI2006 | No replication data for server session session number |
Explanation |
No modifications have been made for a server session on the master database. |
Action |
No action required. |
INODSI2007 | Replication of server session session number from timestamp started |
Explanation |
The replication processing has started to process the log space data of the specified server session of the master database. |
Action |
No action required. |
INODSI2008 | Replication of server session session number completed |
Explanation |
The server completed replication of a master database's server session |
Action |
No action required. |
INODSI2009 | Replication of server session session number resumed using replication data from timestamp |
Explanation |
The server continued replication processing after replication database startup. |
Action |
No action required. |
INODSI2010 | Server session session number replicated until time stamp |
Explanation |
This is the current replication status of the database. |
Action |
No action required. |
INODSI2011 | Starting replication using data from database database name |
Explanation |
Replication processing has started. The master database must be active to supply replication data. |
Action |
No action required. |
INODSI2012 | Initial server session session number for new replication database |
Explanation |
A replication database is started for replication the first time. |
Action |
No action required. |
INODSI2017 | Updating backup generations |
Explanation |
Older backups are being removed if the number of backup generations has been exceeded. |
Action |
No action required. |
INODSI2018 | Using hostname as host name for the Software AG XTS Directory Server entries |
Explanation |
The specified hostname has been assigned to the server property "server host name". This name will be registered in the Software AG XTS Directory Server as the host where the database is located. |
Action |
No action required. |
INODSI2021 | The following file type file was not deleted: file name |
Explanation |
In the case of abnormal server terminations, log and dump files will be written. To be able to analyze several problems, these files could be helpful and will not be deleted. Be aware that dump files could be very large. |
Action |
It might be useful to keep the dump and log files for further examination. If you want to generate a new database in the same location you should move those files to a different location by hand. |
INODSI2040 | File 'name' copied to directory |
Explanation |
This is an informational message. |
Action |
No activity required. |
INODSI2044 | Infofile 'path' created |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSI2074 | Corrupted block repaired on space |
Explanation |
Due to a previous crash the latest written block may be corrupted (in the journal or log). In some cases this can be detected and repaired. |
Action |
Check if the previous session was abnormally aborted. Only in this case should this message appear. |
INODSI2091 | Process can make use of 3GB virtual address space |
Explanation |
The process can make use of 3GB virtual address space. |
Action |
No action required. |
INODSI2100 | Web server configuration changed, server server notified |
Explanation |
The web server configuration changed and the server was notified. |
Action |
No action required. |
INODSI2115 | Execution continues |
Explanation |
This message is displayed by debug-enabled executables if they have been selected for debugging. |
Action |
No action required. |
INODSI2146 | Replication of server session session number resumed using replication data from timestamp. Simultaneous query permitted. |
Explanation |
The server continued replication processing after replication database startup. |
Action |
No action required. |
INODSW2147 | Replication of server session session number resumed using replication data from timestamp. Simultaneous query will be enabled when replication database is up-to-date. |
Explanation |
The server continued replication processing after replication database startup. |
Action |
No action required. The database server will automatically enable simultaneous read when the locking information becomes available, at the latest when replicating the current master database session. |
INODSI2148 | At least one replication database allows simultaneous query |
Explanation |
The replication master writes additional locking information to the log space. A replication database with 'Simultaneous Query' enabled may be accessed with queries while it replicates updates. |
Action |
No action required. |
INODSI2149 | No replication databases allow simultaneous query |
Explanation |
The replication master does not write additional locking information to the log space. A replication database with 'Simultaneous Query' enabled cannot processs queries while replicating updates of this session. |
Action |
No action required. |
INODSI2150 | Database database name set to replication type with simultaneous query |
Explanation |
If at least one replication database is defined with 'simultaneous query' the master database writes additional locking information to the log space. If this replication database is the first of this kind, the master switches to a new session. |
Action |
No action required. |
INODSI2151 | Database database name set to replication type without simultaneous query |
Explanation |
If no replication database is defined with 'simultaneous query' the master database does not write additional locking information to the log space. If replication database mentioned is the last of that kind, the master switches to a new session |
Action |
No action required. |
INODSI2154 | Replication of server session session number from timestamp started. Simultaneous query permitted. |
Explanation |
The replication processing has started to process the log space data of the specified server session of the master database. |
Action |
No action required. |
INODSW2155 | Replication of server session session number from timestamp started. Simultaneous query will be enabled when replication database is up-to-date. |
Explanation |
The replication processing has started to process the log space data of the specified server session of the master database. |
Action |
No action required. The database server will automatically enable simultaneous read when the locking information becomes available, at the latest when replicating the current master database session. |
INODSI2158 | Backup from backup_date deleted |
Explanation |
After backup, the number of backup generations is updated, i.e older backups are removed. For further information, please refer to the documentation of the server parameter "number of backup generations". |
Action |
No action required. |
INODSI2166 | Initial backup removed |
Explanation |
After backup, the number of backup generations is updated, i.e older backups are removed. For further information, please refer to the documentation of server parameter "number of backup generations". |
Action |
No action required. |
INODSE2169 | Received response error text (text) while starting server |
Explanation |
Starting the server failed. |
Action |
Please contact your software supplier. |
INODSI2190 | Doctype doctype has been loaded |
Explanation |
The specified doctype has been successfully loaded. |
Action |
No action required. |
INODSI2196 | Connection to master database database name reestablished |
Explanation |
The replication database obtained new replication data from its master database. |
Action |
No action required. |
INODSI2199 | Replication data of session session was generated with different update or hotfix level of Tamino version version: update level update, hotfix number hotfix |
Explanation |
At the master database node a new update of a Tamino version was installed. |
Action |
Install the same update of the Tamino version at the replication database node. |
INODSE2211 | No valid location provided for backup |
Explanation |
There can be a number of reasons for this error, for example no free space or the location directory was deleted outside of Tamino. The exact reason for the error is contained in the job log. |
Action |
Study the job log to find the exact reason for the error. If the job log indicated that there is no space, free some space on the location device. Alternatively, you may provide another location for the backup. |
INODSI2239 | The backup tape from initial savepoint has been unregistered |
Explanation |
The information about the availability of the initial backup tape has been removed. |
Action |
The tape may be removed from the archive. |
INODSI2259 | Creating / deleting database process active, wait for continue |
Explanation |
Another job which creates or deletes a database is active on the current node. View running jobs for more information. |
Action |
Wait until this task has been completed. You should not wait longer than a couple of seconds. |
INODSI2267 | Convert database to version version |
Explanation |
The database will be converted to the version displayed. |
Action |
No action required. |
INODSI2300 | Keep backup file filename |
Explanation |
The backup file was not deleted because it was selected to be kept by the user. |
Action |
Keep in mind that there is still a backup file occupying disk space. |
INODSI2310 | Licensed for name with ID id |
Explanation |
Display customer/partner information from the license file. |
Action |
No action required. |
INODSI2311 | Licensed for name sub-licensed by name with ID id |
Explanation |
This is a display of customer/partner information from the license file. |
Action |
No action required. |
INODSI2312 | Licensed for name with ID text sub-licensed by name |
Explanation |
This is a display of customer/partner information from the license file. |
Action |
No action required. |
INODSI2313 | Licensed for name with ID text sub-licensed by name with ID id |
Explanation |
This is a display of customer/partner information from the license file. |
Action |
No action required. |
INODSI2314 | Licensed for name with ID id, license expires on date |
Explanation |
Display customer/partner and expiration information from the license file. |
Action |
No action required. |
INODSI2315 | Licensed for name sub-licensed by name with ID id, license expires on date |
Explanation |
This is a display of customer/partner and expiration information from the license file. |
Action |
No action required. |
INODSI2316 | Licensed for name with ID text sub-licensed by name, license expires on date |
Explanation |
This is a display of customer/partner and expiration information from the license file. |
Action |
No action required. |
INODSI2317 | Licensed for name with ID text sub-licensed by name with ID id, license expires on date |
Explanation |
This is a display of customer/partner and expiration information from the license file. |
Action |
No action required. |
INODSI2343 | Backup created with backup key 'value' (from) |
Explanation |
The identification of the last created backup is displayed. |
Action |
No action required. |
INODSI2344 | backup key 'value' (from) |
Explanation |
This is a display of backup information. |
Action |
No action required. |
INODSI2345 | backup key 'value' (initial backup) |
Explanation |
This is a display of backup information. |
Action |
No action required. |
INODSI2346 | Deleting disabled backup from date |
Explanation |
A disabled backup file is being deleted. |
Action |
No action required. |
INODSI3469 | Dataset name created on date |
Explanation |
The dataset was created on the specified date. |
Action |
No action required. |
INODSE4100 | Failure accessing file |
Explanation |
An error has occurred accessing a Tamino file. The file may possibly be corrupt. |
Action |
Check that it is the correct file and repeat the operation. If the error persists, contact your software supplier. |
INODSI5263 | Restoring pending transactions |
Explanation |
Pending global transactions are being restored during the server startup processing. |
Action |
No action required. |
INODSI5270 | Use parameter "value" to force server registration |
Explanation |
The server could not register with the XTS directory service, because an entry for the server is already present. If this entry is no longer necessary the specified parameter can be used to overwrite the existing entry. |
Action |
Set the specified parameter to YES to force server registration. |
INODSI5282 | Overwriting Software AG XTS Directory Server entries |
Explanation |
The Software AG XTS Directory Server entries already existed. They are overwritten. |
Action |
No action required. |
INODSI5286 | New block allocations for database |
Explanation |
There were container size/blocksize correlations which require new allocations for all files in the database. |
Action |
No action required. |
INODSI5299 | Data space container, file file name removed |
Explanation |
The database space with the qualified type and name has been removed from the file system. |
Action |
No action required. |
INODSI5339 | Log space of server session session number from different version - recovery stopped |
Explanation |
The next log space to be processed was created by another program version. |
Action |
See the product documentation for further information about migration between program versions. |
INODSI5352 | Preparing for external backup |
Explanation |
The database is in synchronized mode, so an external backup can now take place. |
Action |
No action required. |
INODSI5353 | Continuing after external backup |
Explanation |
The synchronized mode of the database has ended. Normal database processing can resume. |
Action |
No action required |
INODSQ1651 | The currently inserted tape has been processed |
Explanation |
The currently inserted tape has been completely filled (backup) or completely read (restore). |
Action |
Please insert the next tape in the set so that processing may continue. |
INODSQ1652 | The diskette is full |
Explanation |
An operation writing to a diskette has completely filled up the diskette. |
Action |
Provide the information you are prompted for to enable Tamino to switch to a new diskette. |
INODSQ1653 | Please insert the next sequential tape and verify the selected device name is correct. |
Explanation |
Another tape is required in the current backup or restore sequence. |
Action |
Insert the next sequential tape and verify the device name is correct. |
INODSQ1654 | Please insert diskette diskette number and specify the device name |
Explanation |
Another diskette is required. |
Action |
Insert the indicated diskette and specify the device name. |
INODSQ1655 | First tape required |
Explanation |
The first tape is required. |
Action |
Insert the first tape. |
INODSQ1656 | First diskette required |
Explanation |
The first diskette is required. |
Action |
Insert the first diskette. |
INODSQ1657 | Please insert first tape again and specify the device name |
Explanation |
The first tape is required. |
Action |
Insert the first tape and specify the device name. |
INODSQ1658 | Waiting for space on LOG device |
Explanation |
The server can no longer perform update operations, because there is no more free space on the LOG device. |
Action |
Create free space on the LOG device, e.g. by deleting files. |
INODSQ1659 | Try to get free space on device where LOG is located |
Explanation |
The server can no longer perform update operations, because there is no more free space on the LOG device. |
Action |
Create free space on the LOG device, e.g. by deleting files. |
INODSQ1660 | Continue server startup or re-execute restore/recover |
Explanation |
When you continue the server startup, autorepair will be used. Database modifications not recovered during the recovery run of the previous aborted server session will be lost. |
Action |
Decide whether to continue or abort the server startup. |
INODSQ1661 | Please reply "yes" or "no" to continue server startup |
Explanation |
At this point in time you can continue or abort the server startup. |
Action |
Enter "yes" to continue the server startup, enter "no" to abort it. |
INODSQ2224 | Transfer via pipe stalled |
Explanation |
The backup activity via named pipe is hanging. One reason could be that the partner pipe process died for some reason, for example if the disk is full. |
Action |
Find out the reason why the pipe processing is hanging and answer 'OK' to continue or 'Abort' to abort the backup processing. |
INODSQ2225 | Continue or abort ? |
Explanation |
Continue or abort the processing. If you answer 'abort' the process immediately terminates with an appropriate message. Answer 'OK' to continue processing if you are sure that the pipe process is still active. |
Action |
no action |
INODSQ2256 | File extent number missing |
Explanation |
A physical file extent of e.g. a backup file was not specified. |
Action |
Enter the file/device name of the required file extent. |
INODSQ2257 | Enter file/device name |
Explanation |
Enter here the full qualified file name of the required extent. Pipe or tape devices may be entered as well. |
Action |
No action required. |
INODSQ2295 | No location for database space extent number |
Explanation |
There is no location given for this database space. |
Action |
Select a valid location. |
INODSR1479 | Creating database space extent number of number of extents |
Explanation |
This is an informational message indicating how many extents of a group of extents have been created for the database space. |
Action |
No action required. |
INODSR1483 | Deleting database space extent number of number of extents |
Explanation |
This is an informational message indicating how many extents of a group of extents for the database space have been deleted. |
Action |
No action required. |
INODSR1682 | Analyzing journal information |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSR1683 | Re-applying changes. Processing journal block block number. |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSR1684 | Reconstructing consistent index structures. Processing journal block block number. |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSR1685 | Resetting unfinished transactions. Processing journal block block number. |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSR1686 | Recovered from abnormal termination |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSR1687 | Reading parameters |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSR2029 | Offline conversion phase |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSR2077 | Re-applying updates started |
Explanation |
The recover process has started. |
Action |
No action required. |
INODSR2078 | Re-applying updates of session session |
Explanation |
The recover process has started re-applying updates of the next session. |
Action |
No action required. |
INODSR2079 | Re-applying updates completed |
Explanation |
The recover process has finished. |
Action |
No action required. |
INODSR5347 | Preparing external backup |
Explanation |
This is an information message. |
Action |
No action required. |
INODSR5348 | Synchronizing database |
Explanation |
This is an information message. |
Action |
No action required. |
INODSR5349 | Processing external backup |
Explanation |
This is an information message. |
Action |
No action required. |
INODSR5350 | Performing final cleanup |
Explanation |
This is an information message. |
Action |
No action required. |
INODSR5351 | Processing external restore |
Explanation |
This is an information message. |
Action |
No action required. |
INODSR5362 | Processing backup |
Explanation |
A backup operation is currently being processed. |
Action |
No action required. |
INODSR5363 | Processing restore |
Explanation |
A restore operation is currently being processed. |
Action |
No action required. |
INODSS1005 | Create database space |
Explanation |
This message indicates that the specified function is in progress. |
Action |
No action required. |
INODSS1009 | Delete database space |
Explanation |
This message indicates that the specified function is in progress. |
Action |
No action required. |
INODSS1711 | Recovering from abnormal termination |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSS1712 | Starting database server |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSS1713 | Checking database for index inconsistencies |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSS1714 | Deleting database 'database name' |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSS2025 | Creating database ... |
Explanation |
Tamino is creating a new database. |
Action |
No action required. |
INODSS2076 | Performing recovery |
Explanation |
The restore/recover process is in the recover phase. |
Action |
No action required. |
INODSS2159 | Converting database |
Explanation |
The database is being upgraded or downgraded. |
Action |
No action required. |
INODST1751 | Start of Tamino name version modifierversionmodifier on system information |
Explanation |
This is an informational message. |
Action |
No action required. |
INODST1752 | Database database name Session session number (name modifierversion on system information, process ID pid) |
Explanation |
This is an informational message. |
Action |
No action required. |
INODST1753 | Database database name Read-Only Session (name modifierversion on system information, process ID pid) |
Explanation |
This is an informational message. |
Action |
No action required. |
INODST1766 | Database database name Replication Session (name modifierversion on system information, processID pid) |
Explanation |
The server started for a replication database. |
Action |
No action required. |
INODSV1053 | Database autorepair suppressed |
Explanation |
The previous server session terminated abnormally. The server attempted to perform an autorepair, but the autorepair has been suppressed by external manipulation. The database might be in an inconsistent state. |
Action |
Determine what kind of manipulation has occurred and contact your software supplier. |
INODSV1129 | System error text occurred |
Explanation |
A system error has occurred in the context of the current task. |
Action |
Check the manufacturer's manual. |
INODSV1174 | No input data available |
Explanation |
The specified input file is empty. |
Action |
Ensure that the correct input file is being used. |
INODSV1245 | Error information: log space of server session session number - block block, location record |
Explanation |
The information describes the location of the recently processed log space data |
Action |
Keep this information when log space data analysis is required. |
INODSV1258 | Journal overflow. Server cannot proceed. |
Explanation |
The journal space was insufficient. The current server session has to be terminated. |
Action |
Check if more journal space can be provided. Restart the server. |
INODSV1281 | Component name called at extension point name returned response error text |
Explanation |
The Tamino server called an external component which returned an error response. |
Action |
Please contact your software supplier. |
INODSV1473 | The database server is active on the local node |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSV1587 | Internal event SCLOST has occurred |
Explanation |
A sort action has failed due to resource problems. A retry will be started automatically. |
Action |
No action required. |
INODSV1801 | Previous server session failed during write operation |
Explanation |
The previous server session was performing a write operation on modified data when the server session terminated abnormally. |
Action |
If you can be sure that a single write operation is atomic on your system, you can ignore this warning. You can always assume so if there was no power failure and if the previous server session did not abort due to an I/O error. If you cannot be sure, recover your database from the last backup. |
INODSV1806 | Aborted by operator |
Explanation |
The operator has explicitly aborted the operation. |
Action |
No action required. |
INODSV1818 | Log space of server session session number is empty |
Explanation |
An input file to be used for recovery is empty. |
Action |
Check that the correct log space files are present at the log space location. |
INODSV2083 | Unlocking port allocation lock failed with response text - error text |
Explanation |
An unexpected response was received while trying to unlock the port allocation lock. |
Action |
Please contact your software supplier. |
INODSV2118 | Unlocking raw section lock failed with response text - error text |
Explanation |
Unexpected response received while trying to unlock the raw section lock. |
Action |
Please contact your software supplier. |
INODSV2139 | Unlocking raw section lock failed with response text - error text |
Explanation |
Unexpected response received while trying to unlock the container move lock. |
Action |
Please contact your software supplier. |
INODSV2226 | System error error (string) occurred |
Explanation |
An internal system service error occurred. |
Action |
Analyze the error number and the human readable text. |
INODSV2273 | The server name is active |
Explanation |
The specified server is active. |
Action |
No action required. |
INODSV2276 | Aborted by High Availability monitor |
Explanation |
The High Availability monitor detected that the server did not respond within a specific timeout limit and forced an abnormal crash of this server. There could be two cases: either the server is really hanging or there is something very busy that the check by the High Availability monitor takes a very long time (e.g. a huge buffer flush is in progress). |
Action |
Check if the HA timeout value is reasonable with the context. One dangerous situation can be a long enduring buffer flush which might block applications for a long time. Maybe it is reasonable to run with small flush limit and/or flush group size parameters. |
INODSV2281 | System error text (errtxt) when opening database space space number (path) |
Explanation |
An internal operating system error has occurred while trying to open a database space. |
Action |
Analyse the error text and consult the manufacturer's manual. |
INODSV5266 | Journal overflow. Current activity cancelled. |
Explanation |
The journal space was insufficient. The current activity has been cancelled. Typically, a transaction has been rolled back internally. |
Action |
Provide more journal space. Restart the terminated activity. |
INODSV5269 | Server is already registered with the Software AG XTS Directory Server |
Explanation |
When the server starts it registers with the Software AG XTS Directory Server. It is possible that entries for the server are already present (server already started somewhere else or previous server session failed). If this message comes as a warning message, the entry found exactly matches the one that should be entered. If this message comes as an error message, the entry found did not match the entry that the server wanted to add. |
Action |
If this message comes as a warning message no action is required. If this message comes as an error message the Software AG XTS Directory Server entry found for the server should be checked and, if no longer necessary, the next server start should be done with the parameter for overwriting the Software AG XTS Directory Server entry activated. |
INODSW1014 | Creation of word fragment index failed |
Explanation |
Creation of word fragment index failed, because corresponding index tree is inaccessible. |
Action |
Use the function "check and repair database" and restart the server. |
INODSW1017 | Due to license restrictions, recovery of the database will not be possible |
Explanation |
Your license file does not allow logging to be enabled. Due to this restriction, recovery of the database will not be possible. |
Action |
Contact your software supplier for an upgrade of your license. |
INODSW1035 | Synchronization semaphore lost and recreated |
Explanation |
The synchronization semaphore was deleted from outside and a new one was created. |
Action |
No action required. |
INODSW1151 | Further recovery for doctype doctype will not include index |
Explanation |
Due to an error during recovery the index of the doctype has been disabled. |
Action |
Even though the index was disabled, data has been recovered. The index can be rebuilt using the"Check and Repair" function. |
INODSW1340 | The last available backup could not be deleted |
Explanation |
It doesn't make much sense to delete all backups. To avoid the situation that someone deletes the last backup by mistake, this deletion is not allowed. |
Action |
If you want to delete this special last backup, you have to create a new one. |
INODSW1409 | Error when opening database space space number (at path): size mismatch |
Explanation |
The size of the database space is not equal to the size expected by the server. |
Action |
Please contact your software supplier. |
INODSW1410 | Error when opening database space space number (at path) |
Explanation |
The database space could not be opened. |
Action |
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. |
INODSW1411 | Error when opening database space, compressed state is not permitted (at path) |
Explanation |
The database file has the compressed attribute, which is not permitted, because write errors should be avoided if the device is getting full. |
Action |
Remove the compressed attribute from the database file. |
INODSW1412 | System error text when opening database space space number (path) |
Explanation |
The specified operating system error has occurred. |
Action |
Please consult the manufacturer's manual. |
INODSW1414 | System error text when opening database space space number (path) |
Explanation |
The specified operating system error has occurred. |
Action |
Please consult the manufacturer's manual. |
INODSW1455 | Database start not allowed because of pending "set version" operation. Please re-execute "set version". |
Explanation |
A previous "set version" operation aborted. The database may be inconsistent. |
Action |
Try "set version" again. If it fails also the second time, report the problem to your software supplier. |
INODSW1482 | Log space of server session session number not to be processed. |
Explanation |
The log space of the specified server session was not processed because it was skipped by a previous recovery run. |
Action |
Verify that the skipped log space has also been skipped by the previous recovery run. |
INODSW1529 | switch internal I/O mode |
Explanation |
The I/O mode was switched because an internal I/O function is not supported by given platform. This could happen if a platform does not support the call lio_listio(). |
Action |
No action required. |
INODSW1602 | Insufficient disk space for journal space, resize to: size MB |
Explanation |
There is insufficient disk space to create journal space of the required size; a reduced size will be used. |
Action |
No action required. |
INODSW1689 | Parallel backup not available on Windows, a sequential backup will be performed. |
Explanation |
The Windows version of backup does not support 'parallel backup', therefore a sequential backup will be performed. |
Action |
No action required. |
INODSW1784 | There is a pending autorepair for the database |
Explanation |
The database had previously not terminated correctly. |
Action |
When the database has been restarted, it will perform an autorepair operation. |
INODSW1800 | This is an emergency restart |
Explanation |
The server stopped the previous server session due to shortage of journal space. If this restart fails, data may be lost or inconsistent. |
Action |
If the restart fails, please recover your data from the last backup. |
INODSW1802 | A transaction has been heuristically rolled back at time |
Explanation |
The database system has rolled back a transaction for which a decision of the transaction manager was pending. |
Action |
No action required. |
INODSW1803 | A transaction has been heuristically committed at time |
Explanation |
The database system has committed a transaction for which a decision of the transaction manager was pending. |
Action |
No action required. |
INODSW1804 | Backup task not responding. Ignoring backup activity. |
Explanation |
A backup task was running when the server came up. The server synchronization with this backup task has failed. The backup will terminate eventually. |
Action |
Check if the backup activity is still running. If so, it can be terminated. Redo the backup. |
INODSW1805 | The server cannot proceed until the backup activity has finished |
Explanation |
The server will wait for the backup activity to complete. When it has finished, the server will continue. |
Action |
No action required. |
INODSW1807 | Switched to read-only mode because a database space is not writable |
Explanation |
The database will not accept updates. |
Action |
If this behavior is not intended, make all database spaces write-accessible. |
INODSW1808 | Read-only database |
Explanation |
The database is read-only. Some functions are disabled. |
Action |
No action required. |
INODSW1809 | Error when opening database space space number (at path): size mismatch, expected bytes bytes |
Explanation |
The size of the database space is not equal to the size expected by the server. |
Action |
If the operation does not complete successfully, please contact your software supplier. |
INODSW1810 | database space space number opened for read-only access |
Explanation |
The specified database space was opened for read-only access. No updates will be possible on this database space. |
Action |
No action required. |
INODSW1811 | Database might be corrupted |
Explanation |
An inconsistency has been found in the database. |
Action |
Check the database for consistency. |
INODSW1812 | Backup process is not responding |
Explanation |
The synchronization between the backup process and the server has been lost. One possible reason is that the backup process has been killed. The backup will not come to a normal end. |
Action |
Restart the backup. |
INODSW1813 | Backup process is not communicating completion |
Explanation |
The synchronization between the backup process and the server has been lost. One possible reason is that the backup process has been killed. The backup will not come to a normal end. |
Action |
Restart the backup. |
INODSW1814 | Backup process is not fetching modified data |
Explanation |
The synchronization between the backup process and the server has been lost. One possible reason is that the backup process has been killed. The backup will not come to a normal end. |
Action |
Restart the backup. |
INODSW1815 | Before image mismatch for number instances on doctype doctype |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INODSW1817 | Read-only database server accessed |
Explanation |
A utility is being run against a read-only database server. Certain functions may not be available. |
Action |
No action required. |
INODSW1819 | Invalid starting block number block number for log space from session session number |
Explanation |
The log space does not contain correct log information. |
Action |
Check if files have been moved or copied to the log space location. |
INODSW1823 | Unable to remove shared memory |
Explanation |
It has not been possible to remove a shared memory segment. |
Action |
Remove any allocated shared memory with available system tools. |
INODSW1825 | Unexpected database error: error text |
Explanation |
An internal database error has occurred. |
Action |
Please contact your software supplier. |
INODSW1827 | Function is deactivated |
Explanation |
The requested function is not activated at present. |
Action |
No action required. |
INODSW1828 | Doctype deleted but de-allocation failed (reason code reason) |
Explanation |
A doctype has been deleted from the database but it could not be de-allocated. |
Action |
Determine the cause of the failure from the supplied reason code. |
INODSW1829 | Unable to remove utility flag and/or write event |
Explanation |
The utility was in its final cleanup phase but could not complete all required actions. |
Action |
The utility has terminated successfully, but the cause of the cleanup failure should be determined. |
INODSW1830 | Event could not be written due to response response |
Explanation |
The utility has failed to write a final event due to the response reported. |
Action |
The utility will end successfully. The response code indicates the reason for the failure to write an event. |
INODSW1835 | Waiting for debugger to attach |
Explanation |
This message is displayed by debug-enabled executables if they have been selected for debugging. |
Action |
Please contact your software supplier. |
INODSW1836 | Mass load recovery files not archived |
Explanation |
The mass load recovery files could not be copied to the archive location. |
Action |
Check for a reason why files could not be created at the archive location. Copy the mass load recovery files manually. |
INODSW1837 | An error occurred during the create index process on doctype doctype |
Explanation |
The error is caused by an attempt to create a unique index for non-unique data values. |
Action |
Contact your software supplier. |
INODSW1838 | Log space of server session session number processed until time |
Explanation |
None of the information generated after the given end timestamp of the log space of the specified server session was processed. |
Action |
Verify that the skipped part of the log space is the same as was skipped with a previous recovery. |
INODSW1839 | Log space of server session session number extent extent number not archived |
Explanation |
A log space extent could not be copied to the archive location. |
Action |
Check the log archive location name and for available space. |
INODSW1840 | Log space of server session session number extent extent number not closed |
Explanation |
A log space extent could not be closed. |
Action |
No action required. |
INODSW1841 | Database successfully checked and repaired. Number of repaired indexes is number. |
Explanation |
The database has been repaired. |
Action |
No action required. |
INODSW1842 | Update in internal configuration store could not be logged |
Explanation |
Configuration was successfully updated, however the update could not be logged. Possible reasons may be - update log file is read-only or there is not enough space on device where Tamino is installed. |
Action |
In most cases this warning can be ignored. Inform your system administrator about the warning. |
INODSW1843 | No information about previous recovery processing |
Explanation |
Recovery processing was aborted without being able to write recovery progress information. |
Action |
See the instructions within subsequent messages. |
INODSW1845 | Continuing server startup will disable all existing backups |
Explanation |
A preceding Restore/Recover operation that specified an "until" date that is earlier than the latest backup was performed. This means that any backup that was performed after the "until" date of the Restore/Recover operation is no longer valid. |
Action |
Create a new database backup as soon as possible. |
INODSW1846 | All backups disabled, create a new backup copy |
Explanation |
No information about previous recovery processing was available, all backups have been disabled. |
Action |
Create a new database backup as soon as possible. |
INODSW1848 | Container file could not be extended, but attempt to continue |
Explanation |
The database could not be extended as the backup file signalled. The restore is continued but later I/O errors are possible. |
Action |
You can ignore this message if the restore terminates successfully. If the restore fails due to an I/O error you must check why the database could not be extended. |
INODSW1980 | Skipping recovery terminated with warning status |
Explanation |
While skipping the recovery a situation occurred that requires further investigation. |
Action |
Check for additional messages in the event log. |
INODSW1981 | Recovery terminated with warning status |
Explanation |
During recovery a situation occurred that requires further investigation. |
Action |
Check for additional messages in the event log. |
INODSW1993 | keyword combination not allowed |
Explanation |
The supplied keyword combination is invalid. |
Action |
Correct the input parameters. |
INODSW1997 | Due to license restrictions, the database will be started in readonly mode |
Explanation |
Your license is restricted to readonly mode. Due to this restriction, updates of the database will not be possible. |
Action |
Contact your software supplier for an upgrade of your license. |
INODSW2047 | Version cd database version not installed, using compatible version instead |
Explanation |
The version of the CD database is not installed on the target system. However a compatible version was found and will be used. |
Action |
No action required. |
INODSW2066 | Journal size specified is less than the minimum allowed size of numberMB. Increasing to numberMB. |
Explanation |
The journal size specified is less than the minimum required to allow correct operation of the server. Tamino is adjusting the journal size up to the minimum size. |
Action |
No action required. |
INODSW2073 | Previous log file corrupted (reason: reason). Please perform a database backup as soon as possible. |
Explanation |
During restart after a database crash it was detected that the log file of the previous session is corrupt. A database recovery may fail, therefore a new backup would resolve this situation. Moreover a further database replication would fail, therefore if the database is or will be a replication master the replication must be newly set up with a new database backup. |
Action |
Perform a new database backup. Revise replication. Reestablish replication with the new database backup. |
INODSW2089 | Port port already in use as name by server server |
Explanation |
The port to check is already in use. |
Action |
Choose another port or be aware that problems with port usage might occur. |
INODSW2090 | Port port used as name by server server is located in selected dynamic port range |
Explanation |
An allocated port was found in the dynamic port range. |
Action |
Specify another dynamic port range or change the allocated port so that it is located outside the dynamic port range. |
INODSW2098 | Web server webserver assigned to database server |
Explanation |
The web server is assigned to a database and must not be removed before it is deassigned. |
Action |
Keep this web server definition or deassign it from all databases. |
INODSW2101 | Web server configuration changed, notification of server server failed (rc1,rc2,rc3) |
Explanation |
The web server configuration was changed, but the server notification failed. |
Action |
The server has to be restarted manually. |
INODSW2102 | Web server configuration changed for web server webserver, but server notification failed |
Explanation |
The web server configuration was changed, but the notification of active servers failed. |
Action |
Restart all active servers which have assigned the web server in question. |
INODSW2112 | User specified record ID number is not within proposed range |
Explanation |
The load utility was called with at least one record ID which is within a used range. In the event of a crash the internal doctype may have a corruption. |
Action |
This is an internal problem. Please contact your software supplier. |
INODSW2113 | Cleanup of a mass load failed with error |
Explanation |
The cleanup task, e.g. within a rollback, of a mass load failed for internal reasons. |
Action |
Please contact your software supplier. |
INODSW2133 | Nothing to verify, no data available |
Explanation |
The item only contains index values, therefore no verification is necessary. |
Action |
No action required. |
INODSW2152 | Port port is currently active and may not be usable |
Explanation |
The specified port is currently active and may not be usable by the Tamino server. |
Action |
Specify another port for the Tamino server or free up the active port before starting the Tamino server. |
INODSW2153 | Flush limit too high. Value adjusted to new value. |
Explanation |
The flush limit specified was too high. It has been adjusted to a reasonable value. |
Action |
To avoid this warning at each startup of the database, configure a lower value. |
INODSW2156 | Database name1 is fully overlaid with backup from database name2 |
Explanation |
The backup file which was created by a foreign database has been restored into the current database. The previous content of the database has been completely deleted. |
Action |
No action required. |
INODSW2161 | corrupted data repaired |
Explanation |
A detected corruption was repaired immediately by Tamino. |
Action |
No action required. |
INODSW2171 | Replication data of session session requires new Tamino version version |
Explanation |
The replication database is using a different Tamino version than the master database. |
Action |
Install the required Tamino version at the repliction database node. If the required version is already installed and the error still exists, re-create the replication database using a backup created from this Tamino version. |
INODSW2172 | Master database must be restarted before a replication database can be set up |
Explanation |
The name of the first replication database has been added to the permission list. The database can be set up as a replication database of this master only after the master has been stopped and restarted. |
Action |
Stop the master database and start it again. |
INODSW2180 | Connection to server lost, reason reason |
Explanation |
The working process must be terminated because the server is stopping or has already stopped. There are 2 possible reasons: 0 means the server has stopped, 1 means the server is stopping and has aborted the process. |
Action |
Check why the server stopped. |
INODSW2186 | The configured buffer pool size (size MB) exceeds the machine's physical memory size (size MB) |
Explanation |
The buffer pool size is configured so that it exceeds the physical memory size of the machine. This does not make sense because the buffer pool replacement strategy will collide with the operating systems memory management. |
Action |
Choose a buffer pool size that is at least smaller than the machine's physical memory size. |
INODSW2191 | The maximum number of threads allowed per process (number) may not be sufficient to manage the database server |
Explanation |
The current parameter configuration may not allow the creation of all necessary threads to manage the database server. |
Action |
Either the system defined maximum number of threads per process is too low and should be increased, or the database parameter configuration should be changed to decrease the number of threads to be created. |
INODSW2195 | Connection to master database database name interrupted |
Explanation |
The replication database cannot obtain replication data from its master database. |
Action |
No action required. |
INODSW2197 | Replication of server session session number stopped. Replication data processed until timestamp. |
Explanation |
Replication processing is stopped due to an error as described in previous messages. If simultaneous queries were permitted, then the replication database stays online and may be used for further queries. |
Action |
Try to solve the problem at the master database's side or recreate the replication database from a new backup of the master. |
INODSW2198 | Update logging in internal configuration store is not active |
Explanation |
Updates in the internal configuration store are not logged because update logging is not activated in the current process. |
Action |
Please contact your software supplier. |
INODSW2207 | No reading process attached to pipe path |
Explanation |
Backup location is a named pipe and no process has the pipe open for reading. This situation may occur during database backup or database creation, when initial backup is being made. |
Action |
Start the process that reads from the pipe and perform the backup again. |
INODSW2209 | Inconsistent location definition (location) - expected type expected, real type real |
Explanation |
The location type is unexpected. This is typically the result of user intervention , for example the user deletes a location directory and creates a file with the same name. |
Action |
Make sure that Tamino locations are not modified outside of Tamino. |
INODSW2210 | Location location is nearly full |
Explanation |
Not enough disk space is left on the location. |
Action |
Free some space or use another location. |
INODSW2230 | Logging error in internal configuration store occurred at time, future updates may not be logged |
Explanation |
The internal configuration store showed an update logging error that occurred in the past. There is a chance that future updates will also not be logged, thus preventing a repair of the internal configuration store after a severe error. This message is displayed at each server startup unless you execute the described actions. |
Action |
To be sure to be able to recreate all configuration data, you can do the following: Copy your registry (all under the key 'Tamino') to a file. Use the 'export' function of your registry editor. Then clean your registry logging file or use another file. The registry logging file is defined with a string value at the registry key 'Tamino'. Combining both files lets you repair your Tamino registry in the case of a corruption. Finally you can remove the 'registry logging error' string value from the registry either with your registry editor or with the Registry functions of your Tamino manager. |
INODSW2238 | No space to remove |
Explanation |
The request to remove database space cannot be performed, because trailing space is in use. |
Action |
No action required. |
INODSW2240 | File/path path does not exist or is not accessible |
Explanation |
The given file/pathname does not exist or is not accessible. It will just be skipped. |
Action |
Check the file/pathname. |
INODSW2244 | Cannot create initial backup - reference to original one is not possible; perform backup for the database as soon as possible |
Explanation |
The initial backup for the new database could not be created. It tries to reference this backup, but the backup is already registered with another active database. So the database is left without a valid backup ! |
Action |
Perform a database backup as soon as possible. |
INODSW2245 | Cannot create initial backup - but referred to original one |
Explanation |
The creation of the initial backup of the new database failed. Nevertheless a backup entry was set up pointing to the file/device where the creation-backup comes from. This has the same effect as when the nocopyoption has been used. |
Action |
No action required. |
INODSW2246 | Reference to original backup is not possible; perform backup for the database as soon as possible |
Explanation |
The create from backup was used with the nocopy option, which means that the incoming backup file will just be referenced instead of copied. But it is not permitted to reference a backup file which is already registered with an active database. Now there is no valid backup for the created database |
Action |
Perform a database backup as soon as possible. |
INODSW2247 | Location skipped (no space) |
Explanation |
The given location has not enough space for creating a database file. It skips to the next location if any. |
Action |
Check the space in this location. |
INODSW2248 | Location skipped, (internal error text) |
Explanation |
The current location cannot be used and will be skipped. The internal error displayed gives the detailed reason. |
Action |
Analyse the error and check the path name of the location. |
INODSW2260 | create / delete database synchronization failed with (error) |
Explanation |
The semaphore synchronisation failed with an internal error. |
Action |
Do not start another create / delete database in parallel. |
INODSW2261 | Removing backup file (filename) failed due to internal error error |
Explanation |
The given backup file cannot be removed due to displayed error reason, but it will be unregistered. |
Action |
Delete the backup file by hand if you decide that it would never be needed any more. |
INODSW2262 | Problem during referencing initial backup file (file), reason: reason |
Explanation |
A reference operation (insert/delete) to a backup file failed. A reference will be set up at create database from backup to the source backup file. If the setting of a reference failed, then it may happen that the owner of the backup deletes the backup fie although a foreign database has it still registered. If this operation failed at the owner side, it may happen that the backup file remains in the file system although it was logically deleted. |
Action |
Check the databases where this backup file is registered. Maybe perform a new backup of databases which have this backup file registered. |
INODSW2269 | Failed to load ADABAS interface (library) |
Explanation |
The Tamino server failed to load the ADABAS interface. |
Action |
Provide a valid ADABAS interface in one of the locations searched during the library load. |
INODSW2277 | Buffer pool size set to size MB due to shortage of shared memory |
Explanation |
The available shared memory was not large enough to allocate the buffer pool with the configured size. |
Action |
Check whether the configured size of the buffer pool meets the memory resources available within the given environment. |
INODSW2297 | Perform emergency shutdown, because server is within a space wait situation |
Explanation |
The server is waiting for space on the log file, therefore a clean shutdown is not possible. It aborts the server with a pending autorepair. |
Action |
Clean up the log space location and restart the server. |
INODSF2306 | License timer interval too short |
Explanation |
The license timer detected an unexpected system data and time. |
Action |
Please contact your software supplier. |
INODSF2307 | Invalid combination of customer/partner information found in the license file |
Explanation |
An invalid combination of customer/partner information was found in the license file. |
Action |
Please contact your software supplier to extend your license. |
INODSW2318 | The license for name with ID id expires in number days |
Explanation |
The license expires soon. After license expiration the server cannot be used any longer. The server will abort and cannot be restarted. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2319 | The license for name sub-licensed by name with ID id expires in number days |
Explanation |
The license expires soon. After license expiration the server cannot be used any longer. The server will abort and cannot be restarted. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2320 | The license for name with ID text sub-licensed by name expires in number days |
Explanation |
The license expires soon. After license expiration the server cannot be used any longer. The server will abort and cannot be restarted. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2321 | The license for name with ID text sub-licensed by name with ID id expires in number days |
Explanation |
The license expires soon. After license expiration the server cannot be used any longer. The server will abort and cannot be restarted. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2322 | The license for name with ID id expires in 1 day |
Explanation |
The license expires soon. After license expiration the server cannot be used any longer. The server will abort and cannot be restarted. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2323 | The license for name sub-licensed by name with ID id expires in 1 day |
Explanation |
The license expires soon. After license expiration the server cannot be used any longer. The server will abort and cannot be restarted. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2324 | The license for name with ID text sub-licensed by name expires in 1 day |
Explanation |
The license expires soon. After license expiration the server cannot be used any longer. The server will abort and cannot be restarted. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2325 | The license for name with ID text sub-licensed by name with ID id expires in 1 day |
Explanation |
The license expires soon. After license expiration the server cannot be used any longer. The server will abort and cannot be restarted. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2326 | The license for name with ID id has expired, server will abort in number days |
Explanation |
The license has expired. The server will not restart any more. Final abort after a grace period of 10 days after license expiration. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2327 | The license for name sub-licensed by name with ID id has expired, server will abort in number days |
Explanation |
The license has expired. The server will not restart any more. Final abort after a grace period of 10 days after license expiration. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2328 | The license for name with ID text sub-licensed by name has expired, server will abort in number days |
Explanation |
The license has expired. The server will not restart any more. Final abort after a grace period of 10 days after license expiration. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2329 | The license for name with ID text sub-licensed by name with ID id has expired, server will abort in number days |
Explanation |
The license has expired. The server will not restart any more. Final abort after a grace period of 10 days after license expiration. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2330 | The license for name with ID id has expired, server will abort in 1 day |
Explanation |
The license has expired. The server will not restart any more. Final abort after a grace period of 10 days after license expiration. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2331 | The license for name sub-licensed by name with ID id has expired, server will abort in 1 day |
Explanation |
The license has expired. The server will not restart any more. Final abort after a grace period of 10 days after license expiration. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2332 | The license for name with ID text sub-licensed by name has expired, server will abort in 1 day |
Explanation |
The license has expired. The server will not restart any more. Final abort after a grace period of 10 days after license expiration. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW2333 | The license for name with ID text sub-licensed by name with ID id has expired, server will abort in 1 day |
Explanation |
The license has expired. The server will not restart any more. Final abort after a grace period of 10 days after license expiration. |
Action |
Please contact your software supplier to extend your license. Activate the new license with the Tamino Manager. |
INODSW5255 | Internal parameter error (value), using default |
Explanation |
An invalid internal parameter value was found. The default parameter value is used. |
Action |
Please contact your software supplier. |
INODSW5274 | number updates excluded on doctype doctype |
Explanation |
Due to an error during recovery, not all updates have been re-applied. |
Action |
Check the previous error messages to find more information about the error. |
INODSW5275 | Updates performed between server startup and recovery start |
Explanation |
Updates between server startup and recovery start are not allowed. |
Action |
Please check subsequent messages for more information. |
INODSW5294 | waiting for buffer flush end |
Explanation |
The dump utility must wait until the Tamino server completes the buffer flush action. |
Action |
No action required. |
INODSW5329 | Sort request couldn't be specified, reason error text |
Explanation |
A sort request failed, for the reason specified in the message |
Action |
Contact your software supplier. |
INODSW5340 | Collating key truncated to size bytes |
Explanation |
The collation key was truncated due to the size limit for index values. Only less important information was truncated. |
Action |
Normally, collation should be defined only for small pieces of data ( e.g. words), not for the large texts. Consider reviewing your collation definitions. |
INODSW5355 | File system UNMOUNT problem, reason reason errtxt |
Explanation |
Restoring an external backup may require the remounting of the file system. This is necessary to flush the file system cache. |
Action |
Remount the file system manually and contact your software supplier. |
INODSW5356 | File system MOUNT problem, reason reason errtxt |
Explanation |
Restoring an external backup may require the remounting of the file system. This is necessary to flush the file system cache |
Action |
Remount the file system manually and contact your software supplier. |
INODSW5400 | Internal sort order lost |
Explanation |
A sort request could not be satisfied due to internal reasons. |
Action |
You can force a memory dump with "inodba database=name trap=9299" for further analysis after reproducing the error. |
INODSW5401 | Function not completely executed |
Explanation |
A request failed due to internal reasons. |
Action |
You can force a memory dump with "inodba database=name trap=9298" for further analysis after reproducing the error. |
INODSE1204 | Administration function terminated with error errornumber: errorstring |
Explanation |
An administration function failed with given error string. |
Action |
Please restart the command using the option to write a job log and check if there is additional error information. If not, contact your software supplier. |
INODSE1205 | Replication permission denied for hostname |
Explanation |
The host name is not in the master's list of permitted databases for replication |
Action |
Add the host name of the replication instance to allow replication. |
INODSE1206 | Cannot connect to master dbname on hostname |
Explanation |
An attempt accessing the master database failed. |
Action |
Check that the master database is active on the specified node and retry the command. |
INODSI1207 | rplname inserted into permission list of dbname |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSI1208 | rplname removed from permission list of dbname |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSI1211 | dbname set as replication server of master on hostname using port number |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSI1218 | dbname set as replication server with simultaneous query, master is masterdb |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSI1219 | dbname set as replication server without simultaneous query, master is masterdb |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSI1220 | Replication server dbname reset to normal server |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSE1234 | Server parameter 'number of backup generations' larger than 1 required |
Explanation |
Supplying replication data requires log spaces to be kept for more than one backup. |
Action |
For a master server set the server property 'number of backup generations' to value larger than 1. |
INODSE1032 | Incremental backup cannot be used for database creation |
Explanation |
The backup file selected is an incremental one, but databases can only be created from full backups. |
Action |
Use a full backup for database creation. |
INODSE1042 | Incremental backup is not enabled |
Explanation |
Incremental backup cannot be issued because the feature is not enabled. |
Action |
Switch on the server parameter for enabling incremental backup. |
INODSE1043 | Incremental backup is not possible |
Explanation |
Incremental backup is not possible because there is no valid associated full or incremental backup present, or for some reason the server has deactivated the incremental block collection. |
Action |
Perform a full backup to resolve this situation. |
INODSE1045 | Incremental Backup is disabled at the database to be restored |
Explanation |
The database is not prepared to receive the given incremental backup. |
Action |
Check the database. Possibly you must restore a full backup first. |
INODSE1046 | Backup file has invalid or missing incremental backup data |
Explanation |
The backup file to be restored incrementally has no incremental backup data, or the backup data is corrupted. |
Action |
Please contact your software supplier. |
INODSE1048 | Backup numbers do not fit together: database dbnr, backup bcknr |
Explanation |
The incremental backup file and the database to receive the backup file no not fit together according the backup numbers. The backup number of the backup file must be one higher than the current backup number of the database |
Action |
Check all your backup files and their numbers. |
INODSE1058 | Incremental Backup does not fit to latest database restore (different database backup ID) |
Explanation |
The incremental backup to be restored into the database cannot be performed because there the associated full database restore was a different one. |
Action |
Check whether incremental backup file and its restored master full backup fit together. |
INODSE1066 | Associated full backup not found for incremental backup savepoint |
Explanation |
A full backup as a base of a selected incremental backup was not found. |
Action |
There is possibly a corruption of the internal configuration store. |
INODSE1090 | Inconsistency detected when checking backup for timestamp savepoint |
Explanation |
A series of incremental backups cannot be restored completely. |
Action |
Check if all incremental backups exist. If no backup is missing, please contact your software supplier. |
INODSE1091 | Incremental Backup does not fit to latest database restore (database modified meanwhile) |
Explanation |
The incremental backup to be restored into the database cannot be performed because there were some updates to the database in the meantime. |
Action |
Check if the database has been started between the restore of all involved backups and if there were any updates. |
INODSE1092 | Incremental Backup does not fit to latest database restore (different backup sequence) |
Explanation |
The incremental backup to be restored into the database cannot be performed because the latest incremental or full backup restored and the given incremental backup are not in the expected chain. |
Action |
Check if the incremental backup file and the most recently restored backup file really fit together. |
INODSE1093 | Options "parallel" and "incremental" are mutually exclusive |
Explanation |
An incremental parallel backup is not supported. |
Action |
Select only one of the options. |
INODSE1095 | Incremental backup from timestamp must not be deleted |
Explanation |
A single incremental backup must not be deleted. |
Action |
Select only full backups to be deleted. When deleting a full backup, associated incremental backups will be deleted as well. |
INODSE1097 | An incremental backup must not be used to create a database |
Explanation |
Only full backups are allowed to be used to create a database. |
Action |
Select a full backup to create a database. |
INODSE1098 | Inconsistent backup count count1 found, expected count is count2 |
Explanation |
The existing incremental backups do not represent a valid sequence. |
Action |
Check if all incremental backups exist. If no backup is missing, please contact your software supplier. |
INODSF1062 | Replacing the license file after expiration failed |
Explanation |
Replacing the license file after expiration failed. |
Action |
Provide a valid license to be able to start the server. |
INODSI1010 | Backup file from older version version |
Explanation |
Indicates that the input backup file is from a previous version. |
Action |
No action required. |
INODSI1019 | Database of older version version |
Explanation |
The database used for restore is from a previous version. |
Action |
No action required. |
INODSI1041 | Starting mode database backup |
Explanation |
Indicates the start of database backup processing. |
Action |
No action required. |
INODSI1044 | Starting restore database using type backup from timestamp |
Explanation |
Indicates the backup that was used to start restore processing. |
Action |
No action required. |
INODSI1049 | Starting mode restore of database |
Explanation |
Indicates that the restore processing has been started. |
Action |
No action required. |
INODSI1059 | The time-limited license for the server has expired, switched to an unlimited Community Edition license |
Explanation |
The time-limited license for the server has expired. The server automatically switched to an unlimited Community Edition license. Some product features may no longer be available. |
Action |
No action required. |
INODSI1110 | Waiting time for count users to start a new transaction - min: min seconds, max: max seconds, average: average seconds seconds |
Explanation |
This message is used to give information about waiting times for users who want to open a new transaction while other users have not yet finished their transaction. This synchronization of all users who do not have an open transaction is required at the end of a backup. |
Action |
No action required. |
INODSI1113 | No real modified data for Incremental Backup |
Explanation |
There is no modification in the database, so an incremental backup will save no new data. Nevertheless a backup with only global data will be created. |
Action |
No action required. |
INODSI1114 | Incremental backup from date deleted |
Explanation |
A full backup to be deleted causes the deletion of dependent incremental backups as well. |
Action |
No action required. |
INODSS1089 | Creating database with reorganization ... |
Explanation |
The database will be created from a backup with defragmentation of the database layout. |
Action |
No action required. |
INODSW1115 | Incremental backup disabled due to buffer pool allocation failure |
Explanation |
An incremental backup is not possible because no space was available for the information of modified blocks. |
Action |
Create the next backup as a full backup. To avoid the allocation failure increase the buffer pool. |
INODSW1116 | Incremental backup disabled due to error error |
Explanation |
An incremental backup is not possible due to an error when maintaining the information of modified blocks. |
Action |
Create the next backup as a full backup. If the error persists, contact your software supplier. |
INODSE1119 | Invalid date/time specified. Valid format is YYYY-MM-DD:hh:mm:ss |
Explanation |
The date and time specified is invalid. |
Action |
Specify a date and time using format YYYY-MM-DD:hh:mm:ss. |
INODSE1122 | Service name for server servername not found |
Explanation |
The service name for the server was not found in the configuration store. |
Action |
Please contact your software supplier. |
INODSE1123 | SCM open failed with error rsp |
Explanation |
Service Control Manager open failed. |
Action |
Please contact your software supplier. |
INODSE1127 | SCM service open failed with error rsp |
Explanation |
Service Control Manager open service failed. |
Action |
Please contact your software supplier. |
INODSE1134 | SCM service start failed with error rsp |
Explanation |
Service Control Manager start service failed. |
Action |
Please contact your software supplier. |
INODSE1135 | SCM query service status failed with error rsp |
Explanation |
Service Control Manager query service status failed. |
Action |
Please contact your software supplier. |
INODSI1146 | Archive Log Location has been reset |
Explanation |
An Archive Log Location will not be used. |
Action |
None. |
INODSI1147 | path set as location name |
Explanation |
A path or a set of paths has been set for the specified location type. |
Action |
None. |
INODSE1149 | Too many paths specified for a location |
Explanation |
Only 8 paths are allowed to be specified for a location. |
Action |
Use less paths for the location to be set up. |
INODSE1153 | filename is an invalid file name for a database space |
Explanation |
The specified file name for a database space is not valid. |
Action |
Specify a valid file name for a database space. |
INODSE1155 | filename is not a database space for server dbname |
Explanation |
The specified file name is not a database space for the given database name. |
Action |
Make sure that the file name of the database space is a database space of the specified database. |
INODSI1177 | Database database name Session session number (name modifierversion on system info, process ID pid) |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSI1178 | Database database name Replication Session (name modifierversion on system info, processID pid) |
Explanation |
The server started for a replication database. |
Action |
No action required. |
INODSI1179 | Database database name Read-Only Session (name modifierversion on system info, process ID pid) |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSF1180 | The operating system is not specified within the license file |
Explanation |
Check operating systems specification in the license file. |
Action |
Verify that the license file is valid for the operating system used. |
INODSI1183 | size MB empty data space found |
Explanation |
The amount of empty data space assigned to specific doctypes that can be returned to global free space |
Action |
None. |
INODSI1184 | No empty data space found |
Explanation |
Empty data space that can be returned to global free space does not exist |
Action |
None. |
INODSI1188 | Creating a temporary backup for free space defragmentation |
Explanation |
A temporary backup is created to be used for defragmenting free space |
Action |
Wait until the reorganization is completed. |
INODSE1189 | Reorganize database is not permitted while database is active |
Explanation |
To preserve data consistency, the database must not be active while reorganize function is processed. |
Action |
Shut down the database |
INODSI1190 | size MB empty data space converted to global free space |
Explanation |
The amount of empty data space that was de-allocated from specific doctypes and returned to global free space. |
Action |
None. |
INODSI1191 | Free data space in database is size MB (percent %) |
Explanation |
Information about the amount of global free data space after reorganization. |
Action |
None. |
INODSI1193 | Free space less than percent %, no free space defragmentation and data space shrinking |
Explanation |
The reorganize function converted empty space to global free space, but the amount of free space is less than a minimum value considered as worthwhile performing a free space defragmentation and data space shrinking. |
Action |
None, if you are satisfied with the minimum value for free space defragmentation and data space shrinking. In any other case, use the reorganize function with a differnet minimum value. |
INODSI1195 | Defragmenting free space |
Explanation |
A temporary backup is used for restore to defragment free space. |
Action |
Wait until the reorganization is completed. |
INODSI1196 | Shrinking data space |
Explanation |
The size of the data space is reduced by de-allocating free space. |
Action |
Wait until the reorganization is completed. |
INODSI1197 | No free data space found |
Explanation |
Free data space does not exist. |
Action |
None. |
INODST1781 | Start of product name on system info |
Explanation |
This is an informational message. |
Action |
No action required. |
INODSE1247 | Replication processing disabled because master database was restored without full recovery |
Explanation |
When the master database was restored not using 'recover all' option, synchronization is lost by updates already replicated but not recovered for the master database. |
Action |
Delete the replication database and set it up again using a backup created after the restore was done. |
INODSI1248 | No backup exists for dbname - create a backup as soon as possible |
Explanation |
After converting a replication database to a normal database a backup of the database is not available, thus a restore/recover is not possible until a backup exists. |
Action |
Create a backup of the database. |
INODSA1249 | Starting recovery until time |
Explanation |
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. |
Action |
Wait for the end of the recovery processing before using your database. |
INODSI1252 | Starting restore database using type backup from timestamp |
Explanation |
Indicates the backup that was used to start restore processing. |
Action |
No action required. |
INODSI1253 | Incremental backup from date deleted |
Explanation |
A full backup to be deleted causes the deletion of dependent incremental backups as well. |
Action |
No action required. |
INODSI1294 | Log space of server session session number from time opened |
Explanation |
The log space of the specified server session has been opened. |
Action |
No action required. |
INODSI1304 | Read-only database db_name , startup at startup |
Explanation |
This message shows the time at which the database was started in read-only mode. |
Action |
No action required. |
INODSI1314 | Database db_name, startup at startup |
Explanation |
This message shows the time at which the database was started. |
Action |
No action required. |
INODSI1315 | Log space of server session session number processed until time |
Explanation |
All information generated before the given end timestamp of the log space of the specified server session was processed. |
Action |
No action required. |
INODSI1316 | The backup tape from time has been unregistered |
Explanation |
The information about the availability of the given backup tape has been removed. |
Action |
The tape may be removed from the archive. |
INODSI1333 | Log space data processing end time stamp is time |
Explanation |
This is a progress message about the aborted recovery run or an abort of replication processing. |
Action |
In the case of a recovery run, the information can be used to start a recover until. |
INODSI1339 | Replication of server session session number suspended replication data processed until timestamp |
Explanation |
Replication processing is suspended due to a server shutdown request of the replication database. |
Action |
No action required. |
INODSI1352 | Replication of server session session number from timestamp started |
Explanation |
The replication processing has started to process the log space data of the specified server session of the master database. |
Action |
No action required. |
INODSI1361 | Replication of server session session number resumed using replication data from timestamp |
Explanation |
The server continued replication processing after replication database startup. |
Action |
No action required. |
INODSI1365 | Server session session number replicated until time stamp |
Explanation |
This is the current replication status of the database. |
Action |
No action required. |
INODSI1368 | Replication of server session session number resumed using replication data from timestamp. Simultaneous query permitted. |
Explanation |
The server continued replication processing after replication database startup. |
Action |
No action required. |
INODSI1370 | Replication of server session session number from timestamp started. Simultaneous query permitted. |
Explanation |
The replication processing has started to process the log space data of the specified server session of the master database. |
Action |
No action required. |
INODSI1389 | Backup from backup_date deleted |
Explanation |
After backup, the number of backup generations is updated, i.e older backups are removed. For further information, please refer to the documentation of the server parameter "number of backup generations". |
Action |
No action required. |
INODSI1393 | Backup created with backup key 'backupkey' (from) |
Explanation |
The identification of the last created backup is displayed. |
Action |
No action required. |
INODSI1394 | Backup key 'backupkey' (from) |
Explanation |
This is a display of backup information. |
Action |
No action required. |
INODSI1397 | Deleting disabled backup from backup_date |
Explanation |
A disabled backup file is being deleted. |
Action |
No action required. |
INODSI1399 | Dataset dsn created on date |
Explanation |
The dataset was created on the specified date. |
Action |
No action required. |
INODSI1400 | A transaction has been heuristically rolled back at time |
Explanation |
The database system has rolled back a transaction for which a decision of the transaction manager was pending. |
Action |
No action required. |
INODSW1401 | A transaction has been heuristically committed at time |
Explanation |
The database system has committed a transaction for which a decision of the transaction manager was pending. |
Action |
No action required. |
INODSW1406 | Log space of server session session number processed until time |
Explanation |
None of the information generated after the given end timestamp of the log space of the specified server session was processed. |
Action |
Verify that the skipped part of the log space is the same as was skipped with a previous recovery. |
INODSW1407 | Replication of server session session number resumed using replication data from timestamp. Simultaneous query will be enabled when replication database is up-to-date. |
Explanation |
The server continued replication processing after replication database startup. |
Action |
No action required. The database server will automatically enable simultaneous read when the locking information becomes available, at the latest when replicating the current master database session. |
INODSW1415 | Replication of server session session number from timestamp started. Simultaneous query will be enabled when replication database is up-to-date. |
Explanation |
The replication processing has started to process the log space data of the specified server session of the master database. |
Action |
No action required. The database server will automatically enable simultaneous read when the locking information becomes available, at the latest when replicating the current master database session. |
INODSW1418 | Replication of server session session number stopped. Replication data processed until timestamp. |
Explanation |
Replication processing is stopped due to an error as described in previous messages. If simultaneous queries were permitted, then the replication database stays online and may be used for further queries. |
Action |
Try to solve the problem at the master database's side or recreate the replication database from a new backup of the master. |
INODSI1422 | Using backup filename |
Explanation |
Indicates the backup which is used to create the new database. |
Action |
No action required. |
INODSE1419 | Incremental backup from timestamp must not be deleted |
Explanation |
A single incremental backup must not be deleted. |
Action |
Select only full backups to be deleted. When deleting a full backup, associated incremental backups will be deleted as well. |
INODSE1421 | Backup time has become invalid |
Explanation |
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. |
Action |
Use another backup for restore/recover. The selected backup can only be used to create new database. |
INODSI1423 | Using location location |
Explanation |
Indicates the location which is to be used for the database spaces. |
Action |
No action required. |
INODSI1426 | Meta data created for backup filename |
Explanation |
A registry entry was created to enable usage of an archived backup. |
Action |
None. |
INODSI1427 | Meta data created for number backup files |
Explanation |
Displays the number of registry entries created for archived backups. |
Action |
None. |
INODSI1428 | Meta data created for recovery file filename |
Explanation |
A registry entry was created to enable usage of an archived recovery input file. |
Action |
None. |
INODSI1429 | Meta data created for number recovery input files |
Explanation |
Displays the number of registry entries created for archived recovery input files. |
Action |
None. |
INODSI1430 | No recovery input files found for database key key on directory path |
Explanation |
On the specified directory no recovery input files have been found with the given database key. |
Action |
Check whether the path of the archive location and the database key was specified correctly. |
INODSE1434 | filename created before first backup (timestamp) |
Explanation |
The recovery input file found was created at an earlier point of time than the first registered backup. |
Action |
If the recovery input file is to be processed, search for the backup created before and create the meta data for this backup first. |
INODSI1435 | A pipe is only allowed as backup location |
Explanation |
Using a named pipe is not supported for other locations. |
Action |
Use a directory as location. |
INODSI1437 | A pipe is not allowed as default location |
Explanation |
A named pipe is not allowed to be set as default location or backup default location. |
Action |
Specify the named pipe as backup location after the database has been created. |
INOINE2051 | Resetting the unique status on all indices |
Explanation |
Duplicate values were detected. Therefore the unique status could not be set for the indices. |
Action |
Resolve any uniqueness conflicts before trying to set the unique status. |
INOINE2053 | Index name already in use |
Explanation |
The specified index name is already in use for this doctype. |
Action |
Retry the required operation with an unused index name. |
INOINF2251 | Sort file too small or work pool too large |
Explanation |
The sort file used is too small or the specified work pool is too large for the given sort file. |
Action |
Ensure that a sufficiently large sort file is available. |
INOINF2252 | Sort file too small |
Explanation |
The sort file used is too small. |
Action |
Ensure that a sufficiently large sort file is available. |
INOINF2253 | Corrupt index found |
Explanation |
Corrupt information has been found in the index. |
Action |
Please contact your software supplier, and/or reload the data to repair the damage. |
INOINI2174 | Index processing completed on doctype doctype |
Explanation |
The requested index operation has ended. |
Action |
No action required. |
INOINI2452 | Index modification started |
Explanation |
The database index modification process has started. |
Action |
No action required. |
INOINI2453 | Index modification completed |
Explanation |
The index modification process has completed. |
Action |
No action required. |
INOINI2454 | Index cannot be sorted in main memory |
Explanation |
The index process cannot perform the sort in main memory. This is an informational message. An external sort will be performed. |
Action |
No action required. |
INOINI2455 | Index cannot be sorted |
Explanation |
It is not possible to sort the index, probably due to a lack of space. |
Action |
Allow more space to be allocated for a main memory sort of the index, if possible. |
INOINI2456 | Index cannot be processed in two passes |
Explanation |
It is not possible to process the index in two passes due to insufficient temporary storage. |
Action |
Allocate more temporary storage to allow the index to be processed in two passes. |
INOINI2457 | Index cannot be processed in one pass |
Explanation |
It is not possible to process the index in one pass due to a lack of temporary storage. |
Action |
Allocate more temporary storage to allow the index to be processed in one pass. |
INOINI2459 | Index verification limit has been reached |
Explanation |
The number of errors found while verifying the index has reached the allowed limit. |
Action |
Correct the errors in the index, and run the certification process again. |
INOINI2460 | Data space passes required: count |
Explanation |
This is the number of passes of the data space required to perform the index operation. |
Action |
No action required. |
INOINI2461 | Sort file efficiency: value % |
Explanation |
This is the calculated efficiency of the sort file during the index process. |
Action |
No action required. |
INOINI2462 | Work pool efficiency: value % |
Explanation |
This is the calculated efficiency of the work pool during the index process. |
Action |
No action required. |
INOINI2467 | Recommended minimum temporary storage size = size KB |
Explanation |
This is the recommended (minimum) temporary storage size that will be allocated for the process. |
Action |
No action required. |
INOINI2471 | Temporary storage size = size KB |
Explanation |
This is the size of the required temporary storage. |
Action |
No action required. |
INOINI2472 | Temporary storage size (1 pass) = size MB |
Explanation |
This is the temporary storage size required for 1 pass processing. |
Action |
No action required. |
INOINI2473 | Temporary storage size (2 passes) = size MB |
Explanation |
This is the temporary storage size required for 2 pass processing. |
Action |
No action required. |
INOINI2474 | Sorting index |
Explanation |
The index field is being sorted. |
Action |
No action required. |
INOINI2475 | No values for index (name) |
Explanation |
No values are present for the index field. |
Action |
No action required. |
INOINI2476 | Loading index |
Explanation |
The index field specified is being loaded. |
Action |
No action required. |
INOINI2477 | Verifying index (name) |
Explanation |
The index field specified is being verified. |
Action |
No action required. |
INOINI2478 | Unique status for specified index is being set |
Explanation |
The unique status for the specified index field is being set. |
Action |
No action required. |
INOINI2479 | Unique status for specified index is being reset |
Explanation |
The unique status for the specified index field is being reset. |
Action |
No action required. |
INOINI2480 | Unique status removed for index |
Explanation |
The unique status of an index field has been removed. |
Action |
No action required. |
INOINI2481 | No index fields were found for the specified doctype |
Explanation |
The index function could not be performed because no index fields were found in the specified doctype. |
Action |
Check that the correct doctype was specified for the index operation. |
INOINI2482 | Index processing started on doctype doctype |
Explanation |
The requested index operation has started. |
Action |
No action required. |
INOINW2800 | Errors found for count indices |
Explanation |
A number of indices were found to be in error during the index process. |
Action |
Correct the errors and attempt to perform the index process again. |
INOINW2801 | Number of errors found in index: count |
Explanation |
This message shows the number of indices found to be in error during index processing. |
Action |
Correct the indices in error and perform the index operation again. |
INOINW2802 | Unique conflict detected |
Explanation |
Duplicate values were detected when trying to create a unique index. |
Action |
Remove any unique conflicts in the data. |
INOLDE3010 | Invalid combination of keywords |
Explanation |
The combination of keywords supplied is not allowed. |
Action |
Check the keyword combination and retry the operation. |
INOLDE3016 | FIELDS may be specified only once |
Explanation |
The parameter FIELDS may be specified only once. |
Action |
Continue with other parameter settings. |
INOLDE3051 | Invalid output status returned by user exit |
Explanation |
A user exit has returned an invalid output status to the load process. |
Action |
Ensure that the user exit always returns a valid output status. |
INOLDE3054 | Invalid range of sequence numbers |
Explanation |
The range of sequence numbers to be deleted is invalid. |
Action |
Please contact your software supplier. |
INOLDE3055 | Value must be less than or equal to value |
Explanation |
A value has exceeded the specified maximum. |
Action |
Decrease the value specified. |
INOLDE3056 | Invalid record length |
Explanation |
The input record length must be a multiple of four for binary data. |
Action |
Check the input file. |
INOLDE3057 | Sequence number to be deleted is not present |
Explanation |
The sequence number to be deleted is either not present or outside the specified doctype's limits. |
Action |
Ensure that the sequence numbers to be deleted were specified correctly. |
INOLDE3058 | Dataset dataset, record record, offset offset |
Explanation |
An error has occurred in the specified dataset at the position indicated. |
Action |
Correct the input and retry the operation. |
INOLDE3059 | Index index not defined for doctype doctype |
Explanation |
The specified index is defined in the load description file but is not present in the doctype to be updated. |
Action |
Ensure that the load description file contains the correct information and that the correct doctype is specified. |
INOLDE3060 | Read-only database, function not permitted to run |
Explanation |
The specified database is read-only and the requested function is not allowed for a read-only database. |
Action |
Ensure that the database being accessed is not read-only for this type of operation. |
INOLDF3018 | The requested doctype is locked, load aborted |
Explanation |
The doctype referenced is locked and the load is unable to proceed. |
Action |
Wait until the doctype is available. If the lock is due to a previous problem or corrupt doctype, a server restart may clear the lock and return the doctype to a usable state. |
INOLDF3251 | Load aborted in user exit at record number: record |
Explanation |
The load process has been aborted by a user exit while processing the specified record number. |
Action |
Check the user exit for the reason for aborting the load process. |
INOLDF3252 | Record too big for data storage device |
Explanation |
The record is too large for the data storage device used. |
Action |
Decrease the size of the input record, or use a data storage device with a larger block size. |
INOLDF3253 | Incomplete load definition file |
Explanation |
The input file containing the load definitions is incomplete. |
Action |
Check the load definition file and ensure that it contains the correct information. |
INOLDF3254 | Internal buffer overflow |
Explanation |
An unexpected overflow of an internal buffer has occurred. |
Action |
Please contact your software supplier. |
INOLDF3255 | Sort I/O error |
Explanation |
An I/O error has occurred on the sort data space. |
Action |
Check the sort data space for system errors. |
INOLDF3256 | Selection not yet implemented |
Explanation |
The selection of sequence numbers to be deleted is not yet implemented. |
Action |
No action possible. |
INOLDF3257 | Unexpected error while connecting |
Explanation |
An unexpected error has occurred while trying to connect to the server. |
Action |
Please contact your software supplier. |
INOLDF3260 | Error in user store function |
Explanation |
An error has occurred in a user-supplied store function. |
Action |
Check and correct any user-supplied store functions. |
INOLDF3261 | No free sequence numbers |
Explanation |
An internal shortage of sequence numbers has occurred. |
Action |
Please contact your software supplier. |
INOLDF3263 | No free sequence numbers |
Explanation |
There are no more free sequence numbers available. |
Action |
Please contact your software supplier. |
INOLDF3264 | Cannot allocate user-defined sequence number |
Explanation |
An error has occurred when trying to allocate a user-defined sequence number. |
Action |
Check that the user routine that allocates sequence numbers is correct. |
INOLDF3265 | No index read slots |
Explanation |
An internal error has occurred because there are no read slots available for the index. |
Action |
Please contact your software supplier. |
INOLDF3266 | Error while generating index |
Explanation |
An internal error has occurred while generating an index. |
Action |
Please contact your software supplier. |
INOLDF3267 | Temp stream overflow |
Explanation |
A stream overflow has occurred while processing the temporary data space. |
Action |
Please contact your software supplier. |
INOLDF3268 | Doctype locking failed |
Explanation |
It was not possible to lock a doctype for access. |
Action |
Ensure that nothing else is accessing the doctype to be locked. |
INOLDF3269 | Unexpected error while removing utility entry |
Explanation |
An unexpected internal error has occurred while removing a utility entry. |
Action |
Please contact your software supplier. |
INOLDF3270 | Unexpected error while opening sort space |
Explanation |
An unexpected internal error has occurred while opening the sort space. |
Action |
Ensure that there is enough sort space available. |
INOLDF3271 | Load description does not match |
Explanation |
The definitions in the load description file do not match those of the current doctype. |
Action |
Check that the specifications in the load description file are correct. |
INOLDI3002 | Preparing documents for load |
Explanation |
Preparing documents for load. |
Action |
No action required. |
INOLDI3019 | Loading documents in collection |
Explanation |
The collection is being modified. |
Action |
No action required. |
INOLDI3451 | Termination forced by user exit |
Explanation |
A user exit has forced the load process to terminate. |
Action |
If the termination was unexpected, check the user exit for the reason. |
INOLDI3452 | Number of records read: records |
Explanation |
This is the number of input records read during the load process. |
Action |
No action required. |
INOLDI3456 | Number of documents added to doctype doctype: number |
Explanation |
The load process has added the given number of documents to the specified doctype. |
Action |
No action required. |
INOLDI3457 | Number of documents deleted from doctype doctype: number |
Explanation |
The load process has deleted the given number of documents from the specified doctype. |
Action |
No action required. |
INOLDI3458 | Number of documents unloaded from doctype doctype: number |
Explanation |
The load process has unloaded the given number of documents from the specified doctype. |
Action |
No action required. |
INOLDI3459 | The specified number of records have been loaded |
Explanation |
The number of records to be loaded has been reached. |
Action |
No action required. |
INOLDI3460 | Preparing existing indices for merge |
Explanation |
Existing indices are being backed up before creating new ones. |
Action |
No action required. |
INOLDI3461 | No index modification |
Explanation |
No modifications have been made to any indices. |
Action |
No action required. |
INOLDI3464 | Data space is being modified |
Explanation |
The data space is being modified. |
Action |
No action required. |
INOLDI3465 | Data space prepared for delete |
Explanation |
The data space will be prepared for deleting records. |
Action |
No action required. |
INOLDI3467 | Number of referential integrity violations: number |
Explanation |
This message indicates the number of referential integrity violations encountered during the load process. |
Action |
No action required. |
INOLDI3468 | Erasure from referenced doctype is not supported |
Explanation |
It is not possible to erase from the referenced doctype. |
Action |
No action possible. |
INOLDI3474 | Sorting and loading indices |
Explanation |
The indices are being sorted and loaded. |
Action |
No action required. |
INORBE4002 | Function only permitted if restore database |
Explanation |
A function was chosen that is not permitted in the current context. |
Action |
Use the function while restoring the database. |
INORBE4005 | Backup not currently possible; parts of database are locked |
Explanation |
It is not currently possible to start a backup because parts of the database are locked by other users or operations. |
Action |
Retry the backup when there are no longer any users or operations locking any parts of the database. |
INORBE4006 | This function is not permitted on a system file while Tamino server is active |
Explanation |
To preserve data consistency, the Tamino server should not be active while restoring the database. |
Action |
Shut down the Tamino server. |
INORBE4007 | Restore database is not permitted while Tamino server is active |
Explanation |
To preserve data consistency, the Tamino server should not be active while restoring the database. |
Action |
Shut down the Tamino server. |
INORBE4053 | Terminator of backup copy not found |
Explanation |
The terminator of the backup copy could not be found. The error can occur if the backup was modified outside of Tamino. |
Action |
Make sure that the backup copy was not modified outside of Tamino. If the problem persists , contact your software supplier. |
INORBE4056 | Invalid database space size change |
Explanation |
The value for changing the database space size is invalid. |
Action |
Specify a valid value. |
INORBE4057 | No space for database block allocation at database space (number KB at block) |
Explanation |
The restore requires more space for the database, but it failed. There are two possible reasons: either the database cannot be extended because there is no more space on the disk, or there are internal structure problems. |
Action |
Make sure that there is enough space for the database to be enlarged. |
INORBE4060 | Input file is empty |
Explanation |
The input file specified for the operation is empty. |
Action |
Check that the correct input file has been specified. |
INORBE4061 | Invalid sequence of backup copy files |
Explanation |
The sequence of the specified backup copy files is incorrect. |
Action |
Check that the correct backup copy files have been specified. |
INORBE4064 | Synchronization with database server lost |
Explanation |
The synchronization with the database server has been lost. |
Action |
Retry the backup operation. If the problem persists, contact your software supplier. |
INORBE4065 | Invalid block type type |
Explanation |
I/O from an unexpected database space is going to be logged so command logging has been deactivated. |
Action |
This is an unexpected error. Please contact your software supplier. |
INORBE4067 | Unable to open journal space |
Explanation |
An error has occurred when trying to open the journal space. |
Action |
Check that the journal space exists and is correctly defined. |
INORBE4068 | Reference to missing doctype detected |
Explanation |
A doctype that does not exist has been referenced. |
Action |
This is an internal error. Please contact your software supplier. |
INORBF4013 | Server is in startup phase, backup not possible. |
Explanation |
The server is still in the startup phase and therefore a backup is not possible. This is probably caused by another (offline) backup running, or the server being started. |
Action |
Wait until the other backup has finished, or the server has started, and run the backup again. |
INORBF4251 | Invalid block allocation detected (blocks are shared between different doctypes) |
Explanation |
The database server is in an inconsistent state. |
Action |
This is an internal error. Please contact your software supplier. |
INORBF4253 | Error error number during backup: error message |
Explanation |
A fatal error occurred during backup. |
Action |
Try to solve the problem based on the text of the error message. Otherwise, contact your software supplier. |
INORBF4255 | An error occurred when updating the internal configuration store |
Explanation |
The operation has been terminated because an error occurred while trying to update the internal configuration store. |
Action |
Please contact your software supplier and provide the message text of all messages displayed. |
INORBF4257 | Corrupt structure on backup copy |
Explanation |
The backup copy does not contain the correct structure. |
Action |
Check your input file assignments, and ensure that the correct backup copy is being used. |
INORBF4259 | Error occurred in I/O block number |
Explanation |
An I/O error has occurred on the specified block. |
Action |
The backup copy is corrupt; back up the database again to create another backup copy. |
INORBF4260 | Online backup already active |
Explanation |
Another backup function is active. Only one online backup is possible at one time. |
Action |
No action required. |
INORBF4263 | Utility not permitted to run |
Explanation |
This utility is currently not permitted to run. |
Action |
Wait until the database is available. |
INORBF4265 | Internal error found in backup copy |
Explanation |
An internal structure error has occurred in the backup copy. The backup copy may be corrupt. A possible cause of the error is that the backup copy was modified outside of Tamino. |
Action |
Check that the backup copy was not modified outside of Tamino. If the problem persists, please contact your software supplier. |
INORBF4266 | Block size of output file too small |
Explanation |
The block size of the output file is too small. |
Action |
Use an output device with a larger block size. |
INORBF4267 | Invalid record detected, block number |
Explanation |
The backup copy file has a structure error with printed information. This backup copy file cannot be used as input for a restore. |
Action |
Run the backup function again. |
INORBF4268 | Internal configuration delete by Tamino utility failed |
Explanation |
The final stage of saveset processing failed; the internal configuration is incorrect. |
Action |
Retry the operation. |
INORBF4269 | Internal configuration update by Tamino utility failed because key could not be moved |
Explanation |
A utility attempted to create an internal configuration entry, but this call failed for the stated reason. The utility will now terminate, and the administration agent will carry out any necessary recovery tasks. |
Action |
No action required. Please contact your system administrator for further information. |
INORBF4270 | Internal configuration get by Tamino utility failed because value could not be read |
Explanation |
A utility attempted to read the values for an internal configuration entry, but this call failed for the stated reason. The utility will now terminate, and the administration agent will carry out any necessary recovery tasks. |
Action |
No action required. Please contact your system administrator for further information. |
INORBF4271 | Internal configuration set by Tamino utility failed because value could not be set |
Explanation |
A utility attempted to set the value for an internal configuration entry, but this call failed for the stated reason. The utility will now terminate, and the administration agent will carry out any necessary recovery tasks. |
Action |
No action required. Please contact your system administrator for further information. |
INORBF4272 | Internal configuration get by Tamino utility failed because values could not be enumerated |
Explanation |
A utility attempted to count the number of values for an internal configuration entry, but this call failed for the stated reason. The utility will now terminate, and the administration agent will carry out any necessary recovery tasks. |
Action |
No action required. Please contact your system administrator for further information. |
INORBF4273 | Internal configuration create by Tamino utility failed |
Explanation |
A utility attempted to create a new internal configuration, but this call failed. The utility will now terminate, and the administration agent will carry out any necessary recovery tasks. |
Action |
No action required. Please contact your system administrator for further information. |
INORBF4276 | This operation is not allowed while the Tamino server is active |
Explanation |
The operation cannot be executed when the database has been started. |
Action |
Stop the database and retry the operation. |
INORBI4063 | Access to the Tamino server's shared memory is not possible |
Explanation |
It is not possible to access shared memory of the Tamino server. Synchronization with the server is lost. A possible cause is that the Tamino server has been shut down in the meantime. |
Action |
Retry the backup operation. If the problem persists, please contact your software supplier. |
INORBI4452 | Waiting for autorestart |
Explanation |
The utility action cannot be performed until the database has completed an autorestart. |
Action |
No action required. |
INORBI4453 | Initialization phase |
Explanation |
This is an informational message indicating that a utility is initializing. |
Action |
No action required. |
INORBI4454 | Waiting for transactions to commit |
Explanation |
The requested operation is waiting for all transactions to commit. |
Action |
No action required. |
INORBI4455 | Backup copy successfully checked |
Explanation |
The backup copy has been successfully checked. |
Action |
No action required. |
INORBI4456 | No doctype in backup copy |
Explanation |
The backup copy used for this operation does not contain any doctypes. |
Action |
No action required. |
INORBI4457 | Restore of database completed successfully |
Explanation |
The database has been successfully restored. |
Action |
No action required. |
INORBI4459 | Within allocation |
Explanation |
This informational message occurs when a utility is allocating space. |
Action |
No action required. |
INORBI4464 | Formatting of database space completed |
Explanation |
This informational message indicates the completion time of the formatting operation. |
Action |
No action required. |
INORBI4465 | Formatting of database space started |
Explanation |
This informational message indicates that the formatting operation has started. |
Action |
No action required. |
INORBI4466 | Database identification set to 'database name' |
Explanation |
The database identification has been set to the specified name. |
Action |
No action required. |
INORBI4468 | Backup of database space completed |
Explanation |
The indicated database space has been backed up. |
Action |
No action required |
INORBI4469 | Terminator block: type |
Explanation |
This message shows the value of the terminator block. |
Action |
No action required. |
INORBI4475 | New block allocations for doctype doctype |
Explanation |
New blocks have been allocated for the specified doctype. |
Action |
No action required. |
INORBI4478 | Doctype doctype contained in saveset |
Explanation |
The doctype specified is contained in the backup saveset. |
Action |
No action required. |
INORBI4631 | Backup of database completed successfully |
Explanation |
A database copy has been backed up successfully. |
Action |
No action required. |
INORBQ4000 | Error accessing database space extent number at location restore location |
Explanation |
The database space was not found at the specified location. The are many possible causes for this. The container may be corrupt or missing, the defined 'Location' may be missing or corrupt or you may not have sufficient access privileges for the specified location. If you have replaced a location and/or container that was previously missing, this error appears because the database server did not expect the container to re-appear after it detected it was missing. |
Action |
Verify that the container exists in the correct location. If you have replaced a previously missing container, please move it out of the way to allow the database server to recreate the container and allow the restore process to continue. If the problem persists, please contact your software supplier. |
INORBQ4001 | Confirm location for recreation of database space extent number |
Explanation |
Confirm the location for recreation of the database space. |
Action |
Enter the location name. |
INORBR4681 | Backing up database space |
Explanation |
The specified server space is being backed up. |
Action |
No action required. |
INORBS4009 | Restoring database with reorganization ... |
Explanation |
The database is being restored and a data reorganization will be done.. |
Action |
No action required. |
INORBS4458 | Restoring database ... |
Explanation |
The database is being restored. |
Action |
No action required. |
INORBV4012 | Doctype loaded = number; actual number of doctypes = number |
Explanation |
The number of doctypes loaded differs from the number of doctypes in the backup copy. |
Action |
Please contact your software supplier with an exact description of the functions that caused the error. |
INORBW4010 | External backup/restore request failed, detailed info in file filename |
Explanation |
The specific external backup or restore action failed due to an internal reason. Please view the output file indicated by the error message for the problem. |
Action |
Analyze the problem in the error file. |
INORBW4015 | The space size will be increased by size MB |
Explanation |
The container size specified during create is not sufficient. Tamino is automatically extending the container to accommodate the data. |
Action |
No action required. |
INORBW4803 | Database identification could not be changed |
Explanation |
The database identification could not be changed. |
Action |
Ensure that the database identification of the new database is correct. |
INORBW4805 | Waiting for database restart |
Explanation |
The operation is waiting for the restart of the database (due to its abnormal termination). |
Action |
Start the database. |
INORBW4806 | Block block number ignored, run verify and repair function for doctype doctypes |
Explanation |
During backup a corrupt index block was found which will not be backed up to the backup copy. |
Action |
Recreate the index of specified doctype and rerun the backup function. |