INOAAE0001 | Function not selected : name |
Explanation |
The server extension function is not selected so that the parameter cannot be modified. |
Action |
Select the server extension function first. |
INOAAE0004 | Cannot modify journal space |
Explanation |
The journal space of the specified database cannot be modified. |
Action |
Check whether the data space is already in use. Check the database location for remaining disk space. |
INOAAE0018 | Port number 'port' for 'name' indication |
Explanation |
The port number cannot be used. |
Action |
Change the port parameter value. |
INOAAE0019 | fail - delete database dbname read only parameter is set |
Explanation |
The database parameter "read only" must be cleared before the database can deleted. |
Action |
Remove the read only flag in the database parameters. |
INOAAE0020 | Modify Email notification properties failed |
Explanation |
The modification of Email notification properties failed. |
Action |
Look at the detailed error message and action. |
INOAAE0022 | mvcount spaces successfully moved from oldloc to newloc, one or more spaces couldn't be moved because of errors/warnings |
Explanation |
The given number of spaces were moved successfully but one or more spaces could not be moved because an error or a warning occurred during the execution of the command. |
Action |
Find out why spaces were not moved and try to move them via the 'Move' command of the database spaces entry. |
INOAAE0024 | Change License file failed |
Explanation |
Change license file failed. |
Action |
Check the license file. |
INOAAE0026 | The parallel option is not supported for incremental backups |
Explanation |
Options "parallel" and "incremental" are mutually exclusive. |
Action |
Select only one of the options. |
INOAAE0032 | Cannot activate dynamic property 'name' |
Explanation |
The property cannot be updated in the current server session, but will be active after a restart of the database. |
Action |
Restart the database to activate the property. |
INOAAE0038 | Cannot open file path, file does not exist or is opened by another one or not enough access rights |
Explanation |
The file does not exist or is already open. |
Action |
Check the filename. |
INOAAE0039 | Unknown database space number |
Explanation |
The database space number is not valid for this database. |
Action |
Use a valid database space number. |
INOAAE0040 | This command is valid for journal space only |
Explanation |
The database space type is not valid for this command. |
Action |
Use the journal space. |
INOAAE0042 | CD database information file not found |
Explanation |
The error message information file for the CD database not found. |
Action |
Check the path and filename. |
INOAAE0043 | CD database information file doesn't contain all necessary data or was created on a different platform |
Explanation |
The content of the information file is not complete or the file is not the required information file is from a different operating system. |
Action |
Check the content of the information file. |
INOAAE0044 | CD database from different operating system cannot be registered |
Explanation |
Only CD databases from the same operating system can be registered. |
Action |
Use a CD database that was created on the same operating system. |
INOAAE0045 | Operation not allowed on CD database or read only database |
Explanation |
The operation is not allowed on a CD database or read only database. |
Action |
No action required. |
INOAAE0054 | The "Add database space" function has failed |
Explanation |
The attempt to add one or more of the database spaces failed. |
Action |
Check the database locations for remaining disk space. The server property "read only" may be set to "yes". |
INOAAE0055 | More than one replication database is not yet supported |
Explanation |
Only one replication database is allowed. |
Action |
No action required. |
INOAAE0056 | Re-invert of database dbName has failed |
Explanation |
The re-invert operation failed. Possible reasons are that the database is not active or, if active, one or more indices could not be repaired. |
Action |
Check your database status. |
INOAAE0058 | Invalid Access Control Element name |
Explanation |
Function names cannot be part of paths. |
Action |
Use either a function name or a path but not both. |
INOAAE0059 | Invalid master database name |
Explanation |
The master database name specified is invalid. |
Action |
Specify another database name for the master database. |
INOAAE0060 | Specification of key parameter is mandatory |
Explanation |
The parameter must be specified. |
Action |
Specify the parameter and try again. |
INOAAE0065 | Server extension 'name' not defined |
Explanation |
The specified server extension does not exist. |
Action |
No action required. |
INOAAE0066 | Internal configuration store key _default not found |
Explanation |
The default internal configuration store key could not be found. |
Action |
Please contact your software supplier. |
INOAAE0067 | File 'path' not found |
Explanation |
The specified file could not be found. |
Action |
Specify a valid filename. |
INOAAE0068 | Different server extension names: name1 is different from name2 |
Explanation |
The server extension names differ. |
Action |
No action required. |
INOAAE0069 | File 'path' not extracted |
Explanation |
The server extension installation file was not extracted. |
Action |
No action required. |
INOAAE0070 | File 'path' already installed |
Explanation |
The server extension installation file was previously installed. |
Action |
No action required. |
INOAAE0072 | Document 'path' not installed |
Explanation |
The server extension installation document was not installed. |
Action |
The action depends on previous error messages. Please check the previous messages for more information. |
INOAAE0073 | File 'path' not created |
Explanation |
The server extension installation file was not created. |
Action |
Correct the access rights for the directory and retry the operation. |
INOAAE0074 | Server extension name 'name' not defined |
Explanation |
The name of the server extension is not defined. |
Action |
Specify the name of the server extension and retry the operation. |
INOAAE0075 | Server extension name 'name' already defined |
Explanation |
The name of the server extension already exists. |
Action |
Change the name of the server extension and retry the operation. |
INOAAE0076 | Directory 'path' already exists |
Explanation |
The server extension installation directory already exists. |
Action |
Remove the directory and retry the operation. |
INOAAE0077 | Document 'path' already installed |
Explanation |
The server extension installation document is already installed. |
Action |
Remove the server extension installation document. |
INOAAE0078 | Execution failed: command |
Explanation |
The specified operating system command failed. |
Action |
The action depends on previous error messages. Please check the previous messages for more information. |
INOAAE0079 | Database name not defined |
Explanation |
The required database name was not specified. |
Action |
Please contact your software supplier. |
INOAAE0080 | No functions defined: name |
Explanation |
There are no functions defined in the server extension. |
Action |
Add functions to the server extension and retry the installation. |
INOAAE0081 | The Tamino server returned an invalid server extension response document |
Explanation |
The server extension response document does not correspond to the agreed protocol with the Tamino server. |
Action |
Please contact your software supplier. |
INOAAE0082 | Server extension 'name' does not exist |
Explanation |
The specified server extension does not exist. |
Action |
Correct the name of the server extension and retry the operation. |
INOAAE0083 | File 'path' already open |
Explanation |
The server extension installation package is already open. |
Action |
Wait until the package is not being used and retry the operation. |
INOAAE0084 | File 'path' not open |
Explanation |
The server extension installation package is not open. |
Action |
Wait until the package is not being used and retry the operation. |
INOAAE0085 | File 'path' not previously closed |
Explanation |
The server extension installation package is not closed. |
Action |
Wait until the package is not being used and retry the operation. |
INOAAE0086 | Operation 'type' not implemented |
Explanation |
The requested operation is not implemented. |
Action |
No action required. |
INOAAE0087 | Command 'type' not allowed |
Explanation |
This command is not allowed for the requested server extension. |
Action |
Ensure that you use one of the commands allowed for the server extension. |
INOAAE0088 | message |
Explanation |
This is a generic container for Tamino error messages. |
Action |
See the content of the message during online Tamino operation for further information. |
INOAAE0089 | Not an installation package: path |
Explanation |
The provided file is not a server extension installation package. |
Action |
Use a valid installation package. |
INOAAE0092 | Error during write to inodmn, write interrupted or socket closed by inodmn |
Explanation |
This is an internal error. It could be caused by not fully compatible versions of Tamino and System Management Hub. |
Action |
Please contact your software supplier. |
INOAAE0093 | Error during read from inodmn, read interrupted or socket closed by inodmn |
Explanation |
This is an internal error. It could be caused by not fully compatible versions of Tamino and System Management Hub. |
Action |
Please contact your software supplier. |
INOAAE0094 | Command is an illegal number |
Explanation |
This is an internal error in the event logging protocol. |
Action |
Please contact your software supplier. |
INOAAE0095 | This command requires a different database state |
Explanation |
An attempt was made to execute a command that either requires an active database, but the database is inactive, or the command can be executed only in inactive mode, but the database is active. |
Action |
Start or stop the database to bring it into the appropriate mode (active or inactive) and retry the command. |
INOAAE0096 | The command requested cannot be executed because it is already running |
Explanation |
The command you wish to execute is already being executed by someone else, but the command cannot be executed in parallel. |
Action |
Wait until the running command has completed. The argevsrv process keeps track of running commands. If the command is blocked although it is obviously not running, try restarting the argevsrv process. |
INOAAE0097 | Insufficient resources to complete the command |
Explanation |
This is an internal error in the event logging protocol. Some resource (usually disk or main storage) is exhausted and the function failed to complete. |
Action |
Check if there is enough free disk space. Delete temporary and otherwise expandable files, then try again. |
INOAAE0098 | Path 'path/name' not created |
Explanation |
The specified path name is too long. |
Action |
Choose another file structure with shorter path names. |
INOAAE0099 | Path 'path' not converted |
Explanation |
The specified path name was not converted to a URL or vice versa. Either the path name or the URL is too long. |
Action |
Choose another file structure with shorter path names. |
INOAAE0110 | Internal error with database startup by changing replication database to a normal database |
Explanation |
An internal error occurred when starting the database. |
Action |
Please contact your software supplier. |
INOAAE0111 | No valid destination directory for backup files given. |
Explanation |
No valid destination directory was given. |
Action |
Specify at least one valid directory with write access for Tamino and enough space for the backups. |
INOAAE0113 | Path 'path' not extracted |
Explanation |
The specified path was not extracted from the internal configuration store. This is an internal error. |
Action |
Please contact your software supplier. |
INOAAE0114 | Execution mode 'name' not extracted |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOAAE0115 | Execution mode not compatible: mode1 != mode2 |
Explanation |
The specified execution modes are not compatible. |
Action |
Select a compatible execution mode. |
INOAAE0116 | GUID not extracted |
Explanation |
The GUID was not extracted from the internal configuration store. This is an internal error. |
Action |
Please contact your software supplier. |
INOAAE0117 | DLL 'path' is not registered |
Explanation |
The specified DLL cannot be used. |
Action |
Specify another DLL. |
INOAAE0118 | DLL 'path' not unregistered |
Explanation |
The specified DLL cannot be used. |
Action |
Specify another DLL. |
INOAAE0119 | Remove of all server extensions failed |
Explanation |
The server extensions could not be removed. |
Action |
Check the extensions. |
INOAAE0120 | XML port not defined for database 'name' |
Explanation |
The XML port value is missing in the internal configuration store. |
Action |
Please contact your software supplier. |
INOAAE0121 | Not enough memory |
Explanation |
There is not enough memory for an http request. |
Action |
Close some of your applications. |
INOAAE0122 | XML template processing failed, template template missing or incorrect |
Explanation |
This is an internal error of the Tamino Manager browser interface. |
Action |
Check if the quoted template file exists and if it is intact. If not, either reinstall or contact your software supplier. |
INOAAE0123 | No package name defined: name |
Explanation |
For a server extension the Java package name is required. |
Action |
If you generated the Java package yourself, use a unique name for your Java package. If it is a third-party product, get a new package from your software vendor. |
INOAAE0124 | Unknown database dbname : rename failed or no information from Software AG XTS Directory Server |
Explanation |
The database to be renamed could not be found. |
Action |
Check if the specified database exists and if the Software AG XTS Directory Server is running. |
INOAAE0125 | Directory 'path' not deleted |
Explanation |
The directory is in use. Therefore it cannot be deleted. |
Action |
Wait until the directory is no longer in use and try again. |
INOAAE0126 | No valid location type found |
Explanation |
The location type parameter is missing. |
Action |
Specify the location type parameter. |
INOAAE0127 | Location type 'type' is unknown |
Explanation |
An unknown location type is specified. |
Action |
Specify a valid location type. |
INOAAE0128 | File 'path' not copied |
Explanation |
The specified file was not copied to the target file. |
Action |
Check your permissions or check your disk space. |
INOAAE0129 | Please specify at least the location path |
Explanation |
The path parameter is missing. |
Action |
Specify the path parameter. |
INOAAE0130 | Path path exceeds the maximum path length of maxpathlen characters |
Explanation |
The length of the specified path exceeds the allowed maximum length of a directory path. |
Action |
Specify a shorter directory path. |
INOAAE0131 | Location path path includes no valid directory |
Explanation |
The root of the specified directory path is invalid. A possible cause is that the specified directory path could be on a removable drive or RAM disk. |
Action |
Specify a valid directory path. |
INOAAE0132 | Location path path is located on a remote drive. Please choose a local drive. |
Explanation |
A remote drive is not allowed for a location path. |
Action |
Specify the location path on a local drive. |
INOAAE0133 | Name name exceeds the maximum name length of maxnamelen characters |
Explanation |
The length of the specified name exceeds the allowed maximum length. |
Action |
Specify a shorter name. |
INOAAE0134 | Name name already exists as database location name |
Explanation |
The specified location name is the name of an existing database location. |
Action |
Change the location name. |
INOAAE0135 | Path path already exists as database location path |
Explanation |
The specified location path is the path of an existing database location. |
Action |
Change the location path specification. |
INOAAE0136 | Database location name not found |
Explanation |
The specified location name was not found in the internal configuration store. |
Action |
Specify an existing location name. |
INOAAE0137 | Location name is the current default location |
Explanation |
Deleting the current default location is not allowed. |
Action |
Change the default location. |
INOAAE0138 | Location name is the current default backup location |
Explanation |
Deleting the current default backup location is not allowed. |
Action |
Change the default backup location. |
INOAAE0140 | Database dbname uses database location name with location path path as 'category'. If you still want to delete the location, all spaces from that location must be moved to another location before you can delete it. |
Explanation |
The specified location is defined as a category location for a database, so deleting is not allowed. Move the database spaces on that location to another one. |
Action |
Change the default database location category specification. |
INOAAE0141 | No response document received |
Explanation |
There was no response document received from the server. |
Action |
Check if the network communication is established. |
INOAAE0142 | Value for property 'name' too small - minimum is minval |
Explanation |
The value for the given property is smaller than the minimum allowed. |
Action |
Specify a larger value. |
INOAAE0143 | Value for property 'name' too large - maximum is maxval |
Explanation |
The value is larger than the maximum allowed. |
Action |
Specify a smaller value. |
INOAAE0144 | Invalid numeric value for property 'name' |
Explanation |
The property is a numeric property and the value has the wrong type. |
Action |
Change the property value to numeric. |
INOAAE0145 | Property 'name' must be 'yes' or 'no' |
Explanation |
The property is a boolean property and the value has the wrong type. |
Action |
Change the property value to 'yes' or 'no'. |
INOAAE0146 | The sequence of backup spaces is not complete. |
Explanation |
One or more streams or extents are missing in the selected backup spaces. Only complete backups can be restored. Spaces missing at the end of the sequence will be only detected at runtime when data is loaded into the new database. |
Action |
Check the stream or extent numbers of the selected backup spaces and add missing spaces. Check if the sequence of backup spaces (Extent 1, Extent 2, ..) is correct. |
INOAAE0149 | Web server wsname already assigned |
Explanation |
The web server is already assigned to the specified database. |
Action |
Check the specified web servers and the web server assignments. |
INOAAE0153 | Web server wsname not assigned |
Explanation |
The specified web server is not assigned to the specified database, therefore the assignment cannot be deleted. |
Action |
Check the web server assignments to the specified database. |
INOAAE0154 | Error retrieving collection/doctype information: the requested document(s) could not be locked |
Explanation |
The document is already locked or cannot be locked. A possible reason can also be an unclosed session. |
Action |
Wait for a short time and try this command again. |
INOAAE0155 | Unknown location location name |
Explanation |
The given location does not exist. |
Action |
Choose a valid location. |
INOAAE0157 | Parameter parameter name missing |
Explanation |
The parameter with the given name is not specified. |
Action |
Specify the required parameter. |
INOAAE0158 | parameter name: invalid path, directory does not exist or is not writable |
Explanation |
The given path does not exist or is not writeable. |
Action |
Use a path that exists and is writable. |
INOAAE0159 | Database dbname already exists |
Explanation |
The "rename database" command failed because the database name already exists. |
Action |
Use a different name or remove the database. |
INOAAE0162 | Cannot delete database space spaceNo |
Explanation |
The specified database space cannot be deleted from the location. |
Action |
Check whether the database space is already in use. |
INOAAE0165 | Cannot expand database space spaceNo |
Explanation |
The specified database space cannot be expanded. |
Action |
Check whether the database space is already in use. Check the database location for remaining disk space. If the database is read-only it cannot be expanded. |
INOAAE0169 | Database database name exists |
Explanation |
A database with the same name exists either on the local computer, or in the scope of XTS Directory Service (which may know databases on multiple computers). |
Action |
Choose a different name. On Windows platforms, it is not sufficient to have two names differ only in upper/lowercase. |
INOAAE0170 | Configuration 'configuration' already exists for external backup method 'method' |
Explanation |
The configuration name already exists for this external backup method. |
Action |
Specify a new configuration name which does not exist already. |
INOAAE0174 | Could not initialize TCP stack |
Explanation |
This is an internal error in the event logging protocol. The communication between a logging client and the logging server could not be established. Basic functions and commands may be unaffected by this failure but messages will not be stored permanently or displayed in the Tamino Manager browser interface. |
Action |
This failure is most likely due to extreme shortage of resources, or missing operating system components. Check the disk space. Check the integrity of the installation. Contact you software supplier to check if there is a software update. |
INOAAE0175 | Error in inodmn conversation: unexpected response buffer |
Explanation |
This is an internal error of the event logging protocol. |
Action |
Please contact your software supplier. |
INOAAE0177 | Error in inodmn conversation: invalid number |
Explanation |
This is an internal error in the event logging protocol. |
Action |
Please contact your software supplier. |
INOAAE0178 | Function not implemented |
Explanation |
This is an internal error of the event logging protocol, a feature is not implemented in the version installed. Basic functions and commands are probably not affected. |
Action |
No action necessary. Please contact your software supplier for a possible software update. |
INOAAE0179 | Error in inodmn conversation: request failed |
Explanation |
This is an internal error in the event logging protocol. It could be caused by not fully compatible Tamino and System Management Hub versions. |
Action |
Please contact your software supplier for a possible software update. |
INOAAE0180 | Too many parameters |
Explanation |
A parameter has been specified repeatedly, but is only allowed once. |
Action |
Change the command and retry. |
INOAAE0181 | Database does not exist |
Explanation |
There is no database with the given name. |
Action |
Choose a valid database name. |
INOAAE0182 | Space space is not a valid backup space |
Explanation |
The file or tape specified has not been recognized as a valid Tamino backup. The file or tape could be damaged or access to the medium could be denied. |
Action |
Use a valid backup space. |
INOAAE0183 | Backup spaces have not been specified in the sequence determined by their extent or stream numbers |
Explanation |
The spaces are not ordered by their extent or stream number. The first space does not have the extent number 1. |
Action |
Specify backup spaces in the order of the extent or stream number. |
INOAAE0184 | Creation of directory path failed |
Explanation |
The directory at the given path could not be created. |
Action |
Check the permissions for the given path. |
INOAAE0186 | Unknown command |
Explanation |
The command is unknown in this context. |
Action |
Specify a valid command for this context. |
INOAAE0187 | Missing parameter |
Explanation |
A parameter specification is missing. |
Action |
Specify the needed parameter. |
INOAAE0188 | Not allowed to set a location of type 'type' as default location |
Explanation |
The location represents a type which is not allowed to be set as the default location. |
Action |
Set another location as the default location. |
INOAAE0189 | No valid location category specified |
Explanation |
The specified category is not a valid location category. |
Action |
Specify a valid location category. |
INOAAE0190 | Memory fault |
Explanation |
An error has occurred while allocating memory storage. |
Action |
Reboot the system. |
INOAAE0191 | database space spaceNo at location oldLoc not found |
Explanation |
A database space cannot be moved from one location to another, because the space does not exist at the source location. |
Action |
Search for the space at another location. |
INOAAE0192 | database space spaceNo at location newLoc already exists |
Explanation |
The database space cannot be moved to the new location. The space already exists. |
Action |
Delete the space from the new location. |
INOAAE0193 | Cannot remove database space spaceNo from location oldLoc |
Explanation |
A database space cannot be removed from the source location. |
Action |
Check the permissions for the database space. The database space could be in use by a running database. Do a shutdown of the database and try again. |
INOAAE0194 | Cannot write internal configuration store |
Explanation |
The write operation into the internal configuration store failed. |
Action |
Check the permissions. |
INOAAE0195 | Unknown database dbname or no information from Software AG XTS Directory Server |
Explanation |
The database is unknown or there is no information from the Software AG XTS Directory Server. |
Action |
Check the database name, and check if the Software AG XTS Directory Server is running. |
INOAAE0196 | Database dbname ID or port not found |
Explanation |
The database ID or port was not found in the internal configuration store. |
Action |
Please contact your software supplier. |
INOAAE0197 | Database dbname already active |
Explanation |
The database is already active. |
Action |
Stop the database and re-execute the operation. |
INOAAE0198 | Database dbname not active |
Explanation |
The database is not active. |
Action |
Start the database and re-execute the operation. |
INOAAE0203 | Function 'name' not found |
Explanation |
The function was deleted, but the display has not been refreshed. |
Action |
Refresh your display. |
INOAAE0204 | Invalid function type 'type' |
Explanation |
The type of a server extension function was invalid. This is an internal error. |
Action |
Please contact your software supplier. |
INOAAE0205 | File 'path' not added |
Explanation |
The file was not added to the server extension package. This is an internal error. |
Action |
Please contact your software supplier. |
INOAAE0208 | Not allowed to specify a recoverydate with recoveryoption=no |
Explanation |
If a recoverydate is specified, recoveryoption=no is not allowed. |
Action |
Specify recoveryoption=yes or do not use the recoveryoption parameter. |
INOAAE0209 | Access Violation - You are not allowed to access the requested database |
Explanation |
You are not authorized to access the database. |
Action |
Get authorization from the database administrator. |
INOAAE0210 | Min Port must be lower than Max Port and Port Ranges cannot overlap |
Explanation |
An invalid port range was specified. Min Port must be lower than Max Port and Port Ranges cannot overlap. |
Action |
Change the ports and retry the operation. |
INOAAE0212 | Error reading database locations |
Explanation |
An error occurred while reading database locations from the internal configuration store. |
Action |
Please contact your software supplier. |
INOAAE0215 | Unknown category |
Explanation |
The agent was called with an invalid category. |
Action |
Use a valid category for this agent. |
INOAAE0216 | Missing database name |
Explanation |
The database name is missing in the object ID. |
Action |
Use a valid object ID. |
INOAAE0217 | Missing Object ID |
Explanation |
The object ID is missing in the agent call parameter. |
Action |
Use a valid object ID. |
INOAAE0218 | Missing database space type |
Explanation |
The database space type is missing in the agent call parameter. |
Action |
Use a valid database space type. |
INOAAE0219 | Unknown database space category |
Explanation |
The database space category in the agent call parameter is unknown. |
Action |
Use a valid database space category . |
INOAAE0220 | The database dbname does not exist |
Explanation |
One of the following errors may have occurred: - XTS not configured in the "hosts" file - the XTS service not running - the database is not specified in the XTS configuration file xtsurl.cfg. |
Action |
Choose another database name, check XTS configuration. |
INOAAE0222 | The database dbname must be offline |
Explanation |
The database must be stopped for this operation. |
Action |
Shut down the database. |
INOAAE0225 | Leave command request on Event Service failed |
Explanation |
This request is part of the command synchronization scheme. This scheme synchronizes the execution of commands that might interfere otherwise and it prevents parallel execution of commands that should be executed only once per database at a time (like a backup). |
Action |
Check if the Event Service is running. If it is running, stop and re-start the service to initialize command synchronization |
INOAAE0226 | Database status request on event demon failed |
Explanation |
The status of a database could not be received from the event demon. |
Action |
Check if the event demon is running. |
INOAAE0229 | Tape path does not exist |
Explanation |
The tape with the specified path does not exist. |
Action |
Specify an existing tape path. |
INOAAE0230 | Device path does not exist |
Explanation |
The device with the specified path does not exist. |
Action |
Specify an existing device path. |
INOAAE0231 | Could not create location name at path |
Explanation |
Creating the location failed because of an internal configuration store error. |
Action |
Check access rights (privileges) of the connected user; the user must be a power user (administrator). |
INOAAE0232 | Could not delete location name |
Explanation |
Deleting the location failed because of an internal configuration store error. |
Action |
Please contact your software supplier. |
INOAAE0233 | Could not rename location name to newname |
Explanation |
Renaming the location failed because of an internal configuration store error. |
Action |
Please contact your software supplier. |
INOAAE0234 | Could not set location name as default database location |
Explanation |
Setting the location as the default location failed because of an internal configuration store error. |
Action |
Please contact your software supplier. |
INOAAE0235 | Could not set location name as default backup database location |
Explanation |
Setting the location as the default backup location failed because of an internal configuration store error. |
Action |
Please contact your software supplier. |
INOAAE0236 | Could not modify default of database location category 'category' |
Explanation |
Modifying the default database location category failed because of an internal configuration store error. |
Action |
Please contact your software supplier. |
INOAAE0238 | Archive path is empty |
Explanation |
The archive is empty or corrupt. Try with a correct archive. |
Action |
Correct the archive you want to work with. |
INOAAE0242 | No database name specified |
Explanation |
The database name must be specified. |
Action |
Specify the database name. |
INOAAE0243 | database registration failed |
Explanation |
The registration of a read only database failed. |
Action |
Check the source file/path and database name. |
INOAAE0268 | Move command for location type 'type' not supported |
Explanation |
The move command is not supported for some location types, especially tape. |
Action |
Specify a valid location type as the target of the move command. |
INOAAE0272 | Backup date 'bckDate' specifies no valid backup set for database dbName |
Explanation |
The given date was not found as a savepoint entry in the internal configuration store. |
Action |
Specify a valid date which corresponds to a valid savepoint entry in the internal configuration store. |
INOAAE0274 | No collection name specified |
Explanation |
The collection name must be specified for this operation. |
Action |
Specify the collection name. |
INOAAE0284 | Unregister is not allowed for normal databases; use "delete" command |
Explanation |
Use the "delete" command to remove a normal database. |
Action |
Use the batch command "delete" instead of "unregister". |
INOAAE0285 | Delete is not allowed for CD databases; use "unregister" command |
Explanation |
Use the "unregister" command to remove a CD database. |
Action |
Use the batch command "unregister" instead of "delete". |
INOAAE0287 | External function name exceeds 80 characters |
Explanation |
The length of the external function name may not exceed 80 characters. |
Action |
Specify a shorter function name. |
INOAAE0294 | No file restored : name |
Explanation |
No file was restored. Maybe there are no server extensions installed. |
Action |
If there are server extensions installed check your database. |
INOAAE0295 | Directory not created : path |
Explanation |
The specified directory was not created. |
Action |
Check the permissions of your file system. |
INOAAE0296 | Directory not found : path |
Explanation |
The specified directory was not found. |
Action |
Check the permissions of your file system. |
INOAAE0297 | Database not running : name |
Explanation |
The specified database is not running. |
Action |
Start the database. |
INOAAE0298 | Server returned error code : type |
Explanation |
The Tamino server returned an error code. |
Action |
Please contact your software supplier. |
INOAAE0304 | Fail - command log switch to mode buffers buffers |
Explanation |
This is a result message for a batch command. |
Action |
Check the database. |
INOAAE0305 | Parameter not defined : name |
Explanation |
No value given for a mandatory parameter. |
Action |
Retry the command with the specified parameter value. |
INOAAE0306 | Invalid object identification : name |
Explanation |
The given object identification is invalid. |
Action |
Retry the command with a correct object identification. |
INOAAE0307 | Update of settings failed : name |
Explanation |
The update of the given settings parameter failed. |
Action |
Check the job log for further information. |
INOAAE0310 | Path exists; please remove it or use another one |
Explanation |
This is an error message for creating a CD database in batch mode. A specified pathname exists already, so a different pathname must be supplied or the existing path must be removed. |
Action |
Remove the path or use another one. |
INOAAE0311 | Invalid character used in the specified location name at position position |
Explanation |
An invalid character has been specified in the location name. This can be a non-ASCII character or one of the special characters " %&,;!\=#[]\"\<>`'". |
Action |
Change the character. |
INOAAE0312 | Invalid character used in the specified path at position position |
Explanation |
An invalid character has been specified in the given path. This can be a non-ASCII character or one of the special characters "\/:*?\"<>|&`" for Windows or ":*? \"<>|;,&!\`'" for all other operating systems. |
Action |
Change the character. |
INOAAE0313 | Mapped documents exist : name |
Explanation |
Mapped XML documents exist for the server extension. |
Action |
Delete the XML documents before uninstalling the server extension. |
INOAAE0314 | Command not allowed if no function is selected |
Explanation |
The server extension must contain at least one selected function. |
Action |
Select some functions from the object being packed. |
INOAAE0315 | Database name contains invalid character "&" (ampersand) |
Explanation |
A database name can't contain the "&" character. |
Action |
Remove the "&" from the database name. |
INOAAE0347 | Database could not be connected |
Explanation |
The security manager could not connect to Tamino. |
Action |
Check if the database has been started. |
INOAAE0355 | The first and last character of a name should not be a blank |
Explanation |
Blanks are not allowed at the beginning and end of a name. |
Action |
Change the first/last character. |
INOAAE0356 | ACL name contains invalid character: |
Explanation |
Special characters are not allowed. |
Action |
Remove special characters from ACL name. |
INOAAE0359 | Group name contains invalid allowed character: |
Explanation |
Special characters are not allowed. |
Action |
Remove special characters from the group name. |
INOAAE0361 | User ID contains invalid character: |
Explanation |
Special characters are not allowed. |
Action |
Remove special characters from the user ID. |
INOAAE0362 | User created with escaped XML special characters in description |
Explanation |
XML special characters are not allowed. |
Action |
Remove special characters from the description. |
INOAAE0363 | Special characters are not allowed in an ACE name: |
Explanation |
Special characters are not allowed in an ACE name. |
Action |
Remove special character from ACE name. |
INOAAE0370 | TSM@DLL PARSE_ERR |
Explanation |
The retrieved XML-document is invalid or the XML parser could not retrieve data. |
Action |
Shut down the database and restart it. |
INOAAE0372 | TSM@DLL UNKNOWN ACL OR ACL NOT RETRIEVABLE |
Explanation |
The mentioned ACL is no longer available. Maybe another concurrent session deleted it. |
Action |
Refresh the data within the Tamino Manager and try again. |
INOAAE0373 | TSM@DLL UNKNOWN GROUP |
Explanation |
The mentioned GROUP is no longer available. Maybe another concurrent session deleted it. |
Action |
Refresh the data within the Tamino Manager and try again |
INOAAE0377 | Access control element 'name' already exists in access control list |
Explanation |
The access control element already exists in an access control list. |
Action |
Change the name of the access control element. |
INOAAE0378 | Version with compatibility level level of Tamino not found |
Explanation |
For reading the backup, a Tamino version of the same compatibility level is required. |
Action |
Install a Tamino version of the required compatibility level. |
INOAAE0381 | No container size information in backup file filename found |
Explanation |
The backup file does not contain important information for restoring. |
Action |
Check the backup file or generate a new one. |
INOAAE0382 | Not enough free memory |
Explanation |
Not enough free memory. |
Action |
try closing other applications to free memory. |
INOAAE0386 | Access Control List 'name' already exists |
Explanation |
An access control list with the specified name already exists. |
Action |
Change the name of the access control list. |
INOAAE0387 | User 'name' already exists |
Explanation |
The given user already exists in the ino:user doctype. |
Action |
Supply a new user ID. |
INOAAE0388 | User 'name' does not exist |
Explanation |
The user ID has not been found in the ino:user doctype. |
Action |
Create the required user ID. |
INOAAE0389 | Access control list 'name' does not exist |
Explanation |
The access control list has not been found in the ino:acl doctype. |
Action |
Create the required access control list. |
INOAAE0390 | User group 'name' does not exist |
Explanation |
A user group with the given name has not been found in the ino:group doctype. |
Action |
Create the required group. |
INOAAE0391 | Acename has not been defined |
Explanation |
The command line parameter "acename" has not been provided. |
Action |
Provide the "acename" parameter. |
INOAAE0392 | Permission has not been defined |
Explanation |
The command line parameter "permission" has not been provided. |
Action |
Provide the parameter "permission". |
INOAAE0393 | Aclname has not been defined |
Explanation |
The command line parameter "aclname" has not been provided. |
Action |
Provide the parameter "aclname". |
INOAAE0394 | Database is readonly |
Explanation |
The database is readonly, updates are not possible. |
Action |
No action required. |
INOAAE0395 | UserID has not been defined |
Explanation |
The command line parameter "userid" has not been provided. |
Action |
Provide the parameter "userid". |
INOAAE0396 | Groupname has not been defined |
Explanation |
The command line parameter "groupname" has not been provided. |
Action |
Provide the parameter "groupname". |
INOAAE0397 | Ace permission is not defined |
Explanation |
The permission for the access control element is not defined. |
Action |
Provide the permission for the access control element. |
INOAAE0398 | Permission has to be set to an allowed value |
Explanation |
Permission has not been set to an allowed value. |
Action |
Set permission to an allowed value. |
INOAAE0399 | Description has not been defined |
Explanation |
Description has not been provided. |
Action |
Provide description. |
INOAAE0400 | User group 'name' already exists |
Explanation |
The usr group already exists in the ino:group doctype. |
Action |
Change the group name to one that does not already exist. |
INOAAE0401 | Missing compatibility level : type |
Explanation |
The source or target compatibility level was not specified. |
Action |
Specify the compatibility level and execute the command again. |
INOAAE0402 | Set database version failed |
Explanation |
The "set database" action failed. Read the error messages to get more information. |
Action |
Check the error messages that are generated before this message at runtime to get the reason. |
INOAAE0408 | Some databases may be still active at system shutdown |
Explanation |
An error occurred while all active databases were stopped. |
Action |
Shut down manually all active databases prior to the system shutdown; get assistance from your software supplier to fix the problems that were reported. |
INOAAE0412 | This request is in conflict with another request that is currently being executed |
Explanation |
Some commands that access the same resources are mutually exclusive. This message can also appear if a process has been killed with operating system means or has crashed while the crash held the critical section locked. |
Action |
Retry later. If no other command is active and no one else is currently executing administrative commands, shut down and restart the System Management Hub Event Layer Service. |
INOAAE0413 | The request cannot be executed because a condition is missing |
Explanation |
The request requires another command to be active. |
Action |
No action possible. Please contact your software supplier. |
INOAAE0414 | Restore of database dbName failed |
Explanation |
An error occurred while restoring the specified database. |
Action |
Try to detect the error, otherwise contact your software supplier. |
INOAAE0417 | Web server 'wsname' does not exist |
Explanation |
The IP address and/or port of web server cannot be changed; the specified web server does not exist. |
Action |
Use an existing web server. |
INOAAE0418 | IP address of web server 'wsname' is invalid |
Explanation |
The IP address of the web server is invalid. |
Action |
Specify the IP address in a valid format. |
INOAAE0419 | File 'path' already exists |
Explanation |
The server extension installation file already exists. |
Action |
Select another path name. |
INOAAE0423 | Unable to execute command with version 'argbatchversion' for database from version 'version'. Please use 'version=version' parameter for argbatch command, or change your environment : 'argbatch set environment version=version'. |
Explanation |
A Tamino agent was called from the wrong version. |
Action |
Use the "version" parameter for the argbatch command or change your environment with: "argbatch set environment version=...". |
INOAAE0428 | Web server 'wsname' not defined |
Explanation |
The specified web server is not defined in the web server management. |
Action |
Add the specified web server in the web server management. |
INOAAE0439 | Tamino plug-in for argevsrv not installed or not properly initialized |
Explanation |
The Tamino plug-in was not installed, or the System Management Hub Event Service was unable to load it. Tamino will work without it but some administrative commands will not be be synchronized. This will cause problems only in rare conditions when multiple databases are created at the same time on the same computer. |
Action |
Avoid creating multiple databases at the same time on the same computer; please contact your software supplier to find out why the Tamino plug-in was not loaded by the System Management Hub Event Service. |
INOAAE0441 | version of database not found |
Explanation |
The database was found but not the version of Tamino that it requires. |
Action |
Check if the correct Tamino version for database is installed or set the version to one installed on the machine. |
INOAAE0442 | Tamino version not found |
Explanation |
The specified Tamino version was not found. |
Action |
Check if the Tamino version is installed on the machine. |
INOAAE0443 | highest Tamino version not found |
Explanation |
The highest Tamino version was not found. |
Action |
Check if Tamino is installed on the machine |
INOAAE0444 | Max and/or Min port not found or RGS error |
Explanation |
The Max and/or Min port was not found, or there was an RGS error. |
Action |
Please contact your software supplier. |
INOAAE0456 | The "Move database space" function failed |
Explanation |
An attempt to move a database space failed. Additional information is supplied in error messages that have occurred earlier. |
Action |
Please follow the actions of the error messages displayed earlier in the same job log. |
INOAAE0459 | The "Create Database" function failed |
Explanation |
An attempt to create a database failed. Additional information is supplied in error messages that have occurred earlier. |
Action |
Please follow the actions of the error messages displayed earlier in the same job log. |
INOAAE0462 | The "Delete Database" function failed |
Explanation |
An attempt to delete a database failed. Additional information is supplied in error messages that have occurred earlier. |
Action |
No action required. Please follow the actions of the error messages displayed earlier in the same job log. |
INOAAE0463 | The database information is available in ONLINE mode only |
Explanation |
The information can only determined when the database is started. |
Action |
Start the database and call the information function again. |
INOAAE0472 | Backup of database dbName failed |
Explanation |
Errors occurred while backing up the specified database. A possible reason could be low system memory. |
Action |
Try to detect the error, otherwise contact your software supplier. |
INOAAE0474 | Start of database dbName failed |
Explanation |
Errors occurred while starting the database. |
Action |
Try to detect the error, otherwise contact your software supplier. |
INOAAE0475 | Stop of database dbName failed |
Explanation |
Errors occurred while stopping the specified database. |
Action |
If you cannot identify the error from a previous error message, please contact your software supplier. |
INOAAE0480 | Add database space spaceNo to location newLoc failed |
Explanation |
An attempt to add database spaces to the specified location failed. |
Action |
No action required. |
INOAAE0481 | Not enough space on location newLoc |
Explanation |
The new location to which the database space should be moved is not big enough. |
Action |
Choose a larger location for moving the database space. |
INOAAE0491 | Error(s) occurred during modify of database properties |
Explanation |
An error occurred while attempting to modify database properties. Only the properties with an error message or a warning were not modified. All other properties are changed. |
Action |
Please contact your software supplier. |
INOAAE0509 | External function name already used : name |
Explanation |
The external name of a server extension function is already in use. |
Action |
Change the external function name and retry the operation. |
INOAAE0510 | Java classpath not modified : text |
Explanation |
The Java classpath was not modified according to the modification rules. |
Action |
Correct the modification parameters and retry the operation. |
INOAAE0534 | File 'path' not deleted |
Explanation |
The server extension DLL file could not be deleted. |
Action |
Delete the DLL manually. |
INOAAE0547 | Directory path does not exist |
Explanation |
The directory with the specified path does not exist. |
Action |
Specify an existing path. |
INOAAE0548 | No location name specified |
Explanation |
No location name was specified. |
Action |
Specify a location name. |
INOAAE0549 | Character '' not allowed as part of location name |
Explanation |
The character '\' is not allowed as part of the location name, because this name is used as internal configuration store key, and the '\' is the internal configuration store key delimiter. |
Action |
Replace this character by another one. |
INOAAE0567 | There is currently only one location defined. Please create at least one more file system location using the Location Management 'Add' command. |
Explanation |
No second location is defined that can be used as destination location for the move command . |
Action |
Create a second location and then start this command again. |
INOAAE0605 | Wrong date or date format. Format 'datepattern' required. |
Explanation |
An invalid date is specified or an invalid date format is used. |
Action |
Specify a valid date (use same format as used in 'argbatch show backups'). |
INOAAE0608 | No other Tamino version installed, set version not possible |
Explanation |
Because there is no other Tamino version installed, it makes no sense to change the version. |
Action |
No action required. |
INOAAE0611 | Named pipe path does not exist |
Explanation |
The named pipe with the specified path does not exist. |
Action |
Specify an existing named pipe path. |
INOAAE0619 | Device path is not a named pipe |
Explanation |
The specified path is not a named pipe. |
Action |
Specify an existing named pipe path. |
INOAAE0637 | Directory name 'path' not compatible with object identification 'name' |
Explanation |
The directory name must consist of the first part of the object identification. |
Action |
Create a new server extension package with the correct directory name. |
INOAAE0638 | Server extension function 'name' does not exist |
Explanation |
The specified server extension function does not exist. |
Action |
Correct the function name. |
INOAAE0639 | Server extension function parameter 'name' does not exist |
Explanation |
The specified server extension function parameter does not exist. |
Action |
Correct the parameter name. |
INOAAE0641 | Internal error from DSIF interface name returncode returncode error number errornr |
Explanation |
This is an internal error message. |
Action |
Please contact your software supplier. |
INOAAE0645 | Stop of XML session 'session' failed |
Explanation |
Errors occurred while stopping the specified XML session. |
Action |
Try to detect the error, otherwise contact your software supplier. |
INOAAE0646 | Error reading backup methods for database dbname |
Explanation |
No backup methods were found in the internal configuration store for the database. |
Action |
Please contact your software supplier. |
INOAAE0648 | Error reading parameters of backup method 'method' |
Explanation |
No parameters were found for the backup method in the internal configuration store. |
Action |
Please contact your software supplier. |
INOAAE0651 | Could not set global parameters for external backup method 'method' of database dbname |
Explanation |
Setting of global parameters failed because of an internal configuration store error. |
Action |
Please contact your software supplier. |
INOAAE0653 | Could not set configuration parameters for external backup method 'method' of database dbname |
Explanation |
Setting of configuration parameters failed because of an internal configuration store error. |
Action |
Please contact your software supplier. |
INOAAE0656 | Could not delete configuration 'configuration' of method 'method' of database dbname |
Explanation |
The deletion of the configuration failed. |
Action |
Please contact your software supplier. |
INOAAE0658 | Error reading configurations for database dbname of backup method 'method' |
Explanation |
An error occurred while reading the configuration data. |
Action |
Please contact your software supplier. |
INOAAE0659 | No configuration found for database dbname of backup method 'method' |
Explanation |
No configuration data was specified for this method and database. |
Action |
Specify configuration data for this method and database using the 'External Backup Environment' dialog. |
INOAAE0660 | Replication database name expected |
Explanation |
The replication database name must be specified for this function. |
Action |
Specify the replication database name |
INOAAE0662 | The database replication_db cannot be added into the permission list |
Explanation |
An error occurred while adding the replication database name to the permission list. |
Action |
Check the subsequent error messages for more details. |
INOAAE0665 | Database database cannot be set as replication database |
Explanation |
An error occurred during the type change. The database cannot be set to a replication database. Possible reason: This database is a master database. |
Action |
Check for related additional messages. |
INOAAE0667 | Replication database database cannot be reset to normal type |
Explanation |
The database cannot be reset to a normal database. |
Action |
See the subsequent error messages. |
INOAAE0668 | Database master_database is not active or is not a master database |
Explanation |
The master database must be in the active state or permit this database to be replicated. |
Action |
Start up the master database and check the permission list for replication databases. |
INOAAE0669 | Replication of master database master_database is not permitted |
Explanation |
Permission to replicate the master database was denied. |
Action |
Ask the administrator to permit replication access to the master database. |
INOAAE0672 | Not enough space at location newLoc for additional newsize MB - maximum free is freesize MB |
Explanation |
The new location to which the database space should be moved or added is not big enough. |
Action |
Choose a larger location for the database space operation. |
INOAAE0680 | Backup(s) not found wrongbackups please use one of the following backups |
Explanation |
Wrong backups were specified. |
Action |
Use only valid backups of the database. You can see all backups with the command "argbatch show backups database=mydatabase". |
INOAAE0681 | At least one backup must be given or don't use keepbackups |
Explanation |
For the option keepbackups, at least one backup must be given/selected. |
Action |
Give/select at least one backup. |
INOAAE0683 | Switching log space for database dbName has failed |
Explanation |
Errors occurred while switching log space for the database. |
Action |
Try to detect the error, otherwise contact your software supplier. |
INOAAE0684 | At least one destination directory must be given with parameter "destinationdirectory_0" |
Explanation |
the option "keep backup files" needs at least one destination directory. |
Action |
Specify a destination directory with the parameter "destinationdirectory_0". |
INOAAE0685 | For option "keepbackups=selected" at least one backup date and at least one destination directory must be given with parameter "destinationdirectory_0", "backupdate_0" |
Explanation |
Give at least one backup date and one destination directory in the parameter list. |
Action |
Use the parameter "backupdate_0" to specify a backup to be kept and "destinationdirectory_0" for the destination directory. |
INOAAE0691 | Could not add backup method 'method' for database dbname |
Explanation |
Adding the backup method failed because of an internal configuration store error. |
Action |
Please contact your software supplier. |
INOAAE0694 | Could not delete method 'method' of database dbname |
Explanation |
Deleting the backup method failed because of an internal configuration store error. |
Action |
Please contact your software supplier. |
INOAAE0696 | Internal error errno during modify property 'name' to 'value' |
Explanation |
An error occurred while setting a new property value. |
Action |
Please contact your software supplier. |
INOAAE0699 | Deletion of backup 'bckDate' of database dbName failed |
Explanation |
An error occurred while deleting the specified backup. |
Action |
Check the additional messages. |
INOAAE0707 | 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. |
INOAAE0708 | Update server sessions exist |
Explanation |
The database has already update sessions so that it cannot be used to replicate another database. |
Action |
Use a newly created database and retry this operation. |
INOAAE0709 | Passwords not matched |
Explanation |
The passwords entered do not match. |
Action |
Please ensure the passwords match. |
INOAAE0725 | Error while changing port ranges |
Explanation |
An error occurred while changing the port ranges. |
Action |
Please contact you software supplier. |
INOAAE0727 | path is not a raw section |
Explanation |
The specified path must be a raw section. |
Action |
Ensure that the path specifies a raw section. |
INOAAE0728 | Unable to load data for CD databases |
Explanation |
This database is a CD database. Data load not possible. |
Action |
No action required. |
INOAAE0731 | Rename web server failed |
Explanation |
The web server could not be renamed, the operation failed. |
Action |
The reason why the web server could not be renamed is in the job log. Check it and retry. |
INOAAE0733 | Add web server failed |
Explanation |
The web server could not be added, the operation failed. |
Action |
The reason why the web server could not be added is in the job log. Check it and retry. |
INOAAE0737 | Delete web server failed |
Explanation |
The web server could not be deleted, the operation failed. |
Action |
The reason why the web server could not be deleted is in the job log. Check it and retry. |
INOAAE0740 | Modify web server failed |
Explanation |
The web server could not be modified, the operation failed. |
Action |
The reason why the web server could not be modified is in the job log. Check it and retry. |
INOAAE0741 | Domain 'name' does not exist |
Explanation |
Domain has not been defined. |
Action |
Please check the defined domains list in Tamino and create the domain if necessary. |
INOAAE0744 | parameter name: must not be a location on a raw section, is only allowed on DATA, INDEX, JOURNAL and RESERVED location |
Explanation |
A location on raw section is only allowed as DATA, INDEX, JOURNAL and RESERVED location. |
Action |
Use a location that is not located on a raw section. |
INOAAE0745 | All reserved locations are located on raw section(s), at least one location must not be located on a raw section |
Explanation |
At least one reserved location for a database must not be on a raw section. |
Action |
Use at lease one location not located on a raw section. |
INOAAE0746 | Location locname is of type type, this type is not allowed for loctype |
Explanation |
Some location types are only allowed for special locations. For example locations on a tape are only allowed for backup locations. |
Action |
Use a location which is allowed for the current location type. |
INOAAE0747 | Not allowed to set a location of type 'type' as default backup location |
Explanation |
The default backup location cannot be in a location of type "raw". |
Action |
Use a location of a type that is allowed for a backup location. |
INOAAE0749 | This command is deprecated. Please use the new command "show acls". |
Explanation |
The command has been replaced by a new command. |
Action |
Please use the new command. |
INOAAE0750 | This command is deprecated. Please use the new command "show groups". |
Explanation |
The command is deprecated. |
Action |
Please use the new command. |
INOAAE0753 | Query internal configuration store key key failed |
Explanation |
An error occurred when querying the given internal configuration store key. |
Action |
Please contact your software supplier. |
INOAAE0754 | This command is deprecated. Please use the new command "show users". |
Explanation |
The command is deprecated. |
Action |
Please use the new command. |
INOAAE0755 | Access to internal configuration store value value key key failed |
Explanation |
An error occurred when getting the given internal configuration store key value. |
Action |
Please contact your software supplier. |
INOAAE0761 | parameter name: must be the logical name of an existing location |
Explanation |
The parameter must specify the short, "logical" name of a location (not its entire path), and the location must exist. |
Action |
Display the the "Locations" tree node in the System Management Hub (under the "Tamino" node) to display a list of existing locations or to add a new location. |
INOAAE0762 | parameter name: must contain only digits 0 to 9 |
Explanation |
The value for this parameter must be an integer number with no fractional parts. |
Action |
Re-enter the parameter using only digits 0-9. |
INOAAE0763 | parameter name: must be "yes" or "no" |
Explanation |
This parameter must have either the value "yes" or "no", all lowercase characters. |
Action |
Re-enter either "yes" or "no" (without the double quotes). |
INOAAE0764 | parameter name: must only contain digits 0-9, comma, dot, "E" or "e" for exponentiation |
Explanation |
The value for this parameter must be a valid floating point number, or a number with an exponent. |
Action |
Re-enter he parameter value as floating point number, or with an exponent. Depending on the locale settings on the local computer, the decimal sign may be expected either as "," or as a ".". |
INOAAE0766 | Size for space type extent extend is missing and no default size available |
Explanation |
No default size could be obtained for this space type. |
Action |
A size must be specified, and it must be above the minimum value for this space type. |
INOAAE0767 | The size specified for space type extent extend is under the minimum (minimum size Mb) |
Explanation |
The given size for the extent is too small. |
Action |
A size of at least the given minimum must be specified. |
INOAAE0768 | At least one backup location must be in the filesystem if no tape is supplied as initial backup |
Explanation |
If no tape is supplied to create the database from (in the "Create From Backup" command) the initial backup is created at creation time as a file and requires a location that is in the file system. Before this message was issued, attempts were made to create it in one of the provided backup locations, in the default backup location and in the default location. |
Action |
Create a location in the file system using the "Add" command the System Management Hub browser interface, tree node Tamino/DB Locations and make it the default location (by clicking the new location and executing the "Set Default" command). |
INOAAE0769 | At least one backup location is required for the initial backup of the new database |
Explanation |
Specify one or more location where backups shall be created later on. This location is already required and used during the creation of the new database. |
Action |
Specify one or more writable, random accessible backup locations for the database to be created |
INOAAE0774 | Database version with compatibility level of CD database not installed or found |
Explanation |
A Tamino of the same compatibility level of CD database must be installed to use the CD database |
Action |
Install a database of the same compatibility level. |
INOAAE0775 | Database name contains invalid character "*" (asterisk) |
Explanation |
A database name cannot contain the "*" character. |
Action |
Remove the "*" from the database name. |
INOAAE0776 | This command is deprecated. Please use the new command "show users". |
Explanation |
This command is not supported as the user descriptions can be seen in the results of the new command. |
Action |
Please do not use this command and use the new one instead. |
INOAAE0778 | Database name contains invalid character "/" (slash) |
Explanation |
A database name cannot contain "/" character. |
Action |
Remove the "/" from database name. |
INOAAE0779 | Port address 'buf' is invalid. Valid range is 0 - 65535. |
Explanation |
The specified port address is not valid. |
Action |
Specify a valid port address in the range 0 to 65535. |
INOAAE0784 | Database name contains invalid character "<" (less than) |
Explanation |
A database name cannot contain the "<" character. |
Action |
Remove the "<" from database name. |
INOAAE0785 | Database name contains invalid character ">" (greater than) |
Explanation |
A database name cannot contain the ">" character. |
Action |
Remove the ">" from database name |
INOAAE0786 | This command is deprecated. Please use the new command "show acesofacl". |
Explanation |
The command is deprecated. |
Action |
Please use the new command. |
INOAAE0787 | Domain parameters missing |
Explanation |
Some or all of the necessary parameters for the domain creation/modification are missing. |
Action |
Please ensure that all necessary domain parameters are defined. |
INOAAE0788 | Unrecognized domain parameters |
Explanation |
The domain parameters defined are not valid for the domain type being created/modified. |
Action |
Please ensure that the correct domain parameters for the domain type being created/modified are defined. |
INOAAE0792 | Namespace declarations required. Please check that all namespaces are defined. |
Explanation |
There are some namespace prefixes for which no namespace declarations have been defined. |
Action |
Please ensure namespace declarations exist for all namespace prefixes. |
INOAAE0794 | Internal error occurred |
Explanation |
Internal error code 41 occurred. |
Action |
Please contact your software supplier. |
INOAAE0797 | Domain 'name' already exists |
Explanation |
A domain with the same name exists. |
Action |
Please choose another name. |
INOAAE0798 | Failed to open input file filename for data load |
Explanation |
The file cannot be opened or does not exist. |
Action |
Check the input and start the operation again. |
INOAAE0799 | Parameter 'newname' or 'new_name' missing. The 'new_name' parameter is deprecated, please use the 'newname' parameter for the new name of the database. |
Explanation |
No parameter with the new name of the database was given. |
Action |
Provide the database name using the parameter 'newname'. |
INOAAE0802 | Could not connect to inodmn. Port number not found in internal configuration store, probably not installed. |
Explanation |
The Software AG EventLayer Service is not installed correctly. |
Action |
Try re-installing the System Management Hub. Check for a fix or an update from your software supplier. |
INOAAE0803 | Could not connect to inodmn, service not running |
Explanation |
The "Software AG EventLayer Service" is not running, database functions and commands are probably unaffected. |
Action |
Restart the service. If the problem persists, contact your software supplier for an update or fix. |
INOAAE0807 | Invalid parameter name 'name' specified. |
Explanation |
The parameter name specified is not valid since it contains one or more space characters. |
Action |
Specify a parameter name that does not contain space characters. |
INOAAE0812 | Web server IP address 'ipAddress' is invalid |
Explanation |
The specified web server IP address is invalid. |
Action |
Specify a valid IP address. The valid range is 0 - 255. |
INOAAE0817 | No license for raw section support |
Explanation |
The use of raw sections requires an appropriate license option. |
Action |
Contact your software supplier for a license option to support raw sections. |
INOAAE0818 | No raw section support for the used platform |
Explanation |
There is no raw section support for the used platform. |
Action |
Do not use raw sections. |
INOAAE0819 | Raw section support internal error |
Explanation |
There was an internal error while processing a raw section. |
Action |
Please contact your software supplier. |
INOAAE0820 | Raw section initialization failed |
Explanation |
An error occurred while initializing a raw section. |
Action |
Check the raw section. |
INOAAE0825 | 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. |
INOAAE0826 | 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. |
INOAAE0831 | Only one location specified for parallel backup |
Explanation |
More than one location is required for parallel backup. |
Action |
Please specify more than one location for the parallel backup. |
INOAAE0832 | Renaming a replication database master is not allowed. |
Explanation |
Renaming a replication database master is not allowed, because the link between the master and replication databases would be lost. |
Action |
No action required. |
INOAAE0834 | Database is a replication database master database. Deleting the replication database master is not allowed. No replication databases can be updated from this master database if this database is deleted. |
Explanation |
Deleting this master database would mean that no replication databases could be updated from this master database. If you really want to delete this replication master database use the "force=yes" parameter for argbatch or check the "Force Delete of Replication Master Database" checkbox in the GUI. |
Action |
Use the "force=yes" parameter for argbatch or check the "Force Delete of Replication Master Database" checkbox in the GUI. |
INOAAE0835 | Data load for database dbName failed |
Explanation |
Load of data failed with error. |
Action |
Check the other related messages for more information. |
INOAAE0836 | Unload data from database dbName failed |
Explanation |
An error occurred while data was being unloaded from the database. |
Action |
Check for other messages related to this error for possible reasons. |
INOAAE0837 | Location path path is read only |
Explanation |
The location path specified is read only. |
Action |
Specify a location path with write access. |
INOAAE0838 | Server extension does not contain a function |
Explanation |
It was detected that no function has been defined for the server extension. Such a server extension is considered as invalid. |
Action |
Extend your server extension by at least one function. |
INOAAE0841 | Uninstall of server extension name aborted |
Explanation |
The uninstall operation for the server extension has not been completed due to functions that are used in some schema. |
Action |
Restart the uninstall operation with the parameter "force" set to "yes" (batch command). |
INOAAE0842 | Uninstall of server extension 'name' failed |
Explanation |
The uninstall operation failed. |
Action |
Check the job log to find the reason for the failure. |
INOAAE0843 | Please specify either parameter IP address or node |
Explanation |
The specification of the IP address or node is invalid. |
Action |
Please specify either the IP address or the node. |
INOAAE0844 | Unable to find the replication database name from the permission list |
Explanation |
The replication database name is not in the permission list. |
Action |
Check the parameter. |
INOAAE0845 | Please specify either parameter IP address or node |
Explanation |
Either the parameter IP address or node must be specified. |
Action |
Please specify either the parameter IP address or node. |
INOAAE0846 | Upgrade from this database to Vversion not possible |
Explanation |
This error occurs because the database cannot be upgraded directly to the target version. |
Action |
Upgrade to the next higher version and after that try a "set version" to the target version. |
INOAAE0847 | Named pipe path not allowed for the specified location type |
Explanation |
A named pipe is not allowed to set for the specified target location. Only the backup location type accepts named pipes. |
Action |
Specify another location for the target location. |
INOAAE0849 | Cannot open event log session |
Explanation |
Open event log session on argevsrv failed. |
Action |
Check that argevsrv is running. |
INOAAE0850 | parameter name: must be of type FileSystem or RAW Section |
Explanation |
Data, Index and Journal location must be of type FileSystem or RAW Section. |
Action |
Use a location of type FileSystem or RAW Section. |
INOAAE0852 | This command is deprecated. Please use the new command "inoload". |
Explanation |
This command is set to deprecated, use the new command instead. |
Action |
Use inoload to load or unload data in batch mode. |
INOAAE0855 | Output directory directory does not exist |
Explanation |
The output directory should exist. |
Action |
Create the output directory or check the permission if it already exists. |
INOAAE0868 | Stop request requestid failed :errortext |
Explanation |
Stop of a request failed. |
Action |
Check the error text for an explanation of why the operation failed. |
INOAAE0870 | Query current active requests failed : message |
Explanation |
A query of the current requests failed. |
Action |
Check the error message for more information. |
INOAAF0002 | Version 'version' of Tamino not found. Please use 'set version' command to change the version to the installed version. |
Explanation |
The specified Tamino version was not found. |
Action |
Use the "set version" command and change the version of the database. |
INOAAF0007 | Cannot create database: reason |
Explanation |
A database cannot be created with the parameters specified. |
Action |
Alter specified parameter value or provide missing parameter. |
INOAAF0253 | Error reading savepoints for database dbname |
Explanation |
An error occurred when reading database savepoint entries in the internal configuration store. |
Action |
Please contact your software supplier. |
INOAAF0254 | Could not create XML document |
Explanation |
An error occurred when creating an XML document. |
Action |
Reboot and restart the system. |
INOAAF0256 | Open of event log failed |
Explanation |
An error occurred when creating an event session. |
Action |
Check the event demon. |
INOAAF0262 | Error reading database locations for savepoint 'savepoint' |
Explanation |
No database locations were found in the internal configuration store for the savepoint. |
Action |
Please contact your software supplier. |
INOAAF0264 | Duplicate parameter name parameter |
Explanation |
The parameter appears more than once in the parameter list, but only a single value is allowed. |
Action |
Check where the parameter given is repeated and issue the command again without it. |
INOAAF0265 | Job initialization failed |
Explanation |
The job log could not be initialized because of insufficient resources. This could be memory or SMP resources like locks or threads. |
Action |
Free resources and retry. |
INOAAF0267 | Rename database failed |
Explanation |
The database could not be renamed. |
Action |
The reason why the database could not renamed is in the job log. Check it and retry. |
INOAAF0369 | TSM@DLL *** FATAL ERROR NO ROLLBACK POSSIBLE (SESSION LOST) *** |
Explanation |
Tamino reported an invalid session ID. |
Action |
Shut down the database and restart it. |
INOAAI0000 | Change License file |
Explanation |
Change license file. |
Action |
No action required. |
INOAAI0003 | Modify journal space of database dbname |
Explanation |
The size of the journal space is being modified. |
Action |
No action required. |
INOAAI0005 | Modify journal space successfully finished |
Explanation |
This message indicates that the "Modify journal space" function completed successfully. |
Action |
No action required. |
INOAAI0006 | Modification and reorganization of journal space in location Location from oldsize MB to one journal space of newsize MB |
Explanation |
The journal space size is being modified at the given location. If more the one journal space exists, the journal space is reorganized to one of the given size. |
Action |
No action required. |
INOAAI0008 | Modify properties of Email notification |
Explanation |
Email notification properties are being modified. |
Action |
No action required. |
INOAAI0009 | Add location name at path |
Explanation |
Start of the "add location" function. |
Action |
Information message, no action required. |
INOAAI0010 | Delete location name |
Explanation |
Start of the "delete location" function. |
Action |
Information message, no action required. |
INOAAI0011 | Moving location oldloc to newloc |
Explanation |
Start of the "move location" function. |
Action |
Information message, no action required. |
INOAAI0012 | Rename location name to newname |
Explanation |
Start of the "rename location" function. |
Action |
Information message, no action required. |
INOAAI0013 | Set location name as default database location |
Explanation |
Start of the "set default location" function. |
Action |
Information message, no action required. |
INOAAI0014 | Set location name as default backup database location |
Explanation |
Start of the "set default backup location" function. |
Action |
Information message, no action required. |
INOAAI0015 | Modify default of database location category 'category' |
Explanation |
Start of the "modify default of database location category" function. |
Action |
Information message, no action required. |
INOAAI0016 | Database Version set to version |
Explanation |
The database was set to the specified version. |
Action |
Information message, no action required. |
INOAAI0017 | Modify Email notification properties successfully finished |
Explanation |
Email notification properties have been modified successfully. |
Action |
No action required. |
INOAAI0021 | Unregistering database dbName |
Explanation |
This is a job log identification message. |
Action |
No action required. |
INOAAI0023 | New license file sucessfully applied. |
Explanation |
The license file was successfully applied. |
Action |
No action required. |
INOAAI0025 | Please log in again to the web application in order to use the new product license! |
Explanation |
The new functionality is available after you log in again. |
Action |
Log in again and restart your web applications. |
INOAAI0028 | Confirmed all pending alerts |
Explanation |
All warnings, errors and fatal errors of the job records specified have been acknowledged. |
Action |
No action required. |
INOAAI0033 | New value of dynamic property 'name' is effective now |
Explanation |
The property value has been updated and is active from now on. |
Action |
No action required. |
INOAAI0035 | Database has been successfully unregistered |
Explanation |
This message indicates, that the "Unregister Database" function is completed. |
Action |
No action required. |
INOAAI0037 | Pending alerts of all jobs have been confirmed |
Explanation |
All warnings, errors and fatal errors have been confirmed. The job records may be deleted now. |
Action |
No action required. |
INOAAI0048 | Server extension command execution |
Explanation |
This is an informational message. |
Action |
No action required. |
INOAAI0049 | Command Name : name |
Explanation |
This message specifies the command name of a server extension. |
Action |
No action required. |
INOAAI0050 | Collection Name : name |
Explanation |
This message specifies the collection name of an XML document. |
Action |
No action required. |
INOAAI0051 | Master database set to masterdb |
Explanation |
The database named is the master database. |
Action |
No action required. |
INOAAI0063 | Tamino will close the current log space extent and open a new one when the current log space block has been filled up |
Explanation |
Tamino writes log information in blocks. When the currently used block has been filled up completely, Tamino will close the current log space extent and open a new one. As a consequence, you might encounter a minimal growth of the current log space before a new one is created. |
Action |
No action required. |
INOAAI0148 | The name 'location_name' is not the name of an existing location; the default location is used instead |
Explanation |
An invalid location name was specified or extracted from a backup. It could be a valid location on the host where the backup was created. |
Action |
No action required. The location defined as default in the location management will be used. |
INOAAI0152 | No item selected for modification |
Explanation |
No item was selected to be modified. |
Action |
Select an item and retry. |
INOAAI0160 | Delete database space of database dbname |
Explanation |
The database space with the highest extent is being deleted. The deletion will not proceed when the space is in use. |
Action |
No action required. |
INOAAI0161 | Delete database space successfully finished |
Explanation |
This message indicates that the "Delete database spaces" function completed successfully. |
Action |
No action required. |
INOAAI0163 | Expand database space of database dbname |
Explanation |
The last database space is being expanded. |
Action |
No action required. |
INOAAI0164 | Expand database space successfully finished |
Explanation |
This message indicates that the "Expand database spaces" function completed successfully. |
Action |
No action required. |
INOAAI0167 | Deleting database space spaceNo from location Location |
Explanation |
The specified database space is being deleted from the given location. |
Action |
No action required. |
INOAAI0168 | Expanding database space spaceNo in location Location from oldsize MB to newsize MB |
Explanation |
The specified database space is being expanded at the given location. |
Action |
No action required. |
INOAAI0176 | Restoring of database dbName without further recovery successfully completed |
Explanation |
The specified database has been restored successfully. Changes that occurred later than the backup time were not reapplied. |
Action |
No action required. |
INOAAI0211 | Data load in collection collectionname |
Explanation |
Data has been loaded into the named collection. |
Action |
No action required. |
INOAAI0227 | Data unload from collection collectionname |
Explanation |
Data will be unloaded into the named collection. |
Action |
No action required. |
INOAAI0237 | mvcount spaces successfully moved from oldloc to newloc |
Explanation |
The specified number of spaces were moved from one location to another one. |
Action |
Information message, no action required. |
INOAAI0248 | Document path : path |
Explanation |
This message specifies the path name of an XML document. |
Action |
No action required. |
INOAAI0249 | Query string : text |
Explanation |
This message specifies the query string to retrieve XML documents. |
Action |
No action required. |
INOAAI0250 | Schema name : name |
Explanation |
This message specifies the schema name of a XML Document. |
Action |
No action required. |
INOAAI0269 | Execution of command 'name' successful |
Explanation |
A server extension command was successfully executed. |
Action |
No action required. |
INOAAI0273 | Location locCount : locName |
Explanation |
This is an informational message for one default database location of the category. |
Action |
Information message, no action required. |
INOAAI0275 | No pending alerts found |
Explanation |
An attempt was made to confirm all pending alerts, but no job with pending alerts was found. Either there are no alerts in the display, or the alerts in the display have been confirmed meanwhile by someone else. |
Action |
No action required. |
INOAAI0276 | When all pending alerts are confirmed, the "Pending Alerts" folder is cleared. Each individual job is still in the "Running Jobs" or in the "Completed Jobs" folder until it is deleted by automatic cleanup; up to that point, the warning, error and alert messages are still visible in the single job view. |
Explanation |
No job or message is really removed when alerts are confirmed; they are just moved away from the Alerts folder. |
Action |
No action required |
INOAAI0277 | When a job record is deleted, it is removed from the job log and its disk file is deleted. Jobs that are not completed (i.e. stopped or still running) and jobs that have unconfirmed alert messages are not deleted and remain in their respective folders. |
Explanation |
Only finished jobs with no pending alerts are deleted. |
Action |
No action required |
INOAAI0280 | Object Identification : text |
Explanation |
The given text provides the object identification of the server extension. |
Action |
No action required. |
INOAAI0286 | Execution type: type |
Explanation |
The specified type is the selected server extension execution type. |
Action |
No action required. |
INOAAI0288 | Backing up all server extensions for database 'name' |
Explanation |
All server extensions in the specified database are being backed up. |
Action |
No action required. |
INOAAI0289 | Backup of all server extensions successful |
Explanation |
All server extensions have been backed up successfully. |
Action |
No action required. |
INOAAI0290 | Restoring server extension for database 'name' |
Explanation |
A server extension of the specified database is being restored. |
Action |
No action required. |
INOAAI0291 | Restore of server extension 'name' successful |
Explanation |
The specified server extension has been restored successfully. |
Action |
No action required. |
INOAAI0292 | Restoring all server extensions for database 'name' |
Explanation |
All server extensions of the specified database are being restored. |
Action |
No action required. |
INOAAI0293 | Restore of all server extensions successful |
Explanation |
All server extensions have been restored successfully. |
Action |
No action required. |
INOAAI0299 | Storing binary file 'path' |
Explanation |
A binary file is being stored in the database. |
Action |
No action required. |
INOAAI0300 | Restoring binary file 'path' |
Explanation |
A binary file is being restored from the database. |
Action |
No action required. |
INOAAI0301 | Removing binary file 'path' |
Explanation |
A binary file is being removed from the database. |
Action |
No action required. |
INOAAI0303 | Command log switched mode buffers buffers |
Explanation |
This is a result message for a batch command. |
Action |
No action required. |
INOAAI0308 | Update of settings successful : name |
Explanation |
The update of the given settings parameter value was successful. |
Action |
No action necessary. |
INOAAI0316 | Backing up server extension for database 'name' |
Explanation |
A server extension in the specified database is being backed up. |
Action |
No action required. |
INOAAI0317 | Backup of server extension 'name' successful |
Explanation |
The specified server extension has been backed up successfully. |
Action |
No action required. |
INOAAI0318 | Deleting document : name |
Explanation |
The XML document will be deleted. |
Action |
No action necessary. |
INOAAI0319 | No mapped document : name |
Explanation |
No XML document is mapped to the server extension. |
Action |
No action necessary. |
INOAAI0320 | Trace server extensions in database 'name' |
Explanation |
The server extension trace mode is changed in the specified database. |
Action |
No action required. |
INOAAI0321 | Trace switched on successfully |
Explanation |
The server extension trace is switched on. |
Action |
No action required. |
INOAAI0322 | Trace switched off successfully |
Explanation |
The server extension trace is switched off. |
Action |
No action required. |
INOAAI0323 | Store server extensions in database 'name' |
Explanation |
The storing of server extension files is changed to the specified database. |
Action |
No action required. |
INOAAI0324 | Store server extension files switched on successfully |
Explanation |
The storing of server extension files is switched on. |
Action |
No action required. |
INOAAI0325 | Store server extension files switched off successfully |
Explanation |
The storing of server extension files is switched off. |
Action |
No action required. |
INOAAI0326 | Analyze object for a new server extension |
Explanation |
The object for a new server extension will be analyzed. |
Action |
No action required. |
INOAAI0327 | Object File : path |
Explanation |
This specifies the object file for the new server extension. |
Action |
No action required. |
INOAAI0328 | Analysis of new server extension object successful |
Explanation |
The analysis of the object for the new server extension was successful. |
Action |
No action required. |
INOAAI0329 | Remove server extension object |
Explanation |
The object of a new server extension will be removed. |
Action |
No action required. |
INOAAI0330 | Select function for a new server extension |
Explanation |
The function for a new server extension will be selected. |
Action |
No action required. |
INOAAI0331 | Select function for a new server extension successful |
Explanation |
The function for a new server extension was successfully selected. |
Action |
No action required. |
INOAAI0332 | Display trace state successful |
Explanation |
The server extension trace state is displayed successfully. |
Action |
No action required. |
INOAAI0333 | Create Database from Backup |
Explanation |
Button Create Database from Backup |
Action |
none |
INOAAI0357 | Access Control List 'name' created |
Explanation |
A new access control list has been created. Details are generally provided in other messages. |
Action |
No action required. |
INOAAI0358 | User group 'name' created |
Explanation |
A new user group has been created. |
Action |
No action required. |
INOAAI0360 | User 'name' created |
Explanation |
A new user has been created. Details are generally provided in other messages. |
Action |
No action required. |
INOAAI0364 | Access control list 'name' modified |
Explanation |
The current ACL has been modified. |
Action |
No action required. |
INOAAI0365 | User group 'name' modified |
Explanation |
The user group has been modified. |
Action |
No action required. |
INOAAI0366 | User 'name' modified |
Explanation |
The user has been modified. |
Action |
No action required. |
INOAAI0368 | Access control element 'name' added to the access control list |
Explanation |
An ACE has been added successfully to an ACL. |
Action |
No action required. |
INOAAI0374 | Access control list 'name' deleted |
Explanation |
The access control list has been deleted. |
Action |
No action required. |
INOAAI0375 | User 'name' deleted |
Explanation |
The user has been deleted. |
Action |
No action required. |
INOAAI0376 | User group 'name' deleted |
Explanation |
The user group has been deleted. |
Action |
No action required. |
INOAAI0406 | Shutdown of all active databases completed |
Explanation |
All active databases are about to shut down, or they are already inactive. |
Action |
No action required. |
INOAAI0407 | All autostart databases checked |
Explanation |
All databases with autostart parameter set have been started. |
Action |
No action required. |
INOAAI0410 | op of operation done |
Explanation |
This message provides information about operation progress. |
Action |
No action required |
INOAAI0424 | New value : text |
Explanation |
This describes a new value for a Java public or private classpath. |
Action |
No action required. |
INOAAI0425 | Starting autostart databases of version version |
Explanation |
Databases with the autostart parameter set to 'yes' are being started. |
Action |
No action required. |
INOAAI0426 | Stopping all active databases of version version |
Explanation |
Active databases are being stopped |
Action |
No action required. |
INOAAI0429 | Confirming all alerts |
Explanation |
Fatal error, error and warning messages are being confirmed. Once all alerts are confirmed, a job will be scheduled for cleanup (will be removed later), or it can be delete explicitly as a single job or along with all completed jobs. |
Action |
No action required. |
INOAAI0431 | Deleting all completed jobs |
Explanation |
All jobs without unconfirmed alerts are being deleted. |
Action |
No action required. |
INOAAI0432 | All job records of completed jobs successfully deleted by user (except jobs with pending alerts) |
Explanation |
Deleted job records will not appear in the job monitor list any more; the corresponding files have been deleted on disk. |
Action |
No action required. |
INOAAI0445 | Setting version for database 'dbName' |
Explanation |
Set the version of a specific database. |
Action |
Data must be unloaded and loaded into a new database manually. |
INOAAI0446 | No property has been modified. All properties already set to the given values. |
Explanation |
A property will be changed when the new property value is different from the value stored in the internal configuration store. |
Action |
No action required. |
INOAAI0448 | 'param' has been changed from 'oldValue' to 'newValue' |
Explanation |
A database property was changed successfully by the "modify property" command. |
Action |
No action required. |
INOAAI0451 | Adding database space for database dbName |
Explanation |
This message indicates the beginning of the execution of the "Add database spaces" function. |
Action |
No action required. |
INOAAI0452 | Add database space successfully finished |
Explanation |
This message indicates that the "Add database spaces" function completed successfully. |
Action |
No action required. |
INOAAI0454 | Moving database space for database dbName |
Explanation |
This message indicates the beginning of the execution of the "Move database spaces" function. |
Action |
No action required. |
INOAAI0455 | Move database space successfully finished |
Explanation |
This message indicates that the "Move database spaces" function completed successfully. |
Action |
No action required. |
INOAAI0457 | Creating database dbName |
Explanation |
This message indicates the beginning of the execution of the "Create Database" function. |
Action |
No action required. |
INOAAI0458 | Create database successfully finished |
Explanation |
This message indicates that the database was created successfully. |
Action |
No action required. |
INOAAI0460 | Deleting database dbName |
Explanation |
This message indicates the beginning of the execution of the "Delete Database" function. |
Action |
No action required. |
INOAAI0461 | Database has been successfully deleted |
Explanation |
This message indicates that the "Delete Database" function completed successfully. |
Action |
No action required. |
INOAAI0465 | Start of database dbName successful |
Explanation |
This message indicates that the specified database has been started successfully. |
Action |
No action required. |
INOAAI0467 | Stop of database dbName successful |
Explanation |
This message indicates that the specified database has been stopped successfully. |
Action |
No action required. |
INOAAI0468 | Backup of database dbName |
Explanation |
This message indicates that a backup of the specified database is being created. |
Action |
No action required. |
INOAAI0469 | Restore database dbName using backup 'bckDate' with recovery |
Explanation |
This message indicates the beginning of the execution of a database restore function with a database recovery based on the log spaces. |
Action |
No action required. |
INOAAI0470 | Restore database dbName using backup 'bckDate' without recovery |
Explanation |
This message indicates the beginning of the execution of a database restore function without a database recovery based on the log spaces. |
Action |
No action required. |
INOAAI0471 | Backup of database dbName successfully completed |
Explanation |
This message indicates that the specified database has been backed up successfully. |
Action |
No action required. |
INOAAI0476 | Restoring and recovering of database dbName successfully completed |
Explanation |
The specified database has been restored and recovered successfully. |
Action |
No action required. |
INOAAI0477 | Moving database space spaceNo from location oldLoc to newLoc |
Explanation |
A database space is being moved from one location to another. |
Action |
No action required. |
INOAAI0479 | Adding size MB database space to location newLoc |
Explanation |
The specified database space is being added to the given location. |
Action |
No action required. |
INOAAI0484 | Uninstalling all server extensions in database 'name' |
Explanation |
All server extensions in a database are being uninstalled from the specified database and the file system. If a restore is being performed the server extensions will be recovered from the backup database. |
Action |
No action required. |
INOAAI0490 | Modify database properties successfully finished |
Explanation |
Database properties have been modified successfully. |
Action |
No action required. |
INOAAI0492 | Modify properties for database dbName |
Explanation |
Database properties are being modified. |
Action |
No action required. |
INOAAI0493 | Restore database dbName using backup 'bckDate' with partial recovery |
Explanation |
A database restore function with partial recovery has been started. |
Action |
No action required. |
INOAAI0494 | Checking and repairing database dbName |
Explanation |
A function to check and repair the database has been started. |
Action |
No action required. |
INOAAI0495 | Check and repair of database dbName finished successfully |
Explanation |
The check and repair function was successfully applied to the specified database, i.e. the recreation of the indices was successful. |
Action |
No action required. |
INOAAI0497 | help |
Explanation |
This is a standard information message to show the server version in space and property commands. |
Action |
No action required. |
INOAAI0501 | Uninstall of all server extensions successful |
Explanation |
All server extensions in a database have been uninstalled successfully. This is an informational message. |
Action |
No action required. |
INOAAI0502 | Registering Java class 'path' |
Explanation |
The installation count for the Java class is added to the internal configuration. This is an informational message. |
Action |
No action required. |
INOAAI0505 | Function name: 'name' |
Explanation |
This is the name of a server extension function. This is an informational message. |
Action |
No action required. |
INOAAI0506 | External name: 'name' |
Explanation |
This is the external name of a server extension function. This is an informational message. |
Action |
No action required. |
INOAAI0511 | Parameter 'para' not valid |
Explanation |
The specified parameter is not valid for the current command. |
Action |
Check the spelling of the parameter. If the spelling is correct, check whether the parameter is valid in the current context. |
INOAAI0514 | message |
Explanation |
This is an informational message about a server extension document that has been returned from the Tamino server. |
Action |
No action required. |
INOAAI0515 | Listing server extensions in database 'name' |
Explanation |
A list of all installed server extensions for the specified database is being generated. |
Action |
No action required. |
INOAAI0516 | Installing server extension in database 'name' |
Explanation |
A new server extension is being installed in the specified database. |
Action |
No action required. |
INOAAI0517 | Package file: path |
Explanation |
The specified path is the pathname of the packed server extension file. |
Action |
No action required. |
INOAAI0518 | Execution mode: mode |
Explanation |
The specified mode is the selected server extension execution mode. |
Action |
No action required. |
INOAAI0519 | Installation of server extension 'name' successful |
Explanation |
The specified server extension was installed successfully. |
Action |
No action required. |
INOAAI0520 | Uninstalling server extension from database 'name' |
Explanation |
A server extension is being uninstalled from the specified database. |
Action |
No action required. |
INOAAI0521 | Server extension name: 'name' |
Explanation |
This message specifies the name of a server extension. |
Action |
No action required. |
INOAAI0522 | Uninstall of server extension 'name' successful |
Explanation |
The specified server extension has been uninstalled successfully. |
Action |
No action required. |
INOAAI0523 | Modifying server extension in database 'name' |
Explanation |
A server extension in the specified database is being modified. |
Action |
No action required. |
INOAAI0524 | Modification of server extension 'name' successful |
Explanation |
The specified server extension has been modified successfully. |
Action |
No action required. |
INOAAI0525 | Deleting help URL 'path' |
Explanation |
The specified help file for a server extension is being deleted. |
Action |
No action required. |
INOAAI0526 | Executing command 'call' |
Explanation |
The specified operating system command is being executed. |
Action |
No action required. |
INOAAI0527 | De-registering server extension DLL 'path' |
Explanation |
The specified server extension DLL file is being de-registered. |
Action |
No action required. |
INOAAI0528 | Deleting server extension DLL 'path' |
Explanation |
The specified server extension DLL file is being deleted. |
Action |
No action required. |
INOAAI0529 | Deselect function of a new server extension |
Explanation |
A selected function for a new server extension is being deselected. This is an informational message. |
Action |
No action required. |
INOAAI0530 | Extracting entry 'name' |
Explanation |
An entry is being extracted from a packed file. |
Action |
No action required. |
INOAAI0531 | Inserting document 'path' |
Explanation |
The URL of a help file for a server extension is being inserted into the server extension's installation document. |
Action |
No action required. |
INOAAI0532 | Registering DLL 'path' |
Explanation |
A server extension DLL file is being registered. |
Action |
No action required. |
INOAAI0533 | DLL 'path' already registered |
Explanation |
The specified server extension DLL file is already registered. |
Action |
No action required. |
INOAAI0535 | Deleting file 'name' |
Explanation |
The specified server extension installation file is being deleted. |
Action |
No action required. |
INOAAI0536 | Deleting directory 'path' |
Explanation |
The specified server extension installation directory is being deleted. |
Action |
No action required. |
INOAAI0537 | Showing server extension attributes in database 'name' |
Explanation |
The attributes of a server extension in the specified database are being listed. |
Action |
No action required. |
INOAAI0538 | Setting access rights for server extension in database 'name' |
Explanation |
The access rights of a server extension are being set in the specified database. |
Action |
No action required. |
INOAAI0543 | Stopping database dbName in normal mode |
Explanation |
This message indicates that the specified database is being stopped in normal mode. |
Action |
No action required. |
INOAAI0544 | Stopping database dbName in abort mode |
Explanation |
This message indicates that the specified database is being stopped in abort mode. |
Action |
No action required. |
INOAAI0545 | Stopping database dbName in rollback mode |
Explanation |
This message indicates that the specified database is being stopped in rollback mode. |
Action |
No action required. |
INOAAI0568 | Unexpected messages received |
Explanation |
This message is the header for subsequent messages. |
Action |
No action required. |
INOAAI0569 | Edit details for a new server extension |
Explanation |
Details for a new server extension will be edited. |
Action |
No action required. |
INOAAI0570 | Description: text |
Explanation |
This is a short description of the new server extension. |
Action |
No action required. |
INOAAI0571 | Author name: name |
Explanation |
This is the name of the new server extension author. |
Action |
No action required. |
INOAAI0572 | Help file: name |
Explanation |
This is the name of a help file for the new server extension. |
Action |
No action required. |
INOAAI0573 | Editing of new server extension details successful |
Explanation |
The editing of the new server extension details was successful. |
Action |
No action required. |
INOAAI0574 | Starting database dbName |
Explanation |
A Tamino database is being started. |
Action |
No action required. |
INOAAI0577 | Unloading document 'path' |
Explanation |
The server extension object information document is being unloaded. |
Action |
No action required. |
INOAAI0578 | Edit details for a new server extension function |
Explanation |
Details for a new server extension function will be edited. |
Action |
No action required. |
INOAAI0579 | Function type: text |
Explanation |
This message displays the type of a server extension function. |
Action |
No action required. |
INOAAI0580 | Editing of new server extension function details successful |
Explanation |
The editing of the new server extension function details was successful. |
Action |
No action required. |
INOAAI0581 | Loading document 'path' |
Explanation |
A server extension analyzer document is being loaded. |
Action |
No action required. |
INOAAI0582 | Start Database |
Explanation |
This is a command for the Tamino agent dbagent. |
Action |
No action required. |
INOAAI0583 | Stop Database |
Explanation |
This is a command for the Tamino agent dbagent. |
Action |
No action required. |
INOAAI0584 | Delete Database |
Explanation |
This is a command for the Tamino agent dbagent. |
Action |
No action required. |
INOAAI0587 | Check and Repair |
Explanation |
This is a command for the Tamino agent dbagent. |
Action |
No action required. |
INOAAI0589 | Information |
Explanation |
This is a command for the Tamino agent dbagent. |
Action |
No action required. |
INOAAI0591 | Database Spaces |
Explanation |
This is a command for the Tamino agent dbagent. |
Action |
No action required. |
INOAAI0592 | Properties |
Explanation |
This is a command for the Tamino agent dbagent. |
Action |
No action required. |
INOAAI0598 | Register CD Database |
Explanation |
This is a command button for the Tamino agent dblist. |
Action |
No action required. |
INOAAI0599 | Prepare for CD |
Explanation |
This is a command for the Tamino agent dblist. |
Action |
No action required. |
INOAAI0600 | Unregister CD Database |
Explanation |
This is a command button for the Tamino agent dbagent. |
Action |
No action required. |
INOAAI0601 | Create a new server extension package |
Explanation |
This is an informational message. |
Action |
No action required. |
INOAAI0602 | Package path: path |
Explanation |
This is the pathname of the server extension package. |
Action |
No action required. |
INOAAI0603 | Creation of package 'name' successful |
Explanation |
A server extension package was created successfully. |
Action |
No action required. |
INOAAI0604 | Port range successfully changed |
Explanation |
The port range was successfully changed. |
Action |
none |
INOAAI0607 | inodmp return erg |
Explanation |
This message shows a return value of inodmp. |
Action |
No action required. |
INOAAI0612 | Deselection of function 'name' successful |
Explanation |
The server extension function was successfully deselected. |
Action |
No action required. |
INOAAI0613 | Modify parameter of server extension function |
Explanation |
The parameter name and XML type of a selected server extension function will be modified. |
Action |
Insert the corresponding values. |
INOAAI0614 | Parameter name: name |
Explanation |
This specifies the name of the parameter being modified. |
Action |
No action required. |
INOAAI0615 | Modified name: name |
Explanation |
This specifies the modified name of the parameter. |
Action |
No action required. |
INOAAI0616 | XML type: type |
Explanation |
This specifies the modified XML type of the parameter. |
Action |
No action required. |
INOAAI0617 | Modification of parameter 'name' successful |
Explanation |
A server extension function parameter was successfully modified. |
Action |
No action required. |
INOAAI0618 | Preparation of CD database successful |
Explanation |
This is an informational message. |
Action |
No action required. |
INOAAI0625 | Renaming database dbname to newdbname |
Explanation |
The database is being renamed. |
Action |
No action required. |
INOAAI0626 | Database successfully renamed |
Explanation |
The database was renamed successfully. |
Action |
No action required. |
INOAAI0627 | Server extension class 'name' |
Explanation |
This message specifies the Java class name of a server extension. |
Action |
No action required. |
INOAAI0629 | database successfully registered |
Explanation |
A database has been successfully registered. |
Action |
No action required. |
INOAAI0630 | Registering CD database dbname |
Explanation |
The CD database is being registered. |
Action |
No action required. |
INOAAI0631 | Location name at path successfully added |
Explanation |
The location was successfully added. |
Action |
No action required. |
INOAAI0632 | Location name successfully deleted |
Explanation |
The location was successfully deleted. |
Action |
No action required. |
INOAAI0633 | Location name successfully renamed to newname |
Explanation |
The location was successfully renamed. |
Action |
No action required. |
INOAAI0634 | Location name successfully set as default database location |
Explanation |
The location was successfully set as the default database location. |
Action |
No action required. |
INOAAI0635 | Location name successfully set as default backup database location |
Explanation |
The location was successfully set as the default backup location. |
Action |
No action required. |
INOAAI0636 | Default of database location category 'category' successfully modified |
Explanation |
The default database location category was successfully modified. |
Action |
No action required. |
INOAAI0642 | Stopping XML session |
Explanation |
The XML session is being stopped. |
Action |
No action required. |
INOAAI0649 | Setting global parameters for external backup method 'method' of database dbname |
Explanation |
Global parameters for external backup method are being set. |
Action |
No action required, information message. |
INOAAI0650 | Global parameters for external backup method 'method' of database dbname successfully set |
Explanation |
The global parameters were successfully set. |
Action |
No action required, information message. |
INOAAI0652 | Setting configuration parameters for external backup method 'method' of database dbname |
Explanation |
The configuration parameters for the external backup method are being set. |
Action |
No action required, information message. |
INOAAI0654 | Configuration parameters for external backup method 'method' of database dbname successfully set |
Explanation |
The configuration parameters were successfully set. |
Action |
No action required, information message. |
INOAAI0655 | Deleting configuration 'configuration' of method 'method' of database dbname |
Explanation |
The "delete configuration" function was started. |
Action |
No action required, information message. |
INOAAI0657 | Configuration 'configuration' of method 'method' of database dbname successfully deleted |
Explanation |
The configuration parameters were successfully deleted. |
Action |
No action required, information message. |
INOAAI0661 | Replication database name replication_db added into the permission list |
Explanation |
This is a status report that the replication database name has been added into the permission list. |
Action |
No action required. |
INOAAI0663 | Replication database name replication_db removed from the permission list |
Explanation |
The replication database name has been removed from the permission list. |
Action |
No action required, this is an information message. |
INOAAI0664 | Database database set to replication type |
Explanation |
The database is set to the type "replication database". |
Action |
No action required, this is an information message. |
INOAAI0666 | Replication database database has been reset to normal type |
Explanation |
The replication database was reset so that it is a normal database. |
Action |
No action required, this is an information message. |
INOAAI0670 | Private Classpath: path |
Explanation |
The displayed path is the server extension private Java classpath. |
Action |
No action required. |
INOAAI0671 | type Classpath: path |
Explanation |
The specified operation type is performed with the server extension private Java classpath. |
Action |
No action required. |
INOAAI0673 | Keep files from backup datetime |
Explanation |
This indicates that the backup files will be saved. |
Action |
No action required, information message. |
INOAAI0674 | Move backup space to "destination" |
Explanation |
The backup space is being moved moved to new location. |
Action |
No action required, information message. |
INOAAI0682 | Switching log space for database dbName |
Explanation |
A switch of the log space is initiated. |
Action |
No action required. |
INOAAI0687 | Nothing has changed: mode |
Explanation |
The specified server extension attribute did not change. |
Action |
No action required. |
INOAAI0688 | Attribute: mode |
Explanation |
This specifies a new attribute of the parameter. |
Action |
No action required. |
INOAAI0689 | Default value : text |
Explanation |
This specifies the default value of the parameter. |
Action |
No action required. |
INOAAI0690 | Adding backup method 'method' for database dbname |
Explanation |
An external backup method of the database is being added. |
Action |
No action required, information message. |
INOAAI0692 | Backup method 'method' successfully added for database dbname |
Explanation |
The backup method has been successfully added. |
Action |
No action required, information message. |
INOAAI0693 | Deleting method 'method' of database dbname |
Explanation |
An external backup method of the database is being deleted. |
Action |
No action required, information message. |
INOAAI0695 | Method 'method' of database dbname successfully deleted |
Explanation |
The backup method has been successfully deleted. |
Action |
No action required, information message. |
INOAAI0697 | Deleting backup 'bckDate' of database dbName |
Explanation |
The backup of the database is being deleted. |
Action |
Information message, no action required. |
INOAAI0698 | Deletion of backup 'bckDate' of database dbName successfully completed |
Explanation |
The specified database backup has been deleted successfully. |
Action |
Information message, no action required. |
INOAAI0701 | Remove permitted replication database name replicationdb from master database masterdb |
Explanation |
This is a title for the messages for removing a database name from the permission list. |
Action |
No action required. |
INOAAI0702 | Add permitted replication database name |
Explanation |
This is a title for adding database name into the permission list. |
Action |
No action required. |
INOAAI0704 | Set type to normal database |
Explanation |
This is a title for setting the database type to a normal one. |
Action |
No action required. |
INOAAI0705 | Create replication database list |
Explanation |
This is a title for create replication database list. |
Action |
No action required. |
INOAAI0706 | Retrieve replication database information |
Explanation |
This is a title for retrieving the information of databases. |
Action |
No action required. |
INOAAI0711 | Domain 'name' created |
Explanation |
The domain has been created. |
Action |
No action required. |
INOAAI0713 | Domain 'name' modified |
Explanation |
The domain has been modified. |
Action |
No action required. |
INOAAI0715 | Domain 'name' deleted |
Explanation |
The domain has been deleted. |
Action |
No action required. |
INOAAI0718 | Creating database dbName from backup dated timestamp |
Explanation |
A new database is created with the content of a given backup. The log spaces belonging to the backup are not recovered. |
Action |
No action required. |
INOAAI0721 | Web server assignments changed. |
Explanation |
The web server assignments for this database have changed. |
Action |
No action required. |
INOAAI0722 | Setting port ranges for Tamino databases |
Explanation |
The static and dynamic port ranges are being set. |
Action |
No action required. |
INOAAI0726 | Port ranges successfully changed |
Explanation |
The port ranges were successfully changed. |
Action |
No action required. |
INOAAI0729 | Renaming web server 'wbsname' to 'newwbsname' |
Explanation |
The web server is being renamed. |
Action |
No action required. |
INOAAI0730 | Web server successfully renamed |
Explanation |
The web server was successfully renamed. |
Action |
No action required. |
INOAAI0732 | Web server successfully added. |
Explanation |
The web server was added successfully. |
Action |
No action required. |
INOAAI0734 | Adding web server 'newwbsname' |
Explanation |
The web server is being added. |
Action |
No action required. |
INOAAI0735 | Deleting web server 'wbsname' |
Explanation |
The web server is being deleted. |
Action |
No action required. |
INOAAI0736 | Web server successfully deleted |
Explanation |
The web server was deleted successfully. |
Action |
No action required. |
INOAAI0738 | Modifying web server 'wbsname'. New IP address: 'ipaddress', new node: 'node', new port: 'port'. |
Explanation |
The web server is being modified. |
Action |
No action required. |
INOAAI0739 | Web server successfully modified |
Explanation |
The web server was modified successfully. |
Action |
No action required. |
INOAAI0751 | Preparing CD database dbname |
Explanation |
A CD database is being prepared. |
Action |
No action required. |
INOAAI0770 | Could not create database, cleaning up now |
Explanation |
The "Create Database" or "Create Database From Backup" command has failed. Files, internal configuration store entries and XTS entries made during this process are deleted. |
Action |
No action required. |
INOAAI0771 | Location location selected for initial backup |
Explanation |
The initial backup could not be created in the first backup location specified. It has been created in the location indicated in the message text instead. |
Action |
No action required. |
INOAAI0781 | The command requires an active database |
Explanation |
An attempt was made to execute a command that requires an active database, but the the database is inactive. |
Action |
The database must be started before the command can be executed. |
INOAAI0782 | The command requires an inactive database |
Explanation |
An attempt was made to execute a command but the database is active and the command requires an inactive database. |
Action |
The database must be stopped before the command can be executed. |
INOAAI0789 | Web server assignments changed. Please restart all databases which have this web server assigned to make your changes effective. |
Explanation |
The web server assignments for this database have changed. |
Action |
Please restart all databases which have this web server assigned to make your changes effective. |
INOAAI0795 | Set type to replication database with simultaneous query |
Explanation |
The flag for simultaneous query for replication is set to 'enabled'. |
Action |
No action required. |
INOAAI0796 | Set type to replication database without simultaneous query |
Explanation |
The flag to allow simultaneous query for replication is disabled. |
Action |
No action required. |
INOAAI0821 | Initialize raw section |
Explanation |
This is an event log message while the raw section is being initialized. |
Action |
No action required. |
INOAAI0822 | Raw section successfully initialized |
Explanation |
The raw section has been successfully initialized. |
Action |
No action required. |
INOAAI0827 | Set static min port min |
Explanation |
The static minimum port is being set. All Tamino database static ports must be greater than or equal to this value. |
Action |
No action required. |
INOAAI0828 | Set static max port max |
Explanation |
The static maximum port is being set. All Tamino database static ports must be lower than or equal to this value. |
Action |
No action required. |
INOAAI0829 | Set dynamic min port dmin |
Explanation |
The dynamic minimum port is being set. Tamino databases use the port range for dynamically allocated ports. This port range should not be used by any other software. |
Action |
No action required. |
INOAAI0830 | Set dynamic max port dmax |
Explanation |
The dynamic maximum port is being set. Tamino databases use the port range for dynamically allocated ports. This port range should not be used by any other software. |
Action |
No action required. |
INOAAI0840 | Function func is used in collection coll, schema schm, doc type doc |
Explanation |
The server extension to be uninstalled contains a function that is still used in the given context. |
Action |
Typically no action is required but be aware that in the case of a forced uninstall the corresponding functions cannot be executed any longer. |
INOAAI0848 | Restart parameter ignored, because only dynamic properties changed |
Explanation |
A restart parameter was given, but a restart is only useful if a static property is changed. |
Action |
No action required. |
INOAAI0865 | Moving database space spaceNo of database dbname from oldLoc to newLoc |
Explanation |
The database space of the named database is being moved from one location to another location. |
Action |
No action required. |
INOAAI0866 | Stop current request(s) |
Explanation |
Stop a current running request. |
Action |
No action required. |
INOAAI0867 | Request requestid successfully stopped |
Explanation |
A request has been successfully stopped. |
Action |
No action required. |
INOAAI0869 | No current active requests found |
Explanation |
No requests are running on the XML Server. |
Action |
No action required. |
INOAAW0071 | Higher server extension versions exist : name |
Explanation |
In other databases, higher versions of this server extension exist. |
Action |
Back up the server extension. |
INOAAW0150 | Backup spaces are copied because one or more spaces could still be part of an existing backup generation |
Explanation |
To protect integrity of backup generations, spaces with the Tamino backup filename extension "1B0" are always copied because they could be part of a backup generation on the local host, or another remote host. |
Action |
Make sure that the selected backup spaces are not used in a backup generation by a local database or elsewhere, and then change their filename extension to something different from "1B0". |
INOAAW0166 | Parameter 'para' unknown |
Explanation |
The specified database parameter name is not known by the Tamino server. |
Action |
Check the spelling of the parameter. If the spelling is correct, check whether the parameter is valid in the current context. |
INOAAW0206 | Required spacetype size could not be obtained from the backup, using minimum sizes where not specified otherwise |
Explanation |
Minimum sizes will be used if not specified otherwise but the new database might refuse to start with these settings. |
Action |
Specify the effective spaces of the saved database if creating with the minimum sizes does not succeed. |
INOAAW0271 | Cannot move space of database database, because the database is online |
Explanation |
The database of the database space to move is in an active state. |
Action |
Stop the database. |
INOAAW0411 | Show progress aborted |
Explanation |
The progress information process is aborted because no more progress is determined, but operation is not finished. |
Action |
No action required. |
INOAAW0422 | An error has occurred when user user attempted to remove the records of all completed jobs without pending alerts from the joblog |
Explanation |
One or more job records may remain in the given job log after the attempt to delete all due records. |
Action |
Check if the service is running. If the problem persists, job records can be deleted "physically" by deleting the files with the extensions "0G0" and "0F0" in the directory were job records are stored (try the "log" directory in the Tamino or System Management Hub root directory) and restarting the service. This however will also delete records with pending alerts and records of active commands and should only be done as a last resort. |
INOAAW0433 | File 'path' not deleted |
Explanation |
The server extension file could not be deleted. |
Action |
No action necessary. |
INOAAW0434 | File 'path' not found |
Explanation |
The specified file could not be found. |
Action |
No action necessary. |
INOAAW0435 | Directory 'path' not deleted |
Explanation |
The directory is in use. Therefore it cannot be deleted. |
Action |
Wait until the directory is not in use, then retry the operation. |
INOAAW0436 | Directory 'path' not found |
Explanation |
The specified directory was not found. |
Action |
Check the permissions of your file system. |
INOAAW0440 | Automatic assign of ports for the database failed, please assign the ports manually |
Explanation |
The database is not usable until the ports are assigned manually. |
Action |
Assign the ports for the database manually. |
INOAAW0640 | After restarting the Tamino server the server extension will be updated correctly |
Explanation |
The Tamino server crashed. The server extension will be usable after restart. |
Action |
Restart the Tamino server to use this server extension . |
INOAAW0676 | Please store the tape(s) from backup datetime in a safe place! |
Explanation |
Tapes cannot be saved, the user must store them in a safe place. |
Action |
Keep the backup in a safe place. |
INOAAW0677 | Please store the files from external backup datetime in a safe place! |
Explanation |
External backups cannot be saved, the user must store them in a safe place. |
Action |
Keep the external backup in a safe place. |
INOAAW0700 | Updating existing server extension 'name' |
Explanation |
A previous version of the server extension is already installed in the database and will be updated. |
Action |
No action required. |
INOAAW0800 | Disabling autostart for database dbName |
Explanation |
The parameter "autostart" of the database has been set to "false". |
Action |
No action required. |
INOAAW0804 | No property changed, property name and value is missing |
Explanation |
There is no property name in the command. |
Action |
Supply the name of the property and the new value (propertyname=value) at the end of the batch command. |
INOAAW0815 | Parameter 'name' is ignored for server extensions with execution type 'type' |
Explanation |
The parameter cannot be used for server extensions of the given execution type. |
Action |
No action required. |
INOAAW0833 | Force ignore replication database master status is set. |
Explanation |
Normally it is not allowed to delete a replication database master, so force ignore replication master status is set. The database will be removed. |
Action |
No action required. |
INOAAW0839 | Server extension name is used in schema |
Explanation |
In some node of a schema a function of the server extension name is used. |
Action |
See the following messages for detailed information. |
INOAAW0851 | No backups with user data found, please don't use option "Keep Backups" |
Explanation |
No backups with user data found, please don't use option "Keep Backups". |
Action |
Do not use the option "Keep Backups". |
INOAAW0853 | This command is deprecated. Please use the new command "inoload". |
Explanation |
This command is set to the deprecated state and will be disabled in the next version |
Action |
Use the new command inoload instead of this command. |
INOAAW0854 | COM server extension registration/deregistration suppressed |
Explanation |
When packaging the COM server extension, the option to suppress the registration/deregistration commands has been used. |
Action |
It is the installer's responsibility to make sure the COM objects are correctly registered/deregistered using the methods provided by the underlying infrastructure. |
INOAAW0871 | Can't connect to XTS directory server rc = xtsrc |
Explanation |
Can't connect to XTS directory server. This server is necessary for Tamino databases. |
Action |
Check the XTS directory server. |
INOCVE8065 | Collection collection contains non-migrated indexes |
Explanation |
The upgrade was rejected because there are non-migrated indexes in Tamino 4.1.4. |
Action |
Please migrate the indexes. Refer to the migration documentation for details. |
INOCVE8067 | Collection collection contains doctypes that are not namespace clean |
Explanation |
The upgrade was rejected because at least one doctype in the database is not namespace clean. |
Action |
Please perform a namespace cleanup. Refer to the migration documentation for details. |
INOCVE8069 | Conversion of data mapping to version version has failed with response response |
Explanation |
An error occurred during the conversion of data mapping for standard index and collations. |
Action |
Please contact your software supplier. |
INOCVE8070 | number TSD2 user collections exist |
Explanation |
TSD2 user collections exist and must be migrated to TSD3. |
Action |
Please use the migration tool to migrate the TSD2 user collections. |
INOCVE8071 | The count of existing user collections has failed with response response |
Explanation |
The query to count existing user collections has failed. |
Action |
Please contact your software supplier. |
INOCVE8073 | number installed COM server extensions found, conversion not allowed |
Explanation |
It is not possible to convert a Tamino database to this version as COM server extensions are installed. |
Action |
Contact your software supplier for help with switching versions. |
INOCVE8074 | Counting existing COM server extensions has failed with response response |
Explanation |
The query to count existing COM server extensions has failed. |
Action |
Contact your software supplier for help with switching versions. |
INOCVE8075 | Request to create indexes for doctype doctype in collection collection is pending |
Explanation |
A request to create indexes is pending. |
Action |
Please correct the current status using the admin-command ino:repairIndex with option CONTINUE or DROP. |
INOCVE8077 | The schema check for existing user collections has failed |
Explanation |
The test define of existing user collection during "set version" has failed. |
Action |
Please contact your software supplier. |
INOCVE8078 | The check for server extension installation has failed |
Explanation |
The query to check whether a server extension is installed has failed. |
Action |
Please contact your software supplier. |
INOCVW8066 | Schema "schema" in collection "collection" contains unknown attributes |
Explanation |
The given schema in the given collection contains unknown attributes. |
Action |
Remove additional attributes before next schema update. |
INOCVW8076 | The schema check for schema schema in collection collection has failed with response response |
Explanation |
The test of defining all existing user collections during "set version" has failed. |
Action |
Please check the schema using the following admin-command ino:CheckSchema(collection-name, schema-name). Correct the schema and update it in Tamino. |
INODCE6507 | Parameter structure mismatch |
Explanation |
A parameter structure mismatch was detected. |
Action |
Please check and correct the given parameters and try again. |
INODCE6508 | Not enough memory to create communication area |
Explanation |
There was not enough memory to create the communication area. |
Action |
Please free some memory and try again. |
INODCE6509 | Fatal error - unload aborted |
Explanation |
A fatal error was detected and the unload was aborted. |
Action |
Please check for other error messages to obtain the cause of the abort. |
INODCE6510 | Specify either the '-database' or the '-server' parameter, but do not specify both parameters together |
Explanation |
Please specify either the '-database' or the '-server' parameter, but do not specify both parameters together. |
Action |
Please do not specify both parameters together. |
INODCE6511 | Processing failed - cannot get server version |
Explanation |
The processing failed because it was not possible to get the server version. |
Action |
Please check that you are using a version of the data loader client which is compatible with the server. |
INODCE6512 | Path and/or file name too long |
Explanation |
The path and/or file name is too long. |
Action |
Please change the file name and try again. |
INODCE6514 | Cannot open log file 'file' |
Explanation |
It was not possible to open the log file. |
Action |
Please make sure the log file can be written and try again. |
INODCE6515 | Processing failed - corrupted response from server |
Explanation |
Processing failed because a corrupted response was received from the server. |
Action |
Please contact your software supplier. |
INODCE6517 | Server does not support mass loading of data |
Explanation |
The server does not support mass loading of data. |
Action |
No action required. |
INODCE6518 | Cannot retrieve information for input file 'file' |
Explanation |
It was not possible to retrieve information for the input file. |
Action |
Please make sure the input file can be read and try again. |
INODCE6519 | Cannot process an empty input file 'file' |
Explanation |
It is not possible to process the input file because it is empty. |
Action |
Please make sure you specify the correct input file and try again. |
INODCE6520 | Cannot open input file 'file' |
Explanation |
It was not possible to open the input file. |
Action |
Please make sure the input file can be read and try again. |
INODCE6521 | WSAStartup failed |
Explanation |
WSAStartup failed. |
Action |
Please check the network configuration. |
INODCE6522 | Winsock version mismatch |
Explanation |
A Winsock version mismatch was detected. |
Action |
Please check the network configuration. |
INODCE6523 | Not enough memory to create client host name |
Explanation |
There was not enough memory to create client host name. |
Action |
Please free some memory and try again. |
INODCE6524 | Invalid cursor handle delivered |
Explanation |
An invalid cursor handle was delivered. |
Action |
Please contact your software supplier. |
INODCE6525 | No cursor handle delivered |
Explanation |
No cursor handle was delivered. |
Action |
Please contact your software supplier. |
INODCE6526 | Not enough memory to create query object |
Explanation |
There was not enough memory to create the query object. |
Action |
Please free some memory and try again. |
INODCE6527 | Not enough memory to create query name buffer |
Explanation |
There was not enough memory to create the query name buffer. |
Action |
Please free some memory and try again. |
INODCE6528 | Cannot open output file 'file' |
Explanation |
It was not possible to open the named output file. |
Action |
Please make sure the output file can be written and try again. |
INODCE6529 | Invalid output format |
Explanation |
An invalid output format was detected. |
Action |
Please contact your software supplier. |
INODCE6530 | Cannot unload non-XML documents into a single file |
Explanation |
It is not possible to unload non-XML documents into a single file. |
Action |
Please make sure you specified a valid output location for non-XML documents and try again. |
INODCE6531 | Unload to a single file is not allowed |
Explanation |
An unload to a single file is not allowed. |
Action |
Please make sure you specified a valid output location and try again. |
INODCE6532 | Unload to a directory is not allowed |
Explanation |
An unload to a directory is not allowed. |
Action |
Please make sure you specified a valid output location and try again. |
INODCE6534 | Cannot read input file - I/O error code |
Explanation |
The input file could not be read due to an I/O error. |
Action |
Please make sure the input file can be read and try again. |
INODCE6536 | Not enough memory to create save area |
Explanation |
There was not enough memory to create the save area. |
Action |
Please free some memory and try again. |
INODCE6538 | Cannot initialize multi thread context |
Explanation |
It was not possible to initialize a multi thread context. |
Action |
Please contact your software supplier. |
INODCE6539 | Not enough memory to create request |
Explanation |
The was not enough memory to create a request. |
Action |
Please free some memory and try again. |
INODCE6543 | Not enough memory to create file offset area |
Explanation |
There was not enough memory to create the file offset area. |
Action |
Please free some memory and try again. |
INODCE6544 | Processing failed - no response from server |
Explanation |
The processing failed because there was no response from the server. |
Action |
Please contact your software supplier. |
INODCE6545 | Received empty answer from Tamino server |
Explanation |
An empty reply was received from the Tamino server. |
Action |
Please contact your software supplier. |
INODCE6547 | Invalid function code detected |
Explanation |
An invalid function code was detected. |
Action |
Please enter either "load", "unload" or "define" for the parameter "-function" |
INODCE6548 | Parameter 'parm' is only available with function code 'func' |
Explanation |
The given parameter is only available with the given function code. |
Action |
Please correct your input and try again. |
INODCE6549 | Argument for parameter 'arg' missing |
Explanation |
An argument for the given parameter is missing. |
Action |
Please correct your input and try again. |
INODCE6550 | Query filter must be enclosed in brackets: [...] |
Explanation |
A query filter must be enclosed in brackets: [...]. |
Action |
Please correct your input and try again. |
INODCE6551 | Please specify the parameter 'parm' only once |
Explanation |
The given parameter was specified more than once. Please specify the parameter only once. |
Action |
Please correct your input and try again. |
INODCE6552 | Doctype is required |
Explanation |
A doctype is required. |
Action |
Please correct your input and try again. |
INODCE6553 | Server name is required |
Explanation |
The server name is required. |
Action |
Please correct your input and try again. |
INODCE6554 | Port number is required |
Explanation |
A port number is required. |
Action |
Please correct your input and try again. |
INODCE6555 | Parameter 'p1' not allowed in conjunction with parameter 'p2' |
Explanation |
The first parameter cannot be used together with the second parameter. |
Action |
Please correct your input and try again. |
INODCE6556 | Memory allocation failed during parsing |
Explanation |
Memory allocation failed during the parsing phase. |
Action |
Please free some memory and try again. |
INODCE6557 | Invalid hexBinary parameter detected |
Explanation |
An invalid hexBinary parameter was detected. |
Action |
Please correct your input and try again. |
INODCE6558 | Invalid parameter detected: 'parm' |
Explanation |
An invalid parameter was detected. |
Action |
Please correct your input and try again. |
INODCE6559 | Invalid argument for parameter -outputformat detected |
Explanation |
An invalid argument for parameter -outputformat was detected. |
Action |
Please enter either "singlefile" or "multifiles". |
INODCE6560 | Invalid argument for parameter -docname detected |
Explanation |
An invalid argument for parameter -docname was detected. |
Action |
Please enter either "no", "full", "name" or "nameext". |
INODCE6561 | Specify both '-sessionid' and '-sessionkey' or neither |
Explanation |
You must specify either both '-sessionid' and '-sessionkey' or neither. |
Action |
Please correct your input and try again. |
INODCE6562 | Mandatory parameter '-server' or '-database' missing |
Explanation |
The mandatory parameter '-server' or '-database' is missing. |
Action |
Please correct your input and try again. |
INODCE6563 | Mandatory parameter '-collection' missing |
Explanation |
The mandatory parameter '-collection' is missing. |
Action |
Please correct your input and try again. |
INODCE6566 | msg |
Explanation |
This is a general placeholder for a message text. |
Action |
See the text of the message in the job log for more details. |
INODCE6567 | Cannot open rejects file 'file' |
Explanation |
The rejects file could not be opened. |
Action |
Please make sure the rejects file can be opened and try again. |
INODCE6568 | Cannot write rejects file 'file' |
Explanation |
It was not possible to write to the rejects file. |
Action |
Please make sure the rejects file can be written and try again. |
INODCE6570 | Access to Tamino Server denied |
Explanation |
Because of security definitions access to the Tamino server is denied. |
Action |
Please check your security definitions and try again. |
INODCE6575 | Cannot write to output file - I/O error code |
Explanation |
The output file could not be written due to an I/O error. |
Action |
Please make sure the output file can be written and try again. |
INODCE6578 | Tamino Data Loader finished with errors |
Explanation |
The Tamino Data Loader has finished its processing with some error messages. |
Action |
Check the log output, correct errors and try again. |
INODCE6579 | libxni provided data buffer of bsize bytes, minimum of nsize bytes needed |
Explanation |
Internal error in massload utility detected. |
Action |
Please contact your software supplier. |
INODCE6580 | Memory allocation failed while loading data |
Explanation |
An out of memory condition occurred. |
Action |
Restart the command when virtual memory is available. |
INODCE6581 | Invalid media type specified for input file 'file' |
Explanation |
An invalid media type was specified. You can load only documents of media type xml to a xml doctype. |
Action |
Please specify a legal xml media type and try again. |
INODCE6582 | Error reading from input file 'file' while writing reject file |
Explanation |
A file read error occurred while backing up rejected data. |
Action |
Check the file storage or contact your software supplier. |
INODCE6583 | Cannot contact Tamino Server - HTTP status code code received |
Explanation |
Cannot contact Tamino Server - HTTP status code received. |
Action |
Please contact your system administrator. |
INODCE6584 | The operation was canceled by the user |
Explanation |
The operation was canceled by the user. |
Action |
No action required. |
INODCE6585 | Invalid argument for parameter -streaming detected |
Explanation |
An invalid argument for parameter -streaming was detected. |
Action |
Please enter either "on" or "off". |
INODCE6590 | Server does not support mass deleting of data |
Explanation |
The server does not support mass deleting of data. |
Action |
No action required. |
INODCE6592 | Disconnect from server failed due to a serious communication error |
Explanation |
Disconnect from server failed due to a serious communication error. |
Action |
Please check your network settings. |
INODCI6500 | Tamino Data Loader vvers - (c) Copyright Software AG 2002-year. All rights reserved. |
Explanation |
This is the Tamino Data Loader start message. |
Action |
No action required. |
INODCI6501 | Loading documents to database 'db', collection 'coll', doctype 'doctype' |
Explanation |
Documents are being loaded into the database. |
Action |
No action required. |
INODCI6502 | Loading documents to database on 'server:port', collection 'coll', doctype 'doctype' |
Explanation |
Documents are being loaded into the database. |
Action |
No action required. |
INODCI6503 | Unloading documents from database 'db', collection 'coll', doctype 'doctype' |
Explanation |
Documents are being unloaded from database. |
Action |
No action required. |
INODCI6504 | Unloading documents from database on 'server:port', collection 'coll', doctype 'doctype' |
Explanation |
Documents are being unloaded from the database. |
Action |
No action required. |
INODCI6505 | Defining schemas to database 'db' |
Explanation |
Schemas are being defined in the database. |
Action |
No action required. |
INODCI6506 | Defining schemas to database on 'server:port' |
Explanation |
Schemas are being defined in the database. |
Action |
No action required. |
INODCI6513 | Unloading file 'file' |
Explanation |
The given file is being unloaded. |
Action |
No action required. |
INODCI6516 | Loading file 'file' |
Explanation |
The given file is being loaded. |
Action |
No action required. |
INODCI6533 | No matching documents found |
Explanation |
The query you specified returned no results. |
Action |
Please specify another query and try againg. |
INODCI6535 | start MB of end MB loaded |
Explanation |
This shows the progress information. |
Action |
No action required. |
INODCI6537 | Loading document id |
Explanation |
The given document is being loaded. |
Action |
No action required. |
INODCI6540 | Unloading documents start to end |
Explanation |
The documents in the range from "start" to "end" are being unloaded. |
Action |
No action required. |
INODCI6541 | Data unloading completed, number of documents processed: num |
Explanation |
The unload of the data has completed. |
Action |
No action required. |
INODCI6542 | Committing loaded documents - this may take a while |
Explanation |
The loaded documents are being committed. This activity can last a while. |
Action |
No action required. |
INODCI6546 | Elapsed time: elapse second(s), data processed: amount |
Explanation |
The elapsed time and the amount of data processed are shown here. |
Action |
No action required. |
INODCI6564 | msg |
Explanation |
This is a general placeholder for a message text. |
Action |
See the text of the message in the job log for more details. |
INODCI6565 | Data loading completed, number of documents processed docsproc, loaded docsload, rejected docsrejected |
Explanation |
The data processing has completed with the given number of loaded and rejected documents. |
Action |
No action required. |
INODCI6569 | Process id: id |
Explanation |
The process has the given ID. |
Action |
No action required. |
INODCI6571 | Unloading schemas from database 'db', collection 'coll' |
Explanation |
Schemas are being unloaded from the database. |
Action |
No action required. |
INODCI6572 | Unloading schemas from database on 'server:port', collection 'coll' |
Explanation |
Schemas are being unloaded from the given collection of the database on the given server and port. |
Action |
No action required. |
INODCI6573 | Unloading schemas start to end |
Explanation |
Schemas in the range from "start" to "end" are being unloaded. |
Action |
No action required. |
INODCI6574 | Data unloading completed, number of schema files written: num |
Explanation |
The unloading of data has completed. |
Action |
No action required. |
INODCI6576 | Tamino Data Loader successfully finished |
Explanation |
The Tamino Data Loader has successfully completed its processing. |
Action |
No action required. |
INODCI6586 | Undefining schemas from database 'db' |
Explanation |
Schemas are being undefined from the database. |
Action |
No action required. |
INODCI6587 | Undefining schemas from database on 'server:port' |
Explanation |
Schemas are being undefined from the database. |
Action |
No action required. |
INODCI6588 | Deleting documents from database 'db', collection 'coll', doctype 'doctype' |
Explanation |
Documents are being deleted from database. |
Action |
No action required. |
INODCI6589 | Deleting documents from database on 'server:port', collection 'coll', doctype 'doctype' |
Explanation |
Documents are being deleted from the database. |
Action |
No action required. |
INODCI6591 | Data deleting completed, docsdel documents deleted |
Explanation |
The data deleting has completed with the given number of deleted documents. |
Action |
No action required. |
INODCW6577 | Tamino Data Loader finished with warnings |
Explanation |
The Tamino Data Loader has finished its processing with some warning messages. |
Action |
Check the log output, correct errors and try again. |
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 modifierversionmodifier2 on system info |
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. |
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. |
INODSA2278 | Tamino name modifierversionmodifier2 on system info |
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 (src to dest) 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 errno 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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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 errno 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 no in database space space no (operating system error errno) |
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 errno when opening database space space no (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 err, 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. |
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. |
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. |
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. |
INODSE1096 | Error errno 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. |
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. |
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 errno |
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. |
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. |
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 errno |
Explanation |
The virtual operating system could not open the requested file. |
Action |
Make sure that the file is available. |
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. |
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. |
INODSE1127 | SCM service open failed with error rsp |
Explanation |
Service Control Manager open service failed. |
Action |
Please contact your software supplier. |
INODSE1128 | System error errno 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 errno 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 number1, current is block number2 |
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. |
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. |
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 db 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. |
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. |
INODSE1150 | The indexes of doctype doctype are corrupt, reason rsp |
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. |
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. |
INODSE1154 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
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. |
INODSE1158 | I/O subsystem error (e1/e2): 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. |
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 |
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. |
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. |
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. |
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. |
INODSE1235 | Crash dump file filename could not be created due to operating system error system errno (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. |
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. |
INODSE1289 | Error when opening database space space no (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 no. System error errno 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. |
INODSE1292 | Creation of database space space no (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 no (path) has failed due to system error errno |
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. |
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. |
INODSE1358 | Creation of database space space no (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. |
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 minvalue |
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 maxvalue |
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 minnum character(s) required |
Explanation |
The specified number of characters was too low. |
Action |
Please specify a sufficient number of characters. |
INODSE1387 | Only maxnum 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 param |
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. |
INODSE1413 | System error errno when opening database space space no (path) |
Explanation |
The specified operating system error has occurred. |
Action |
Please consult the manufacturer's manual. |
INODSE1416 | architecture mismatch detected, file from platform |
Explanation |
The crash dump file is from a different platform. |
Action |
Go to the proper platform. |
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. |
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 cont 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 blocksize / 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 'ts' failed: msg |
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 func [mod - line] what parameter param |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2033 | Internal error occurred: OVO func [mod - line] error |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2034 | Internal error occurred: SMP func [mod - line] error |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2035 | Server communication interface [mod - 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 avail 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 file already exists in the destination directory dir |
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 locname not found |
Explanation |
The specified location was not found. |
Action |
Correct the location name parameter and try again. |
INODSE2080 | Internal error occurred: DSIF func [mod - 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 what(bytes) [mod - 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 err - int_err |
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 portmin and portmax |
Explanation |
An invalid port value was detected. |
Action |
Please specify a valid port value. |
INODSE2085 | Invalid port range r1 - r2 detected, minimum min 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 r1 - r2 and dynamic port range r3 - r4 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 r1 - r2 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 func [mod - 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 dbname |
Explanation |
The web server is not assigned to the database. |
Action |
Check your web server registrations. |
INODSE2096 | Environment extension envext not registered for Tamino what what1 |
Explanation |
The environment extension is not registered in the Tamino configuration. |
Action |
No action required. |
INODSE2097 | No environment extension registered for Tamino what what1 |
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 r1 - r2 detected |
Explanation |
An invalid port range was detected. |
Action |
Specify a valid port range. |
INODSE2104 | Component comp already exists for extension point extp in version vers |
Explanation |
The component already exists for the extension point in the specified version. |
Action |
No action required. |
INODSE2105 | Component comp already exists for extensions in version vers |
Explanation |
The component already exists in the extension section of the specified version. |
Action |
No action required. |
INODSE2106 | Component comp does not exist for extension point extp in version vers |
Explanation |
The specified component is not defined for the given extension point and version. |
Action |
No action required. |
INODSE2107 | Component comp does not exist in extensions for version vers |
Explanation |
The specified component does not exist in the extensions for the given version. |
Action |
No action required. |
INODSE2108 | Could not find function func for extension point extp, version vers, component comp |
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 extp does not exist in version vers |
Explanation |
The specified extension point does not exist in the given version. |
Action |
No action required. |
INODSE2110 | Could not load library lib for extension point extp, version vers, component comp |
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 err - int_err |
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: func [mod - line] what parameter param |
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 err - int_err |
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 lev (compatibility comp) |
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 func [mod - line] invalid parameter handle (parhdl) supplied |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier and provide the message text. |
INODSE2143 | Server parameter "param" 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 "param" supplied |
Explanation |
The given server parameter name is invalid. |
Action |
Specify a valid server parameter name. |
INODSE2145 | Static server parameter "param" 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 typ |
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 (bls) |
Explanation |
The blocksize field of first index space does not match the real blocksize. |
Action |
No action required. |
INODSE2164 | Physical extent entry error (typ 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 'type1' , found 'type2' |
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. |
INODSE2169 | Received response rsp (intrsp) while starting server |
Explanation |
Starting the server failed. |
Action |
Please contact your software supplier. |
INODSE2170 | Received response rsp (intrsp) while stopping server |
Explanation |
Stopping the server failed. |
Action |
Please contact your software supplier. |
INODSE2173 | Unexpected internal server error: errorstring |
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: errorstring, 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 from_version to version to_version 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 old_version not supported to upgrade to new_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 master dbname 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 replication dbname 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 master dbname 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. |
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. |
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 rabn, invalid periodic group count count for fieldname |
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 dbname 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 func returncode returncode error error |
Explanation |
This is an internal error message. |
Action |
Please contact your software supplier. |
INODSE2242 | Replication instance replication dbname 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 replication dbname 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 filetype 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 propertyname 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 errno (errtxt) |
Explanation |
The file specified cannot be opened due to an internal operating system error. |
Action |
Consult the manufacturer's manual. |
INODSE2283 | io error error (errtxt) on block block no in database space space no |
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 no (path) has failed due to system error errno (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 dbname 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 servername |
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. |
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. |
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 err |
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: why |
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: why |
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: why |
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. |
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. |
INODSE5309 | Key id could not be changed, msg |
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, msg |
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, msg |
Explanation |
Internal error, while requesting database ID information. |
Action |
Contact your software supplier. |
INODSE5321 | Database name could not be determined, msg |
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 errcode |
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 errcode |
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 errcode |
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 licsize MB, attempted dataspace container size is datasize 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. |
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. |
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. |
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: rspmsg |
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 rsp 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 (int 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 (int 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 (value1, value2) 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-c1-c2 occurred |
Explanation |
An internal error has caused the server to stop. |
Action |
Please contact your software supplier. Restart the server. |
INODSF1282 | Received response rsp (intrsp) while loading function(s) for extension point extp |
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. |
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. |
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 errno |
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 errno 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 errno 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 errno 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 errno 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. |
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. |
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 errno) |
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 info 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 (rsp1) on doctype doctype, caused by: rsp2 |
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 complev1, backup file complev2 (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 [mod-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 complev1, database complev2 |
Explanation |
An invalid compatibility level has been detected. |
Action |
Please contact your software supplier. |
INODSF2123 | CF [mod-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 blknr (doc doc, cont cont) |
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 keyreq, present keypres |
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 errno |
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 errno (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 info 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 interr 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 dbspace at block blocknumber |
Explanation |
Reading the given database block resulted in an internal I/O error. |
Action |
No action required. |
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. |
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 customername sub-licensed by partnername with ID partnerid 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 customername with ID customerid sub-licensed by partnername 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 customername with ID customerid sub-licensed by partnername with ID partnerid 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 dbspace at block blocknumber |
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 db_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. |
INODSF5331 | Version version is not installed |
Explanation |
The required software version is not installed. |
Action |
please contact your software supplier. |
INODSF5332 | Invalid structure level strlev |
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. |
INODSI1010 | Backup file from older version version |
Explanation |
Indicates that the input backup file is from a previous version. |
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. |
INODSI1019 | Database of older version version |
Explanation |
The database used for restore is from a previous version. |
Action |
No action required. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
INODSI1327 | Database stopped |
Explanation |
The database has been stopped. |
Action |
No action required. |
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. |
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 |
INODSI1384 | Setting of parname=parval |
Explanation |
no description available |
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. |
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: vers, level level |
Explanation |
This informational message states the version and level of the dump file. |
Action |
Select the version displayed. |
INODSI1422 | Using backup filename |
Explanation |
Indicates the backup which is used to create the new database. |
Action |
No action required. |
INODSI1423 | Using location location |
Explanation |
Indicates the location which is to be used for the database spaces. |
Action |
No action required. |
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 no (location name) has successfully finished |
Explanation |
The specified database space has been created. |
Action |
No action required. |
INODSI1467 | Tamino name modifierversion on system info |
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 db_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 db_name has been deleted |
Explanation |
The database with the given name has been successfully deleted. |
Action |
No action required. |
INODSI1474 | 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. |
INODSI1475 | Database db_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=chkpt |
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 master dbname |
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. |
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. |
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. |
INODSI2190 | Doctype doctype has been loaded |
Explanation |
The specified doctype has been successfully loaded. |
Action |
No action required. |
INODSI2196 | Connection to master database master dbname 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. |
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 customername sub-licensed by partnername with ID partnerid |
Explanation |
This is a display of customer/partner information from the license file. |
Action |
No action required. |
INODSI2312 | Licensed for customername with ID customerid sub-licensed by partnername |
Explanation |
This is a display of customer/partner information from the license file. |
Action |
No action required. |
INODSI2313 | Licensed for customername with ID customerid sub-licensed by partnername with ID partnerid |
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 customername sub-licensed by partnername with ID partnerid, 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 customername with ID customerid sub-licensed by partnername, 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 customername with ID customerid sub-licensed by partnername with ID partnerid, 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 'backupkey' (from) |
Explanation |
The identification of the last created backup is displayed. |
Action |
No action required. |
INODSI2344 | backup key 'backupkey' (from) |
Explanation |
This is a display of backup information. |
Action |
No action required. |
INODSI2345 | backup key 'backupkey' (initial backup) |
Explanation |
This is a display of backup information. |
Action |
No action required. |
INODSI2346 | Deleting disabled backup from backup_date |
Explanation |
A disabled backup file is being deleted. |
Action |
No action required. |
INODSI3469 | Dataset dsn created on date |
Explanation |
The dataset was created on the specified date. |
Action |
No action required. |
INODSI5263 | Restoring pending transactions |
Explanation |
Pending global transactions are being restored during the server startup processing. |
Action |
No action required. |
INODSI5270 | Use parameter "param" 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 extnumber 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 no |
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. |
INODSS1089 | Creating database with reorganization ... |
Explanation |
The database will be created from a backup with defragmentation of the database layout. |
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 modifierversionmodifier2 on system info |
Explanation |
This is an informational message. |
Action |
No action required. |
INODST1752 | Database database name Session session number (name modifierversion on system info, process ID pid) |
Explanation |
This is an informational message. |
Action |
No action required. |
INODST1753 | Database database name Read-Only Session (name modifierversion on system info, process ID pid) |
Explanation |
This is an informational message. |
Action |
No action required. |
INODST1766 | Database database name Replication Session (name modifierversion on system info, processID pid) |
Explanation |
The server started for a replication database. |
Action |
No action required. |
INODST1781 | Start of product name on system info |
Explanation |
This is an informational message. |
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 errno 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 comp called at extension point extp returned response rsp |
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 err - int_err |
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 err - int_err |
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 err - int_err |
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 servername 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 errno (errtxt) when opening database space space no (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. |
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. |
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. |
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. |
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. |
INODSW1409 | Error when opening database space space no (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 errno when opening database space space no (path) |
Explanation |
The specified operating system error has occurred. |
Action |
Please consult the manufacturer's manual. |
INODSW1414 | System error errno when opening database space space no (path) |
Explanation |
The specified operating system error has occurred. |
Action |
Please consult the manufacturer's manual. |
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. |
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 no (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 no 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: resp |
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. |
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. |
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. |
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. |
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 (lbp MB) exceeds the machine's physical memory size (pms 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 (max_threads) 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 master dbname 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 err) |
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. |
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 customername sub-licensed by partnername with ID partnerid 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 customername with ID customerid sub-licensed by partnername 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 customername with ID customerid sub-licensed by partnername with ID partnerid 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 customername sub-licensed by partnername with ID partnerid 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 customername with ID customerid sub-licensed by partnername 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 customername with ID customerid sub-licensed by partnername with ID partnerid 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 customername sub-licensed by partnername with ID partnerid 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 customername with ID customerid sub-licensed by partnername 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 customername with ID customerid sub-licensed by partnername with ID partnerid 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 customername sub-licensed by partnername with ID partnerid 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 customername with ID customerid sub-licensed by partnername 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 customername with ID customerid sub-licensed by partnername with ID partnerid 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 (param), 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 subc |
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. |
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: sorteff % |
Explanation |
This is the calculated efficiency of the sort file during the index process. |
Action |
No action required. |
INOINI2462 | Work pool efficiency: workeff % |
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 (desc) |
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 (desc) |
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: indexerr |
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 blockno |
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 blockno |
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 no 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 no |
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 = loaded_doctypes; actual number of doctypes = actual_doctypes |
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. |
INOSAE7351 | Duplicate attribute not allowed in element context |
Explanation |
The result element will contain multiple attributes of the same name. This is not allowed in XML. |
Action |
Please verify your query for atrribute construction. |
INOSAE7352 | No serialization for attributes without element context |
Explanation |
A serialization of attributes without element context was requested but is undefined. |
Action |
Please verify that the atrribute construction belong to an element context. |
INOSAE7353 | ino:document serialization supports only one document in serialization |
Explanation |
The ino:document serialization supports only the serialization of a single document. |
Action |
The query returns more than one document. Correct the query and rerun. |
INOSAE7354 | ino:serialization supports only the serialization of document nodes |
Explanation |
The ino:document serialization supports only the serialization of document nodes. |
Action |
Verify that the query returns only nodes of type document. |
INOSAE7356 | ino:document serialization has no Query Result |
Explanation |
The query returned no matching document. |
Action |
Correct the query so that it delivers one single document node. |
INOSAI7355 | Internal error |
Explanation |
During the serialization an internal error occurred. |
Action |
Please contact your software supplier. |
INOSXE6704 | Invalid character 'character' in name for compiler settings |
Explanation |
Names for compiler settings must start with a letter and may be followed by letters or digits. |
Action |
Use a name that obeys this rule. |
INOSXE6705 | Settings for default parameter must not be changed |
Explanation |
The name 'default' is reserved for the compiler settings defined by the Tamino installation. |
Action |
Use a name other than 'default' to save these compiler settings. |
INOSXE6706 | No configuration parameters found for compiler 'compiler' |
Explanation |
The current compiler for Direct X-Tension projects is currently set to the compiler indicated; however, one or all of its configuration parameter files have been deleted. |
Action |
Use the default compiler as your current compiler; check your Tamino installation. |
INOSXE6707 | X-Tension: COM initialization failed |
Explanation |
During X-Tension initialization the initialization of the COM library failed. No COM-based extension functions are available during this server session. |
Action |
If COM-based server extension functions are required, fix the COM problem and start the Tamino server again. |
INOSXE6709 | Invalid usage entry: 'value' |
Explanation |
The Usage entry found in file 'Install.xml' could not be recognized. |
Action |
Check the documentation for valid values. |
INOSXE6710 | Function 'function' not usable as 'usage' |
Explanation |
This function cannot be used as the function type indicated. The function's parameter count or parameter datatypes do not correspond to the specified function type. |
Action |
Please check the 'Usage' entry in file 'Install.xml' as well as the parameter specification of the current function. See the documentation for the parameters required for the given Usage. It is strongly recommended to use the X-Tension development tools to define new X-Tension functions. |
INOSXE6711 | Value missing for Init Function 'func' |
Explanation |
The X-Tension function indicated has been declared as Init Function. However, values are missing for one or more of its parameters. |
Action |
Use the X-Tension tools to create the X-Tension function and be careful editing the file Install.xml. |
INOSXE6712 | The server extension crashed or threw an unknown exception |
Explanation |
Either the server extension has crashed or it threw an exception that could not be caught by the Tamino Server. |
Action |
Please contact the vendor of the server extension. |
INOSXE6713 | Extension tried to open message box. Message: 'message'. |
Explanation |
It is not allowed to display message boxes in a server extension. This terminates the current server extension function. |
Action |
Please check the server extension code carefully. Maybe the C/C++ runtime system tried to open an assertion box because of programming errors in the server extension. |
INOSXE6714 | Value is not of the selected data type 'type' |
Explanation |
The value entered cannot be converted to the data type selected in the 'Add Param' box. |
Action |
Please check the value entered and the data type selected in the 'Add Param' box. See the documentation of Tamino X-Tension for more details on allowed values. |
INOSXE6715 | Extension function 'func': Value of parameter 'param' is not of selected data type type |
Explanation |
The value entered cannot be converted to the data type specified for this parameter. |
Action |
Please check the value entered and the data type specified for this parameter. See the documentation of Tamino X-Tension for more details on allowed values. Use the Tamino X-Tension tools to specify parameter values! |
INOSXE6716 | Unexpected error during callback function 'function' |
Explanation |
An unexpected error occurred during a call of a callback function. Probably it has been called with one or more incorrect parameters. |
Action |
Check the documentation and your server extension code for the correct use of this callback function. |
INOSXE6717 | Server extension function not found |
Explanation |
The desired function name was not found in the SXS repository. Maybe the function name is incorrect, or the function is not installed or was deinstalled. |
Action |
Check and correct the function name or server extension installation. |
INOSXE6725 | Callback not allowed in init function |
Explanation |
An SxsSetProperty callback is not allowed from a server extension init function. |
Action |
Remove the SxsSetProperty callback from your server extension init function and retry the operation. |
INOSXE7000 | Java server extension must have a package name |
Explanation |
The package name for a Java server extension must not be empty. |
Action |
Define a package name, e.g. "package com.softwareag.mysxs". |
INOSXE7001 | File name 'file.sxp' may not be changed |
Explanation |
Only the directory may be selected; the file name must remain unchanged. |
Action |
Select a directory. |
INOSXE7006 | XML callback failed. Transaction was rolled back. |
Explanation |
No more information. |
Action |
Try with a modified XML request. |
INOSXE7009 | Tamino X-Tension not available |
Explanation |
It is not possible to call a Tamino server extension because either X-Tension is not licensed or the X-Tension feature is not available on this platform. |
Action |
If possible, buy a license for Tamino X-Tension. |
INOSXE7010 | Project must be rebuilt before packing. Reason: 'reason'. |
Explanation |
The project must be rebuilt. See 'reason' for more information. |
Action |
Call Build / Build <project name> in the Developer Studio before packing. |
INOSXE7014 | Main class file cannot be removed |
Explanation |
In the Packaging Dialogue of the X-Tension Builder, the class file is about to be removed that contains the main class of the current server extension. |
Action |
Do not remove this class file from the list or select a jar file containing this class. |
INOSXE7015 | Callback not allowed in event function |
Explanation |
From Tamino server event functions, XML and ODBC callback are not allowed. |
Action |
Remove the callback call from your server extension code. |
INOSXE7016 | Illegal database command in callback |
Explanation |
A database command that is not allowed in callbacks was called in a callback. |
Action |
Remove the database command from the callback and try again. |
INOSXE7017 | Tamino server error when calling callback |
Explanation |
An error occurred in the Tamino server when processing the callback, perhaps an XML or query syntax error. |
Action |
Method SXJBase.SXSGetInoMsgNo ( ) gives the error code of the Tamino server. |
INOSXE7018 | Not enough memory for callback |
Explanation |
The Tamino server could not allocate enough memory to process the callback. |
Action |
Try to repeat your query when the Tamino server is less loaded. |
INOSXE7019 | SQL error when calling ODBC callback |
Explanation |
An SQL error occurred while processing an ODBC callback, perhaps due to an SQL syntax error. |
Action |
Method SXJBase.SXSGetSQLMsgNo ( ) gives the SQL error code. |
INOSXE7020 | Illegal handle type for ODBC callback |
Explanation |
The ODBC callback methods SxsSQLAllocHandle and SxsSQLFreeHandle are only allowed for statement handles of type SQL_HANDLE_STMT. |
Action |
We recommend that you use the constant SXJBase.SQL_HANDLE_STMT as the parameter handle type. |
INOSXE7021 | Commit and rollback are not allowed in callbacks |
Explanation |
You must not use the database commands "commit" or "rollback" in your server extensions. |
Action |
Remove these commands from the server extension and try again. |
INOSXE7022 | Result buffer for callback not initialized |
Explanation |
Result buffers for callbacks must not be null, but should be initialized with an empty string. |
Action |
Ensure that all result buffers are initialized. |
INOSXE7023 | Function 'name' failed, because XML callback failed with error 'no' |
Explanation |
An XML callback failed while trying to perform a write operation. To avoid inconsistencies, the extension function must return with an error. |
Action |
Check the error caused by the XML callback and fix the problem that caused it to fail. |
INOSXE7024 | COM error when calling callback |
Explanation |
A COM error occurred during a callback. |
Action |
Consult your COM documentation. |
INOSXE7025 | Another server extension deinstallation is running |
Explanation |
Only one server extension can be deinstalled at any given time. |
Action |
Wait until the other deinstallation procedure has finished. |
INOSXE7026 | Deinstallation timed out. The server extension is in use. |
Explanation |
A server extension cannot be deinstalled as long as an instance of it is in use. The deinstallation procedure has timed out. |
Action |
Try it later. If there is a very long running instance of the server extension, try to stop it. |
INOSXE7027 | The function cannot be executed. The server extension is being deinstalled. |
Explanation |
This function belongs to a server extension that is just being deinstalled. |
Action |
The function cannot not be called again. If you need to, contact the database administrator. |
INOSXE7032 | Cannot create directory 'dir' |
Explanation |
This directory cannot be created. Maybe the disk drive is unavailable or write protected. |
Action |
Check the given path and your disk drive. |
INOSXE7034 | Server extension 'source' threw exception 'errnr', 'errtext' |
Explanation |
The server extension threw an exception. The number and message of the exception are delivered. |
Action |
See the documentation of the server extension in question for more information. |
INOSXE7040 | Extension function name too long: 'name' |
Explanation |
The complete extension function name, consisting of the extension's name plus the function name plus a dot, must not exceed the length of 80 characters. |
Action |
Select a shorter name. |
INOSXE7041 | Wrong character in field: 'char' |
Explanation |
Some special characters (ampersand, "less than", "greater than") are not allowed in comment fields for a server extension. This affects the "Short description" fields and the "Author" field. |
Action |
Avoid these characters. |
INOSXE7045 | X-Tension Trace failed. Transaction was rolled back. |
Explanation |
An internal server error occurred while X-Tension Trace information was written to the Tamino server. |
Action |
Deactivate X-Tension Trace |
INOSXE7046 | XML Callback failed in user session. Transaction must be rolled back. |
Explanation |
A writing XML call from a server extension failed. The current transaction should be rolled back for consistency reasons. |
Action |
Perform a rollback request. |
INOSXE7047 | X-Tension Trace failed in user session. Transaction must be rolled back. |
Explanation |
An internal server error occurred. The current transaction should be rolled back for consistency reasons. |
Action |
Deactivate X-Tension Trace |
INOSXE7048 | Error starting help browser. Reason: 'reason'. |
Explanation |
The currently configured help browser could not be started. See "reason" for more details. |
Action |
Use the function "Help/Configure Help Browser" to change your current help browser. |
INOSXE7049 | 'execfile' execution failed: rc = rc |
Explanation |
The external program 'Program name' was successfully started but it returned with error. |
Action |
See the context of this error message for more information. |
INOSXE7051 | COM error 'errno' occurred: 'errtext' |
Explanation |
A COM error occurred. The COM error number of type HRESULT is delivered. |
Action |
Consult the COM documentation for more information. |
INOSXE7052 | COM error 'errno' calling 'dllname': 'errtext' |
Explanation |
A COM error occurred. The COM error code of type HRESULT and the name of the Tamino server extension DLL which was called is delivered. |
Action |
Consult the COM documentation for more information. |
INOSXE7053 | Error 'errno' calling data map: 'errtext' |
Explanation |
An error occurred when the Tamino server extension part of the data map was accessed. The error number and message received from the Tamino data map is delivered. |
Action |
Look up the delivered error number and see the action described there. |
INOSXE7054 | X-Tension system function cannot be deleted |
Explanation |
An attempt was made to delete a function which is needed for the X-Tension administration. |
Action |
No action required. |
INOSXE7055 | The server extension threw exception 'errtext'. |
Explanation |
The server extension threw an exception. The message and occasionally the number of the exception are delivered. |
Action |
See the documentation of the server extension in question for more information. |
INOSXE7056 | X-Tension caller: Not enough memory |
Explanation |
There was not enough memory for execution of the server extension function. |
Action |
Close some applications and try again. |
INOSXE7057 | X-Tension caller: internal error |
Explanation |
Internal errors occurred within the X-Tension administration structure. |
Action |
Please contact your software supplier. |
INOSXE7058 | X-Tension caller: got no spinlock. Reason: 'retval'. |
Explanation |
An error occurred within the thread synchronization. A server extension could not be locked. The return value received from the thread administration is delivered. |
Action |
Please contact your software supplier. |
INOSXE7059 | X-Tension caller: could not get data map information |
Explanation |
The X-Tension caller was unable to get any data map information. |
Action |
Please contact your software supplier. |
INOSXE7060 | Mapping function 'n': Wrong number of parameters implemented. Expected: 'm'. |
Explanation |
A Tamino server extension mapping function does not support the number of parameters needed for this function type. |
Action |
Install a correctly implemented server extension. |
INOSXE7061 | Extension function 'n': Wrong type of parameter 'm' implemented |
Explanation |
A mapping function does not support the correct parameter types. |
Action |
Compare the parameter type for this type of extension function as described in the manual with the parameter type supported by the extension function (found using Tamino Manager). Install a correctly implemented extension function. |
INOSXE7062 | X-Tension caller: initialization failed |
Explanation |
The X-Tension caller was not initialized when the Tamino server was started. It is impossible to call any extension function, maybe because server extension libraries could not be loaded. |
Action |
Check your Tamino installation. |
INOSXE7063 | X-Tension caller: 'No' server event calls failed |
Explanation |
A server event call to some server extensions failed. The number of failures is delivered. |
Action |
Please contact your software supplier. |
INOSXE7064 | Unexpected end of file encountered before end of source |
Explanation |
During the parsing of the X-Tension installation file, IDL file or one of the server extension source files, an unexpected end of file was found. |
Action |
Check the syntax of the file(s). |
INOSXE7065 | Syntax error. Token: 'Token'. |
Explanation |
An unspecified error was encountered during parsing near or at the place specified by 'Token'. |
Action |
Check the syntax of the X-Tension installation file. |
INOSXE7066 | Unbalanced tag / end tag: 'tag1' /' tag2' |
Explanation |
In the X-Tension installation file, the names of begin-tag and end-tag are different. |
Action |
Check the syntax of the X-Tension installation file. |
INOSXE7067 | Tag 'tagname' not found |
Explanation |
The specified mandatory tag was not found in the X-Tension installation file. |
Action |
Check the syntax of the X-Tension installation file. |
INOSXE7068 | Tag 'tagname' is not a value |
Explanation |
A simple value was expected for the specified tag, but a node has been found. |
Action |
Check the syntax of the X-Tension installation file. |
INOSXE7069 | Tag 'tagname' is not a node |
Explanation |
A node was expected for the specified tag, but a simple value has been found. |
Action |
Check the syntax of the X-Tension installation file. |
INOSXE7070 | Duplicate name: 'name' |
Explanation |
The specified tag name was found twice in the X-Tension installation file. |
Action |
Check the syntax of the X-Tension installation file. |
INOSXE7071 | Error 'character' expected |
Explanation |
The specified character was expected but not found in the X-Tension installation file or one of the server extension source files. |
Action |
Check the syntax of the X-Tension installation file and the server extension source files. |
INOSXE7072 | Error 'character' expected, eof found |
Explanation |
The specified character was expected, but an end of file was found in the X-Tension installation file or one of the server extension source files. |
Action |
Check the syntax of the X-Tension installation file and the server extension source files. |
INOSXE7073 | IDL file 'segment name' is corrupt |
Explanation |
A syntax error was found in the IDL file for the definition of the server extension interface at or near the specified keyword. |
Action |
Check the syntax of the IDL file. |
INOSXE7074 | 'SXF' not defined in interface |
Explanation |
The specified function has been defined in the X-Tension installation file but it had not been entered into the IDL file for the server extension interface. |
Action |
Remove the function definition from the X-Tension installation file and use the X-Tension Developer Studio add-in to define a new one. |
INOSXE7075 | Return type must be HRESULT, not 'type' |
Explanation |
A COM server extension must always return HRESULT. |
Action |
Use the [retval] attribute for the last parameter as a return value of the server extension function. |
INOSXE7076 | Method 'method': Different parameter names: 'param1' / 'param2' |
Explanation |
The parameter name of the indicated server extension function in the X-Tension installation file is different from that defined in the IDL file. |
Action |
Check the implementation of the server extension function; use the X-Tension Developer Studio add-in to define a server extension function. |
INOSXE7077 | Too many parameters: 'SXF' |
Explanation |
The specified server extension function has been implemented with more parameters than are defined in the X-Tension installation file. |
Action |
Check the implementation of the server extension function; use the X-Tension Developer Studio add-in to define a server extension function. |
INOSXE7078 | Cannot map parameter type |
Explanation |
A parameter type is used in the COM interface that cannot be used for server extension function parameters. |
Action |
Use the X-Tension Developer Studio add-in to define a server extension function. |
INOSXE7079 | Server extension implementation file could not be found |
Explanation |
The X-Tension Developer Studio add-in could not find the file with the implementation of the class for the server extension. |
Action |
Use the X-Tension development tool to create a server extension. |
INOSXE7080 | Unknown XML data type: 'type' |
Explanation |
The specification of the XML data type for a server extension function parameter is wrong. See the documentation for allowed data types. |
Action |
Use the X-Tension Developer Studio add-in to define a new server extension function. |
INOSXE7081 | Unknown programming language data type: 'type' |
Explanation |
The function implementation uses a data type for one of its parameters that is not supported when using this function as a server extension function. See the documentation for the allowed data types in this programming language |
Action |
Use the X-Tension development tools to define a server extension function. |
INOSXE7082 | Unknown execution mode: 'mode' |
Explanation |
The specified server extension execution mode is wrong. Allowed modes are: COM-INPROC, COM-LOCAL. |
Action |
Use the Tamino Manager to change this mode. |
INOSXE7083 | Wrong numeric value: 'val' |
Explanation |
The value was expected to be numeric but the given value is not numeric. |
Action |
Enter a numeric value here. |
INOSXE7084 | Wrong parameter position |
Explanation |
The parameter position in the X-Tension installation file must start at 1. |
Action |
Check the parameter position values. Use X-Tension Developer Studio add-in to define a new server extension function. |
INOSXE7085 | Cannot open file 'name' |
Explanation |
The specified file could not be opened. |
Action |
Check if this file really exists, or if it is locked by another process. |
INOSXE7086 | Wrong version format: 'string' |
Explanation |
The server extension version is supposed to be of the form major.minor |
Action |
Check the server extension version. |
INOSXE7087 | Event function 'function' not found |
Explanation |
An event function has been specified in the SXS-EVENT-FUNCTION tag of the X-Tension installation file, but it could not be found in an SXS-FUNCTION tag. |
Action |
Delete the event function specification tag and use the X-Tension Developer Studio add-in to specify a new one. |
INOSXE7088 | Wrong document type for X-Tension administration: 'type' |
Explanation |
The document type (second level tag) of the X-Tension administration file is wrong. Allowed types are: SXS-INSTALL, SXS-DELETE, SXS-SHOW, SXS-RETURN. |
Action |
For a server extension installation, only SXS-INSTALL is valid. |
INOSXE7089 | Missing XML attribute 'attribute' for SXS-SHOW |
Explanation |
No attribute is given for the X-Tension administration type tag SXS-SHOW. |
Action |
One of the attributes list, object, function, permission, document must be given for the SXS-SHOW tag. |
INOSXE7090 | Wrong XML attribute: 'attribute' |
Explanation |
A wrong attribute is given for the X-Tension administration type tag SXS-SHOW. |
Action |
One of the attributes list, object, function, permission, document must be given for the SXS-SHOW tag. |
INOSXE7091 | Wrong parameter attribute: 'attribute' |
Explanation |
A wrong parameter attribute has been specified in the X-Tension installation file. Allowed attributes are: input, output, inout, retval. |
Action |
Use the X-Tension Developer Studio add-in to define a new server extension function. |
INOSXE7092 | No current project |
Explanation |
There is no project open in Developer Studio. The X-Tension add-in will not work. |
Action |
Open a server extension project first. |
INOSXE7093 | This is not a C/C++ project |
Explanation |
The X-Tension add-in will not work for Java or Visual Basic projects. |
Action |
Open a C/C++ project. |
INOSXE7094 | This is not an X-Tension project |
Explanation |
The current project has not been created by an X-Tension development tool. |
Action |
Use the X-Tension development tool to create a server extension. |
INOSXE7095 | File 'filename' is read-only |
Explanation |
The specified file is read-only. Therefore, the X-Tension Developer Studio add-in cannot add the specifications for the new server extension function to it. |
Action |
Change the ReadOnly parameter of the specified file. |
INOSXE7096 | System error: 'errtext' |
Explanation |
An operating system error occurred in the X-Tension Developer Studio add-in. |
Action |
Check the operating system documentation for further details. |
INOSXE7099 | Cannot write to file 'filename' |
Explanation |
The file has been opened, but a write operation failed. Possibly the disk is full. |
Action |
Check your hard disk space. |
INOSXE7100 | Wrong package file: 'filename' |
Explanation |
The file specified is not an output file of the X-Tension Developer Studio add-in package function. |
Action |
Only use package files created by the X-Tension Developer Studio add-in. |
INOSXE7101 | Could not get XML session status. Server extension function rolled back at request end. |
Explanation |
The X-Tension caller could not determine whether there was a regular or an anonymous XML session. So the Tamino server event 'rollback' was sent to all server extensions. |
Action |
No action required. |
INOSXE7102 | Initialization of server extensions: server events not activated |
Explanation |
The Tamino server events could not be activated when the Tamino server was started. Server extensions are not initialized and will not work. |
Action |
Restart the Tamino server. If this does not give the desired result, please contact your software supplier. |
INOSXE7103 | Developer Studio automation error 'errno' (errtext) |
Explanation |
The add-in caused an error when executing a Developer Studio command. |
Action |
Consult the Developer Studio documentation for further information. |
INOSXE7104 | Method 'method' could not be found in file 'objfile' |
Explanation |
The method indicated is not defined in the current server extension object file (Java class file or DLL/Shared Object), or another severe error occurred when accessing the server extension object file. |
Action |
Check the server extension project for the desired method. Use the X-Tension development tools for developing server extensions! |
INOSXE7105 | Project must be rebuilt before packing: 'file' is newer |
Explanation |
One of the project sources is newer than the resulting server extension package. |
Action |
Call Build / Build <project name> in the Developer Studio before packing. |
INOSXE7106 | One or more input fields are empty |
Explanation |
All fields of this form must be set, but at least one field is empty. |
Action |
Make sure that all fields are correctly set. |
INOSXE7107 | 'name' is not a valid identifier |
Explanation |
The name entered does not match C/C++ naming conventions. |
Action |
Check the name for proper syntax. |
INOSXE7108 | Value for 'valuename' of a server extension not found in data map |
Explanation |
A value for the specified name of a server extension was expected in the data map but is not present. The problem occurs due to problems at installation or in the repository. Here, the specified name is the name of an expected value. |
Action |
Re-install the server extension. |
INOSXE7109 | Memory allocation failed |
Explanation |
Memory allocation failed. |
Action |
Please contact your software supplier. |
INOSXE7110 | Character conversion failed; error code = 'errcode' |
Explanation |
An internal character conversion failed. |
Action |
See the Tamino documentation for the given error code. Check if Tamino is properly installed. |
INOSXE7113 | Cannot find function 'funcname' in library 'libname' |
Explanation |
The specified function name could not be found in the library. Maybe there is a version problem. |
Action |
Check your Tamino installation. |
INOSXE7114 | Java error: Errtext: 'errtext'. Stacktrace: 'trace'. |
Explanation |
A Java error occurred. See "Errtext" for more specific details. "Stacktrace" is the exception stack trace. |
Action |
See "Errtext" for more specific details and correct the code accordingly. |
INOSXE7115 | Cannot create Java virtual machine; error 'errcode' |
Explanation |
The Java virtual machine could not be started. |
Action |
Check the Java documentation for the given error code. |
INOSXE7116 | Function 'sxfname' not found in server extension 'sxsname' |
Explanation |
The function could not be found in the server extension. Probably the server extension implementation has been changed after installation. |
Action |
Try to re-install the server extension. |
INOSXE7117 | Illegal call for Java method 'methodname' in class 'classname' |
Explanation |
An error occurred during a call for a Java method. Probably the parameter count or the type(s) of at least one parameter is incorrect. For a server extension function, its implementation may have changed since the last installation. |
Action |
Re-install this server extension. |
INOSXE7118 | 'package' not available on this platform |
Explanation |
The package specified (COM, Java or Direct) is not available on this platform. Server extensions based on this package cannot be executed. |
Action |
No action possible. This server extension cannot be run. |
INOSXE7119 | 'package' not installed on this platform |
Explanation |
The package specified (COM or Java) is not installed on this platform. |
Action |
To run server extensions based on this package, install the specified package. |
INOSXE7120 | X-Tension caller: parameter overflow, function 'name' parameter number 'no' |
Explanation |
The input value was too small or too big. |
Action |
Change the input value and try again. |
INOSXE7121 | XQL query function 'n': Wrong number of parameters. Required: 'm'. |
Explanation |
The user passed a wrong number of parameters to a function called from within an XQL query. |
Action |
Repeat the call with the correct number of parameters. |
INOSXE7122 | XQL query function 'n': Wrong type of parameter 'm' |
Explanation |
The user input is of the wrong data type. |
Action |
Get information about parameter types of called functions (see the Tamino Manager or the third party manual for the corresponding server extension) and repeat the call with the correct input. |
INOSXE7123 | Java error during initialization of Java server extension: 'errtext' |
Explanation |
The error text gives detailed information about the error. |
Action |
Correct the fault and try again. |
INOSXE7124 | Java error during call: 'errtext' |
Explanation |
The error text gives detailed information about the error. |
Action |
Correct the fault and try again. |
INOSXE7125 | Java error during server extension function parameter handling: 'errtext' |
Explanation |
The error text gives detailed information about the error. |
Action |
Correct the fault and try again. |
INOSXE7126 | Server extension failed |
Explanation |
An error occurred when a Tamino server extension was called. The message is followed by another more detailed message. |
Action |
Analyze the detailed message and act accordingly. |
INOSXE7127 | X-Tension : Java initialization failed |
Explanation |
During X-Tension initialization the initialization of the Java virtual machine failed. No Java-based extension functions are available during this server session. |
Action |
If Java-based server extension functions are required, fix the Java problem (e.g. paths and internal configuration store entries) and start the Tamino server again. |
INOSXE7129 | 'location': Got no spinlock. Reason: 'retval'. |
Explanation |
There is no lock available for your thread. |
Action |
Try again later. |
INOSXE7130 | Internal error when 'location' |
Explanation |
An unknown internal error occurred. |
Action |
Please contact your software supplier. |
INOSXE7132 | 'unusedinfrastructur' infrastructure is not available or currently disabled |
Explanation |
The X-Tension infrastructure specified is either not available in this environment or is currently configured as disabled in the Tamino server parameters. |
Action |
If the required infrastructure is available in this environment, turn on the appropriate switch of the Tamino server parameters and restart the Tamino server to activate it. If the infrastructure is not available, the relevant server extension code attempting to use it should be modified to utilise a supported infrastructure. |
INOSXE7136 | Wrong command line for the server extension wrapper tool: 'arg' |
Explanation |
The command line for the server extension wrapper tool has incorrect syntax. |
Action |
Please check the documentation for the command line syntax of the server extension wrapper tool or use the server extension development tools to set up a direct server extension project. |
INOSXE7137 | Duplicate option 'c' |
Explanation |
The given option may not occur more than once in the command line for the server extension wrapper tool. |
Action |
Please check the documentation for the command line syntax of the server extension wrapper tool or use the server extension development tools to set up a direct server extension project. |
INOSXE7138 | Wrong option 'c' |
Explanation |
The given option is invalid in the command line for the server extension wrapper tool. |
Action |
Please check the documentation for the command line syntax of the server extension wrapper tool or use the server extension development tools to set up a direct server extension project. |
INOSXE7140 | No valid JVM, install valid JVM or switch X-Tension Java Usage to 'NO' |
Explanation |
Error detected when loading a JVM for current Tamino version |
Action |
Check if JVM is installed, if a valid JVM Version is installed or switch X-Tension Java Usage to 'NO'. |
INOSXE7141 | Server extension 'name' already locked |
Explanation |
The server extension is locked by another operation. |
Action |
Retry the requested operation when the lock has been removed. |
INOSXE7142 | Server extension 'name' is active |
Explanation |
The server extension is in use. |
Action |
Retry the requested operation when the server extension has finished. |
INOSXE7143 | Server extension 'name' not found |
Explanation |
The server extension does not exist. |
Action |
Correct the server extension name and retry the operation. |
INOSXE7144 | Server extension function 'name' not found |
Explanation |
The server extension function does not exist. |
Action |
Correct the function name and retry the operation. |
INOSXE7145 | Wrong modification operation 'type' |
Explanation |
The requested modification operation is not implemented. |
Action |
Correct the modification operation type and retry the operation. |
INOSXE7146 | Wrong execution mode 'mode' |
Explanation |
The requested execution mode is not allowed. |
Action |
Correct the execution mode and retry the operation. |
INOSXE7147 | Files for server extension 'name' not restored |
Explanation |
Some files of the server extension have not been restored. |
Action |
Ensure that the Tamino server has write access to the file system and retry the operation. |
INOSXE7148 | Files for server extension 'name' not removed |
Explanation |
Some files of the server extension have not been removed. |
Action |
Ensure that the files are not locked by another action and retry the operation. |
INOSXE7149 | Files for server extension 'name' not stored |
Explanation |
Some files of the server extension have not been stored. |
Action |
Ensure that the files are not locked by another action and retry the operation. |
INOSXE7150 | Installation document for server extension 'name' not stored |
Explanation |
The installation document of the server extension has not been stored. |
Action |
Ensure that the installation document is not locked by another action and retry the operation. |
INOSXE7151 | Event Function call failed for server extension: a, Event: b |
Explanation |
Event functions are for cleaning up server extension data after commit, rollback, session end and so on. See the X-Tension manual (server extension Functions/Server Event Functions), for information about which event failed. |
Action |
Analyze the cause of failure. If necessary, ask the programmer or vendor of the server extension. Check the data that was written outside the Tamino server by the failed extension for consistency. |
INOSXE7152 | Attribute 'hidden' cannot be assigned to or removed from this parameter |
Explanation |
An attempt was made to assign or remove the 'hidden' attribute. This operation is only successful if the parameter has the 'input' direction (for assignment) or the parameter is 'hidden' (for removal). |
Action |
Check the server extension function and its parameters and read the documentation. |
INOSXE7153 | This parameter cannot be assigned a default value |
Explanation |
To assign a default value to a parameter, this parameter must have the 'input' direction. |
Action |
Check the current server extension function and its parameters. |
INOSXE7154 | Wrong position for optional / hidden parameter |
Explanation |
The order for parameters must be: mandatory - optional - hidden - return value. |
Action |
Please check the order of the server extension function's parameters and their usage. |
INOSXE7158 | Server extension function parameter 'name' not found |
Explanation |
The server extension function parameter does not exist. |
Action |
Correct the parameter name and retry the operation. |
INOSXE7160 | Duplicate occurrence of 'functiontype' |
Explanation |
Only one event function or init function may be defined within a server extension. |
Action |
Check your server extension and delete one of the functions that is superfluous, or use the X-Tension development tools to create and edit the server extension. |
INOSXE7161 | Invalid input for field: field |
Explanation |
The user input for the specified field is invalid. Either invalid characters have been used or the format of the characters used is incorrect. |
Action |
Please correct the specified field. |
INOSXE7162 | Document not found for specified ino:id/docname |
Explanation |
A document could not be found using the specified ino:id or docname. |
Action |
Please specify a valid ino:id or docname. |
INOSXE7255 | Java Exception |
Explanation |
Specified Java exception occurred |
Action |
Resolve the specified Java exception |
INOSXF6718 | Timeout during execution of server extension function |
Explanation |
Possible reasons are: 1) There is an endless loop in the server extension function. 2) A server extension function is executed with endless recursion. |
Action |
Check the server extension carefully. For example, calling the callback SxsXmlProcess will result in an endless recursion if the collection name is the same as the current server extension function is assigned to. |
INOSXF6719 | Process 'exefile' (for Direct Local) has stopped with rc = rc |
Explanation |
The external process for X-Tension direct infrastructure (local mode) has aborted. See error for more details. |
Action |
Check your server extension. Probably it killed the external process for local mode. |
INOSXF6720 | Stack overflow in server extension function |
Explanation |
A stack overflow occurred during call of a server extension function. |
Action |
Check your server extension. Perhaps it has endless recursion. |
INOSXF7028 | Illegal call of Connect/Disconnect |
Explanation |
This error may occur in a Visual Basic or Natural implementation of a server extension. Reasons for this error may be: The Connect and Disconnect methods of the InoCallback interface have been called outside ISXSConn_Connect or ISXSConn_Disconnect or have been called there more than once. |
Action |
Implement ISXSConn_Connect and ISXSConn_Disconnect exactly as shown in the documentation. Do not call the Connect and Disconnect methods of InoCallback outside ISXSConn_Connect and ISXSConn_Disconnect. |
INOSXF7030 | 'tool' does not support server extensions of type 'type' |
Explanation |
The X-Tension Builder tried to open a COM server extension. |
Action |
With the X-Tension Builder, open Java or Direct server extensions only. |
INOSXF7033 | Server extension 'sxsname' not properly installed. Reason: 'reason'. |
Explanation |
One or more installation steps for this server extension have been skipped or failed. See 'Reason' for more information. |
Action |
Use the X-Tension Administration of the Tamino Manager to install the server extension. |
INOSXF7035 | Cannot load library sxcall |
Explanation |
The library sxcall necessary for Tamino X-Tension cannot be loaded. Therefore no server extensions can be executed in this Tamino installation. |
Action |
Check your Tamino installation. |
INOSXF7036 | Cannot load a function in library sxcall |
Explanation |
Not all functions necessary to run Tamino X-Tension can be found in library sxcall. Therefore no server extensions can be executed in this Tamino installation. Probably there is a version mismatch between the library sxcall and the rest of Tamino. |
Action |
Check your Tamino installation. |
INOSXF7037 | Internal configuration store entry not found |
Explanation |
An internal configuration store entry necessary to initialize Tamino X-Tension or one of the Tamino X-Tension components cannot be found. If this error occurs during Tamino startup, no server extensions can be executed in this Tamino installation. |
Action |
Check your Tamino installation. |
INOSXF7038 | Cannot find current version in internal configuration store |
Explanation |
The 'current version' entry in the internal configuration store that is necessary to initialize Tamino X-Tension or one of the Tamino X-Tension components cannot be found. If this error occurs during Tamino startup, no server extensions can be executed in this Tamino installation. |
Action |
Check your Tamino installation. |
INOSXF7039 | Cannot load jvm library |
Explanation |
The jvm library (libraries) necessary to run Java server extensions cannot be loaded. Therefore no server extensions can be executed in this Tamino installation. |
Action |
Check your Tamino installation as well as your Java installation. Look if $LD_LIBRARY_PATH on UNIX (or %PATH% on Windows) includes all required JDK directories. |
INOSXF7042 | Cannot find executable file 'execfile' |
Explanation |
The indicated file could not be found in any of the directories listed in PATH. |
Action |
Check installation(s) on your computer and check your PATH setting. |
INOSXF7043 | Tamino X-Tension not properly installed. Reason: 'reason'. |
Explanation |
The X-Tension development tool cannot create a new server extension project because Tamino X-Tension component is not properly installed on your computer. |
Action |
Use the Install Tool for a correct installation of Tamino X-Tension. |
INOSXF7044 | Error calling 'execfile'. Reason: 'reason'. |
Explanation |
An error occurred while trying to start an external process with the indicated file. See the additional text for more details. |
Action |
Check the given file for correctness. |
INOSXF7097 | Tamino X-Tension not properly installed |
Explanation |
The X-Tension development tool cannot create a new server extension project because Tamino X-Tension component is not properly installed on your computer. |
Action |
Use the Install Tool for a correct installation of Tamino X-Tension. |
INOSXF7098 | Fatal error |
Explanation |
An unspecified error occurred. |
Action |
Please contact your software supplier. |
INOSXF7111 | Server extension 'sxsname' not properly installed |
Explanation |
One or more installation steps for this server extension have been skipped or failed. |
Action |
Use the X-Tension Administration of the Tamino Manager to install a server extension. |
INOSXF7112 | Cannot load library 'libname': error 'rc' |
Explanation |
The specified library could not be loaded. Maybe it has been moved from its original location, or environment variables or internal configuration store entries have been changed since the last Tamino installation. |
Action |
Check your PATH and your Tamino installation. |
INOSXF7133 | No class has been found that can be used as a direct server extension class. |
Explanation |
Either there is no class defined in the given header file or none of the classes defined here can be used as a direct server extension. |
Action |
Please check the documentation about requirements for direct Server Extension classes or use the X-Tension development tools to create a Server Extension. |
INOSXF7134 | There are at least two classes ('class1', 'class2') that can be used as direct server extensions |
Explanation |
A header file that should be processed by the direct server extension wrapper tool may define only one class that can be used as a direct server extension. |
Action |
Please check the documentation on how to mark C++ classes for use as direct server extensions or move all class definitions except the direct server extension class to a different header file. |
INOSXF7155 | Internal error: 'id' |
Explanation |
A severe internal error occurred. |
Action |
Please note the value of the internal error and contact your software supplier. |
INOSXF7156 | Cannot start process 'exefile' for X-Tension direct infrastructure (local mode) |
Explanation |
The system cannot start a new process for X-Tension direct infrastructure (local mode). |
Action |
Check the existence of the file indicated. It should be located in directory Tamino/<version>/bin. |
INOSXF7157 | Process 'exefile' (for Direct Local) is not running |
Explanation |
The external process for X-Tension direct infrastructure (local mode) has aborted or is not running for other reason. |
Action |
Check your server extension. Perhaps it killed the external process for local mode. |
INOSXF7251 | Thread could not be attached to JVM, return code 'rc' |
Explanation |
The current XML worker thread could not be attached to the Java virtual machine. Tamino server extensions were not initialized. The return code is the return value of the JNI call "AttachCurrentThread()". |
Action |
Analyze why the Java call failed and solve the cause of the problem. Then start Tamino server again. |
INOSXF7252 | Metadata update failed: id |
Explanation |
Metadata update has failed. |
Action |
In the case of CentraSite database startup failure indicated by the production of the console message: "INOSXF7252: Metadata update failed" the following information is essential to analyse the problem. The most useful file in these circumstances is the "inosrv.txt" file. This is normally called something like AABinosrv.HH-MM-SS.txt and would normally be present in the same directory as the actual database data files. inoadmin set CentraSite "request log" "full" norestart inoadmin set CentraSite "X-Tension Java Options" "$-Dlog4j.configuration=file:/{full path to log4j.properties}" restart log4j.rootLogger=WARN, file log4j.logger.com.centrasite.centrasite.onstartup=DEBUG log4j.appender.file=org.apache.log4j.FileAppender log4j.appender.file.layout=org.apache.log4j.PatternLayout log4j.appender.file.layout.ConversionPattern=%d %8r [%t]%-5p %c{3} %x - %m%n log4j.appender.file.File={full path to log file} |
INOSXI6708 | X-Tension usage is currently disabled |
Explanation |
All of the X-Tension infrastructures (COM, Java and Direct) are currently disabled. |
Action |
Turn on the appropriate switch of the Tamino server parameters and restart the Tamino server. |
INOSXI6723 | JVM started with user options 'jvm_options' |
Explanation |
The JVM was started with the specified additional user options. |
Action |
No action required. |
INOSXI7029 | Finished searching the file |
Explanation |
The 'Find What' string has not been found after (Direction Down) or before (Direction Up) the current position. |
Action |
Deselect 'Match case' or select another string. |
INOSXI7050 | COM for server extension is deactivated |
Explanation |
COM for server extension is switched off. |
Action |
Switch on COM for server extension with Tamino Manager. |
INOSXI7128 | Java for server extension is deactivated |
Explanation |
Java for server extensions is switched off |
Action |
Switch on Java for server extension with the Tamino Manager |
INOSXI7131 | X-Tension 'unusedinfrastructur' usage is currently disabled |
Explanation |
The specified X-Tension infrastructure (COM, Java or Direct) is currently disabled. |
Action |
Turn on the appropriate switch of the Tamino server parameters and restart the Tamino server. |
INOSXI7253 | Metadata update succeeded: id |
Explanation |
Metadata update has finished successfully. |
Action |
None |
INOSXI7254 | Metadata update started. |
Explanation |
Metadata update has started. This may be a lengthy operation. |
Action |
None. |
INOSXV6726 | COM server extensions are deprecated |
Explanation |
COM server extensions are deprecated and will not be supported in future. |
Action |
Plan the replacement of your COM server extensions by using a different server extension infrastructure. |
INOSXW6700 | 'function' can no longer be used as 'functype' |
Explanation |
One of the parameters has been modified or deleted. Therefore this server extension function can no longer be used as the specified function type. |
Action |
Check the Tamino server extension documentation for the different function types. |
INOSXW6701 | At least one of the help files does not exist. It will be removed from the list. |
Explanation |
The Install.xml file for your current X-Tension project has an entry for a help file that no longer exists. It will be removed from your list of help files. |
Action |
Select a new file. |
INOSXW6702 | Warning: Settings for compiler 'compiler' already exist and will be overwritten |
Explanation |
Compiler and linker flags already exist for the compiler specified in this warning. Choosing 'OK' will overwrite these settings. |
Action |
Choose 'OK' to overwrite these settings or 'Cancel' to stop this action. |
INOSXW6703 | The path 'path' will be added to the list of executable files of Visual Studio |
Explanation |
Some libraries residing in Tamino system directories are needed to build a server extension. These directories must be listed in the "Executable files" section of your Visual Studio configuration. If not yet present, sxwizard will add these directories automatically. |
Action |
Click on OK to accept these changes to your Visual Studio configuration. If you click on Cancel, no changes will be made and sxwizard will be stopped. |
INOSXW6721 | Project will be moved from platform 'platform1' to 'platform2' |
Explanation |
This (SXS Direct) project has been created on platform1. It is now opened on a different platform platform2, and a new make file will be created such that it can be compiled on this new platform. |
Action |
Click OK to generate a new make file, or click cancel if you do not want to have a new make file created. However, this project probably cannot be compiled on this platform. |
INOSXW6722 | Project will be moved from an older Tamino version to platform 'platform' |
Explanation |
This (SXS Direct) project has been created by an older version of Tamino. It is now opened by a newer Tamino version on a different platform. A new make file will be created such that it can be compiled in this version and on this new platform. |
Action |
Click OK to generate a new make file, or click cancel if you do not want to have a new make file created. However, this project probably cannot be compiled in this Tamino version. |
INOSXW6724 | Unable to start JVM with user options 'jvm_options'. Starting with default options instead. |
Explanation |
Conflicting or incorrect user options were specified for the JVM, so the JVM could not start. The JVM will be started with the default options. |
Action |
Correct the user options specified for the JVM and restart the server. |
INOSXW6727 | The server extension generated a warning. |
Explanation |
The server extension has invoked the warning XML callback. This will insert a warning into the Tamino response. |
Action |
The warning message is for informational purposes. |
INOSXW6728 | Execution failed: command |
Explanation |
The specified operating system command failed. |
Action |
Check the SXS installation values for faults. |
INOSXW7002 | Existing server extension project at 'pathname' will be overwritten |
Explanation |
A server extension project already exists in the given directory. It will be overwritten if you select "Finish". |
Action |
Press "OK" to overwrite this project or select another directory. |
INOSXW7003 | Java initialization failed. Reason: 'errno', 'errtxt'. |
Explanation |
Tamino was not able to create a Java virtual machine. Java based server extensions will not work. |
Action |
Make the Java virtual machine available to Tamino and start the Tamino server again or switch the server property X-Tension Java Usage to 'NO'. |
INOSXW7004 | Java thread initialization failed. Reason: 'errno', 'errtxt'. |
Explanation |
An XML worker thread could not be attached to the Java virtual machine. Java based server extensions will not work. |
Action |
Fix the problem of Java initialization and start the Tamino server again. |
INOSXW7005 | Initialization of COM library failed. Reason: 'errno', 'errtxt'. |
Explanation |
COM based server extensions will not work. |
Action |
Make the COM library available to the Tamino server, then start it again. |
INOSXW7007 | No license for Tamino X-Tension |
Explanation |
A special license must be bought to use the Tamino X-Tension feature. |
Action |
Buy a license for Tamino X-Tension. |
INOSXW7008 | Tamino X-Tension not available |
Explanation |
On this platform the Tamino X-Tension feature is not available. |
Action |
No action required. |
INOSXW7011 | This will remove all previously selected files from your package list |
Explanation |
For a server extension package, either one or more class files or ONE jar file can be used. This warning shows up in one of the following cases: 1) A jar file was selected and a class file will be added to the class file list: The jar file will be removed from the list. 2) One or more class files or another jar file were selected, and a jar file will be added: All recently selected files will be removed. |
Action |
Choose "OK" to confirm or "Cancel" to cancel the current selection |
INOSXW7012 | Main Class File for server extension missing |
Explanation |
For a server extension package, either one or more class files or ONE jar file can be used. This warning shows up when none of the selected class files contains the main class of the server extension. |
Action |
Add another class file that contains the main class of the server extension. |
INOSXW7013 | Server extension might not run without these class(es) |
Explanation |
In the Packaging Dialogue of the X-Tension Builder, one of the selected class files is about to be removed. Without this class file the installation of this server extension will be incomplete. |
Action |
Check if this class file is really unnecessary for the current server extension. |
INOSXW7031 | Directory 'dir' does not exist and will be created |
Explanation |
This directory does not exist and will be created. |
Action |
Select "OK" to create this directory, select "Cancel" to cancel project creation. |
INOSXW7135 | The given class contains no server extension function |
Explanation |
The given class does not contain any method that can be used as a server extension function. |
Action |
Enter some methods using the direct server extension development tools. |
INOSXW7139 | No valid JVM, install valid JVM or switch X-Tension Java Usage to 'NO' |
Explanation |
Error detected when loading a JVM for current Tamino version |
Action |
Check if JVM is installed, if a valid JVM Version is installed or switch X-Tension Java Usage to 'NO'. |
INOSXW7159 | Value will be set to empty string |
Explanation |
A default value or configuration parameter (Init Function) may be set to empty string if data type is charstring. |
Action |
Please check if in this special case this effect is intended. |
INOX2E8000 | Usage of distributed transaction processing is not supported on this platform |
Explanation |
It is not possible to use distributed transaction processing features on the Tamino server platform. |
Action |
None - the platform does not support distributed transaction processing. |
INOX2E8001 | Conversion of the distributed transaction processing transaction identifier was not possible |
Explanation |
The transaction identifier provided does not have a defined method to convert it to the internal format. |
Action |
Contract your software supplier - this is a software error. |
INOX2E8002 | An internal error occurred dealing with the transaction identifier in distributed transaction |
Explanation |
The transaction identifier caused an internal error when being processed. |
Action |
Contract your software supplier - this is a software error. |
INOX2E8003 | Server encountered an error while performing a distributed transaction processing action |
Explanation |
A distributed transaction processing action resulted in the server not being able to complete the action requested. |
Action |
Contract your software supplier - this is a software error. |
INOX2E8004 | The specified distributed transaction processing identifier is unknown by the server |
Explanation |
A transaction identifier was specified which is unknown to the server. This can happen if a timeout occurred or if the transaction has not been prepared before a server restart. |
Action |
This message will be given back by the server to the transaction manager. |
INOX2E8005 | An invalid argument was detected on a distributed transaction processing call |
Explanation |
An argument supplied by the transaction manager was invalid. |
Action |
This message will be given back by the server to the transaction manager. |
INOX2E8006 | Protocol error - an action requested by the transaction manager was invoked in an improper context |
Explanation |
The specified action cannot be carried out in the current distributed transaction state. |
Action |
This message will be given back by the server to the transaction manager. |
INOX2E8007 | An error has occurred which makes server unavailable to process the transaction manager's action |
Explanation |
The action requested by the transaction manager cannot be fulfilled by Tamino currently. |
Action |
This message will be given back by the server to the transaction manager. |
INOX2E8008 | Duplicate distributed transaction identifier encounter while enlisting in a distributed transaction |
Explanation |
A duplicate transaction identifier was encountered while enlisting in a distributed transaction. |
Action |
This is an internal error and should be reported to your software supplier. |
INOX2E8010 | The specified distributed transaction has been rollback |
Explanation |
The server has decided that this distributed transaction can only be rolled back. |
Action |
This message is a reply to a transaction manager request. |
INOX2E8011 | A communications error has occurred |
Explanation |
A communications error occurred while attempting a distributed transaction processing action sent by the transaction manager. |
Action |
This message is a reply to a transaction manager request. |
INOX2E8012 | The server has detected a deadlock involving the specified distributed transaction |
Explanation |
A deadlock has been detected for the specified distributed transaction. The transaction has been rolled back. |
Action |
This message is a reply to a transaction manager request. |
INOX2E8013 | The server has detected an integrity violation for the resources requested by the specified distributed transaction |
Explanation |
An integrity violation has been detected for the specified distributed transaction. The transaction has been rolled back. |
Action |
This message is a reply to a transaction manager request |
INOX2E8014 | The server has detected an unspecified error for the specified distributed transaction |
Explanation |
An unspecified has been detected for the specified distributed transaction. The transaction has been rolled back. |
Action |
This message is a reply to a transaction manager request |
INOX2E8015 | The server has detected an internal protocol error for the specified distributed transaction |
Explanation |
An internal protocol error has been detected for the specified distributed transaction. |
Action |
This message is a reply to a transaction manager request. |
INOX2E8016 | The server has timed out the specified distributed transaction |
Explanation |
The server timed out the specified distributed transaction. |
Action |
This message is a reply to a transaction manager request. |
INOX2E8017 | The server has detected a transient error for the specified distributed transaction |
Explanation |
The server has detected a transient error for the specified distributed transaction. |
Action |
This message is a reply to a transaction manager request. |
INOX2E8018 | The server has heuristically committed the specified distributed transaction |
Explanation |
The server had to heuristically commit the specified distributed transaction. |
Action |
This message is reply to a transaction manager request. |
INOX2E8019 | The server has heuristically rolled back the specified distributed transaction |
Explanation |
The server had to heuristically roll back the specified distributed transaction. |
Action |
This is message is reply to a transaction manager request. |
INOX2E8020 | The server has heuristically completed the distributed transaction. The outcome of the transaction is mixed. |
Explanation |
The server had to heuristically complete the specified distributed transaction. The outcome is however mixed; this means that part of the transaction was committed and the rest was rolled back. |
Action |
This message is a reply to a transaction manager request. |
INOX2E8021 | The specified distributed transaction is read-only |
Explanation |
There were no modifications made to the server by the specified distributed transaction and therefore the server does not need to receive the commit action from the transaction manager. |
Action |
This message is a reply to a transaction manager request. |
INOX2E8022 | An error occurred while issuing a call to the transaction manager |
Explanation |
The transaction manager rejected a request made by Tamino. |
Action |
See the extended error messages for the transaction manager's reason for rejecting the call. |
INOX2E8023 | The command is not allowed while a distributed transaction is active within this session |
Explanation |
An attempt was made to issue either a _DISCONNECT command before the completion of the distributed transaction or a _COMMIT/_ROLLBACK command in the distributed transaction. These are not allowed. |
Action |
Complete the two phase commit transaction before issuing the _DISCONNECT command. |
INOX2E8024 | The current session cannot accept commands while the two phase commit transaction completion protocol is active |
Explanation |
Issuing Tamino commands to a session that is between phase 1 and phase 2 of a two phase commit transaction completion protocol is not allowed. The two phase commit protocol must complete before the session can be used again. |
Action |
Do not issue commands while the two phase commit transaction completion protocol is active. |
INOX2E8025 | The transaction manager specified an invalid recovery action |
Explanation |
The request action on recovery was invalid. |
Action |
This is an error sent to the transaction manager. It is internal and if seen should be reported to your software supplier. |
INOX2E8027 | The outcome of a commit was inconsistent |
Explanation |
The outcome of a commit was inconsistent: one or more data sources failed to commit. |
Action |
Check the extended error information for a list of which data sources failed to commit the transaction, then perform appropriate repairs. |
INOX2E8028 | The outcome of a rollback was inconsistent |
Explanation |
The outcome of a rollback was inconsistent: one or more data sources failed to roll back. |
Action |
Check the extended error information for a list of which data sources failed to commit the transaction, then perform appropriate repairs. |
INOX2E8030 | Invalid transaction token |
Explanation |
An invalid transaction token was specified. |
Action |
Provide a valid transaction token with the correct format. |
INOX2E8047 | Recovery of distributed transactions has found outstanding transactions that are not for the current transaction manager |
Explanation |
After completion by the transaction manager of recovery for distributed transactions, there are outstanding transactions that do not belong to the transaction manager. |
Action |
Contact your software supplier for help in resolving the outstanding transactions. |
INOX2E8049 | An internal error occurred in the distributed transaction processing components of the server. |
Explanation |
An internal error occurred. |
Action |
This is an internal error. Please contact your software supplier. |
INOX2F8026 | Cannot find distributed transaction processing (DTP) library ino2pc |
Explanation |
The shared library/DLL ino2pc cannot be found. |
Action |
This is a software installation configuration problem. Contact Software AG support for help |
INOX2I8046 | Distributed transaction transaction_token with resource manager identifier rmid has been manually resolved to the 'state' state |
Explanation |
This event is generated when someone manually resolves a distributed transaction. |
Action |
No action required. This message helps to track the progress of the distributed transaction. |
INOX2I8048 | Server start-up detected pending or heuristically complete distributed transactions |
Explanation |
On starting the server, it has been detected that there are outstanding distributed transactions. These transactions should normally be resolved by the transaction manager. |
Action |
Check the transaction manager log to check that all outstanding distributed transactions are resolved. If the transactions are not resolved, then contact your software supplier to get help in resolving them. |
INOXCE8100 | Internal error: duplicate root element |
Explanation |
Invalid migrated data records with duplicate root elements were detected. |
Action |
Please contact your software supplier. |
INOXCE8102 | Internal error: document stack corrupted |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXCE8103 | Memory allocation failed |
Explanation |
There was not enough main memory available to perform the request. |
Action |
Possibly the machine is overloaded. Try again later. |
INOXCE8104 | Internal error during document composition |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXCE8105 | Invalid X-Tension response |
Explanation |
An X-Tension function returned a string that is not well-formed XML. |
Action |
Correct the implementation of the X-Tension function |
INOXCE8106 | Internal error: unknown request |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier. |
INOXCE8107 | Map to object: illegal document ID encountered. |
Explanation |
The query attached to a node with map-type=object is of the form "@ino:id=%parent". The document ID found in the parent node is either zero or contains non-digit characters. |
Action |
The document ID in the parent node is illegal, correct it. |
INOXCE8108 | Insufficient mapping information, document cannot be composed |
Explanation |
An XML document could not be created due to insufficient mapping information. |
Action |
Look at the <ino:messageline> element in the <ino:response> document to find more information about the cause of the problem. |
INOXCE8109 | Cannot delete externally mapped data |
Explanation |
Tamino X-Query is not able to delete XML documents that are composed from external data sources like ODBC or Adabas if those documents have not been stored through Tamino. Typically, when displayed, these documents do not have an "ino:id" attribute. Similarly, X-Query cannot delete data from doctypes with "tsd:pure" mapping. |
Action |
Modify the query that selects the documents to be deleted. In the case of pure mapping, use XQuery update in order to delete documents. |
INOXCE8110 | Internal error: document data corrupted |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXCE8111 | Error in XNode Adabas processing during conversion of Natural date/time value |
Explanation |
An error occurred while converting a Natural date or time value. The Tamino response contains details about the offending value, as well as an internal error code. |
Action |
Analyze the error. |
INOXCE8114 | Document ID unknown, mapping type infofield |
Explanation |
This error message should never occur. |
Action |
None |
INOXCE8117 | Internal error:Document not found |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXCE8118 | Mapping type object: number of resulting objects too large |
Explanation |
This message should never occur |
Action |
None |
INOXCE8119 | Internal error: structure description too large |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXDE7500 | NOTATION must be restricted by an enumeration |
Explanation |
NOTATION must be restricted by an enumeration. |
Action |
Please modify your XML schema accordingly. |
INOXDE7501 | (a-props-correct.2) default or fixed value is not of declared type |
Explanation |
If there is a default or fixed value specification, the canonical lexical representation of its value must be valid with respect to the type definition. |
Action |
Please modify your XML schema accordingly. |
INOXDE7502 | (a-props-correct.3) If attributes has type ID or a derived type it must not have a value constraint, i.e. a default or fixed value |
Explanation |
Attributes of type ID or a derived type must not have a value constraint, i.e. a default or fixed value. |
Action |
Please modify your XML schema accordingly. |
INOXDE7503 | (e-props-correct.2) default or fixed value is not of declared type |
Explanation |
If there is a default or fixed value specification, the canonical lexical representation of its value must be valid with respect to the type definition. |
Action |
Please modify your XML schema accordingly. |
INOXDE7504 | (e-props-correct.4) Elements of type ID or a derived type must not have a value constraint, i.e. a default or fixed value |
Explanation |
Elements of type ID or a derived type must not have a value constraint, i.e. a default or fixed value. |
Action |
Please modify your XML schema accordingly. |
INOXDE7505 | (ct-props-correct.4) attributes must not have identical names |
Explanation |
Two distinct attribute declarations in the attribute uses must not have identical names. |
Action |
Please modify your XML schema accordingly. |
INOXDE7506 | (ct-props-correct.5) only one attribute may have type ID or a derived type |
Explanation |
Two distinct attribute declarations in the attribute uses must not have type ID or a derived type. |
Action |
Please modify your XML schema accordingly. |
INOXDE7507 | (au-props-correct.2) attribute's fixed value does not match declaration's fixed value |
Explanation |
If the attribute declaration has a fixed value constraint, then if the attribute use itself has a value constraint, it must also be fixed and its value must match that of the attribute declaration's value constraint. |
Action |
Please modify your XML schema accordingly. |
INOXDE7508 | (sch-props-correct.2) name conflict with global declarations |
Explanation |
Each of the type definitions, element declarations, attribute group definitions, model group definitions and notation declarations must not contain two or more schema components with the same name. |
Action |
Please modify your XML schema accordingly. |
INOXDE7509 | invalid type of default value |
Explanation |
If the type definition is a simple type definition, then the string must be valid with respect to that definition. |
Action |
Please modify your XML schema accordingly. |
INOXDE7510 | content type is neither a simple type definition nor mixed |
Explanation |
If an element declaration specifies a default value and the type definition is a complex type definition, then its content type must be a simple type definition or mixed. |
Action |
Please modify your XML schema accordingly. |
INOXDE7511 | element default value does not match type |
Explanation |
If an element declaration specifies a default value and the type definition is a complex type definition and its content type is a simple type definition, then the default value must be of declared type. |
Action |
Please modify your XML schema accordingly. |
INOXDE7512 | content type does not allow for default value |
Explanation |
If an element declaration specifies a default value and the type definition is a complex type definition and its content type is mixed, then the content type's particle must be emptiable. |
Action |
Please modify your XML schema accordingly. |
INOXDE7513 | missing name in type definition |
Explanation |
If the particles contain, either directly, indirectly or implicitly two or more element declaration particles with the same name, then all their type definitions must be the same top-level definitions. |
Action |
Please modify your XML schema accordingly. |
INOXDE7514 | type definitions have different names |
Explanation |
If the particles contain, either directly, indirectly or implicitly two or more element declaration particles with the same name, then all their type definitions must be the same top-level definitions. |
Action |
Please modify your XML schema accordingly. |
INOXDE7515 | type definitions have different namespaces |
Explanation |
If the particles contain, either directly, indirectly or implicitly two or more element declaration particles with the same name, then all their type definitions must be the same top-level definitions. |
Action |
Please modify your XML schema accordingly. |
INOXDE7516 | (no-xmlns) attribute name not allowed |
Explanation |
The name of an attribute declaration must not match xmlns. |
Action |
Use the targetNamespace attribute of the schema's root node in order to associate the current schema and objects defined therein with a namespace URI. The import element can be used to compose schemas defining objects for different namespaces. |
INOXDE7517 | Below Attribute there may be only attributeInfo node but no schemaInfo or elementInfo nodes |
Explanation |
Below Attribute there may be only attributeInfo node but no schemaInfo or elementInfo nodes. |
Action |
Please modify your XML schema accordingly. |
INOXDE7518 | (enumeration-valid-restriction) value of enumeration does not match base type definition |
Explanation |
The value attribute of an enumeration item must match the definition of the restriction's base type. |
Action |
Adapt your schema. |
INOXDE7519 | (notation-defined-restriction) value of enumeration is not defined in a global notation element. |
Explanation |
An enumeration value being used in a type derived from NOTATION must be defined in a global notation element. |
Action |
Adapt your schema. |
INOXDE7520 | invalid index |
Explanation |
It is not possible to define indices on elements or attributes with type "xs:long", "xs:unsignedLong" or "xs:decimal". |
Action |
Please modify your XML schema accordingly. |
INOXDE7521 | invalid text index |
Explanation |
It is not possible to define text indices on elements or attributes with numeric types. |
Action |
Please modify your XML schema accordingly. |
INOXDE7522 | The element pointed to by tsd:refers needs to have a reference index defined for it |
Explanation |
(mp-valid-refers.5:) The element pointed to by tsd:refers needs to have a reference index defined for it. |
Action |
Please modify the schema to include a reference index on the element pointed to by tsd:refers and try to define the schema again. |
INOXDE7523 | Collations can only be defined for string datatypes (derived types of string in W3C XML schema part 2) |
Explanation |
Collations can only be defined for string datatypes (derived types of string in W3C XML schema part 2). |
Action |
Please modify your XML schema accordingly. |
INOXDE7524 | (src-single-facet-value) Facet is only permitted to be defined once |
Explanation |
A facet has been specified more than once. This facet is only permitted to be defined once. |
Action |
Please modify the XML Schema accordingly. |
INOXDE7525 | (cos-element-consistent) Element declarations are not consistent |
Explanation |
If the particles contain, either directly, indirectly or implicitly two or more element declaration particles with the same name, then all their type definitions must be the same top-level definitions. |
Action |
Please modify your XML schema accordingly. |
INOXDE7526 | (maxInclusive-maxExclusive) 'maxInclusive' and 'maxExclusive' facets cannot be used together |
Explanation |
A simple type restriction, containing both 'maxInclusive' and 'maxExclusive' facets, has been found. |
Action |
Remove either of the 'maxInclusive' or 'maxExclusive' facets. |
INOXDE7527 | (minInclusive-minExclusive) 'minInclusive' and 'minExclusive' facets cannot be used together |
Explanation |
A simple type restriction, containing both 'minInclusive' and 'minExclusive' facets, has been found. |
Action |
Remove either of the 'minInclusive' or 'minExclusive' facets. |
INOXDE7528 | Node declarations are not consistent |
Explanation |
The schema violates a constraint which is a Tamino-specific extension of the (cos-element-consistent) constraint as imposed by XML schema: If there are two attribute or element declarations in the set of complex type definitions being allowed for a given element node due to usage of the xsi:type attribute, then these attributes (or elements) must be consistent. Consistency requirements cover the datatype as well as physical properties (mapping, indexing,...), or logical properties (collation, trigger, ...). |
Action |
Modify the schema to avoid violation of the constraint. For example it may help to use the 'block' attribute of <xs:element> or <xs:complexType> , or the 'blockDefault' attribute of <xs:schema> in order to control the {prohibited substitutions} with respect to xsi:type. In particular, you may use blockDefault="#all" if you do not need to allow for usage of the xsi:type attribute in your XML documents. |
INOXDE7529 | (src-resolve.1.1) Global type reference could not be resolved |
Explanation |
Reference to a global complex or simple type definition could not be resolved. |
Action |
Check the names of the global type definition and the associated reference. |
INOXDE7530 | (src-resolve.1.2) The ref attribute of an attribute needs to reference an existing global attribute |
Explanation |
An attribute defined in the schema uses the 'ref' attribute, however the global attribute with that name cannot be found. |
Action |
Check that the global attribute is not missing. Also check that the global attribute name and reference have been correctly specified. |
INOXDE7531 | (minLength-less-than-equal-to-maxLength) 'minLength' facet value must be 'less than or equal to' that of facet 'maxLength' |
Explanation |
A simple type restriction, where the value of facet 'minLength' is greater than that of 'maxLength', has been found. |
Action |
Revise the facet values. |
INOXDE7532 | Invalid pattern facet value found |
Explanation |
The schema being defined contains a pattern facet which has an invalid value. |
Action |
Check the schema and consider revising the pattern facet's value. |
INOXDE7533 | Below Schema there needs to be exactly one appinfo node which defines Tamino mappings |
Explanation |
Below Schema there needs to be exactly one appinfo node which defines Tamino mappings. |
Action |
Modify the XML schema accordingly. |
INOXDE7534 | (src-import.1.1) Invalid import element. If the namespace attribute is present, then its value must not match the value of the enclosing schema's targetNamespace attribute. |
Explanation |
The schema being defined contains an import element. The namespace attribute is present and its value is the same as the targetNamespace of the enclosing schema. This is not allowed. |
Action |
Revise either the namespace attribute of the import element or the targetNamespace of the schema. |
INOXDE7535 | (src-import.1.2) Invalid import element. If the namespace attribute is not present, then the enclosing schema must have a targetNamespace attribute. |
Explanation |
The schema being defined contains an import element. The namespace attribute is not present and the enclosing schema does not specify a targetNamespace. This is disallowed. |
Action |
Revise the import element and/or the schema element. |
INOXDE7536 | (src-import.2) Invalid import element. Schema reference could not be resolved. |
Explanation |
The schema being defined contains an import element. The schema referenced using either a schemaLocation or namespace attribute could not be located. |
Action |
If referencing using schemaLocation, check the name of the referenced schema (and optionally the collection name also). If referencing using namespace alone, check the targetNamespace of the referenced schema. |
INOXDE7537 | (src-import.3.1) Invalid import element. If there is a namespace attribute, then its value must be identical to the value of the targetNamespace attribute of the referenced schema. |
Explanation |
The schema being defined contains an import element. The namespace attribute is different from the targetNamespace of the referenced schema. This is not allowed. |
Action |
Revise either the namespace attribute of the import element or the targetNamespace of the referenced schema. |
INOXDE7538 | (src-import.3.2) Invalid import element. If there is no namespace attribute, then the referenced schema must have no targetNamespace attribute. |
Explanation |
The schema being defined contains an import element. The namespace attribute is not present, but the referenced schema specifies a targetNamespace. This is not allowed. |
Action |
Revise the import element and/or the referenced schema element. |
INOXDE7539 | The value of schema attribute targetNamespace is not allowed if another schema in the same database already imports the corresponding namespace using only the namespace attribute of the import element |
Explanation |
The value of the targetNamespace attribute of the schema that you are trying to define is not allowed. This is because another schema in the same database already imports that namespace, using an import element with namespace alone. |
Action |
Revise the schema and/or the other schema importing that namespace. Either change the targetNamespace of the current schema, or change the import element of the referencing schema to also use the schemaLocation attribute. |
INOXDE7540 | Found node with a mapped value which is used to construct index entries |
Explanation |
A node with a mapped value must not be used to construct index entries. This restriction applies for text and standard as well as for the components of a compound index referring to an ancestor of the current node. |
Action |
Remove index definition causing this conflict. |
INOXDE7541 | Undefine of schema failed. Schema to be undefined is referenced by other schema(s) in the database. |
Explanation |
The undefine of a specific schema was performed. Other schema(s) in the database still reference this schema. |
Action |
Before the schema can be undefined, you must first undefine all referencing schemas. |
INOXDE7542 | Attribute targetNamespace of element schema, if present, must not be empty. |
Explanation |
The schema being defined specifies an empty targetNamespace attribute. |
Action |
Revise the schema. Either provide the targetNamespace attribute with a value, or completely remove it. |
INOXDE7543 | Import using namespace attribute alone is forbidden, if more than one schema with the corresponding targetNamespace is already stored in the current database |
Explanation |
The schema being defined contains an import element with only a namespace attribute. More than one schema stored in the current database already contains a corresponding targetNamespace attribute. |
Action |
Revise the schema and/or other schemas stored inside the current database. Consider using the schemaLocation attribute of import to clarify exactly which schema was intended. |
INOXDE7544 | An import element must have attributes |
Explanation |
The schema being defined specifies an import element without attributes. |
Action |
Revise the schema. Add either namespace or schemaLocation attributes to the import element, or remove it and consider using Tamino's content element with value open. |
INOXDE7545 | Cannot define standard index or unique constraint based on a node whose associated datatype has a variety of 'union' |
Explanation |
It is not supported to define an index or unique constraint based on a node whose datatype has a variety of 'union' or which is derived via <xs:list> with an item type whose variety is 'union'. |
Action |
Modify the schema accordingly. |
INOXDE7546 | An element defined as a primary key cannot be defined as nillable |
Explanation |
An element which is defined as a primary key value cannot be defined as nillable. |
Action |
Revise the schema. Either remove the xsi:nillable attribute or set the value to false. |
INOXDE7547 | Undefine of collection failed. One or more schemas contained inside the collection to be undefined are referenced by other schema(s), from other collection(s) in the current database. |
Explanation |
The undefine of a specific collection was performed. Other schema(s) from other collection(s) in the database still reference one or more schemas contained inside the collection to be undefined. |
Action |
Before the collection can be undefined, you must first undefine all referencing schemas. |
INOXDE7548 | Cannot define standard index or unique constraint based on this element node with complex content if there is a validly derived complex type with simple content which can be used in an xsi:type attribute on that element node |
Explanation |
It is not allowed to define a standard index or unique constraint based on an element node whose associated datatype is a complex type with complex content if there is another complex type with simple content which can be validly used in an xsi:type attribute on that element node. |
Action |
Either remove the index definition or modify type definitions to avoid violation of this constraint. |
INOXDE7549 | Mapping not allowed for datatype of variety |
Explanation |
Mapping (ADABAS, SQL and SXS) is not allowed for datatypes derived via xs:list or xs:union. |
Action |
Please change the datatype and try to define the schema again. |
INOXDE7550 | ElementInfo node is not allowed with a schema reference to a global element definition |
Explanation |
Below Element an elementInfo node is only allowed if the element node starts an element definition. An elementInfo is not allowed with a reference to a global element definition. |
Action |
Please modify your XML schema accordingly. |
INOXDE7551 | AttributeInfo node is not allowed with a schema reference to a global attribute definition |
Explanation |
Below Attribute an attributeInfo node is only allowed if the attribute node starts an attribute definition. An attributeInfo is not allowed with a reference to a global attribute definition. |
Action |
Please modify your XML schema accordingly. |
INOXDE7552 | The path contains invalid expressions |
Explanation |
The path can only consists of named child steps with abbreviated XPath syntax. In particular, it cannot contain *, .., // operators. |
Action |
Modify the XML schema accordingly. |
INOXDE7553 | The index types of elements and attributes having the same multipath index label must be identical |
Explanation |
The index types of elements and attributes having the same multipath index label must be identical. |
Action |
Please change the schema so that multipath definitions with the same label are only used when the index types are identical and then try to define the schema again. |
INOXDE7554 | (src-attribute-group.2) Intentional intersection of namespace constraints is not expressible |
Explanation |
This may happen e.g. if two attribute wildcards are to be merged due to resolution of a reference to an attributeGroup definition. If those two attribute wildcards both have a namespace constraint ##other, thus referring to different target namespaces, the intentional intersection is not expressible. |
Action |
Adapt the schema according to XML schema constraint src-attribute-group.2 |
INOXDE7555 | The name attribute of tsd:unique definitions has to be unique within a doctype |
Explanation |
The name attribute of tsd:unique definitions has to be unique within a doctype. |
Action |
Please change the duplicate name and try to define the schema again. |
INOXDE7556 | The elements and attributes pointed to in tsd:unique definitions must have a cardinality of 1 |
Explanation |
The elements and attributes pointed to in tsd:unique definitions must have a cardinality of 1. |
Action |
Please change the cardinality and try to define the schema again. |
INOXDE7557 | The path specified the xpath attribute of a field element needs to point to an existing element or attribute |
Explanation |
The path specified the xpath attribute of a field element needs to point to an existing element or attribute. |
Action |
Please make sure the specified path is correct and try to define the schema again. |
INOXDE7558 | multipath index definitions are not allowed in doctypes which have the structureIndex set to none |
Explanation |
Multipath index definitions are not allowed in doctypes which have the structureIndex set to none. |
Action |
Please change the structure index to condensed or full and try to define the schema again. |
INOXDE7559 | The elements and attributes having the same multipath index label must have matching datatypes |
Explanation |
The elements and attributes having the same multipath index label must have matching datatypes. |
Action |
Please change the wrong datatype and try to define the schema again. |
INOXDE7560 | The elements and attributes having the same multipath index label must have matching collations |
Explanation |
The elements and attributes having the same multipath index label must have matching collations. |
Action |
Please change the wrong collation and try to define the schema again. |
INOXDE7561 | The elements and attributes having the same multipath index label must have matching tsd:refers definitions |
Explanation |
The elements and attributes having the same multipath index label must have matching tsd:refers definitions. |
Action |
Please change the wrong tsd:refers definition and try to define the schema again. |
INOXDE7562 | The path defined in tsd:refers has to point to an existing element |
Explanation |
The path defined in tsd:refers has to point to an existing element. |
Action |
Please change the path and try to define the schema again. |
INOXDE7563 | The path defined in tsd:refers has to point to an element which is a predecessor of the element or attribute where it is defined |
Explanation |
The path defined in tsd:refers has to point to an element which is a predecessor of the element or attribute where it is defined. |
Action |
Please change the path and try to define the schema again. |
INOXDE7564 | The path defined in tsd:refers may only point to elements that are locally stored in a Tamino database |
Explanation |
The path defined in tsd:refers may only point to elements that are locally stored in a Tamino database. |
Action |
Please change the path and try to define the schema again. |
INOXDE7565 | The path defined in tsd:refers must point either to the doctype element or to an element for which a tsd:reference is defined |
Explanation |
The path defined in tsd:refers must point either to the doctype element or to an element for which a tsd:reference is defined. |
Action |
Please change the path and try to define the schema again. |
INOXDE7566 | The path specified in the xpath attribute of a field element needs to point to an element or attribute that is locally stored in a Tamino database |
Explanation |
The path specified in the xpath attribute of a field element needs to point to an element or attribute that is locally stored in a Tamino database. |
Action |
Please change the path and try to define the schema again. |
INOXDE7567 | The path specified in the xpath attribute of a field element of a compound index definition needs to point to a leaf node (an attribute or element having no children) |
Explanation |
The path specified in the xpath attribute of a field element of a compound index definition needs to point to a leaf node (an attribute or element having no children). |
Action |
Please change the path and try to define the schema again. |
INOXDE7568 | For a uniqueness constraint a certain path may only be defined once |
Explanation |
For a uniqueness constraint a certain path may only be defined once. |
Action |
Please change the path and try to define the schema again. |
INOXDE7569 | A reference index may not be defined for a doctype element |
Explanation |
A reference index may not be defined for a doctype element. |
Action |
Please change the reference index value and try to define the schema again. |
INOXDE7570 | There may only be one tsd:reference index definition per tsd:physical |
Explanation |
There may only be one tsd:reference index definition per tsd:physical. |
Action |
Please make sure there is only one tsd:reference index definition per tsd:physical and try to define the schema again. |
INOXDE7571 | If an index has been defined as a multipath index, there may not be a tsd:refers defined for that same index |
Explanation |
If an index has been defined as a multipath index, there may not be a tsd:refers defined for that same index. |
Action |
Please remove either the multipath definition or the tsd:refers and try to define the schema again. |
INOXDE7572 | For a compound index a certain path may only be defined once |
Explanation |
For a compound index a certain path may only be defined once. |
Action |
Please change the schema and try to define it again. |
INOXDE7573 | (src-resolve.1.4) Reference to an attribute group definition could not be resolved |
Explanation |
Reference to an attribute group definition could not be resolved. |
Action |
Check the qualified names of the attribute group definition and the reference. |
INOXDE7574 | (src-resolve.1.5) Reference to a model group definition could not be resolved |
Explanation |
Reference to a model group definition could not be resolved. |
Action |
Check the qualified names of the model group definition and the reference. |
INOXDE7575 | (src-attribute-group.3) Circular attribute group reference is disallowed |
Explanation |
A cycle of attribute group references has been found. |
Action |
Check the attribute group references and remove the circular reference. |
INOXDE7576 | (mg-props-correct.2) Circular group reference is disallowed |
Explanation |
Within the particles of a group there must not be at any depth a reference to the group itself. |
Action |
Check group definition and remove circular reference inside. |
INOXDE7577 | (src-include.2.1) Target namespace of the including and the included schema do not match. |
Explanation |
The values of the targetNamespace attributes of the including and the included schema may not differ if both are present. |
Action |
Check targetNamespace attributes. |
INOXDE7578 | (src-include.2.2) Included schema has target namespace whereas including has no target namespace. |
Explanation |
If the including schema has no targetNamespace attribute, the included schema must not have a targetNamespace attribute as well. |
Action |
Check and adapt the schema documents. |
INOXDE7579 | (src-include.2.3) Target namespace of included schema missing. Tamino does not yet support "chameleon include". |
Explanation |
This is a current limitation of Tamino. |
Action |
Define the included schema using the same targetNamespace attribute as the including schema's targetNamespace. |
INOXDE7580 | (src-include.1) Invalid include element. Schema reference could not be resolved. |
Explanation |
The schema being defined contains an include element. The schema referenced by the schemaLocation attribute could not be located. |
Action |
Check the name of the referenced schema and, optionally, the collection name as well. |
INOXDE7581 | invalid collation language |
Explanation |
The specified language string is not valid. |
Action |
Please change the wrong collation language string and try to define the schema again. |
INOXDE7583 | Invalid open content found in pure X-Node mapped doctype |
Explanation |
For pure X-Node mapping, no open content is allowed for that doctype. This includes wildcards with processContents being "strict" or "lax" and element nodes with type "xs:anyType" or no type at all. |
Action |
Ensure that the doctype with the pure X-Node mapping is set to closed content, that any of the doctype's wildcards (xs:any and xs:anyAttribute) in scope have processContents set to "strict", and that all elements in scope have a non-absent type specification different from "xs:anyType". |
INOXDE7584 | Invalid mixed content found in complex type within a pure X-Node mapped doctype |
Explanation |
Elements in a pure X-Node mapped doctype must not have a mixed content model. |
Action |
Set the mixed attribute of the corresponding complex type definition to "false". |
INOXDE7585 | Invalid mapping found in root element of pure X-Node mapped doctype |
Explanation |
Currently, only Adabas mapping is allowed for the root node of a pure X-Node mapped doctype. |
Action |
Check the mapping of the root element. |
INOXDE7586 | Invalid mapping found in non-root node within pure X-Node mapped doctype |
Explanation |
All leaf nodes must be mapped corresponding to the mapping type of the root element, e.g. to Adabas fields if the root node is mapped to an Adabas file. |
Action |
Check the mapping of the node. |
INOXDE7587 | Found invalid recursion in pure X-Node mapped doctype |
Explanation |
Within a pure X-Node mapped doctype no recursive structures are permitted. |
Action |
Remove the recursion. |
INOXDE7588 | Found empty leaf node in pure X-Node mapped doctype |
Explanation |
A pure X-Node mapped doctype must not contain empty leaf nodes. |
Action |
Either remove the node or map to an X-Node data item, i.e. either an Adabas field or an SQL column. |
INOXDE7589 | Reference index definitions are not allowed in doctypes which have the structureIndex set to none |
Explanation |
Reference index definitions are not allowed in doctypes which have the structureIndex set to none. |
Action |
Please correct the schema and try to define it again. |
INOXDE7590 | Unique index constraints may not be defined on elements or attributes on node of given type |
Explanation |
Unique index constraints may not be defined on elements or attributes of xs:duration or any data type allowing for an optional timezone indicator, e.g. xs:dateTime. |
Action |
Please correct the schema and try to define it again. |
INOXDE7591 | Found xs:include or xs:import referencing current schema |
Explanation |
An xs:include or xs:import must not reference the current schema. |
Action |
Adapt the schema. |
INOXDE7592 | Invalid level of structure index for pure X-Node mapped doctype |
Explanation |
A pure X-Node mapped doctype must not have a full structure index. |
Action |
Set the structure index to 'condensed' or 'none'. |
INOXDE7593 | A default function has been defined at an element node with a complex type |
Explanation |
A default function may only be defined at a node with a simple type. |
Action |
Modify the schema in an appropriate way. |
INOXDE7594 | Default function defined for required attribute node |
Explanation |
If a default function is defined for an attribute, the attribute must be optional. |
Action |
Check and adapt schema in an appropriate way. |
INOXDE7595 | Default function defined for a node which has a value constraint |
Explanation |
An element or attribute node may define either a default function or a value constraint (i.e. a default or fixed value) but not both. |
Action |
Adapt the schema correspondingly. |
INOXDE7596 | Too many tsd:elementInfo or tsd:attributeInfo nodes |
Explanation |
There may be only one tsd:elementInfo or tsd:attributeInfo node per xs:element or xs:attribute node. |
Action |
Modify the schema accordingly. |
INOXDE7597 | (src-list-itemType-or-simpleType) Definition of simple type via <xs:list> contains both 'itemType' attribute and <xs:simpleType> child. |
Explanation |
Either the 'itemType' attribute or the <xs:simpleType> child of the <xs:list> element must be present, but not both. |
Action |
Remove either the 'itemType' attribute or the <xs:simpleType> child. |
INOXDE7598 | (src-restriction-base-or-simpleType) Definition of simple type via <xs:restriction> must contain either 'base' attribute or <xs:simpleType> child. |
Explanation |
Either the 'base' attribute or the <xs:simpleType> child of the <xs:restriction> element must be present, but not both. |
Action |
Remove either 'base' attribute or the <xs:simpleType> child. |
INOXDE7599 | (src-union-memberTypes-or-simpleTypes) The 'memberTypes' attribute of the <xs:union> element is empty and there is no <xs:simpleType> child. |
Explanation |
Either the 'memberTypes' attribute of the <xs:union> element must be non-empty or there must be at least one <xs:simpleType> child. |
Action |
Add either the 'memberTypes' attribute of the <xs:union> element or at least one <xs:simpleType> child. |
INOXDE7614 | The noConversion option may only be changed for empty doctypes |
Explanation |
Changing the noConversion option could make the existing data in the doctype invalid, so this option may only be modified for empty doctypes. |
Action |
Adapt the schema so that the noConversion option is not changed or make sure there are no documents stored in the doctype for which you are trying to modify the schema. |
INOXDE7619 | Invalid type of parameter for server extension |
Explanation |
The type of the parameter is invalid in the current context. |
Action |
Check and modify the type of parameter to be passed to the server extension function. for example, parameters being passed to a trigger function may only have a simple predefined type. |
INOXDE7620 | Invalid parameter value |
Explanation |
The value of the parameter is not valid with respect to the declared type. |
Action |
Modify the type or value in order to create a consistent parameter definition. |
INOXDE7621 | (cos-st-restricts.1.1) Invalid base type definition of simple type |
Explanation |
The base type definition must be an atomic simple type definition or a built-in primitive datatype. |
Action |
Adapt the type definitions or type hierarchy. |
INOXDE7622 | (cos-st-restricts.1.2) Invalid base type of simple type definition - the 'final' attribute does not permit derivation of another simple type |
Explanation |
The {final} of the {base type definition} of a simple type definition must not contain restriction. |
Action |
Adapt the schema according to the constraint. |
INOXDE7623 | (cos-st-restricts.2.1) Invalid item type definition of simple type derived via <xs:list> |
Explanation |
The {item type definition} must have a {variety} of atomic or union (in which case all the {member type definitions} must be atomic). |
Action |
Adapt the schema according to the constraint. |
INOXDE7624 | (cos-st-restricts.2.3.1.1) Invalid item type definition of simple type derived via <xs:list> |
Explanation |
The {final} of the {item type definition} must not contain list. |
Action |
Adapt the schema according to the constraint. |
INOXDE7625 | (cos-st-restricts.3.3.2.2) Invalid base type for simple type derived via <xs:restriction> |
Explanation |
The {final} of the {base type definition} must not contain restriction. |
Action |
Adapt the schema according to the constraint. |
INOXDE7626 | (cos-st-restricts.2.3.2.2) Invalid base type for simple type derived via <xs:restriction> |
Explanation |
The {final} of the {base type definition} must not contain restriction. |
Action |
Adapt the schema according to the constraint. |
INOXDE7627 | (cos-st-restricts.2.3.2.4) Invalid facet for simple type derived via <xs:list> |
Explanation |
Only length, minLength, maxLength, whiteSpace, pattern and enumeration facet components are allowed among the {facets}. |
Action |
Adapt the schema according to the constraint. |
INOXDE7628 | (cos-st-restricts.3.1) Invalid member type definition for simple type derived via <xs:union> |
Explanation |
The {member type definitions} must all have {variety} of atomic or list. |
Action |
Adapt the schema according to the constraint. |
INOXDE7629 | (cos-st-restricts.3.3.1.1) Invalid member type definition for simple type derived via <xs:union> |
Explanation |
All of the {member type definitions} must have a {final} which does not contain union. |
Action |
Adapt the schema according to the constraint. |
INOXDE7630 | (cos-st-restricts.3.3.2.4) Invalid facet for simple type derived via <xs:union> |
Explanation |
Only pattern and enumeration facet components are allowed among the {facets}. |
Action |
Adapt the schema according to the constraint. |
INOXDE7631 | (a-props-correct.1) Invalid type of attribute declaration - must be a simple type |
Explanation |
The type definition of an attribute declaration must be a simple type. |
Action |
Modify the type definition of the attribute declaration. |
INOXDE7632 | (st-props-correct.2) Invalid or circular type hierarchy of simple type definition |
Explanation |
All simple type definitions must be derived ultimately from the simple ur-type definition - circular definitions are disallowed. |
Action |
Adapt the schema according to the constraint. |
INOXDE7633 | (ct-props-correct.2) Invalid derivation of complex type with simple base type definition |
Explanation |
If the {base type definition} is a simple type definition, the {derivation method} must be extension. |
Action |
Adapt the schema according to the constraint. |
INOXDE7634 | (ct-props-correct.3) Invalid or circular type hierarchy of complex type definition |
Explanation |
Circular definitions are disallowed, except for the ur-type definition. That is, it must be possible to reach the ur-type definition by repeatedly following the {base type definition}. |
Action |
Adapt the schema according to the constraint. |
INOXDE7635 | (no-xsi) Invalid attribute declaration for targetNamespace |
Explanation |
The {target namespace} of an attribute declaration, whether local or top-level, must not match http://www.w3.org/2001/XMLSchema-instance, unless it is one of the four built-in declarations for xsi:type, xsi:nil, xsi:schemaLocation, xsi:noNamespaceSchemaLocation. |
Action |
Adapt the schema according to constraint. See XML Schema Part 1 for a valid declaration of the four built-in declarations. |
INOXDE7636 | (src-ct.1) Invalid base type definition of complex type with complex content |
Explanation |
If the <complexContent> alternative is chosen, the type definition resolved to by the actual value of the 'base' attribute must be a complex type definition. |
Action |
Adapt the schema according to the constraint. |
INOXDE7637 | (src-ct.2.1) Invalid base type definition of complex type simple content |
Explanation |
The type definition resolved to by the actual value of the 'base' attribute must be one of the following: (1) a complex type definition whose {content type} is a simple type definition; (2) only if the <restriction> alternative is also chosen, a complex type definition whose {content type} is mixed and a particle which is emptiable. |
Action |
Adapt the schema according to the constraint. |
INOXDE7638 | (src-ct.2.2) Missing <xs:simpleType> below <xs:restriction> for a complex type with simple content which is derived from a complex type via restriction |
Explanation |
If the <simpleContent>/<restriction> alternative is chosen with the 'base' attribute resolving to a complex type definition whose {content type} is mixed and a particle which is emptiable, there must be a <simpleType> among the [children] of <restriction>. |
Action |
Adapt the schema according to the constraint. |
INOXDE7639 | (cos-ct-extends.1.1) Invalid base type of complex type derived via <xs:extension> |
Explanation |
The {final} of the {base type definition} must not contain extension. |
Action |
Adapt the schema according to the constraint. |
INOXDE7640 | (cos-ct-extends.1.4.1) Simple content types of complex type derived via <xs:extension> and the respective base type definition do not match |
Explanation |
The {content type} of the {base type definition} and the {content type} of the complex type definition itself must be the same simple type definition. |
Action |
Adapt the schema according to the constraint. |
INOXDE7641 | (cos-ct-extends.1.4.2) If the content type of a complex type derived via <xs:extension> is empty, the content type of the respective complex base type definition must be empty as well |
Explanation |
The {content type} of both the {base type definition} and the complex type definition itself must be empty. |
Action |
Adapt the schema according to the constraint. |
INOXDE7642 | (cos-ct-extends.1.4.3.1) Invalid content type of a complex type definition derived via <xs:extension> given the content type of the complex base type definition |
Explanation |
The {content type} of the complex type definition itself must specify a particle. |
Action |
Adapt the schema according to the constraint. |
INOXDE7643 | (cos-ct-extends.1.4.3.2.2.1) Invalid content type of complex type definition derived via <xs:extension> from complex type definition |
Explanation |
Both {content type}s must be mixed or both must be element-only. |
Action |
Adapt the schema according to the constraint. |
INOXDE7644 | (cos-ct-extends.2.2) Invalid base type of complex type definition derived via <xs:extension> |
Explanation |
The {final} of the {base type definition} must not contain extension. |
Action |
Adapt the schema according to the constraint. |
INOXDE7645 | (derivation-ok-restriction.1) Invalid base type definition of complex type derived via <xs:restriction> |
Explanation |
The {base type definition} must be a complex type definition whose {final} does not contain restriction. |
Action |
Adapt the schema according to the constraint. |
INOXDE7646 | (derivation-ok-restriction.2.1.1) Invalid value of 'use' attribute of attribute in complex type definition derived via <xs:restriction> compared to value of 'use' attribute for respective attribute in complex base type definition. |
Explanation |
If there is an attribute use in the {attribute uses} of the {base type definition} (call this B) whose {attribute declaration} has the same {name} and {target namespace}, then one of the following must be true: (1) B's {required} is false. (2) the restricted type's {required} is true. |
Action |
Adapt the schema according to the constraint. |
INOXDE7647 | (derivation-ok-restriction.2.1.2) Invalid type of attribute in complex type definition derived via <xs:restriction> compared to type of respective attribute in complex base type definition. |
Explanation |
If there is an attribute use in the {attribute uses} of the {base type definition} (call this B) whose {attribute declaration} has the same {name} and {target namespace}, then the restricted type's {attribute declaration}'s {type definition} must be validly derived from B's {type definition}. |
Action |
Adapt the schema according to the constraint. |
INOXDE7648 | (derivation-ok-restriction.2.1.3) Invalid value constraint of attribute in complex type definition derived via <xs:restriction> compared to value constraint of respective attribute in complex base type definition |
Explanation |
If there is an attribute use in the {attribute uses} of the {base type definition} (call this B) whose {attribute declaration} has the same {name} and {target namespace}, then one of the following must be true: (1) B's effective value constraint is absent or default. (2) the restricted type's effective value constraint is fixed with the same string as B's. |
Action |
Adapt the schema according to the constraint. |
INOXDE7649 | (derivation-ok-restriction.2.2) Invalid attribute use in complex type definition derived via <xs:restriction>, the complex base type definition neither contains a matching attribute use nor an attribute wildcard. |
Explanation |
If there is no attribute use in the {attribute uses} of the {base type definition} (call this B) whose {attribute declaration} has the same {name} and {target namespace}, the {base type definition} must have an {attribute wildcard} and the {target namespace} of the restricted type's {attribute declaration} must be valid with respect to that wildcard. |
Action |
Adapt the schema according to the constraint. |
INOXDE7650 | (derivation-ok-restriction.3) Invalid value of 'use' attribute of attribute in complex type definition derived via <xs:restriction> compared to value of 'use' attribute for respective attribute in complex base type definition |
Explanation |
For each attribute use in the {attribute uses} of the {base type definition} whose {required} is true, there must be an attribute use with an {attribute declaration} with the same {name} and {target namespace} as its {attribute declaration} in the {attribute uses} of the complex type definition itself whose {required} is true. |
Action |
Adapt the schema according to the constraint. |
INOXDE7651 | (derivation-ok-restriction.4.1) Invalid attribute wildcard in complex type definition derived via <xs:restriction>, complex base type definition does not have an attribute wildcard |
Explanation |
If there is an {attribute wildcard}, the {base type definition} must also have one. |
Action |
Adapt the schema according to the constraint. |
INOXDE7652 | (derivation-ok-restriction.4.2) Invalid attribute wildcard in complex type definition derived via <xs:restriction>, its namespace constraint is not a subset of the namespace constraint of the attribute wildcard in the complex base type definition |
Explanation |
If there is an {attribute wildcard}, the complex type definition's {attribute wildcard}'s {namespace constraint} must be a subset of the {base type definition}'s {attribute wildcard}'s {namespace constraint}. |
Action |
Adapt the schema according to the constraint. |
INOXDE7653 | (derivation-ok-restriction.4.3) Invalid 'processContents' of attribute wildcard in complex type definition derived via <xs:restriction> compared to 'processContents' of attribute wildcard in complex base type definition |
Explanation |
If there is an {attribute wildcard}, and the {base type definition} is not the ur-type definition, the complex type definition's {attribute wildcard}'s {process contents} must be identical to or stronger than the {base type definition}'s {attribute wildcard}'s {process contents}, where strict is stronger than lax is stronger than skip. |
Action |
Adapt the schema according to the constraint. |
INOXDE7654 | (derivation-ok-restriction.5.1.2) Invalid base type for complex type with simple content derived via <xs:restriction> |
Explanation |
If the {content type} of the complex type definition is a simple type definition, one of the following must be true: (1) The {content type} of the {base type definition} must be a simple type definition from which the {content type} is validly derived (2) The {base type definition} must be mixed and have a particle which is emptiable |
Action |
Adapt the schema according to the constraint. |
INOXDE7655 | (derivation-ok-restriction.5.2.2) Invalid base type for complex type with empty content derived via <xs:restriction> |
Explanation |
If the {content type} of the complex type is empty, one of the following must be true: (1) The {content type} of the {base type definition} must also be empty. (2) The {content type} of the {base type definition} must be elementOnly or mixed and have a particle which is emptiable |
Action |
Adapt the schema according to the constraint. |
INOXDE7656 | (derivation-ok-restriction.5.3.1) Invalid base type for complex type with neither simple nor empty content derived via <xs:restriction> |
Explanation |
If the {content type} of the complex type definition is neither a simple type definition nor empty, one of the following must be true: (1) The {content type} of the complex type definition itself must be element-only (2) The {content type} of the complex type definition itself and of the {base type definition} must be mixed. |
Action |
Adapt the schema according to the constraint. |
INOXDE7657 | (derivation-ok-restriction.5.3.2) The particle of the complex type derived via restriction does not satisfy the "Particle Valid (Restriction)" constraint with respect to the particle of the complex base type |
Explanation |
If the {content type} of the complex type definition is neither a simple type definition nor empty, the particle of the complex type definition itself must be a valid restriction of the particle of the {content type} of the {base type definition}. |
Action |
Adapt the schema according to the constraint. |
INOXDE7658 | An element's or attribute's shortname definition does not match Adabas field definition |
Explanation |
A field with the given shortname does not exist in the Adabas file defined for this element. |
Action |
Adapt the schema to the corresponding Adabas field and file definitions. |
INOXDE7659 | The element's or attribute's Adabas format definition does not match the Adabas field definition |
Explanation |
The Adabas format definition cannot be converted to the format defined in the Adabas FDT. |
Action |
Adapt your schema to the corresponding Adabas field definitions. |
INOXDE7660 | An element's periodic group definition does not match the Adabas field definition |
Explanation |
The correspondingf Adabas field is not defined as a periodic group in the Adabas FDT. |
Action |
Adapt your schema corresponding to the Adabas field definition |
INOXDE7661 | An element's multiple field definition does not match the Adabas field definition |
Explanation |
The corresponding Adabas field is not defined as multiple field in Adabas. |
Action |
Adapt your schema definition to the corresponding Adabas definitions. |
INOXDE7662 | An element nillable definition does not match the Adabas field definition |
Explanation |
The element defined as xsi:nillable is not defined with NC (SQL NUll-Value Representation) -option in the Adabas FDT. |
Action |
Adapt the schema corresponding to the Adabas field definition. |
INOXDE7663 | An element's or attribute's format definition xs:date does not match the Adabas field definition |
Explanation |
An element defined as xs:date must be mapped to an ADABAS field with format P4. |
Action |
Adapt the schema to the corresponding Adabas definition. |
INOXDE7664 | An element's or attribute's format definition xs:dateTime does not match the Adabas field definition |
Explanation |
The element which is defined as xs:dateTime must be mapped to an Adabas field with format P7. |
Action |
Adapt the schema definition to the corresponding Adabas format. |
INOXDE7665 | (c-props-correct.1) An <xs:keyref> refers to an unknown <xs:key> |
Explanation |
The 'refer' attribute of <xs:keyref> must refer to a sibling node of type <xs:key> with a matching value of its 'name' attribute. |
Action |
Correct the schema document. |
INOXDE7666 | (c-props-correct.2) Invalid cardinality of <xs:field> child nodes of <xs:keyref> |
Explanation |
If the {identity-constraint category} is keyref, the cardinality of the {fields} must equal that of the {fields} of the {referenced key}. |
Action |
Correct the schema document. |
INOXDE7667 | (e-props-correct.3) The 'substitutionGroup' resolves to an unknown or invalid global element declaration |
Explanation |
The 'substitutionGroup' attribute of an element declaration, E1, must resolve to a global element, say E2, whose effective 'block' attribute, i.e. the substitution group exclusions do not contain the value "substitution". The {type definition} of E1 must be validly derived from the {type definition} of E2, using a derivation method not given in the effective 'block' attribute. |
Action |
Adapt the schema to match this constraint. |
INOXDE7668 | (cos-equiv-derived-ok-rec.1) Invalid relation of types of current element and its substitution group affiliate |
Explanation |
The derivation method of the type of the current element must be derived from the type of the substitution group affiliate's (i.e. the global element referenced by the 'substitutionGroup' attribute) type. The derivation method must be compatible with the substitution group exclusions defined by the 'block' attribute of the affiliate and the 'blockDefault' attribute of the respective schema node. |
Action |
Adapt schema to meet this constraint. |
INOXDE7669 | (e-props-correct.5) Found circular substitution group |
Explanation |
Circular substitution groups are disallowed. That is, it must not be possible to return to an element declaration by repeatedly following the {substitution group affiliation} property. |
Action |
Modify the schema to fulfill the constraint. |
INOXDE7670 | The 'final' attribute of a simple or complex type definition is more restrictive in the new schema compared to the old schema |
Explanation |
The 'final' attribute must not become more restrictive. |
Action |
Either adapt the value of the 'final' attribute or use instance validation when updating the schema. |
INOXDE7671 | A type definition has been set to abstract in the new schema |
Explanation |
When setting a type definition to abstract, this might cause documents to be invalid with respect to the new schema. |
Action |
Either make the type definition non-abstract as in the old schema or use instance validation when updating the schema. |
INOXDE7672 | An element declaration has been set to abstract in the new schema |
Explanation |
When setting an element declaration to abstract, this might cause documents to be invalid with respect to the new schema. |
Action |
Either make the element declaration non-abstract as in the old schema or use instance validation when updating the schema. |
INOXDE7673 | A complex type definition's 'block' attribute has been made more restrictive in the new schema |
Explanation |
When making a complex type definition's 'block' attribute more restrictive, this might cause documents to be invalid with respect to the new schema. |
Action |
Either set the complex type definition's 'block' attribute as in the old schema or use instance validation when updating the schema. |
INOXDE7674 | An element declaration's 'block' attribute has been made more restrictive in the new schema |
Explanation |
When making an element declaration's 'block' attribute more restrictive, this might cause documents to be invalid with respect to the new schema. |
Action |
Either set the element declaration's 'block' attribute as in the old schema or use instance validation when updating the schema. |
INOXDE7675 | An element's 'nillable' attribute was set to false in new schema |
Explanation |
If an element's 'nillable' attribute is set to false during a schema update, existing documents may become invalid. |
Action |
Either leave the element declaration's 'nillable' attribute unchanged or use instance validation for schema update. |
INOXDE7676 | Mismatch of identity constraints found during schema update |
Explanation |
It is not possible to modify existing or add new identity constraints during a schema update without using instance validation. |
Action |
Either do not add or modify identity constraints during schema update, or use instance validation. |
INOXDE7677 | An elements 'substitutionGroup' attribute was omitted or modified during schema update. |
Explanation |
An element's 'substitutionGroup' attribute may not be omitted or modified during schema update unless instance validation is being used. |
Action |
Either leave the 'substitutionGroup' attribute as is or use instance validation during schema update. |
INOXDE7680 | (length valid restriction) the length facet has been changed compared to the length facet of the base type |
Explanation |
It is an error if length is among the members of {facets} of {base type definition} and {value} is not equal to the {value} of the parent length. |
Action |
Modify the schema accordingly. |
INOXDE7681 | (maxLength valid restriction) the maxLength facet has been increased compared to the maxLength facet of the base type |
Explanation |
It is an error if maxLength is among the members of {facets} of {base type definition} and {value} is greater than the {value} of the parent maxLength. |
Action |
Modify the schema accordingly. |
INOXDE7682 | (minLength valid restriction) the minLength facet has been decreased compared to the minLength facet of the base type |
Explanation |
It is an error if minLength is among the members of {facets} of {base type definition} and {value} is less than the {value} of the parent minLength. |
Action |
Modify the schema accordingly. |
INOXDE7683 | (totalDigits valid restriction) the totalDigits facet has been increased compared to the totalDigits facet of the base type |
Explanation |
It is an error if totalDigits is among the members of {facets} of {base type definition} and {value} is greater than the {value} of the parent totalDigits. |
Action |
Modify the schema accordingly. |
INOXDE7684 | (fractionDigits valid restriction) the fractionDigits facet has been increased compared to the fractionDigits facet of the base type |
Explanation |
It is an error if fractionDigits is among the members of {facets} of {base type definition} and {value} is greater than the {value} of the parent totalDigits |
Action |
Modify the schema accordingly. |
INOXDE7685 | (maxExclusive valid restriction) the maxExclusive facet has been increased compared to the maxExclusive facet of the base type |
Explanation |
It is an error if any of the following conditions is true: 1. maxExclusive is among the members of {facets} of {base type definition} and {value} is greater than the {value} of the parent maxExclusive 2. maxInclusive is among the members of {facets} of {base type definition} and {value} is greater than the {value} of the parent maxInclusive 3. minInclusive is among the members of {facets} of {base type definition} and {value} is less than or equal to the {value} of the parent minInclusive 4. minExclusive is among the members of {facets} of {base type definition} and {value} is less than or equal to the {value} of the parent minExclusive |
Action |
Modify the schema accordingly. |
INOXDE7686 | (maxInclusive valid restriction) the maxInclusive facet has been increased compared to the maxInclusive facet of the base type |
Explanation |
It is an error if any of the following conditions is true: 1. maxInclusive is among the members of {facets} of {base type definition} and {value} is greater than the {value} of the parent maxInclusive 2. maxExclusive is among the members of {facets} of {base type definition} and {value} is greater than or equal to the {value} of the parent maxExclusive 3. minInclusive is among the members of {facets} of {base type definition} and {value} is less than the {value} of the parent minInclusive 4. minExclusive is among the members of {facets} of {base type definition} and {value} is less than or equal to the {value} of the parent minExclusive |
Action |
Modify the schema accordingly. |
INOXDE7687 | (minExclusive valid restriction) the minExclusive facet has been increased compared to the minExclusive facet of the base type |
Explanation |
It is an error if any of the following conditions is true: 1. minExclusive is among the members of {facets} of {base type definition} and {value} is less than the {value} of the parent minExclusive 2. maxInclusive is among the members of {facets} of {base type definition} and {value} is greater the {value} of the parent maxInclusive 3. minInclusive is among the members of {facets} of {base type definition} and {value} is less than the {value} of the parent minInclusive 4. maxExclusive is among the members of {facets} of {base type definition} and {value} is greater than or equal to the {value} of the parent maxExclusive |
Action |
Modify the schema accordingly. |
INOXDE7688 | (minInclusive valid restriction) the minInclusive facet has been increased compared to the minInclusive facet of the base type |
Explanation |
It is an error if any of the following conditions is true: 1. minInclusive is among the members of {facets} of {base type definition} and {value} is less than the {value} of the parent minInclusive 2. maxInclusive is among the members of {facets} of {base type definition} and {value} is greater the {value} of the parent maxInclusive 3. minExclusive is among the members of {facets} of {base type definition} and {value} is less than or equal to the {value} of the parent minExclusive 4. maxExclusive is among the members of {facets} of {base type definition} and {value} is greater than or equal to the {value} of the parent maxExclusive |
Action |
Modify the schema accordingly. |
INOXDE7689 | (whiteSpace valid restriction) the whiteSpace facet has been changed to an invalid value compared to the whiteSpace facet of the base type |
Explanation |
It is an error if whiteSpace is among the members of {facets} of {base type definition} and any of the following conditions is true: 1. {value} is replace or preserve and the {value} of the parent whiteSpace is collapse 2. {value} is preserve and the {value} of the parent whiteSpace is replace |
Action |
Modify the schema accordingly. |
INOXDE7690 | (facet fixed) attempted to specify a different value for a facet which has fixed="true" in the base type definition |
Explanation |
The value of the facet differs from the value of the facet in the base type definition. |
Action |
Omit the facet in the derived value or remove fixed="true" from the base type definition. |
INOXDE7696 | Invalid change of schema-required property of collection |
Explanation |
A collection must be either schemaless or schemas are required for all documents to be stored. It is not allowed to change the schema-required property. |
Action |
Adapt the collection description correspondingly. |
INOXDE7697 | Could not create schemaless doctype in collection ino:etc |
Explanation |
It is not possible to have two schemaless doctypes in collection 'ino:etc' with the same lexical QName but different namespace of the root element. |
Action |
A workaround is to change the namespace prefix of the root element of the first instance to be inserted in a new implicit doctype. |
INOXDE7698 | (c-selector-xpath) Found invalid value of xpath attribute in definition of selector of identity constraint |
Explanation |
The xpath attribute of the selector of an identity constraint must adhere to the (c-selector-xpath) constraint. |
Action |
Fix the value of the xpath attribute: all name tests must use valid QNames, all namespace prefixes must be declared, no attribute steps allowed. |
INOXDE7699 | (c-fields-xpaths) Found invalid value of xpath attribute in definition of selector of identity constraint |
Explanation |
The xpath attribute of all fields of an identity constraint must adhere to the (c-fields-xpaths) constraint. |
Action |
Fix the value of the xpath attribute: all name tests must use valid QNames, all namespace prefixes must be declared, an attribute step is only allowed at the last position. |
INOXDE7700 | successful document validation |
Explanation |
The document validated without error. |
Action |
No action required. |
INOXDE7701 | memory allocation failed |
Explanation |
Memory allocation failed during document validation. |
Action |
Please contact your software supplier. |
INOXDE7702 | internal error |
Explanation |
An internal processing error occurred during document validation. |
Action |
Please contact your software supplier. |
INOXDE7703 | validation has detected an error in document |
Explanation |
The document validation has discovered some invalid document content. |
Action |
Modify your document. |
INOXDE7704 | (Parse error): document not well-formed |
Explanation |
The document content is not well-formed. |
Action |
Modify your document |
INOXDE7705 | (Parse error): junk data |
Explanation |
The document contains junk data after the document content. |
Action |
Modify your input stream. |
INOXDE7706 | (Parse error): close element error |
Explanation |
The document contains a closing tag that does not match opening tag. |
Action |
Modify your document |
INOXDE7707 | (Parse error): multiple attr |
Explanation |
The document contains multiple occurrences of the same attribute. |
Action |
Modify your document |
INOXDE7708 | Invalid root error |
Explanation |
Tamino allows only insertion of documents with root elements whose names correspond to the name of some doctype in the collection where you tried to insert the current document. |
Action |
Modify your document or schema. |
INOXDE7709 | Errors detected during document validation |
Explanation |
Errors were detected during document validation. |
Action |
Please either modify your XML schema or fix errors in your document(s). |
INOXDE7710 | (cvc-complex-type.2.1): empty content error |
Explanation |
The schema requires empty element content but some content was detected. |
Action |
Modify your document or schema. |
INOXDE7711 | (cvc-complex-type.2.3): mixed content error |
Explanation |
The schema does not allow mixed element content but some mixed content was detected. |
Action |
Modify your document or schema. |
INOXDE7712 | (cvc-complex-type.4): required attribute missing |
Explanation |
The schema requires an attribute that is not present in document. |
Action |
Modify your document or schema. |
INOXDE7713 | (cvc-wildcard.2): undeclared wildcard element |
Explanation |
Schema contains ANY with processContent = strict but element content's name does not match any globally declared element. |
Action |
Modify your document or schema. |
INOXDE7714 | (cvc-id.1): undefined IDREF value |
Explanation |
The document contains an IDREF value which does not exist as an ID value. |
Action |
Modify your document. |
INOXDE7715 | (cvc-id.2): duplicate ID value |
Explanation |
The document contains multiple copies of the same ID value. |
Action |
Modify your document. |
INOXDE7716 | (cvc-assess-attr.1): undeclared attribute |
Explanation |
No matching declaration can be found in the schema for an attribute, neither as an explicitly named attribute nor as attribute wildcard. |
Action |
Modify your document. |
INOXDE7717 | (cvc-type.3.1.1): invalid attribute |
Explanation |
A simple type description in the schema does not allow attributes here. |
Action |
Modify your document. |
INOXDE7718 | (cvc-type.3.1.2): invalid element content |
Explanation |
A simple type description in the schema does not allow element children here. |
Action |
Modify your document. |
INOXDE7719 | (cvc-particle): content of element does not match a particle description |
Explanation |
Element content cannot be successfully validated against a particle description in schema. |
Action |
Modify your document. |
INOXDE7720 | (cvc-particle.1.1): element content missing, minOccurs constraint violation in wildcard declaration |
Explanation |
The length of the element content sequence does not satisfy the minOccurs constraint. |
Action |
Modify your document. |
INOXDE7721 | (cvc-particle.1.2): too much element content, maxOccurs constraint violation in wildcard declaration |
Explanation |
The length of the element content sequence does not satisfy the maxOccurs constraint of the wildcard declaration. |
Action |
Modify your document. |
INOXDE7722 | (cvc-particle.2.1): element content missing, minOccurs constraint violation in element declaration |
Explanation |
The length of the element content sequence does not satisfy the minOccurs constraint. |
Action |
Modify your document. |
INOXDE7723 | (cvc-particle.2.2): too much element content, maxOccurs constraint violation in element declaration |
Explanation |
The length of the element content sequence does not match the maxOccurs constraint for the element declaration. |
Action |
Modify your document. |
INOXDE7724 | (cvc-particle.3.1): element content missing, minOccurs constraint violation in all model group declaration |
Explanation |
The length of the element content sequence does not satisfy the minOccurs constraint. |
Action |
Modify your document. |
INOXDE7725 | (cvc-particle.3.1): element content missing, minOccurs constraint violation in choice model group declaration |
Explanation |
The length of the element content sequence does not satisfy the minOccurs constraint. |
Action |
Modify your document. |
INOXDE7726 | (cvc-particle.3.1): element content missing, minOccurs constraint violation in sequence model group declaration |
Explanation |
The length of the element content sequence does not satisfy the minOccurs constraint. |
Action |
Modify your document. |
INOXDE7727 | (cvc-particle.3.2): too much element content, maxOccurs constraint violation in all model group declaration |
Explanation |
The length of the element content sequence does not satisfy the maxOccurs constraint of the all model group declaration. |
Action |
Modify your document. |
INOXDE7728 | (cvc-particle.3.2): too much element content, maxOccurs constraint violation in choice model group declaration |
Explanation |
The length of the element content sequence does not satisfy the maxOccurs constraint of the choice model group declaration. |
Action |
Modify your document. |
INOXDE7729 | (cvc-particle.3.2): too much element content, maxOccurs constraint violation in sequence model group declaration |
Explanation |
The length of the element content sequence does not satisfy the maxOccurs constraint of the sequence model group declaration. |
Action |
Modify your document. |
INOXDE7730 | (cvc-model-group.1):invalid end of sequence |
Explanation |
A sequence does not contain all required elements. In particular, the sequence ends without containing all required elements. |
Action |
Modify your document. |
INOXDE7731 | (cvc-model-group.1):invalid sequence |
Explanation |
A sequence does not contain all required elements. |
Action |
Modify your document. |
INOXDE7732 | (cvc-model-group.2):invalid choice |
Explanation |
An element's child node does not match any choice in schema. |
Action |
Modify your document. |
INOXDE7733 | (cvc-model-group.3):invalid all - missing element |
Explanation |
An element's child node does not contain all required children of the all model group in the schema. |
Action |
Modify your document. |
INOXDE7734 | (cvc-model-group.3):invalid all - undeclared element |
Explanation |
An element's child node does not match any node declared in the all model group in the schema. |
Action |
Modify your document. |
INOXDE7735 | (cvc-model-group.3):invalid all - too many child elements |
Explanation |
All allowed elements in an all model group already appeared, but there are more illegal child elements. |
Action |
Modify your document. |
INOXDE7736 | (cvc-model-group.3):invalid all - repeated occurrence of one element |
Explanation |
Every child element in an all model group may appear at most once, but here the element appears more often. |
Action |
Modify your document. |
INOXDE7737 | (cvc-wildcard-namespace): invalid namespace with respect to namespace constraint of wildcard |
Explanation |
For namespace="##other" a non-absent namespace is required, which differs from the targetNamespace of the schema. For namespace="##targetNamespace" the namespace must match the current schema's targetNamespace. For namespace="##local" the element or attribute matching vs. the wildcard must not belong to any namespace. If the namespace attribute of the wildcard contains a list of URIs the namespace of the element or attribute matching vs. the wildcard must match one of the URIs in the list. |
Action |
Modify your document or schema. |
INOXDE7738 | (cvc-wildcard-namespace.2.3): invalid namespace for wildcard with namespace="##other" |
Explanation |
The namespace of an element or attribute does not differ from the current schema's targetNamespace as required by namespace='##other' specified in a wildcard (xs:any or xs:anyAttribute). |
Action |
Modify your document. |
INOXDE7739 | (cvc-wildcard-namespace.3): invalid namespace for wildcard with namespace="##local" |
Explanation |
An element or attribute belongs to a namespace in contradiction to the namespace="##local" attribute of a wildcard (xs:any or xs:anyAttribute). |
Action |
Modify your document. |
INOXDE7740 | (cvc-complex-type.2.4): element child error |
Explanation |
The list of child elements could not to be partitioned in a way that it becomes valid with respect to the content type's particle. |
Action |
Modify your document or schema. |
INOXDE7741 | A namespace prefix conflict was detected when attempting to insert default or fixed value |
Explanation |
A namespace prefix used in a value constraint for a node whose datatype is xs:QName, xs:NOTATION or a derived type cannot be associated with the intended URI as the document already contains a namespace declaration for that prefix mapped to a different URI. Note that the default namespace is always assumed to be used. |
Action |
Adapt the document to be stored or the fragment to be inserted to avoid conflict. |
INOXDE7742 | (cvc-elt.4.3) The local type definition given by the xsi:type attribute is not validly derived from the type definition as of the underlying schema |
Explanation |
The local type definition given by the xsi:type attribute must be derived from the type definition as of the underlying schema. Derivation methods listed in the attribute named "block" of the element declaration or the associated complex type definition may not be used. |
Action |
Either modify the schema by changing or removing the "block" attribute of the element declaration or complex type definition, or modify or remove the xsi:type attribute from the document to be stored. |
INOXDE7743 | (cvc-elt.2) For an element information item to be locally valid with respect to an element declaration the declaration's abstract must be 'false' |
Explanation |
Found an element declaration which is abstract when attempting to validate an element. |
Action |
Change the value of the 'abstract' property of the respective element declaration. |
INOXDE7744 | (cvc-complex-type.1) For an element information item to be locally valid with respect to a complex type definition the type definition's abstract must be 'false' |
Explanation |
Attempted to validate an element against a complex type definition which is abstract. |
Action |
Either make the type definition non-abstract, or use the xsi:type attribute in the XML document referring to a non-abstract derived type. |
INOXDE7745 | (cvc-identity-constraint.3) An <xs:field> of an identity constraint caused multiple matching nodes or the respective node does not have a simple type |
Explanation |
For each node in the target node set of an identity constraint, all of the {fields} for a selected context node evaluate to either an empty node-set or a node-set with exactly one member, which must have a simple type. |
Action |
Check the XML document or remove the identity constraint from the schema. |
INOXDE7746 | (cvc-identity-constraint.4.1) Found multiple occurrence of same key-sequence for <xs:unique> identity constraint |
Explanation |
No two members of the qualified node set of an <xs:unique> may have key-sequences whose members are pairwise equal. |
Action |
Check the XML document or remove the identity constraint from the schema. |
INOXDE7747 | (cvc-identity-constraint.4.2.1) A field of an <xs:key> identity constraint evaluates to an empty node-set |
Explanation |
For <xs:key>, all the {fields} must evaluate to a node-set with exactly one member. |
Action |
Check the XML document or remove the identity constraint from the schema. |
INOXDE7748 | (cvc-identity-constraint.4.2.2) Found multiple occurrence of same key-sequence for <xs:key> identity constraint |
Explanation |
No two members of the qualified node set of an <xs:key> may have key-sequences whose members are pairwise equal. |
Action |
Check the XML document or remove the identity constraint from the schema. |
INOXDE7749 | (cvc-identity-constraint.4.3) Could not locate matching key sequence in node table of <xs:key> identity constraint referenced by <xs:keyref> |
Explanation |
For each member of the qualified node set of a <xs:keyref> there must be a corresponding entry in the node table of the referenced <xs:key>. |
Action |
Check the XML document or remove the identity constraint from the schema. |
INOXDE7750 | (cvc-elt.3.1) Attribute 'xsi:nil' not allowed if the 'nillable' attribute of the element declaration is not set to 'true' |
Explanation |
The predefined 'xsi:nil' attribute is only allowed on an element information item if the corresponding element declaration in the schema has its 'nillable' attribute to 'true'. |
Action |
Check the schema or remove the 'xsi:nil' attribute from the document. |
INOXDE7751 | (cvc-elt.3.2.1) Found character or element content inside element information item with xsi:nil='true' |
Explanation |
If an element has the xsi:nil='true' attribute, it must not have any character or element content. |
Action |
Modify the document accordingly. |
INOXDE7752 | (cvc-elt.3.2.2) Element declaration corresponding to element information item with xsi:nil='true' attribute has a fixed value constraint |
Explanation |
For an element information item with xsi:nil='true' attribute the corresponding element declaration in the schema must not have a fixed value constraint. |
Action |
Remove either the 'nillable' or the 'fixed' attribute from the element declaration in the schema. |
INOXDE7753 | (cos-equiv-derived-ok-rec.2.1) The effective blocking constraint of the element to be substituted contains 'substitution' |
Explanation |
The blocking constraint of an element to be substituted during validation must not contain 'substitution'. |
Action |
Adapt the XML document or modify the 'block' or 'blockDefault' attributes in the schema to become consistent with the constraint. |
INOXDE7754 | (cos-equiv-derived-ok-rec.2.3) Type derivation between type of element to be substituted and type of the substituting element is blocked by the effective 'block' attribute of the element to be substituted |
Explanation |
The type of the substituting element must be derived from the type of the element to be substituted by means of restriction and/or extension, unless one of those derivation methods is being blocked by the 'block' attribute (if present) of the element to be substituted, or the 'blockDefault' attribute of the parent schema. |
Action |
Adapt the XML document or modify the 'block' or 'blockDefault' attributes in the schema to become consistent with the constraint. |
INOXDE7761 | (cvc-datatype-valid) Overflow detected during validation |
Explanation |
A value overflow has been detected during validation against the XML schema. |
Action |
Ensure that the values adhere to datatype specific limits. |
INOXDE7762 | (cvc-datatype-valid) Value out of range detected during validation |
Explanation |
A value smaller than the valid minimum or larger than the allowed maximum has been detected during validation against the XML schema. |
Action |
Ensure that the values adhere to the datatype specific minimum and maximum. |
INOXDE7763 | (cvc-datatype-valid) An invalid value has been found during validation |
Explanation |
A value outside the lexical space has been detected during validation against the XML schema. |
Action |
Ensure that the value adheres to the datatype specific lexical space. |
INOXDE7764 | (cvc-enumeration-valid) A value not defined in the respective enumeration has been found during validation. |
Explanation |
A value which is not listed in the respective enumeration has been detected during validation against the XML schema. |
Action |
Ensure that the value matches one of the enumeration values specified in the XML schema. |
INOXDE7765 | (cvc-length-valid) Facet 'length' was violated by a value during validation. |
Explanation |
A value whose length does not match the 'length' facet has been detected during validation against the XML schema. |
Action |
Ensure that the value's length matches the restriction given by the schema. |
INOXDE7766 | (cvc-attribute.4): fixed value error |
Explanation |
An attribute declaration in schema requires a fixed value which is different from given value in document. |
Action |
Modify your document. |
INOXDE7767 | (cvc-elt.5.2.2.2.1): fixed value error |
Explanation |
The element declaration in schema requires a fixed value which is different from given value in document. |
Action |
Modify your document. |
INOXDE7768 | (cvc-au): fixed value error |
Explanation |
The attribute use declaration in the schema requires a fixed value which is different from the given value in the document. |
Action |
Modify your document. |
INOXDE7769 | (cvc-elt.5.2.2.2.2): fixed value error |
Explanation |
The element declaration in the schema requires a fixed value which is different from given value in document. |
Action |
Modify your document. |
INOXDE7770 | (cvc-minLength-valid) Facet 'minLength' was violated by a value during validation |
Explanation |
A value whose length is less than the 'minLength' facet has been detected during validation against the XML schema. |
Action |
Ensure that the value's length matches the restriction given by the schema. |
INOXDE7771 | (cvc-maxLength-valid) Facet 'maxLength' was violated by a value during validation |
Explanation |
A value whose length is greater than the 'maxLength' facet has been detected during validation against the XML schema. |
Action |
Ensure that the value's length matches the restriction given by the schema. |
INOXDE7772 | (cvc-pattern-valid) Facet 'pattern' was violated by a value during validation |
Explanation |
A value whose pattern does not match the 'pattern' facet has been detected during validation against the XML schema. |
Action |
Ensure that the value's pattern matches the restriction given by the schema. |
INOXDE7773 | (cvc-enumeration-valid) Facet 'enumeration' was violated by a value during validation |
Explanation |
A value has been found which does not match the valid values specified by the 'enumeration' facet, during validation against the XML schema. |
Action |
Ensure that the value matches the restriction given by the schema. |
INOXDE7774 | (cvc-maxInclusive-valid) Facet 'maxInclusive' was violated by a value during validation |
Explanation |
A value has been found which is greater than the 'maxInclusive' facet, during validation against the XML schema. |
Action |
Ensure that the value matches the restriction given by the schema. |
INOXDE7775 | (cvc-maxExclusive-valid) Facet 'maxExclusive' was violated by a value during validation |
Explanation |
A value has been found which is greater or equal to the 'maxExclusive' facet, during validation against the XML schema. |
Action |
Ensure that the value matches the restriction given by the schema. |
INOXDE7776 | (cvc-minInclusive-valid) Facet 'minInclusive' was violated by a value during validation |
Explanation |
A value has been found which is lower than the 'minInclusive' facet, during validation against the XML schema. |
Action |
Ensure that the value matches the restriction given by the schema. |
INOXDE7777 | (cvc-minExclusive-valid) Facet 'minExclusive' was violated by a value during validation |
Explanation |
A value has been found which is less than or equal to the 'minExclusive' facet, during validation against the XML schema. |
Action |
Ensure that the value matches the restriction given by the schema. |
INOXDE7778 | (cvc-totalDigits-valid) Facet 'totalDigits' was violated by a value during validation |
Explanation |
A numerical value has been found with more digits than specified by the 'totalDigits' facet, during validation against the XML schema. |
Action |
Ensure that the value matches the restriction given by the schema. |
INOXDE7779 | (cvc-fractionDigits-valid) Facet 'fractionDigits' was violated by a value during validation |
Explanation |
A numerical value has been found with more fractional digits (i.e. to the right of the decimal point) than specified by the 'fractionDigits' facet, during validation against the XML schema. |
Action |
Ensure that the value matches the restriction given by the schema. |
INOXDE7780 | Divide by zero error |
Explanation |
An attempt was made to divide by zero. Division by zero is mathematically undefined. |
Action |
Make sure that no division by zero occurs. |
INOXDE7781 | Invalid or unsupported attribute found |
Explanation |
An attribute was found that is not supported by Tamino. |
Action |
In order to enable xsi:type processing you have to set the server parameter "reject xsi:type" to "no". |
INOXDE7782 | Namespace prefix is bound to an invalid URI |
Explanation |
A namespace prefix must be bound to a non-empty URI in a namespace declaration. In addition, some prefixes must be bound to a fixed URI. |
Action |
Ensure e.g. that the prefix 'xml' is bound to 'http://www.w3.org/XML/1998/namespace', and that 'ino' is bound to 'http://namespaces.softwareag.com/tamino/response2'. |
INOXDE7783 | The namespace prefix in an element or attribute value is not declared |
Explanation |
If an element's or attribute's type is xs:QName or xs:NOTATION, the respective prefix must be declared in the schema document. |
Action |
Add the missing namespace declaration. |
INOXDE7784 | Invalid namespace prefix |
Explanation |
A namespace prefix is invalid. |
Action |
Modify the namespace definition and repeat the request. |
INOXDE7785 | The datatype referenced by xsi:type is unknown |
Explanation |
The value of the xsi:type attribute must reference a datatype predefined by XML Schema or a user-defined global datatype. |
Action |
Check the type reference via xsi:type in XML document. |
INOXDE7786 | Invalid prefix bound to URI |
Explanation |
The URI cannot be bound to the given namespace prefix. |
Action |
Use an appropriate prefix. |
INOXDE7787 | Invalid value of 'xsi:nil' attribute |
Explanation |
The value of the 'xsi:nil' attribute must be a valid boolean, i.e. 'true', 'false', '1', or '0'. |
Action |
Modify the document accordingly. |
INOXDE7821 | Class not found |
Explanation |
Tamino schema tree internal error message. |
Action |
Please contact your system administrator. |
INOXDE7822 | Duplicated class name |
Explanation |
Tamino schema tree internal error message. |
Action |
Please contact your system administrator. |
INOXDE7823 | Illegal cast |
Explanation |
Tamino schema tree internal error message. |
Action |
Please contact your system administrator. |
INOXDE7824 | Internal API error |
Explanation |
Tamino schema tree internal error. |
Action |
Please contact your software supplier. |
INOXDE7827 | No memory |
Explanation |
Tamino schema tree internal error message. |
Action |
Please contact your system administrator. |
INOXDE7828 | No such element |
Explanation |
Tamino schema tree internal error message. |
Action |
Please contact your system administrator. |
INOXDE7829 | Not implemented |
Explanation |
Tamino schema tree internal error message. |
Action |
Please contact your system administrator. |
INOXDE7830 | Too many classes |
Explanation |
Tamino schema tree internal error message. |
Action |
Please contact your system administrator. |
INOXDE7831 | XML parser error |
Explanation |
Tamino schema tree internal error message. |
Action |
Please contact your system administrator. |
INOXDE7833 | Operation failed |
Explanation |
An internal error occurred. |
Action |
Please contact your software supplier. |
INOXDE7856 | Buffer size exceeded |
Explanation |
Tamino schema tree error message. |
Action |
Please contact your system administrator. |
INOXDE7860 | Internal error: invalid node type |
Explanation |
This is a Tamino schema tree error message. |
Action |
Please contact your system administrator. |
INOXDE7861 | Index out of range |
Explanation |
Tamino schema tree error message. |
Action |
Please contact your system administrator. |
INOXDE7862 | User abort |
Explanation |
Tamino schema tree internal error message. |
Action |
Please contact your system administrator. |
INOXDE7865 | Schema cache: access denied |
Explanation |
Schema cache: access denied. |
Action |
Please contact your software supplier. |
INOXDE7867 | Internal error: schema not in cache |
Explanation |
Internal error: schema not in cache. |
Action |
Please contact your software supplier. |
INOXDE7868 | Internal error: write lock expected |
Explanation |
Internal error: write lock expected. |
Action |
Please contact your software supplier. |
INOXDE7869 | Internal error: schema not locked |
Explanation |
Internal error: schema not locked. |
Action |
Please contact your software supplier. |
INOXDE7883 | (p-props-correct.2.1) If maxOccurs has a numeric value, then minOccurs must not be greater than maxOccurs |
Explanation |
If maxOccurs has a numeric value, then minOccurs must not be greater than maxOccurs. |
Action |
Modify the XML schema accordingly. |
INOXDE7884 | (p-props-correct.2.2) If maxOccurs has a numeric value, then maxOccurs must be greater than or equal to 1 |
Explanation |
If maxOccurs has a numeric value, then maxOccurs must be greater than or equal to 1. |
Action |
Modify the XML schema accordingly. |
INOXDE7885 | (src-attribute.2) use must have value optional |
Explanation |
If the attribute's "default" and "use" attributes are both present, then "use" must have the value "optional". |
Action |
Modify the XML schema accordingly. |
INOXDE7886 | (src-attribute.4) For attribute the type and simpleType must not both be present |
Explanation |
For attribute, the type and simpleType must not both be present. |
Action |
Modify the XML schema accordingly. |
INOXDE7887 | (src-element.1) For element the attributes default and fixed must not both be present |
Explanation |
For element, the attributes "default" and "fixed" must not both be present. |
Action |
Modify the XML schema accordingly. |
INOXDE7888 | (src-element.3) For element the attributes type and either simpleType or complex Type are mutually exclusive |
Explanation |
For element, the attributes "type" and either "simpleType" or "complex Type" are mutually exclusive. |
Action |
Modify the XML schema accordingly. |
INOXDE7889 | (src-element.2.1) For element either the attribute ref or name must be present, but not both |
Explanation |
For element, either the attribute ref or name must be present, but not both. |
Action |
Modify the XML schema accordingly. |
INOXDE7890 | (src-element.2.2) For element if parent is not schema and attribute ref is present, only attributes minOccurs, maxOccurs and id are allowed in addition to ref |
Explanation |
If the parent of the element is not schema and the attribute ref is present, then all of <xs:complexType>, <xs:simpleType>, <xs:key>, <xs:keyref>, <xs:unique>, nillable, default, fixed, form, block and type must be absent. |
Action |
Modify the XML schema accordingly. |
INOXDE7891 | (valid-data-types.1) The type of nodes and base attribute of restriction nodes may only be of the supported types |
Explanation |
The type of nodes and base attribute of restriction nodes may only be of the supported types, namely: date, decimal, double, float, integer, short, SQLNumeric,, SQLVarchar, string, time, timeinstant, ID, IDREF, IDREFS, NMTOKEN, NMTOKENS. No user-defined complexType or simpleType are allowed for type. |
Action |
Modify the XML schema accordingly. |
INOXDE7895 | (valid-data-types.2) The facet is not valid for the base datatype |
Explanation |
A facet has been specified which is not supported for the base datatype of a restriction. |
Action |
Modify the XML schema accordingly. |
INOXDE7900 | (length and minLength or maxLength) Conflict between length facet and either minLength or maxLength |
Explanation |
It is an error for both length and either of minLength or maxLength to be members of {facets}, unless they are specified in different derivation steps in which case the following must be true: the {value} of minLength <= the {value} of length <= the {value} of maxLength. |
Action |
Modify the XML schema accordingly. |
INOXDE7901 | (fractionDigits less than or equal to totalDigits) The value of the fractionDigits facet is greater than the value of totalDigits |
Explanation |
It is an error for fractionDigits to be greater than totalDigits. |
Action |
Modify the XML schema accordingly. |
INOXDE7902 | The root node of a doctype has a non-trivial substitution group |
Explanation |
The root node of a doctype must not have a non-trivial substitution group. The QName of the root element of an XML document stored in a doctype must be identical to the doctype's QName. |
Action |
Remove the substitutionGroup reference to the root node from the schema. |
INOXDE7906 | Found illegal logical or physical property for shadowXML doctype |
Explanation |
It is not allowed to specify certain logical or physical properties, e.g. XNode mapping, for a shadowXML doctype. |
Action |
Remove the illegal property below <tsd:logical> and <tsd:physical> for the shadowXML doctype. |
INOXDE7907 | (src-resolve.1.3) The ref attribute of an element needs to reference an existing global element |
Explanation |
The ref attribute of an element needs to reference an existing global element. |
Action |
Modify the XML schema accordingly. |
INOXDE7908 | Found logical or physical properties for nonXML doctype |
Explanation |
It is not allowed to specify logical or physical properties for a nonXML doctype. |
Action |
Remove <tsd:logical> and <tsd:physical> for the nonXML doctype. |
INOXDE7909 | (cos-nonambig.1) Unique Particle Attribution failure |
Explanation |
A content model must be formed such that during validation of an element information item sequence, the particle contained directly, indirectly or implicitly therein with which to attempt to validate each item in the sequence in turn can be uniquely determined without examining the content or attributes of that item, and without any information about the items in the remainder of the sequence. |
Action |
Modify the XML schema accordingly. |
INOXDE7910 | (cos-all-limited.1.2) All group limitation failure |
Explanation |
The cardinality of an all-model group must be exactly one. |
Action |
Modify the XML schema accordingly. |
INOXDE7911 | (cos-all-limited.2) All group limitation failure |
Explanation |
The maximum cardinality of all elements in all-model group must be 0 or 1. |
Action |
Modify the XML schema accordingly. |
INOXDE7912 | (src-attribute.1) For attribute declarations, their attributes default and fixed must not both be present |
Explanation |
For attribute declarations, the attributes "default" and "fixed" must not both be present. |
Action |
Modify the XML schema accordingly. |
INOXDE7913 | (src-attribute.3.1) Either attribute ref or name must be present, but not both |
Explanation |
Either the attribute "ref" or the attribute "name" must be present, but not both. |
Action |
Modify the XML schema accordingly. |
INOXDE7914 | (src-attribute.3.2) If attribute's parent is not schema and ref is present, <simpleType>, form and type are not allowed |
Explanation |
The form or type attribute as well as a simpleType cannot be specified with attribute declarations if the parent is not the schema node and the ref attribute is present. |
Action |
Modify the XML schema accordingly. |
INOXDE7915 | The doctype name needs to be unique within a collection |
Explanation |
The doctype name needs to be unique within a collection. |
Action |
Modify the XML schema accordingly. |
INOXDE7916 | The given path must exist in the current schema |
Explanation |
The given path must exist in the current schema. |
Action |
Modify the XML schema accordingly. |
INOXDE7917 | For each doctype name where the doctype is not of plain non-XML type there must be a matching global element with a matching qualified name |
Explanation |
For each doctype name where the doctype is not of plain non-XML type there must be a matching global element with a matching qualified name. In particular, for non-XML doctypes with non-XML indexing via a shadow XML document a matching global element must exist. |
Action |
Modify the XML schema accordingly. |
INOXDE7918 | For each doctype name where the doctype is of type nonXML there must not be a matching global element with the same name |
Explanation |
For each doctype name where the doctype is of type non-XML there must not be a matching global element with the same name. |
Action |
Modify the XML schema accordingly. |
INOXDE7919 | For accessOptions at least one of read, insert, update or delete needs to be given, but no duplicate entries of these are allowed |
Explanation |
For accessOptions at least one of read, insert, update or delete needs to be given, but no duplicate entries of these are allowed. |
Action |
Modify the XML schema accordingly. |
INOXDE7920 | Invalid node name |
Explanation |
The name of an element or attribute does not match the repository naming conventions. |
Action |
Change the name of element or attribute. |
INOXDE7921 | Attempted to re-use a schema specifying physical properties from a schema belonging to a different collection |
Explanation |
This constraint has been introduced in order to prevent database inconsistencies. It may vanish in a future version of Tamino. |
Action |
Change the collection name either of the referenced or the referring schema. |
INOXDE7922 | The given path must exist in the current Schema and lead to the element or attribute for which it is specified |
Explanation |
The given path must exist in the current schema and lead to the element or attribute for which it is specified. |
Action |
Modify the XML schema accordingly. |
INOXDE7923 | No XPath expression may occur twice for one node to avoid conflicting mappings |
Explanation |
No XPath expression may occur twice for one node in order to avoid conflicting mappings (not even if it specifies the same mapping). |
Action |
Modify the XML schema accordingly. |
INOXDE7924 | At most one elementInfo or attributeInfo may have only empty or a nonexistent which-element, which is taken as the default mapping |
Explanation |
At most one elementInfo or attributeInfo may have only empty or a non-existent which element, which is taken as the default mapping (Note: empty which elements are ignored, so an elementInfo which has both empty and filled which elements is interpreted as an elementInfo with filled which elements). |
Action |
Modify the XML schema accordingly. |
INOXDE7925 | Below Schema there may only be one appinfo node which defines Tamino mappings |
Explanation |
Below Schema there may only be one appinfo node which defines Tamino mappings. |
Action |
Modify the XML schema accordingly. |
INOXDE7926 | Below Schema there must be a schemaInfo node but no elementInfo or attributeInfo nodes |
Explanation |
Below Schema there must be a schemaInfo node but no elementInfo or attributeInfo nodes. |
Action |
Modify the XML schema accordingly. |
INOXDE7927 | Below Element there may only be one appinfo node which defines Tamino mappings |
Explanation |
Below Element there may only be one appinfo node which defines Tamino mappings. |
Action |
Modify the XML schema accordingly. |
INOXDE7928 | Below Element there may be only elementInfo node but no schemaInfo or attributeInfo nodes |
Explanation |
Below Element there may be only elementInfo node but no schemaInfo or attributeInfo nodes. |
Action |
Modify the XML schema accordingly. |
INOXDE7929 | Below Attribute there may only be one appinfo node which defines Tamino mappings |
Explanation |
Below Attribute there may only be one appinfo node which defines Tamino mappings. |
Action |
Modify the XML schema accordingly. |
INOXDE7930 | internal error |
Explanation |
While processing a schema document an internal error occurred. |
Action |
Please contact your software supplier. |
INOXDE7931 | An error occurred while processing a schema document |
Explanation |
An error occurred during processing of a TSD3 schema document. |
Action |
Details may be supplied by a secondary error message or can be retrieved using the admin-command ino:CheckSchema(collection-name, schema-name) or ino:CheckSchema() for all schemas in all collections. Correct the schema and update it in the database. |
INOXDE7932 | Errors occurred when checking constraints for schema document |
Explanation |
A TSD3 schema document does not adhere to all relevant restrictions. |
Action |
Check the secondary error message for details. |
INOXDE7933 | Version mismatch occurred during schema processing |
Explanation |
An attempt was made to load a TSD3 schema into a TSD2 collection or vice versa. |
Action |
Ensure that used schema language levels are consistent within a single collection. |
INOXDE7934 | Invalid schema document |
Explanation |
The XML document does not contain a valid TSD3 schema. |
Action |
Ensure that the schema document is consistent with the Tamino schema definition language TSD3. |
INOXDE7935 | Schema not found |
Explanation |
The referenced schema does not exist. |
Action |
Check for the existence of the referenced TSD3 schema. |
INOXDE7936 | Invalid define of system collection |
Explanation |
The schema to be defined refers to a collection reserved for system usage. |
Action |
Choose a different collection name. |
INOXDE7938 | Internal error: invalid or unknown version information |
Explanation |
Internal error occurred when retrieving or checking version information. |
Action |
Please contact your software supplier. |
INOXDE7939 | Invalid schema document |
Explanation |
The schema document contains an invalid or outdated format. |
Action |
Check the schema document. Possibly you are using TSD2. If so, convert to TSD3 using the Tamino Schema Editor. |
INOXDE7940 | Invalid modification of doctype: cannot switch between storage of XML, nonXML and indexed nonXML documents |
Explanation |
An error was detected when updating the schema: an attempt was made to modify between storage of XML, nonXML and indexed nonXML documents. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7941 | Must not omit doctype during schema update |
Explanation |
An error was detected when updating the schema: all doctypes defined in the original schema must occur in the new schema. |
Action |
Check the secondary error message for the context where the error was detected. Either extend the new schema document or undefine the obsolete doctype(s) before the next attempt to update the schema. |
INOXDE7942 | Cannot switch doctype to closed content via schema update |
Explanation |
It is not permitted to turn a doctype back to closed content if it had been configured for open content before. |
Action |
In order to switch a doctype back to closed content mode you have to undefine and re-create the doctype and reload the data. |
INOXDE7943 | Mismatch of minOccurs attribute during schema update |
Explanation |
An error was detected when updating the schema: the new value of the minOccurs attribute must be less than or equal to the old one. |
Action |
Check the secondary error message the for context where the error was detected. |
INOXDE7944 | Mismatch of maxOccurs attribute during schema update |
Explanation |
An error was detected when updating the schema: the new value of the the maxOccurs attribute must be greater than or equal to the old one. If it was previously unbounded, it must not be changed at all. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7945 | Mismatch of mapping detected during schema update |
Explanation |
An error was detected when updating the schema: a path containing mapping information which has been added in the new schema was already valid in the old schema. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7946 | Mismatch of element or attribute name detected during schema update |
Explanation |
An error was detected when updating the schema: names of corresponding elements or attributes in old and new schema are different. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7947 | Mismatch of element or attribute type detected during schema update |
Explanation |
An error was detected when updating the schema: types of corresponding elements or attributes in the old and new schema are different. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7948 | Mismatch of content model detected during schema update |
Explanation |
An error was detected when updating the schema: the content models are not equivalent. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7949 | Mismatch of content model of sequence detected during schema update |
Explanation |
An error was detected when updating the schema: the content model inside a sequence of the new schema contains an additional non-optional component. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7950 | Mismatch of enumeration detected during schema update |
Explanation |
An error was detected when updating the schema: it is only possible to add enumeration values in the new schema if there had been at least one enumeration value in the old schema. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7951 | Mismatch of fixed attribute detected during schema update |
Explanation |
An error was detected when updating the schema: the value of the fixed attribute of an element must not be changed. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7952 | Mismatch of "default which" detected during schema update |
Explanation |
An error was detected when updating the schema: no elementInfo or attributeInfo without a which element may be added in the new schema. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7953 | Invalid modification of processContents attribute detected during schema update |
Explanation |
An error was detected when updating the schema: the processContents attribute may only change from "strict" to "lax" to "skip". |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7954 | Invalid modification of mixed attribute detected during schema update |
Explanation |
An error was detected when updating the schema: the mixed attribute may only change from "false" to "true". |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7955 | Invalid modification of components of choice detected during schema update |
Explanation |
An error was detected when updating the schema: choice in the new schema must contain all components of choice in the old schema in arbitrary order. Additional components may be added for closed content. For open content, components may only be removed from the content model. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7956 | Invalid modification of components of sequence detected during schema update |
Explanation |
An error was detected when updating the schema: sequence in the new schema must contain all components of sequence in the old schema in the same order. Additional optional components with minOccurs=0 may be added in the case of closed content of the doctype. For open content, components may only be removed from the content model. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7957 | Invalid modification of element's or attribute's simpleType detected during schema update |
Explanation |
An error was detected when updating the schema: element or attribute may not be defined with simpleType in the old schema and without simpleType in the new schema or vice versa. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7958 | Invalid modification of element's complexType detected during schema update |
Explanation |
An error was detected when updating the schema: element or attribute may not be defined with complexType in the old schema and without complexType in the new schema or vice versa. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7960 | Invalid path in schema definition |
Explanation |
The specified path inside the which element is invalid for this schema. |
Action |
Check the path and schema definition. |
INOXDE7961 | Invalid path in schema definition |
Explanation |
The specified path inside the which element has an invalid syntax. |
Action |
Check the path value. |
INOXDE7962 | Invalid modification of attribute list detected during schema update |
Explanation |
An error was detected when updating the schema: all attributes defined for an element in the old schema must occur in the new schema in arbitrary order. Optional attributes may be added. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7963 | Additional attribute must be optional during schema update |
Explanation |
An error was detected when updating the schema: all additional attributes must be optional in the case of closed content. For open content, attributes may only be removed. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7964 | Mismatch of use attribute detected during schema update. |
Explanation |
An error was detected when updating the schema: the use attribute of an xsd:attribute may only be changed from "required" to "optional". |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7965 | Invalid modification of components of all detected during schema update |
Explanation |
Invalid modification of components of all detected during schema update. Additional optional components may be added in the case of closed content. For open content, components may only be removed from the content model. |
Action |
Please modify your XML schema. |
INOXDE7966 | Mismatch of targetNamespace attribute detected during schema update |
Explanation |
The targetNamespace attribute may not be changed during a schema update. |
Action |
Please adapt your schema. |
INOXDE7967 | Mismatch of namespace declaration detected during schema update |
Explanation |
Namespace declarations may not be changed during a schema update. |
Action |
Please adapt your schema. |
INOXDE7968 | New global element detected during schema update |
Explanation |
Global elements may not be added during a schema update if there is an <xs:any> element by which they may be referred to implicitly. |
Action |
Please check your schema. |
INOXDE7969 | New global attribute detected during schema update |
Explanation |
Global attributes may not be added during a schema update if there is an <xs:anyAttribute> element they may be referred by implicitly. |
Action |
Please check your schema. |
INOXDE7970 | Invalid attempt to remove an attribute wildcard (xs:anyAttribute) during a schema update |
Explanation |
An attribute wildcard may not be removed during a schema update. |
Action |
Please check your schema. |
INOXDE7971 | Removed global element during schema update |
Explanation |
Global elements may not be removed during a schema update if there is an <xs:any> element they may be referred by implicitly. |
Action |
Please check your schema. |
INOXDE7972 | Removed global attribute during schema update |
Explanation |
Global attributes may not be removed during a schema update if there is an <xs:anyAttribute> element they may be referred by implicitly. |
Action |
Please check your schema. |
INOXDE7973 | Facet added during schema update |
Explanation |
The new schema contains a facet which is not present in the existing schema. |
Action |
Consider removing the facet from the new schema or use instance validation. |
INOXDE7974 | Attempted to make value of facet more restrictive during schema update |
Explanation |
The new schema definition contains a facet with a value more restrictive than in the existing schema. This is not allowed by the restricting facet. |
Action |
Consider changing the value of the facet in the new schema or use instance validation. |
INOXDE7975 | Restriction facet's value must not change during schema update |
Explanation |
The new schema definition contains a facet with a value different from that in the existing schema. This is not allowed by the restricting facet. |
Action |
Consider changing the value of the facet in the new schema or use instance validation. |
INOXDE7976 | Mismatch of pattern detected during schema update |
Explanation |
An error was detected when updating the schema: It is only possible to add pattern values in the new schema if there had been at least one pattern value in the old schema. It is only possible to remove pattern values from the new schema if this results in having no pattern values in the new schema. |
Action |
Check the secondary error message for the context where the error was detected. |
INOXDE7978 | Mismatch of namespace declarations found during schema update checks |
Explanation |
An attempt was made to modify the URI associated with a namespace prefix. This is based on namespace declarations in the schema document. Either a namespace declaration was omitted or the URI has been changed. This is not allowed because it would change the semantics of X-Query requests on namespace-clean doctypes. |
Action |
Modify the schema accordingly. |
INOXDE7979 | Invalid schema changes found when adding a unique constraint - no other schema changes are permitted |
Explanation |
When adding a unique constraint no other schema changes are permitted in the same schema update operation. It is also not permitted to add multiple unique constraints in a single schema update. |
Action |
Either add a single unique constraint or perform other schema changes in separate steps. |
INOXDE7980 | At least one doctype contains instances with xsi:type attributes. Schema update requires explicit validation. |
Explanation |
This error may show up e.g. if the set of global types is going to change due to the schema update. Thus, XML instances containing xsi:type attributes require re-validation. Note that this status of the doctype remains set even after the respective XML documents have been deleted. |
Action |
Perform a schema update with instance validation (_mode=validate). |
INOXDE7981 | Attempted to remove member of substitution group during schema update for doctype with closed content |
Explanation |
You cannot remove a member of a substitution group during a schema update for a doctype with closed content without instance validation. |
Action |
Use instance validation during the schema update. |
INOXDE7982 | Attempted to add member of substitution group during schema update for doctype with open content |
Explanation |
You cannot add a member of a substitution group during a schema update for a doctype with open content without using instance validation. |
Action |
Use instance validation during the schema update. |
INOXDE7988 | Failed to lock schema document. |
Explanation |
A schema document could not be locked due to a parallel transaction. |
Action |
Check for parallel transaction using the same schema with a conflicting type of lock. Typically, commands modifying a schema require a write lock for the schema and will conflict with each other, or with other transactions having a read lock on the schema. |
INOXDE7989 | Cannot define schema in schemaless collection |
Explanation |
It is not allowed to define a schema if the collection is defined with schema use 'prohibited'. |
Action |
Use another collection - or just do not define schema at all. Schemaless collections (like ino:etc) allow documents to be stored without defining a schema. You may also change the collection for optional schema usage. |
INOXDE7992 | Index migration for doctype 'doctype' in collection 'collection' failed with error code errorCode |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXDE7993 | Schema operation failed because the same request has doctype already in use |
Explanation |
Schemas cannot be modified or deleted from a server extension if the calling command has an affected doctype in use. |
Action |
Change your application. |
INOXDE7996 | Doctype requires xsi:type migration - schema update requires instance validation |
Explanation |
The given doctype contains documents with xsi:type attribute(s) that were stored in previous version of Tamino. As the processing of xsi:type was not complete in previous versions of Tamino up to version 4.2, explicit validation of the documents against the schema is required. |
Action |
Perform a schema update with instance validation (_MODE=validate). Depending on the type definitions being referenced by the xsi:type attribute, the original schema may need to be adapted, as the type being referenced by xsi:type must be validly derived from the default type of the respective element as given in the schema. |
INOXDE7997 | Missing 'type' attribute in definition of computed index. |
Explanation |
The <tsd:computed> elements must have a 'type' attribute if it is not a compound index. |
Action |
Fix the schema accordingly. |
INOXDE7998 | Found unexpected 'type' attribute in definition of computed index with multiple components. |
Explanation |
For a compound computed index, i.e. with multiple components, only the component definitions may have a 'type' attribute. |
Action |
Fix the schema accordingly. |
INOXDE7999 | Found component of a computed index which does not have a simple type. |
Explanation |
The component of a computed index must have a simple type. |
Action |
Fix the schema accordingly. |
INOXDF7601 | XML initialization: failed to define collection/doctype, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXDF7613 | Unexpected error (rsp,line) occurred during op (parm). |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXDI7582 | The path specified in the xpath attribute of a field element may not be empty or start with a slash |
Explanation |
mp-valid-field.3: The path specified in the xpath attribute of a field element may not be empty or start with a slash. |
Action |
Please change the schema and try to define it again. |
INOXDI7608 | Upgrade system collections |
Explanation |
The system collections need to be upgraded. |
Action |
No action required. |
INOXDI7991 | Indexes of doctype 'doctype' in collection 'collection' have been migrated successfully |
Explanation |
In the given doctype, all indexes marked for migration have been rebuilt successfully. |
Action |
No action required. |
INOXDS7600 | Define 'doctype' in collection 'collection' |
Explanation |
The given system doctype will be defined or upgraded. |
Action |
No action required. |
INOXDS7602 | Define collection 'collection' |
Explanation |
The given system collection will be defined or upgraded. |
Action |
No action required. |
INOXDS7611 | Define missing collection objects |
Explanation |
For all existing collections the respective objects are now being loaded. |
Action |
No action required. |
INOXDW7678 | Usage of a non-field element as element or attribute in schema definition |
Explanation |
Field is defined as phonetic, sub, super or hyper-descriptor in Adabas field definition. |
Action |
Check your schema definition. |
INOXDW7990 | Doctype 'doctype' in collection 'collection' requires index migration |
Explanation |
The referenced doctype contains nodes whose indexes should be newly created. |
Action |
Refer to the migration related topics in the Tamino documentation. |
INOXDW7994 | Multipath index 'label' in doctype 'doctype' in collection 'collection' is marked as not available |
Explanation |
A previous schema update or index repair option could not be finished successfully. The given multipath index is still marked as being not available, and cannot be used for the efficient evaluation of query results. |
Action |
Update the respective schema in Tamino. This will enforce a rebuild of the respective multipath index. |
INOXDW7995 | Doctype 'doctype' in collection 'collection' requires xsi:type migration |
Explanation |
The given doctype contains documents with xsi:type attribute(s) that were stored in a previous version of Tamino. As the processing of xsi:type was not complete in previous Tamino versions up to version 4.2, explicit validation of the documents against the schema is required. |
Action |
Perform a schema update with instance validation (_MODE=validate). Depending on the type definitions being referenced by the xsi:type attribute, the original schema may need to be adapted, as the type being referenced by xsi:type must be validly derived from the default type of the respective element as given in the schema. |
INOXHA8259 | Start writing XML 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 XML 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. |
INOXHE8152 | Web server ws: specified node host unknown (DNS rsp: rsp). |
Explanation |
The given web server on the given node is defined as one of the web servers that are allowed to communicate with this Tamino database. Unfortunately the Tamino database is not able resolve the specified node name. |
Action |
Check whether the node name is correct. If it is correct, check whether DNS lookups may fail due to network problems. In this case, use the IP address instead of the node name. |
INOXHE8153 | 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 is either that the system defined maximum for the number of threads per process is exceeded, or that there is not enough memory available to allocate the necessary thread resources. |
INOXHE8201 | Cannot connect to server on host host at port port. TCP error code rsp. |
Explanation |
The web server interface module was not able to connect to the Tamino server. |
Action |
Check if the Tamino server is active and accessible (e.g. using Telnet). |
INOXHE8202 | Tamino database unknown |
Explanation |
The web server interface module was not able to determine the network address (hostname and port number) of the Tamino database server. |
Action |
Check if the issued URL really points to the desired Tamino database server. If this is OK, check the configuration data of the web server interface module. If this is OK too, please contact your software supplier. |
INOXHE8203 | Database server and web server interface module not compatible |
Explanation |
The versions of the Tamino database server and the Tamino web server interface module are not compatible. |
Action |
Please use compatible versions of the Tamino database server and the Tamino web server interface module. |
INOXHE8220 | XML initialization:SXS initialization failed: sxsMsg |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHE8254 | Failed to create the Software AG XTS Directory Server entries: why |
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. |
INOXHE8257 | Conversion failed, output encoding enc, error code rsp |
Explanation |
The conversion into the desired document encoding failed. |
Action |
Check the desired encoding and correct it. |
INOXHE8258 | Unable to start request |
Explanation |
There is a resource shortage on the server. |
Action |
Increase number of XML work threads. If the problem persists, increase the number of data working threads also. |
INOXHE8261 | XML crash dump file filename could not be created due to operating system error system errno |
Explanation |
The XML crash dump file needed for error analysis could not be created due to the given reason. |
Action |
Please consult the manufacturer's manual. |
INOXHE8270 | XML internal error num: Session sess, Rsp rsp, time |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHE8278 | Internal error |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXHE8282 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8283 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8284 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8285 | Invalid Session ID |
Explanation |
The specified session does not exist or it is currently executing a different request. |
Action |
Specify a valid Session ID. |
INOXHE8286 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8287 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8288 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8289 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8290 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8291 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8292 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8293 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8294 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8295 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8296 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8297 | Error occurred in communication with client |
Explanation |
A communication problem occurred when receiving a request or sending a response to the client. |
Action |
Please check the web server log files or network configuration for possible reasons. |
INOXHE8298 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHE8299 | Internal error |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INOXHF8155 | Communication method 'SSL' requires a certificate |
Explanation |
The server property 'communication method' is set to 'SSL', but the server property 'SSL certificate file' is not set. A certificate is mandatory for encrypted communication. |
Action |
Specify the location of the certificate that the server should use. |
INOXHF8158 | Set version failed. Reason: reason. Internal response d. |
Explanation |
An error occurred during migration. |
Action |
Please contact your software suplier and provide the server startup logfile. |
INOXHF8159 | Exception d occurred during server startup: msg |
Explanation |
The server could not be started. |
Action |
Please contact your software supplier. |
INOXHF8160 | Communication method 'SSL' requires a private key |
Explanation |
The server property 'communication method' is set to 'SSL', but the server property 'SSL key file' is not set. A private key is mandatory for encrypted communication. |
Action |
Specify the location of the private key that the server should use. |
INOXHF8162 | Error in SSL cipher list detected. |
Explanation |
SSL Cipher list provided shows incorrect syntax. |
Action |
please correct |
INOXHF8200 | XML thread initialization failed |
Explanation |
The initialization of X-Machine failed with the mentioned response code. This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8205 | XML thread initialization: data map initialization failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8206 | XML thread initialization: define of ino:collection failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8207 | XML thread initialization: check of ino:collection failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8208 | XML thread initialization: check of security collection failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8209 | XML thread initialization: insert security collection failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8210 | XML thread initialization: insert vocabulary collection failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8211 | XML thread initialization: check of vocabulary collection failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8212 | XML thread initialization: security initialization failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8213 | XML thread initialization: vocabulary initialization failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8214 | XML thread initialization: commit failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8215 | XML thread initialization: rollback failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8216 | XML thread initialization: Memory allocation failed |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8217 | XML work thread thid abended |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8218 | XML receive thread thid abended |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8219 | XML listen thread accept failed, rsp: tprsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8221 | TCP/IP select failed, rsp: tprsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8223 | XML connection initialization failed (error error number) |
Explanation |
The initialization of the XML communication did not work as expected. The server could not be started. |
Action |
Repeat the action. If it still fails, contact your software supplier. |
INOXHF8224 | Unexpected receive count: cnt |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8225 | XML initialization: data map initialization failed |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8226 | XML initialization:security initialization failed |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8227 | XML initialization: internal error |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8228 | XML thread initialization: creation of anonymous session failed |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8229 | XML thread initialization: server extension thread initialization failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8230 | XML initialization:TCP/IP startup failed |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8233 | XML initialization: gethostname failed |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8234 | XML initialization: gethostbyname failed, host: host, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8235 | XML initialization: invalid port number "port" found for web server webserver |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8237 | XTS Register Server failed for XML: xtsmsg |
Explanation |
The registration of the Tamino XML server via XTS failed. |
Action |
Check and correct the XTS configuration and/or directory server. |
INOXHF8239 | XML initialization: failed to define collection/doctype, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8240 | XML thread thread_number has exited due to communication error error_number (text) |
Explanation |
Either adding the service to the directory server has failed, or registering with the directory server has failed. |
Action |
Check the XTS configuration. |
INOXHF8241 | XML thread thread_number has exited due to communication error error_number (text) |
Explanation |
Either adding the service to the directory has failed, or the registration with the directory server failed. |
Action |
Check the XTS configuration. |
INOXHF8243 | XML processing not initialized |
Explanation |
The initialization of the XML processing did not work as expected. The server could not be started. |
Action |
Repeat the action. If it still fails, contact your support center. |
INOXHF8244 | Binding to TCP/IP socket socket number (port type port) has failed |
Explanation |
The server could not connect to the specified socket. Maybe it is in use. |
Action |
Check the reason for the error. If the error persists, choose another port number. |
INOXHF8255 | XML initialization: invalid IP address "ipaddr" found for web server webserver |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8256 | XML initialization: Memory allocation failed |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8262 | XML thread initialization: initialization of tokenizer failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8263 | XML initialization: No license for tok tokenizer |
Explanation |
No valid license found for the default tokenizer. |
Action |
Please check the setting of database parameter "default tokenizer" and the used license file. If the problem persists, please contact your software supplier. |
INOXHF8264 | XML thread initialization: Create failed for obj |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8266 | Invalid default tokenizer: tok |
Explanation |
The value of the parameter "default tokenizer" is invalid. |
Action |
Use a valid value. |
INOXHF8269 | XML thread initialization: data map initialization for server extensions failed, rsp: rsp |
Explanation |
Internal error: Data map entries needed by X-Tension could not be initialized. |
Action |
Please contact your software supplier. |
INOXHF8271 | XML initialization: invalid/unsupported default encoding 'defEnc' |
Explanation |
An invalid/unsupported MIME or IANA encoding name is specified for the 'default encoding' database parameter. |
Action |
Please check the setting of the 'default encoding' database parameter. If the problem persists, please contact your software supplier. |
INOXHF8272 | XML initialization: Word stemming algorithm initialization failed, rsp: rsp |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INOXHF8273 | Failed to attach definition of system collections |
Explanation |
The shared library containing in particular the meta schema could not be loaded. |
Action |
Check your installation. |
INOXHF8279 | Necessary allocation of static port failed |
Explanation |
The allocation of a necessary static port failed. |
Action |
Please contact your software supplier. |
INOXHI8151 | Communication method: s |
Explanation |
The given communication method will be used for the server that is starting. See the user documentation for the server property "Communication Method" for more information. |
Action |
No action required. |
INOXHI8156 | TCP/IP send failed, rsp: rsp, time |
Explanation |
The Tamino server failed to respond to a request. The communication method used was TCP/IP. The reported response code is the error which the Tamino server got from TCP/IP "send". |
Action |
Please check the state of TCP/IP. |
INOXHI8157 | XTS send failed, rsp: rsp, time |
Explanation |
The Tamino server failed to respond to a request. The communication method used was XTS. The reported response code is the error which the Tamino server got from XTS "SendMessageByRT". |
Action |
Please check the state of XTS. |
INOXHI8222 | TCP/IP receive failed, rsp: rsp |
Explanation |
Error in the TCP/IP stack. |
Action |
Please check the state of TCP/IP. |
INOXHI8242 | Define doctype in collection collection |
Explanation |
A system doctype with given name is being created in the given collection. |
Action |
No action required |
INOXHI8247 | Dynamic what worker thread created |
Explanation |
The server increased the number of worker threads to avoid a possible deadlock. |
Action |
No action required. |
INOXHI8251 | Overwriting Software AG XTS Directory Server entries |
Explanation |
The Software AG XTS Directory Server entries already existed. They are overwritten. |
Action |
No action required. |
INOXHI8252 | type - 'dsentry' |
Explanation |
This is an informational message. |
Action |
No action required. |
INOXHI8253 | Use switch parameter 'param' to force server registration |
Explanation |
This is an informational message. |
Action |
No action required. |
INOXHI8260 | XML crash dump of database finished |
Explanation |
The XML crash dump is complete. |
Action |
No action required. |
INOXHI8265 | Default tokenizer 'tok' |
Explanation |
This is an informational message. |
Action |
No action required. |
INOXHI8267 | User dictionary 'udict' |
Explanation |
This is an informational message. |
Action |
No action required. |
INOXHI8274 | Word stemming index successfully created |
Explanation |
The database parameter 'stemming index' is enabled and the stemming index for documents with text indices is created. |
Action |
No action required. |
INOXHI8275 | Word stemming index successfully dropped |
Explanation |
The database parameter 'stemming index' is disabled and the stemming index for documents with text indices is removed. |
Action |
No action required. |
INOXHI8276 | Web server configuration updated |
Explanation |
The web server configuration was changed and is now updated in the server. |
Action |
No action required. |
INOXHI8277 | Internal error |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXHR8245 | Initializing XML processing |
Explanation |
This is an informational message. |
Action |
No action required. |
INOXHR8246 | Starting XML threads |
Explanation |
This is an informational message. |
Action |
No action required. |
INOXHV8250 | Server is already registered with the Software AG XTS Directory Server |
Explanation |
When the Tamino 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. |
INOXHW8154 | TCP connection timed out |
Explanation |
A violation of Tamino Network Protocol was detected. |
Action |
Check the client application / network. |
INOXHW8161 | HTTP connection timed out |
Explanation |
A violation of Tamino Network Protocol was detected. |
Action |
Check the client application / network. |
INOXHW8204 | XML thread initialization: data map initialization for server extension failed, rsp: rsp |
Explanation |
This is an internal error. Tamino will work as expected unless server extensions are used. |
Action |
Please contact your software supplier. |
INOXHW8231 | No license for Tamino XML |
Explanation |
A special license must be bought to use the Tamino XML feature. |
Action |
Buy a license for Tamino XML. |
INOXHW8232 | Only numLic concurrent XML sessions licensed |
Explanation |
The server parameter "XML maximum sessions" contains a value that is larger than the number of concurrent sessions that is included in the used license. Only the number of sessions that is covered by the license used is allowed. |
Action |
Buy an enhanced license. |
INOXHW8236 | XML connection refused; current number of connections: totCon |
Explanation |
Tamino is not able to accept another XML request. The connection attempt is refused. |
Action |
Increase the number of XML work threads. |
INOXHW8238 | Unable to free storage. |
Explanation |
This is an internal error. X-Machine is not able to free all storage during shutdown. |
Action |
Please contact your software supplier. |
INOXHW8248 | Maximum number of dynamic what worker threads reached |
Explanation |
The maximum number of dynamic worker threads is reached. No further threads are created. |
Action |
The number of worker threads should be increased and the server should be restarted. |
INOXHW8249 | Creation of dynamic what worker thread failed with response err |
Explanation |
The server failed to increase the number of worker threads. |
Action |
No action required. |
INOXHW8268 | Invalid entry in user dictionary 'tok' |
Explanation |
The user dictionary contains an invalid entry. It is ignored. |
Action |
Check the user dictionary contents. |
INOXIE8300 | No matching document found |
Explanation |
The specified query did not not find any matching documents. |
Action |
None. This is only an informational error message. |
INOXIE8301 | Illegal document ID specified |
Explanation |
The specified document ID is illegal. |
Action |
Supply a legal document ID. |
INOXIE8303 | Deleting a document is forbidden |
Explanation |
A _DELETE operation was issued against a doctype where DELETE is missing in the doctype options as supplied in the schema definition. |
Action |
Change the doctype options accordingly. |
INOXIE8304 | Reading a document is forbidden |
Explanation |
An _XQL operation was issued against a doctype where READ is missing in the doctype options as supplied in the schema definition. |
Action |
Change the doctype options accordingly. |
INOXIE8305 | Invalid cursor handle |
Explanation |
The supplied cursor handle is invalid: either it was never created during the current session, or the corresponding cursor was closed in the meantime. |
Action |
Supply a correct cursor handle. |
INOXIE8306 | Invalid cursor position |
Explanation |
The supplied cursor position is invalid: there is no document in the cursor's result set corresponding to the position. In particular, this error will be returned when positioning beyond the end of the cursor result set. |
Action |
Supply a correct cursor position. |
INOXIE8307 | Trying to position backwards in a non-scrollable cursor |
Explanation |
The position supplied with the "fetch cursor" request would result in a backward positioning which is not possible for a non-scrollable cursor. |
Action |
Supply a correct cursor position. |
INOXIE8309 | Duplicate in sort key |
Explanation |
The system cannot handle sort key values which consist of more than a single node. |
Action |
Change your query expression so that no multiple node is to be sorted. |
INOXIE8310 | Invalid parameter detected |
Explanation |
Either the function is unknown or the number of parameters is invalid or the parameter values are invalid. |
Action |
Please check the function name, the number of parameters and the parameter values and correct them. |
INOXIE8312 | Version fromVersion is incompatible with Version toVersion |
Explanation |
The current version of the database is not compatible with the selected version. |
Action |
Data must be unloaded and loaded into a new database manually. |
INOXIE8313 | Internal communication error |
Explanation |
Database cannot be converted because of an internal error. |
Action |
Check that the database is running. |
INOXIE8314 | Database's compatibility level is no longer supported |
Explanation |
Migration from and to this compatibility level is not possible because this compatibility level is no longer supported. |
Action |
Data must be unloaded and loaded into a new database manually. |
INOXIE8315 | Duplicate docnames found in ino:collection = 'collection' ino:doctype='doctype' |
Explanation |
The upgrade has been rejected because because of duplicate docnames. |
Action |
Use the administration command ino:AdminDocname("check-unique") to get a list of duplicate docnames. Please delete the duplicate docnames and call the administration command ino:AdminDocname("set-unique"). |
INOXIE8316 | Attempted to delete a partial document |
Explanation |
With _delete, it is only possible to delete complete XML documents. |
Action |
Supply a query that selects complete documents. |
INOXIE8319 | Internal error occurred during query processing: unknown request |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXIE8320 | Error parsing the XQL query |
Explanation |
One or more errors occurred while parsing the XQL query. |
Action |
Correct query appropriately and re-issue |
INOXIE8321 | Missing end quotation character |
Explanation |
The end quotation character of a literal was not found. It could also be that the start and end quotation characters do not match. |
Action |
Correct query appropriately and re-issue. |
INOXIE8322 | Named axes are not supported |
Explanation |
The specification of named axes is not supported in Tamino. |
Action |
No action possible. |
INOXIE8331 | Failed to set the server parameter |
Explanation |
Failed to set the server parameter. |
Action |
Please contact your software supplier. |
INOXIE8332 | The old server parameter could not be deleted |
Explanation |
The old server parameter could not be deleted. |
Action |
Please contact your software supplier. |
INOXIE8333 | An old TSD2 collection could not be deleted |
Explanation |
An old TSD2 collection could not be deleted. |
Action |
Please contact your software supplier. |
INOXIE8334 | The database contains data which uses lite mapping |
Explanation |
The version to which the database should be upgraded does not support lite mapping. |
Action |
Please delete the data which uses lite mapping and start the upgrade again. |
INOXIE8335 | Upgrade of metaschema failed with following response code RESPONSE. |
Explanation |
The upgrade of the metaschema which was performed during upgrade of the database has failed with the specified response code. |
Action |
Please contact your software supplier. |
INOXIE8336 | Upgrade is not supported |
Explanation |
Upgrade is not supported. |
Action |
Select another version to upgrade the database. |
INOXIE8337 | Downgrade is not supported |
Explanation |
Downgrade to an older Tamino version is not supported. |
Action |
Please contact your software supplier. |
INOXIE8338 | Data format 'VERSION' found in collection 'COLLECTION' doctype 'DOCTYPE'. |
Explanation |
The data format found in the user collection is no longer supported. |
Action |
Please clean up the user collection. |
INOXIE8339 | Unknown function |
Explanation |
The provided function name is unknown. |
Action |
Check if you provided the correct function name and try again. |
INOXIE8340 | Truncated index detected |
Explanation |
An index containing truncated entries was detected at query execution time, though the Data Map had no information about truncation available at compile time. This may occur for an index that has been migrated from Tamino version 4.1.4. As a side effect of the failing query, the index has been marked as truncated in the Data Map. |
Action |
Repeat the query. |
INOXIE8341 | Internal error |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXIE8342 | Memory allocation failed |
Explanation |
There was not enough main memory available to perform the request. |
Action |
Possibly the machine is overloaded. Try again later. |
INOXIE8343 | Postprocessing not supported for non-XML text search |
Explanation |
A query that contains a text search operator can be executed on a non-XML doctype only if a text index has been defined for that doctype and the query does not require postprocessing. |
Action |
Modify your schema definition to contain a non-XML text index or change query to avoid postprocessing. |
INOXIE8344 | Internal error |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXIE8345 | Illegal parent operator follows sort operator |
Explanation |
A query contains a parent operator which might be applied to a node which serves as input for a sort operator. This is not allowed. |
Action |
Please change your query so that no parent operator can be applied to a sort input node. |
INOXIE8346 | Malformed proximity expression |
Explanation |
A subexpression of the query uses either the "adj" or the "near" operator, but there is no corresponding "~=" operator. |
Action |
Correct the query. |
INOXIE8347 | Query not supported |
Explanation |
The specified query is not supported. |
Action |
Change the query. |
INOXIE8348 | Wrong arguments for function |
Explanation |
The function cannot be applied on the current parm settings, i.e. number or type of arguments that a function is called with is not as expected by the function. |
Action |
Check either the XPath specification for the proper usage of XPath's built in functions or check the documentation for server extension functions. |
INOXIE8349 | Maximum word length exceeded |
Explanation |
Text searches are restricted to a maximum word length of 64 characters. |
Action |
Reduce the length of the search pattern inside the query. |
INOXIE8350 | No whitespace search is supported with ~= |
Explanation |
Whitespaces are ignored by a "~=" search, so searching for a whitespace is not possible. |
Action |
Use the "=" operator to find whitespaces. |
INOXIE8351 | Wrong direction of result type |
Explanation |
The result type must be output. |
Action |
Uninstall the function, change the signature of the external function, install the function again. |
INOXIE8352 | Operator used outside a document |
Explanation |
Some operators can only be used inside a document e.g. before/after. |
Action |
Do not use the operator outside of a document context. |
INOXIE8353 | Invalid invocation of ino:fullscan |
Explanation |
The ino:fullscan function can be used only on query level, it cannot be applied to subexpressions. |
Action |
Correct ino:fullscan invocation. |
INOXIE8354 | Invalid invocation of ino:explain |
Explanation |
The ino:explain function can be used only on query level, it can not be applied to subexpressions. |
Action |
Correct ino:explain invocation. |
INOXIE8355 | Too many inter-document sort operators |
Explanation |
The system can process only a single inter-document sort operator. Please note that a "sortby" applied to a root node is also an inter-document sort operator. |
Action |
Please change your query. |
INOXIE8356 | Illegal inter-document sort operators |
Explanation |
Within a query an inter-document sort operator must not follow an intra-document sort operator. |
Action |
Please change your query. |
INOXIE8357 | Internal error |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXIE8358 | Internal error |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXIE8359 | Internal error |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXIE8360 | Nodeset is empty |
Explanation |
The current-node (.) or parent (..) operator was applied upon an empty nodeset during query evaluation. |
Action |
A subquery executed prior to the current-node or parent operation yielded an empty result. |
INOXIE8361 | Invalid type occurred when executing query |
Explanation |
Some query operations can only be applied upon objects of a specific type, e.g. current-node (.) or parent (..) only make sense when working upon nodes. This error may also occur when calling XPath functions upon a set of arguments they cannot be applied upon. |
Action |
Check whether . (=current node) or .. (= parent) are used in connection with nodes, and that an XPath function's usage corresponds to its type. |
INOXIE8362 | Internal Error : Invalid Node |
Explanation |
An invalid XML node was encountered during the evaluation of an XPath function. |
Action |
Please contact your software supplier. |
INOXIE8364 | Conversion failed |
Explanation |
In order to execute a query an invalid conversion was attempted. This happens e.g. if a numerical operation is applied upon data that cannot be converted to a number. This error occurs also if an operator requires two operands of the same type (e.g. between) and the operands are of different types. |
Action |
Check the operand's types. |
INOXIE8366 | Wrong arguments for function |
Explanation |
The function cannot be applied on the current parm settings, i.e. number or type of arguments that a function is called with is not as expected by the function. |
Action |
Check either the XPath specification for the proper usage of XPath's built in functions or check the documentation for server extension functions. |
INOXIE8367 | Internal error : Missing root node |
Explanation |
The query postprocessor encountered a missing node in the XPath parsing tree when evaluating an XPath expression. |
Action |
Please contact your software supplier. |
INOXIE8368 | ICU collator definition failed |
Explanation |
An error was received while opening an ICU collator. |
Action |
Please contact your software supplier. |
INOXIE8369 | Right side of ~= must be a single string |
Explanation |
The match operand requires an operand that evaluates to string on its right side. |
Action |
Check whether your idea of what match does is correct. It typically looks like list-of-nodes ~= 'pattern' or list-of-nodes ~= 'word' . If the right side of your match is detected dynamically from Tamino data, it does not evaluate to a string as you expected. If the right side of your match is given literally in the query, it might help to add quotes. |
INOXIE8371 | Invalid comparison operator |
Explanation |
Within 'adjacent' or 'near' statements, currently only the match comparison operator is allowed. |
Action |
Replace an equal by a match and a not-equal by a match and the XPath function 'not()'. |
INOXIE8372 | Too many match tokens |
Explanation |
The right side of a ~= contains a string that gets tokenized in order to check the expression on the left side for the occurrence of these tokens in the given sequence. The tokenization must not lead to more than ten tokens. |
Action |
Shorten the pattern to avoid tokenization into more than ten tokens. |
INOXIE8374 | Invalid Match Pattern |
Explanation |
The string provided as the right side of a match (~=) must contain at least one character that is not a separation character, i.e. quote or comma. The string may contain wildcards (*), but only in the forms *x, x*, x*x, or *x*. |
Action |
Correct the pattern. |
INOXIE8375 | Sortkey too long |
Explanation |
The internally generated sort key is too long. |
Action |
Reduce the number of sort criteria. |
INOXIE8376 | Duplicate in sort key |
Explanation |
The system cannot handle sort key values which consist of more than a single node. |
Action |
Please try to fix your data or your query. |
INOXIE8378 | Server extension returned binary data without setting media type |
Explanation |
The media type must be defined when a server extension returns binary data. |
Action |
Use the method SxsSetProperty() with the property of SX_PROPERTY_RSP_MEDIATYPE to define the media type of the binary data. |
INOXIE8379 | Internal error occurred during query processing: unknown request |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXII8302 | Overflow during sorting |
Explanation |
internal error |
Action |
Please contact your software supplier. |
INOXII8311 | Version fromVersion is compatible with Version toVersion |
Explanation |
The current version of the database is compatible with the selected version. |
Action |
None |
INOXII8317 | Internal error during sorting |
Explanation |
internal error |
Action |
Please contact your software supplier. |
INOXII8318 | Locking conflict |
Explanation |
internal error |
Action |
Please contact your software supplier. |
INOXII8323 | Recreation of all indices started in collection COLLECTION, doctype DOCTYPE |
Explanation |
The administrative command ino:RecreateIndex was issued. |
Action |
Be aware that the collection is not accessible until index recreation is completed. |
INOXII8324 | Recreation of all indices in collection COLLECTION, doctype DOCTYPE terminated with code CODE |
Explanation |
The administrative command ino:RecreateIndex terminated. |
Action |
Be aware that if the given return code is not 0, the index recreation has been rolled back. |
INOXII8325 | Recreation of all text indices started in collection COLLECTION, doctype DOCTYPE |
Explanation |
The administrative command ino:RecreateTextIndex was issued. |
Action |
Be aware that access to the collection is constricted until the operation is completed. |
INOXII8326 | Recreation of all text indices in collection COLLECTION, doctype DOCTYPE terminated successfully |
Explanation |
The administrative command ino:RecreateTextIndex completed. |
Action |
The collection is fully usable again. |
INOXII8327 | Recreation of all text indices in collection COLLECTION, doctype DOCTYPE terminated with error CODE |
Explanation |
The administrative command ino:RecreateTextIndex aborted due to the stated error code. |
Action |
Repair the indices via the administrative command ino:RepairIndex(). |
INOXII8328 | Repair indices started in collection COLLECTION, doctype DOCTYPE, mode MODE |
Explanation |
The administrative command ino:RepairIndex was issued. |
Action |
Be aware that access to the collection is constricted until the operation is completed. |
INOXII8329 | Repair indices in collection COLLECTION, doctype DOCTYPE, mode MODE terminated successfully |
Explanation |
The administrative command ino:RepairIndex completed successfully. |
Action |
Note that if the mode was "drop", the indices have been dropped from the schema. |
INOXII8330 | Repair indices in collection COLLECTION, doctype DOCTYPE, mode MODE terminated with error CODE |
Explanation |
The administrative command ino:RepairIndex aborted due to the given error. |
Action |
Correct the problem if possible and repeat the command. |
INOXIW8373 | The id() function is not supported |
Explanation |
XPath describes the result of the id() function as being the node-set containing the elements in the same document as the context node that have a unique ID equal to any of the tokens in the id() function's argument list (see XPath 4.1). As specified in XPath, 5.2.1, a unique ID is the value of the attribute that is declared in the DTD as type ID. Since Tamino currently offers no means to declare attributes as type ID, applying the id() function makes no sense, its result will always be the empty node set. |
Action |
If some attribute 'att1' has the semantics of an ID, retrieving the node for which this attribute is set to a certain value, e.g. 'val1', is achieved via //*[@att1="val1"]. |
INOXIW8399 | The required function has not been completely executed |
Explanation |
See details in the warning line accompanying this message. Possible reasons for this warning are: a sort operation was performed based on an index, and that index contains truncated values. The result is sorted according to the truncated values, and not according to the real values. |
Action |
No action required, this is a warning only. |
INOXME8501 | Memory allocation failed |
Explanation |
Allocation of virtual memory failed. |
Action |
Either extend the amount of memory resources available for Tamino on your system or reduce resource consumption of Tamino, e.g. by using a smaller buffer pool. |
INOXME8502 | Internal error: DBMS environment not found |
Explanation |
The DBMS environment could not be found for X-Node - this is an internal error. |
Action |
Please contact your software supplier. |
INOXME8503 | Invalid or unknown encoding found in input document |
Explanation |
The encoding of the input document could not be recognized. |
Action |
Check your input document. |
INOXME8504 | XML maximum request duration exceeded |
Explanation |
The request was cancelled because the maximum request duration was exceeded. |
Action |
Either improve the request performance by tuning the database, or increase the value of the "XML maximum request duration" server parameter. |
INOXME8505 | ODBC error occurred |
Explanation |
While issuing a command via ODBC to the SQL system an error occurred. |
Action |
The text of the external error is provided in the extended message. |
INOXME8506 | Adabas error occurred |
Explanation |
An error occurred when accessing an Adabas database via X-Node. |
Action |
Check the Adabas documentation for the reason for the reported error code. |
INOXME8507 | Maximum parallel databases for session reached |
Explanation |
The number of parallel databases allowed for one session has been reached. |
Action |
No action required. |
INOXME8508 | X-Node licensing error, insufficient rights |
Explanation |
An attempt was made to access an X-Node datasource or an Adabas version that has not been licensed. |
Action |
Check that all datasources defined in the schema are correct, or upgrade the X-Node license. |
INOXME8509 | X-Node datasource mismatch |
Explanation |
The datasource DBMS name given (implicitly or explicitly) in the schema does not match that of the DBMS vendor to which this datasource has attempted to connect. |
Action |
The DBMS name must be the same at execution time as it was at schema creation time. |
INOXME8510 | Request has been cancelled |
Explanation |
The request has been cancelled by the operator or accessor. |
Action |
No action required. |
INOXME8511 | Internal maximum for parallel ODBC access reached |
Explanation |
Within one transaction, Tamino keeps track of parallel OBDC access. An internal list reached its maximum. |
Action |
No action required. |
INOXME8512 | Invalid request ID |
Explanation |
The given ID is invalid either because the respective request is already terminated or because it is invalid as an accessor-provided unique identifier. |
Action |
No action required, if the request is already terminated. Otherwise the request ID cannot be used within _admin=ino:Accessor("cancelRequest",...). |
INOXME8513 | Cannot create unique text index |
Explanation |
A unique index cannot be set because duplicate entries are stored in the translated word table. |
Action |
Please contact your software supplier. |
INOXME8514 | X-Node SQL column not found or authorization error |
Explanation |
The specified column was not found in the SQL table or you are not authorized to access the column/table. |
Action |
Correct the schema. |
INOXME8515 | X-Node SQL table not found or authorization error |
Explanation |
The error may occur because: 1. the specified SQL table/schema was not found OR 2. you are not authorized to access the table. |
Action |
Correct the schema. |
INOXME8516 | Internal error: cannot lock collection |
Explanation |
Migration attempted to lock a collection for which it is not possible. |
Action |
Please contact your software supplier. |
INOXME8517 | Unlock of collection failed |
Explanation |
It was not possible to unlock the specified collection. |
Action |
Please contact your software supplier. |
INOXME8518 | Unlock of collection failed because the lock is in an incorrect state |
Explanation |
It was not possible to unlock the specified collection because the lock is in an incorrect state. |
Action |
Please contact your software supplier. |
INOXME8519 | Cannot cancel a mass load/unload as a session user |
Explanation |
Cancelling of a mass load/unload in a session is not possible. |
Action |
Issue the administration command in an anonymous session. |
INOXME8520 | Error writing to temporary file during data load |
Explanation |
An error occurred while writing to a temporary file during a data load request. |
Action |
Check that temporary directory ($SAGTMP or $TMP) is writable and that disk space is available. |
INOXME8521 | Invalid or unsupported datastore format detected during data load |
Explanation |
An internal error occurred during data load. |
Action |
Please contact your software supplier. |
INOXME8522 | Unsupported datastore descriptor type detected during data load |
Explanation |
An internal error occurred while data was being loaded. |
Action |
Please contact your software supplier. |
INOXME8523 | Unsupported datastore request detected during data load |
Explanation |
An internal error occurred while data was being loaded. |
Action |
Please contact your software supplier. |
INOXME8524 | Value exceeding maximum length detected during data load |
Explanation |
An internal error occurred while data was being loaded. |
Action |
Please contact your software supplier. |
INOXME8525 | Internal error detected in data load module |
Explanation |
An internal error occurred while data was being loaded. |
Action |
Please contact your software supplier. |
INOXME8527 | Data loading/unloading for doctype not supported |
Explanation |
For data loading: - doctypes of map-type NonXML or Lite are not supported. - doctypes created in Tamino version prior to v2.3 are not supported. For data unloading: - doc-types of map-type NonXML are not supported |
Action |
Either migrate your doctype to v2.3 or later or use the XML loaders. |
INOXME8528 | Data loading aborted; cannot create temporary files |
Explanation |
The data loader was unable to create temporary files. |
Action |
Using the Tamino Manager or the batch utility "argbatch", check that the settings for the temporary location are correct and that there is space available. |
INOXME8529 | Data loading into multiple doctypes not supported |
Explanation |
Data loading is only possible into the collection/doctype given when the data loader is started. |
Action |
Remove documents from the input file that do not belong to the doctype specified at the start-up of the XML data loader. |
INOXME8531 | Data load rejected document |
Explanation |
An error was found while processing the document during a data load operation. |
Action |
Correct and restart the data loader. |
INOXME8536 | XML data load recovery of doctype doctype in collection collection was unsuccessful |
Explanation |
During autorestart, it was detected that a XML data load operation was active in the previous Tamino server session. This message provides information that Tamino could not restore the doctype to the state before the XML data load operation was initiated. |
Action |
Perform a restore/regenerate of the Tamino database to get it into a consistent state. |
INOXME8539 | XML data loading failed |
Explanation |
An XML data load operation was aborted or stopped. |
Action |
Depending on the reason for the failure, correct and re-process. |
INOXME8540 | Data loading aborted with rejects |
Explanation |
Data loading has aborted because a reject was found and the norejects option was chosen. |
Action |
Either correct the rejected document or load without setting the norejects option. |
INOXME8543 | Internal error - unexpected response occurred in call to function function, function gave response code(s) codes |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier with the exact message (the function and codes are important). |
INOXME8544 | Query using "mapping-type=object" cannot be evaluated |
Explanation |
The query cannot be evaluated because "mapping-type=object" is involved and the post-processor is needed, or because the "mapping-type=object" node is used within a filter. |
Action |
Supply a correct query. |
INOXME8546 | Feature not implemented |
Explanation |
You attempted to use a feature which is not available in the current environment. |
Action |
Please contact your software supplier. |
INOXME8547 | Invalid syntax of _XQL command inside _HTMLREQ |
Explanation |
An error occurred when converting an _HTMLREQ=_XQL request to an _XQL request. |
Action |
Check the appropriate documentation. |
INOXME8548 | Invalid syntax of _PROCESS command inside _HTMLREQ |
Explanation |
An error occurred when converting an _HTMLREQ=_PROCESS request to a _PROCESS request. |
Action |
Check the appropriate documentation. |
INOXME8549 | Doctype not found |
Explanation |
The doctype indicated in the ino:messageline could not be found during an _UNDEFINE request. |
Action |
Check the specified name. |
INOXME8551 | Invalid doctype |
Explanation |
Storing or deleting documents in the collection "ino:collection" is not permitted. |
Action |
Check the collection name specified in the request. |
INOXME8552 | Not a valid request |
Explanation |
The request has been rejected due to invalid or missing parameters. |
Action |
Check the request parameters using supplementary error diagnostics in other messages. |
INOXME8554 | No message received |
Explanation |
The request did not specify any supported operation or command. |
Action |
Check the parameters of the request. |
INOXME8555 | Session error occurred |
Explanation |
An error occurred when attempting to establish a session context. |
Action |
Check the supplementary diagnostic message for a detailed explanation. |
INOXME8557 | Request rejected because a deprecated feature is used |
Explanation |
The used feature will not be supported in the next version. |
Action |
Change the server parameter to allow and log deprecated features. |
INOXME8558 | Error during commit in user transaction |
Explanation |
A user transaction received an error during commit processing. |
Action |
The error has to be handled in your application. |
INOXME8559 | Error during rollback of user transaction |
Explanation |
A user transaction has been rolled back due to an error. However, the indicated error occurred. |
Action |
Please contact your system administrator. |
INOXME8560 | Failed to allocate SMP key |
Explanation |
An internal error occurred when attempting to allocate a key for thread local storage. |
Action |
Please contact your system administrator. |
INOXME8561 | Failed to deallocate SMP key |
Explanation |
An internal error occurred when attempting to release a key for thread local storage. |
Action |
Please contact your system administrator. |
INOXME8562 | Invalid handle |
Explanation |
Internal error: an invalid handle was passed to an internal interface. |
Action |
Please contact your system administrator. |
INOXME8563 | Invalid parameter |
Explanation |
Internal error: an invalid parameter was passed to an internal interface. |
Action |
Please contact your system administrator. |
INOXME8564 | Illegal load factor |
Explanation |
An internal error occurred when creating a hash map. |
Action |
Please contact your system administrator. |
INOXME8565 | Illegal initial capacity |
Explanation |
An internal error occurred when creating a hash map. |
Action |
Please contact your system administrator. |
INOXME8566 | Duplicate key |
Explanation |
An attempt was made to store the same key twice in a hash map. |
Action |
Please contact your system administrator. |
INOXME8570 | Locking failed during data load operation |
Explanation |
The specified collection or doctype could not be locked. |
Action |
Check the parameters of the data load request. |
INOXME8596 | Internal error in locking |
Explanation |
An unexpected server status caused a lock operation failure. |
Action |
Please contact your software supplier. |
INOXME8598 | Access violation |
Explanation |
The request was rejected due to insufficient access permissions. |
Action |
Check if the request was as intended and if so, try to get the required access privileges from the system administrator. |
INOXME8599 | Internal error |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXMF8530 | Internal error occurred during data loading |
Explanation |
An internal error was detected while data was being loaded. |
Action |
Please contact your software supplier. |
INOXMI8532 | XML data load recovery initiated |
Explanation |
During autorestart, it was detected that a XML data load operation was active in the previous Tamino server session. This message defines the start of recovery handling for cleaning up anything that was left over after the data load operation. |
Action |
No action required. |
INOXMI8533 | XML data load recovery completed |
Explanation |
During autorestart, it was detected that a XML data load operation was active in the previous Tamino server session. This message defines the completion of recovery handling for cleaning up anything that was left over after the data load operation. |
Action |
No action required. |
INOXMI8534 | XML data load recovery initiated for doctype doctype in collection collection |
Explanation |
During autorestart, it was detected that a XML data load operation was active in the previous Tamino server session. This message provides information about which doctypes are being recovered. |
Action |
No action required. |
INOXMI8535 | XML data load recovery of doctype doctype in collection collection completed successfully |
Explanation |
During autorestart, it was detected that a XML data load operation was active in the previous Tamino server session. This message provides information that Tamino has successfully restored the doctype to the state before the XML data load operation was initiated. |
Action |
No action required. |
INOXMI8537 | XML data loading initiated for doctype doctype of collection collection |
Explanation |
This is an information message to indicate the start of XML data load operation. |
Action |
No action required. |
INOXMI8538 | XML data loading completed, number of documents processed docsproc, loaded docsload, rejected docsrejected |
Explanation |
This is an information message to indicate the end of an XML data load operation. |
Action |
Depending on if there were documents rejected, these may need to be investigated and re-processed. |
INOXMV8550 | Deprecated feature used: feature |
Explanation |
The request uses a feature which is planned to be removed in the next product version. |
Action |
Do not use the deprecated feature. |
INOXMW8526 | Failed to write XML request log to path |
Explanation |
An error occurred when attempting to write the XML request log to given location. |
Action |
Check the location for possible reasons such as: a non-existing XML request log folder may have been specified, the directory cannot be accessed, or the disk is full. |
INOXMW8545 | ino:docname uniqueness is not removed in downgrade |
Explanation |
The downgrade does not allow the uniqueness of ino:docnames to be removed. |
Action |
No action required. |
INOXMW8571 | Request logging was switched off dynamically due to IO errors |
Explanation |
Probably the disk is full. |
Action |
Check the disk. Except for request logging, the Tamino server continues operation. |
INOXPE8700 | Internal error: inconsistent document retrieval |
Explanation |
The database storage of the retrieved document is inconsistent. |
Action |
Please contact your software supplier. |
INOXPE8701 | Memory allocation failed |
Explanation |
There was not enough main memory available to perform the request. |
Action |
Possibly the machine is overloaded. Try again later. |
INOXPE8702 | Invalid document prolog |
Explanation |
Invalid document prolog found in the file to be loaded. |
Action |
Please correct the document prolog. |
INOXPE8703 | Invalid document declaration or more than one declaration found in the file to be loaded |
Explanation |
Invalid document declaration or more than one declaration found in the file to be loaded. |
Action |
Correct the document declaration or remove all declarations except for the first. |
INOXPE8704 | Unknown encoding found |
Explanation |
Unknown encoding found. |
Action |
Please correct the document instance. |
INOXPE8705 | Incompatible encoding found |
Explanation |
The given encoding isn't supported yet. |
Action |
Please use another encoding. |
INOXPE8706 | Entity found twice |
Explanation |
An entity with same name was found twice. |
Action |
Please remove one of these entities. |
INOXPE8707 | Wrong entity definition |
Explanation |
The definition of an entity isn't correct. |
Action |
Please correct the entity definition. |
INOXPE8708 | Document without content |
Explanation |
An empty document cannot be loaded. |
Action |
Please provide the document with contents. |
INOXPE8709 | Encoding not supported |
Explanation |
The given encoding isn't supported yet. |
Action |
Please use another encoding. |
INOXPE8710 | Invalid token found or document incomplete |
Explanation |
Invalid token found or the document is incomplete. |
Action |
Please correct the document. |
INOXPE8711 | Document not well-formed |
Explanation |
The document to be loaded isn't well-formed. |
Action |
Please correct the document. |
INOXPE8712 | Invalid element name |
Explanation |
The name of the element is either too long or not correct. |
Action |
Please correct the document. |
INOXPE8713 | Invalid attribute name |
Explanation |
The name of the attribute is either too long or not correct. |
Action |
Please correct the document. |
INOXPE8714 | Invalid document ID (ino:id) specified |
Explanation |
The given document ID (ino:id) is either not numeric or not available. |
Action |
Please correct the document. |
INOXPE8715 | Inserting or changing a document is forbidden |
Explanation |
It isn't permitted when using this doctype to insert or to change documents. |
Action |
Please contact your system administrator. |
INOXPE8716 | Inserting a document is forbidden |
Explanation |
It isn't permitted when using this doctype to insert a new document. |
Action |
Please contact your system administrator. |
INOXPE8717 | Changing a document is forbidden |
Explanation |
It isn't permitted while using this doctype to change a document. |
Action |
Please contact your system administrator. |
INOXPE8718 | Document incomplete |
Explanation |
The document to be loaded is incomplete. |
Action |
Please correct the document. |
INOXPE8719 | Document contains invalid character reference |
Explanation |
The document contains an invalid character reference. |
Action |
Please correct the document. |
INOXPE8720 | Document contains invalid entity reference |
Explanation |
The document contains a reference to an entity which wasn't defined before. |
Action |
Please correct the document. |
INOXPE8721 | Root element does not match doctype declaration |
Explanation |
The given root element doesn't correspond to the root element of the used doctype. |
Action |
Please correct the document. |
INOXPE8722 | Element with wrong obj-type encountered |
Explanation |
The given element is defined in the schema as an attribute. |
Action |
Correct either the document or the accompanying schema. |
INOXPE8723 | Attribute with wrong obj-type encountered |
Explanation |
The given attribute is defined in the schema as an element. |
Action |
Correct either the document or the accompanying schema. |
INOXPE8724 | Invalid attribute value encountered |
Explanation |
The value of the attribute contains contents which aren't permitted. |
Action |
Please correct the document. |
INOXPE8725 | Attribute was found twice |
Explanation |
An attribute with same name was found twice. |
Action |
Please remove one of these attributes. |
INOXPE8726 | Occurrence count does not match multiplicity option |
Explanation |
The occurrence count of an element or attribute in an XML instance does not match the multiplicity option specified in the schema. |
Action |
Please correct the document. |
INOXPE8727 | Document structure does not match schema definition (choice) |
Explanation |
The document structure does not match the schema definition for the choice case. |
Action |
Please correct the document. |
INOXPE8728 | Internal error: parent object not found |
Explanation |
Accompanying parent object couldn't be found. |
Action |
Please contact your system administrator. |
INOXPE8729 | Unclosed CDATA section detected |
Explanation |
Unclosed CDATA section detected. |
Action |
Please correct the document. |
INOXPE8730 | Required child object not specified |
Explanation |
An element or an attribute which is defined in the schema as mandatory wasn't specified in the document. |
Action |
Please correct the document. |
INOXPE8731 | Internal error: Parse in progress |
Explanation |
The attempt was made to parse a second document while still parsing the first document. |
Action |
Please contact your system administrator. |
INOXPE8732 | Value too long |
Explanation |
The value of a numeric node or of a node mapped to an external datasource or of a node with search type STANDARD is too long. |
Action |
Please shorten the corresponding value. |
INOXPE8733 | Value not numeric |
Explanation |
The value for an object with an numeric datatype is not numeric. |
Action |
Please correct the document. |
INOXPE8734 | Numeric value too large |
Explanation |
The value of an object with a numeric datatype is too large. |
Action |
Please shorten the corresponding value. |
INOXPE8735 | Insufficient space to convert data according to encoding |
Explanation |
The length of data in an attribute/element that is defined to AdaField exceeds the defined length in the schema. |
Action |
Correct either the XML input data or modify the schema to increase the defined length. |
INOXPE8736 | Internal error: buffer exceeded |
Explanation |
For InfoFile mapping, the size of a document or the size of parts of a document that are mapped to any InfoField construct (like InfoArray) is limited to 64KB at the node level where map type InfoFile is specified. If there is no node with an explicit map type of InfoFile, the limit of 64KB applies to the root node. |
Action |
Reduce the number of nodes that are mapped to InfoField constructs. Use map type Native instead. |
INOXPE8737 | Invalid document update attempted |
Explanation |
The request tried to modify the document such that it would have generated an SQL UPDATE statement without a WHERE clause. This is not allowed. |
Action |
To accomplish this, delete the document and insert a new document instead of updating the document. |
INOXPE8738 | Only a single document may be processed. |
Explanation |
If the document name or the document ID is given, only a single document can be processed. |
Action |
Please remove additional documents. |
INOXPE8740 | Internal error in document serialization module detected |
Explanation |
An internal error occurred in the serialization module. |
Action |
Please contact your software supplier. |
INOXPE8741 | Internal error in document serialization module detected |
Explanation |
An internal error occurred in serialization module. |
Action |
Please contact your software supplier. |
INOXPE8742 | Recursion of entities detected |
Explanation |
During the processing of references to entities a recursion was discovered. |
Action |
Please check the entity definition and correct the document. |
INOXPE8743 | Entity stack overflow |
Explanation |
Entity stack overflow. |
Action |
Please reduce the nested entity references. |
INOXPE8744 | Internal error in index processing module detected |
Explanation |
An internal error occurred in the index processing module. |
Action |
Please contact your software supplier. |
INOXPE8745 | Internal error in index processing module detected |
Explanation |
An internal error occurred in the index processing module. |
Action |
Please contact your software supplier. |
INOXPE8746 | Internal error |
Explanation |
An internal error occurred during document processing. |
Action |
Please contact your software supplier. |
INOXPE8747 | Internal error in index processing module detected |
Explanation |
An internal error occurred in the index processing module. |
Action |
Please contact your software supplier. |
INOXPE8748 | Internal error in document processing module detected |
Explanation |
Processing aborted due to a server internal error. |
Action |
Please contact your software supplier. |
INOXPE8749 | Access to XNODEs / trigger functions during massload is not allowed |
Explanation |
The access to parts of the schema that specify X-Node or trigger function usage is not allowed when loading data with the Tamino Data Loader. |
Action |
Set "ignore update" for the X-Node or trigger function parts of the schema or use the concurrentWrite option of the Tamino Data Loader. |
INOXPE8750 | Tag or attribute name is too long |
Explanation |
The number of characters of a tag or attribute name exceeds the maximum supported value. |
Action |
Shorten the name of the tag or attribute in question. |
INOXPE8751 | Storing an object of this mapping type is not permitted |
Explanation |
Storing an object which is linked to another object is not permitted. |
Action |
Please correct the document. |
INOXPE8752 | Document not found in database |
Explanation |
A document referenced by the current command was not found in the database, because it was deleted by another concurrent access. |
Action |
Re-issue the command. |
INOXPE8753 | The element has contents although it is defined with object type "EMPTY" |
Explanation |
The element has contents although it is defined with object type "EMPTY". |
Action |
Please correct either the document instance or the schema definition. |
INOXPE8754 | Comments are not allowed between documents |
Explanation |
The input file contains a comment between two documents. This is not allowed. |
Action |
Remove the comment. |
INOXPE8755 | Invalid document name (ino:docname) specified |
Explanation |
The document name given in the attribute ino:docname is empty. |
Action |
Either provide a document name in the attribute ino:docname or remove the ino:docname attribute. |
INOXPE8756 | Invalid versioning mode |
Explanation |
The document could not be stored, because the auto-version mode is invalid or the document is not in the correct versioning state. |
Action |
Make sure that the document is in the checkout-checkin auto-version mode and that the document is not checked out. |
INOXQE6250 | Feature not implemented |
Explanation |
The feature you tried to use is not implemented yet. |
Action |
Try an other method. |
INOXQE6251 | internal exception |
Explanation |
An internal exception has occurred. |
Action |
Please contact your software supplier. |
INOXQE6252 | Type exception: non-atomic type in element/attribute |
Explanation |
This error occurs if a non-atomizable type is encountered where a simple type is required, e.g. an element node belonging to a type that allows sub-elements is provided as a parameter for a function that expects a string. |
Action |
Check the operand's types or adopt the schema definition. |
INOXQE6253 | Type exception: sequence occurred where atomic value required |
Explanation |
Some functions and operators do not operate on sequences that contain that more than one entry. |
Action |
Check the operand types. |
INOXQE6254 | Type can not be compared / sorted |
Explanation |
Only totally ordered types such as numeric types, string types, boolean, dateTime, date and time can be compared and sorted. |
Action |
Try to use a totally ordered type or convert into such a type. |
INOXQE6255 | Invalid argument to aggregation function |
Explanation |
The atomic values in a sequence upon which the avg() or sum() function is applied must have a common super-type that is either numeric or a date/time type. |
Action |
Check the values in the sequence. |
INOXQE6256 | Conversion detected an invalid value |
Explanation |
An invalid value could not be converted. |
Action |
Check the query and the data. |
INOXQE6257 | Invalid type denotation for atomic type |
Explanation |
A string provided as an atomic type denotation, for example with a user-defined function, does not denote a type. |
Action |
Use proper type denotations, for example xs:integer or xdt:anyAtomicType. |
INOXQE6261 | Duplicate function definition |
Explanation |
A query or a module definition contains two definitions of the same function, or an imported module defines a function that is already defined. |
Action |
Remove the extra function definition. |
INOXQE6262 | Module not found |
Explanation |
An XQuery module import directive could not be satisfied, because there is no such module. |
Action |
Correct the import directive, or load an appropriate module definition. |
INOXQE6263 | Invalid server extension type detected |
Explanation |
A server extension function is called that returns or consumes a type that is not supported by the XQuery processor. |
Action |
Check the signature of the called server extension function. |
INOXQE6264 | Cyclic module import |
Explanation |
A module M may not import another module that directly or indirectly imports module M. |
Action |
Remove the cycle from the module import dependencies. |
INOXQE6300 | Internal error |
Explanation |
An internal error has occurred in the XQuery execution engine. |
Action |
Please contact your software supplier. |
INOXQE6301 | Runtime type exception |
Explanation |
An invalid type was detected at XQuery execution time. |
Action |
Correct the query. |
INOXQE6302 | XQuery feature not implemented |
Explanation |
The query uses an unimplemented language feature. Please see the documentation and release notes for current product limitations. |
Action |
Change the query. |
INOXQE6303 | Invalid position for range |
Explanation |
The first position parameter for 'range' is negative or zero. |
Action |
Check the query and data to find the wrong position value. |
INOXQE6304 | Internal error: buffer overflow |
Explanation |
An intermediate result is too large. |
Action |
Please contact your software supplier. |
INOXQE6305 | Division by zero |
Explanation |
A division by zero was attempted (not defined mathematically). |
Action |
Make sure that a divide by zero does not occur. |
INOXQE6306 | numeric overflow has occurred |
Explanation |
An arithmetic operation yielded a result which is not representable with the data type. |
Action |
Make sure that results do not exceed the representable range. |
INOXQE6307 | duplicate attribute name occurred in element constructor |
Explanation |
An element constructor contained multiple attributes of the same name. |
Action |
Make sure that attribute names of constructed elements are unique. |
INOXQE6308 | sort utility failed |
Explanation |
An explicit or implicit invocation of the sorting utility failed. This may occur due to insufficient disk space for temporary files. |
Action |
Check whether sufficient disk space is available for temporary files. |
INOXQE6309 | namespace prefix conflict between constructed element and attribute |
Explanation |
A constructed element contained a conflicting namespace declaration while an attribute was added to it. |
Action |
Use a different namespace prefix in the attribute's target environment. |
INOXQE6310 | Processing of data with X-Tension or X-Node mapping is not supported by XQuery |
Explanation |
Currently no data with X-Tension (server extension) or X-Node mapping can be accessed by an XQuery query. |
Action |
Formulate your query using Tamino X-Query instead of XQuery. |
INOXQE6311 | temporary file access failed |
Explanation |
A problem has occurred while accessing a temporary disk file. This may occur due to insufficient disk space for temporary files. |
Action |
Check whether sufficient disk space is available for temporary files. |
INOXQE6312 | Document access error |
Explanation |
A document did not exist though it was part of a query result. This situation can occur when a query is executed with isolation level "uncommitted document", while another transaction has been rolled back after concurrently inserting the document. |
Action |
Retry the query or use an isolation level different from "uncommitted document". |
INOXQE6313 | Runtime type exception: non-atomic type in element/attribute |
Explanation |
This error occurs if a non-atomizable type is encountered where a simple type is required, e.g. an element node belonging to a type that allows sub-elements is provided as a parameter for a function that expects a string. |
Action |
Check the operand's types or adopt the schema definition. |
INOXQE6314 | Value cannot be converted |
Explanation |
The textual representation of the value does not match the type it is being converted to. |
Action |
Check the query and the data. |
INOXQE6315 | Runtime type exception: sequence occurred where atomic value required |
Explanation |
Some functions and operators do not operate on sequences that contain more than one entry. |
Action |
Check the operand's types. |
INOXQE6316 | Run-time encountered non-comparable type |
Explanation |
Only totally ordered types such as numeric types, string types, boolean, dateTime, date and time can be compared and sorted. |
Action |
Try to use a totally ordered type or convert into such a type. |
INOXQE6317 | Run-time encountered invalid argument to aggregation function |
Explanation |
The atomic values in a sequence upon which the avg() or sum() function is applied must have a common super-type that is either numeric or a date/time type. |
Action |
Check the values in the sequence. |
INOXQE6318 | Runtime type exception: empty sequence occurred where atomic value required |
Explanation |
Some functions and operators do not operate on an empty sequence. |
Action |
Check the operand's types. |
INOXQE6319 | Invalid simple type detected |
Explanation |
In an expression, an invalid simple type was used. |
Action |
Check the actual type and the expected type with your query. |
INOXQE6320 | Invalid combination of operand types for an arithmetic operation |
Explanation |
The type of at least one operand is not valid for an arithmetic operation. |
Action |
Check where the types can occur in your query and correct it. |
INOXQE6321 | Runtime type exception: invalid node-type |
Explanation |
Some operations only operate on nodes of certain types. |
Action |
Check the node's type. Correct the path used to obtain the node. |
INOXQE6322 | Non-simple type detected |
Explanation |
A non-simple type was detected where a simple type is required. |
Action |
Check your query and the data to find a type mismatch. |
INOXQE6323 | Conversion: facet 'minLength' was violated by a value |
Explanation |
The value to be converted was too short. |
Action |
Check the query and the data. |
INOXQE6324 | Incompatible types for cast operation |
Explanation |
The source type cannot be cast to the target type. |
Action |
Check the type of the argument to the cast. |
INOXQE6325 | Conversion error for comparison |
Explanation |
During the execution of a comparison, the values must be converted to a common type. This conversion failed, either because of incomparable types or because of invalid data. |
Action |
Check your query and data to find the mismatch. |
INOXQE6326 | Comparison undefined |
Explanation |
Some data types cannot be compared because they are partially ordered. |
Action |
Check your query and data for undefined comparisons. |
INOXQE6327 | Invalid last position for range |
Explanation |
The last position parameter for 'range' is smaller than the first and is not -1. |
Action |
Check the query and data to find the wrong position value. |
INOXQE6328 | Value out of range |
Explanation |
A value could not be converted into the internal representation because it is out of range, for example the allowed range for a month is 1 to 12. |
Action |
Check your query and/or data. |
INOXQE6329 | Invalid collation URI exception |
Explanation |
The specified collation URI is invalid. |
Action |
Check the collation URI. |
INOXQE6330 | Invalid collation attributes exception |
Explanation |
The specified collation attributes are invalid. |
Action |
Check the collation attributes. |
INOXQE6331 | Namespace prefix undefined |
Explanation |
An invalid namespace prefix was detected when casting a string value as a QName at query execution time. |
Action |
Extend the static namespace context by adding a definition for the missing prefix. |
INOXQE6332 | Invalid content expression in computed processing instruction |
Explanation |
The value of the content expression in a computed processing instruction constructor contains the string "?>". |
Action |
Avoid expressions that may produce strings containing "?>". |
INOXQE6333 | Invalid name for processing instruction |
Explanation |
The name of a constructed processing instruction must be different from "XML" (in any combination of upper and lower case). |
Action |
Avoid expressions that may produce the string "XML". |
INOXQE6334 | "Treat as" operation has detected two non-matching types during query execution |
Explanation |
A "Treat as" operation has detected two non-matching types during query execution. |
Action |
Reformulate your query. |
INOXQE6335 | Call stack overflow |
Explanation |
The call stack for user defined functions has exceeded its defined maximum size. |
Action |
Inspect your XQuery program for potential programming errors, or increase the call stack's maximum size by means of the {?execution?} pragma. |
INOXQE6336 | Memory allocation limit exceeded |
Explanation |
The memory limit that has been set by an XQuery execution pragma has been exceeded. |
Action |
Extend the memory limit, or try to reduce the memory requirements by modifying the query. |
INOXQE6337 | Invalid content expression in computed comment constructor |
Explanation |
The result of the content expression of a computed comment constructor contains two adjacent hyphens or ends with a hyphen. |
Action |
Avoid expressions that produce adjacent hyphens or hyphens at the end. |
INOXQE6338 | Sort buffer overflow |
Explanation |
An internal sort buffer has overflowed, because the representation of a single tuple did not fit into it. |
Action |
Modify the query to reduce the size of tuples to be sorted. |
INOXQE6339 | Multiple element children in document constructor |
Explanation |
An XQuery document constructor was supplied with more than one element child. This is not supported by the underlying data model. |
Action |
Correct the query to avoid constructing multiple element children into a document node. |
INOXQE6340 | XML parsing error while executing fn:parse() |
Explanation |
An XQuery invoked fn:parse, but the argument could not be parsed successfully as XML. |
Action |
Provide well-formed XML. |
INOXQE6349 | fetching result that is not available |
Explanation |
A non-sensitive cursor pre-calculates a system defined maximum number of result items. A fetch request has tried to access an item that was not pre-calculated. |
Action |
Please contact your software supplier. |
INOXQE6350 | Internal error |
Explanation |
An internal error has occurred in the XQuery compiler. |
Action |
Please contact your software supplier. |
INOXQE6351 | XQuery feature not implemented |
Explanation |
The query uses an unimplemented language feature. Please see the documentation and release notes for current product limitations. |
Action |
Change the query. |
INOXQE6352 | XQuery parsing error |
Explanation |
One or more errors occurred while parsing the query. |
Action |
Correct the query appropriately and re-issue. |
INOXQE6353 | End tag does not match start tag |
Explanation |
The end tag of an element constructor does not match the start tag. |
Action |
Correct the query. |
INOXQE6354 | Namespace prefix undefined |
Explanation |
The namespace declaration is missing. |
Action |
Include a namespace declaration in the XQuery prolog. |
INOXQE6355 | Invalid namespace URI specification |
Explanation |
URIs must be given as string constants. |
Action |
Declare the URI literally. |
INOXQE6356 | Attempted to redefine prefix |
Explanation |
A prefix may only be defined once. |
Action |
Rename the prefix in subsequent declarations. |
INOXQE6357 | The prefix 'xml' must be bound to the namespace 'http://www.w3.org/XML/1998/namespace' |
Explanation |
The prefix 'xml' can only be declared when bound to the XML namespace URL as defined by the W3C. |
Action |
If your intent was to include the W3C's XML namespace, correct the URL. Otherwise use a different prefix. |
INOXQE6358 | Function unknown |
Explanation |
This function is unknown. The function name is either misspelt or the wrong prefix is used. |
Action |
Check the spelling and the function namespace. |
INOXQE6359 | Variable undefined |
Explanation |
A variable that is used must be declared in a 'for' or 'let' expression. |
Action |
Check spelling or add a 'for' or 'let' clause. |
INOXQE6360 | Unbound path not allowed here |
Explanation |
Currently access to database data is only allowed via the input() function. |
Action |
Use the input() function. |
INOXQE6361 | Type exception: invalid operands for operator |
Explanation |
Static typing detected invalid operand types for the operator. |
Action |
Please check the static types for the operator. |
INOXQE6362 | Invalid path: documents have no parent |
Explanation |
The path tries to apply the parent axis (or '..') to a document node. |
Action |
Check the path. |
INOXQE6363 | Unknown collection |
Explanation |
The URL refers to a collection that does not exist in the chosen database. |
Action |
Check the URL. |
INOXQE6364 | XQuery applied on non-XML doctype |
Explanation |
XQuery is only applicable to XML data. |
Action |
Use another tool for querying. |
INOXQE6365 | XQuery applied on non-namespace-clean doctype: |
Explanation |
XQuery is only applicable on namespace-clean doctypes. |
Action |
Apply proper namespace migration to doctype or use X-Query. |
INOXQE6366 | Type exception: invalid input for function |
Explanation |
The parameters provided as an input to the function do not have the required type. |
Action |
Check the correct parameter types in the documentation for the function. |
INOXQE6367 | Compile time type exception |
Explanation |
An invalid type has beed detected at XQuery compile time |
Action |
Correct the query. |
INOXQE6368 | Default element namespaces are not allowed |
Explanation |
The XQuery draft is still uncertain whether default element namespaces defined in the query prolog or in generated elements pertain to element steps in location paths. To avoid migration problems with subsequent versions of Tamino, the use of default element namespaces is prohibited. |
Action |
Please use a namespace prefix instead. |
INOXQE6369 | A prefix must not begin with 'xml' |
Explanation |
This is stated in the Errata Document for the XML Namespaces Recommendation. |
Action |
Chose a prefix that does not begin with 'xml'. |
INOXQE6370 | Processing of data with X-Tension or X-Node mapping is not supported by XQuery |
Explanation |
Currently no data with X-Tension (server extension) or X-Node mapping can be accessed by an XQuery query. |
Action |
Formulate your query using Tamino X-Query instead of XQuery. |
INOXQE6371 | The URI 'http://www.w3.org/XML/1998/namespace' can only be bound to the prefix 'xml' |
Explanation |
According to "Namespaces in XML Errata, 4 November 2002" (http://www.w3.org/XML/xml-names-19990114-errataNE05 substantive), the prefix xml is by definition bound to the namespace name http://www.w3.org/XML/1998/namespace. It may, but need not, be declared, and must not be bound to any other namespace name. No other prefix may be bound to this namespace name. |
Action |
Use the prefix 'xml' or a different URI. |
INOXQE6372 | No prefix may be bound to the URI 'http://www.w3.org/2000/xmlns/' |
Explanation |
This URI is by definition bound to the prefix 'xmlns'. It must not be declared. |
Action |
Use a different URI. |
INOXQE6373 | Invalid comparison |
Explanation |
Items to be compared must be of the same type, or both numeric, or both string or one of the types derived thereof. |
Action |
Use string comparison via applying the xf:string() function to non-string operands. |
INOXQE6374 | The prefix xmlns is used only to declare namespace bindings |
Explanation |
The prefix xmlns cannot be used unless in the form xmlns:prefix="uri" to declare a namespace binding. |
Action |
Use another prefix. |
INOXQE6375 | No multiple default collations allowed. |
Explanation |
Only one default collation can be defined. |
Action |
To use more than one collation within a single query give the collation's URI explicitly in the comparison function or use the getCollation() function. |
INOXQE6376 | Collation could not be obtained. |
Explanation |
The getCollation() function was not applied upon a path that pointed to an appropriate node. |
Action |
The input to the getCollation() function must be a path that points to an appropriate element or attribute node. A node is appropriate if its corresponding schema definition contains a collation specification. |
INOXQE6377 | Invalid Collation Identifier |
Explanation |
This string does not denote a valid collation. |
Action |
Correct the spelling or make the collection known to the database. |
INOXQE6378 | Invalid step in path |
Explanation |
A flat structure, i.e. something that is not a node, cannot be stepped into using any other axis than the self axis. |
Action |
Either change the object that is stepped into so that it is of type node or node-set, or use only the self axis (or the dot) to refer to the object. |
INOXQE6379 | Evaluation context undefined |
Explanation |
Processing of an expression relies on some component of the evaluation context that has not been assigned a value. Many context-sensitive functions like local-name() rely on the context item. |
Action |
Make sure that expressions relying on the evaluation context are called when an evaluation context is defined as for example within a filter. |
INOXQE6382 | XQuery cursor request must not specify a serialization method |
Explanation |
It is not possible to use a serialization method for an XQuery cursor request. |
Action |
If you want to apply a serialization method to your query result, use a non-cursor query. |
INOXQE6383 | Type exception: invalid input for internal function |
Explanation |
The parameters provided as an input to an internal function do not have the required type. Calls to internal functions are, for instance, contained in update queries. This error may thus indicate an invalid update statement. |
Action |
Reformulate the update statement or check whether the intended update operation is possible at all. |
INOXQE6384 | Invalid key or value in an optimization pragma. |
Explanation |
Valid optimization keys are "join" (possible values "default" and "index-only") and "level" (possible values "0" and "1"). |
Action |
Correct the optimization key and/or value. |
INOXQE6385 | Invalid output handler function detected |
Explanation |
An invalid output handler has been detected. Please check the signature of the given output handler function. |
Action |
Please check the signature of the given output handler function. |
INOXQE6386 | This name must not be local |
Explanation |
Some names, for example those of user-defined functions, must be in a namespace. They must either be qualified, i.e. consist of a prefix and a local part, or be in a namespace by a default namespace declaration. |
Action |
Use either a prefix declared in the query or add a default namespace declaration. For user-defined functions the predefined prefix 'local' can be used. |
INOXQE6387 | The prefix 'local' may only be used when declaring a user-defined function. |
Explanation |
The 'local' prefix is by definition bound to the URI "http://www.w3.org/2003/11/xquery-local-functions" and is reserved for the definition of user-defined, i.e. local, functions. |
Action |
Use another prefix. |
INOXQE6388 | The name of a computed node is neither a string nor a QName. |
Explanation |
The name of a computed node, such as for example element or attribute node, must either be of type string or derived or of type QName. |
Action |
Ensure that the expression provided as a computed node's name is of an appropriate type. |
INOXQE6389 | A user-defined function returns a non-matching type |
Explanation |
If a user-defined function declares a result type, the type of the function's body must match this declaration. |
Action |
Correct the function's body or delete the result type declaration. |
INOXQE6390 | The prefix 'xs' must be bound to the namespace 'http://www.w3.org/2001/XMLSchema' |
Explanation |
The prefix 'xs' can only be declared when bound to the appropriate namespace URL as defined by the W3C's XML Schema spec. |
Action |
If your intent was to include the W3C's xs namespace, correct the URL. Otherwise use a different prefix. |
INOXQE6391 | The name of a computed PI node is not an NCName. |
Explanation |
The name of a computed PI node must be an NCName. |
Action |
Ensure that the expression provided as a computed PI node's name is of an appropriate type. |
INOXQE6392 | The content of a generated PI must be a string. |
Explanation |
The expression provided as the content of a generated PI node must evaluate to a sequence of strings. |
Action |
Provide suitable content. |
INOXQE6393 | Pragma not supported in library module |
Explanation |
An XQuery library module contains a pragma that is valid only in a main module. |
Action |
Remove the pragma from the library module. |
INOXQE6394 | Invalid node comparison |
Explanation |
A node comparison requires that each operand is either a singleton or an empty sequence. |
Action |
Check the operands. If an operand is possibly a sequence with more than one entry, use round brackets and a [1] filter. |
INOXQE6395 | Invalid key or value in an serialization pragma. |
Explanation |
A valid serialization key is "provide-type-information" (possible values "yes" and "no"). |
Action |
Correct the serialization value. |
INOXQE6396 | Invalid key or value in an execution pragma. |
Explanation |
Valid execution keys are "memory" (possible values are integers) and "call-stack-depth" (possible values are also integers). |
Action |
Correct the execution key/value. |
INOXQE6397 | Duplicate parameter name in user-defined function |
Explanation |
Each parameter in a user-defined function's parameter list must have a unique name. |
Action |
Rename one or more parameters. |
INOXQE6398 | External variable definition does not conform to restricted XQuery syntax |
Explanation |
An XQuery expression that is supplied to define an external variable is restricted to sequences of constants, type-specific constructor functions and node constructors. |
Action |
Reformulate the external variable definition to conform to the restrictions. |
INOXQE6399 | Duplicate import directive |
Explanation |
Two 'import module' declarations specify the same module namespace. |
Action |
Remove the extra import directive or replace it by a namespace declaration. |
INOXQE6400 | Duplicate main-module pragma |
Explanation |
More than a single main-module pragma has been found in an XQuery. |
Action |
Remove the duplicate pragma. |
INOXQE6401 | Multiple declarations of element/type default namespace not allowed |
Explanation |
Only one default namespace for elements/types can be defined. |
Action |
Delete one of the default namespace declarations. |
INOXQE6402 | Multiple declarations of function default namespace not allowed |
Explanation |
Only one default namespace for functions can be defined. |
Action |
Delete one of the default namespace declarations. |
INOXQE6403 | Function is in a namespace different from the module's target namespace. |
Explanation |
The name of every function declared in a library module must have a namespace URI that is the same as the target namespace of the module. |
Action |
Change the function's namespace or move to another module. |
INOXQE6404 | A user-defined function is in a forbidden namespace |
Explanation |
The function name in a function declaration (when expanded) must not be in any of the following namespaces (among others): http://www.w3.org/XML/1998/namespace, http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance, http://www.w3.org/2005/04/xpath-functions, http://www.w3.org/2005/04/xpath-datatypes. |
Action |
Change the user-defined function's namespace by changing the prefix, or the prefix's binding, or the default function namespace. |
INOXQE6406 | Invalid context for updating function |
Explanation |
An updating function was invoked in a context where only a non-updating function is permitted. |
Action |
Modify the query to provide a proper function or context. |
INOXQE6407 | Invalid context for non-updating function |
Explanation |
A non-updating function was invoked in a context where only an updating function is permitted. |
Action |
Modify the query to provide a proper function or context. |
INOXQE6408 | Invalid name for external variable |
Explanation |
A qualified name including a prefix is not supported as the name of an external variable. |
Action |
Use a non-qualified name. |
INOXQE6420 | Query not found |
Explanation |
The given handle does not address any prepared query. |
Action |
Please correct the given query handle. |
INOXQE6421 | Invalid query handle |
Explanation |
The format of the given query handle is wrong. The query handle must be an integer. |
Action |
Correct the query handle. |
INOXQE6424 | Missing parameter for query execution |
Explanation |
The prepared query declares external variables. For at least one of these variables, no suitable input parameter was provided. |
Action |
Provide input parameter. |
INOXQE6450 | Update results in non-well-formed document |
Explanation |
The update statement tries a modification that would result in a non-well-formed document, e.g., insert an element into an attribute, or insert a second root element. The error is accompanied by a message that explains the actual reason in more detail. |
Action |
Correct the update statement. |
INOXQE6451 | Conflicting update operations |
Explanation |
An update statement can consist of several atomic update operations. There may be conflicts between those operations, e.g., a subtree cannot be replaced and deleted at the same time. |
Action |
Correct the update statement. |
INOXQE6452 | Attempted to insert or modify one of the meta-attributes ino:id or ino:docname |
Explanation |
Using XQuery update, it is not allowed to modify the meta-attributes ino:id or ino:docname. |
Action |
Correct your XQuery update statement. |
INOXQE6453 | Attempt to modify a nonxml document |
Explanation |
It is not possible to modify non-XML documents using an XQuery update statement. Only deletion of complete non-XML documents is allowed by XQuery update. |
Action |
Use the _process command in order to replace and thus modify a non-XML document. |
INOXQE6454 | Attempt to update the same XNode-mapped field twice with different values |
Explanation |
An XNode column/field appears at different paths in the schema, and an XQuery update statement tried to modify at least two paths with different values. |
Action |
Correct the XQuery update statement. |
INOXQE6455 | Invalid node type passed to updating function |
Explanation |
A node was passed to an updating function, but the node type was not suitable for the function. tf:setDocname and tdf:setProperty can be applied to document nodes only, while tf:put can be applied to document or element nodes. |
Action |
Modify the query to provide a node with a proper node type. |
INOXQE6456 | Invalid invocation of tdf:setProperty for live property |
Explanation |
tdf:setProperty was used in an XQuery update on a live property. This is not allowed, live properties cannot be updated this way. |
Action |
Modify the update statement, removing the invalid invocation of tdf:setProperty. |
INOXQE6457 | Invalid doctype name |
Explanation |
The URI used in a call to fn:put contained an invalid doctype name. The provided doctype name was either not a valid QName, or it did not match the root element name of the XML document to be stored. |
Action |
Provide a valid doctype name in the URI used with fn:put, or omit the doctype name from the URI. |
INOXQE6458 | XML parsing error while converting nonXML document |
Explanation |
A nonXML document was passed to fn:put() with a URI indicating an XML doctype. The nonXML content however failed to be parsed successfully as XML. |
Action |
Provide well-formed XML or store the document into an XML doctype. |
INOXQE6459 | Cannot update transient node |
Explanation |
A transient node, i.e. a node resulting from a previous constructor, was detected as the subject of an update operation. XQuery update however can only be applied to persistent nodes. |
Action |
Modify XQuery update statement to avoid applying update operations to transient nodes. |
INOXQW6380 | A path expression results in an empty node-set |
Explanation |
An empty node-set as a result of a path expression might indicate an error in referencing the document structure or in a name spelling. |
Action |
Ensure that the empty result is not due to a wrong path. |
INOXQW6405 | Invalid entity or character reference |
Explanation |
The query contains an invalid entity or a character reference that does not map to a valid character. As a corrective action, the ampersand character has been treated as a literal, not as an entity introducer. |
Action |
To avoid this warning, correct the query appropriately and re-issue. |
INOXQW6423 | Execution of prepared query requires recompilation |
Explanation |
Due to schema, security or structure index changes the compiled query yielded by previous preparation is not longer valid. This requires a recompilation of the prepared query. |
Action |
Recompile the prepared query. |
INOXQW6425 | querySearchMode=approximate not applicable for this query |
Explanation |
This query cannot be executed in a streaming mode, thus the specified request parameter querySearchMode=approximate has no effect. |
Action |
Do not use this request parameter. |
INOXRE8802 | Internal error: input parameter error |
Explanation |
Internal error: Data Map was called with missing or invalid parameters. |
Action |
Please contact your software supplier. |
INOXRE8803 | Specified name too long |
Explanation |
The specified name is too long. Length limitations are described in the Tamino documentation. |
Action |
Modify the schema definition and repeat your request. |
INOXRE8805 | Invalid collection, element, attribute or server extension name |
Explanation |
The specified name is not a valid QName. The specified name starts with a colon and/or contains more than one colon. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8806 | Collection is currently used by another user |
Explanation |
The request cannot be executed because at least one of the affected collections is currently held by another user. |
Action |
Repeat the request. |
INOXRE8807 | Doctype is currently used by another user |
Explanation |
There is a persistent lock on a doctype which prevents the current request from continuing. |
Action |
Repeat the request when the request that has the persistent lock has finished. |
INOXRE8808 | Index recreation currently not pending on the specified collection |
Explanation |
There is no index recreation pending to continue or reset. It is not necessary to execute the _admin command. |
Action |
No action required. |
INOXRE8809 | Index recreation is pending |
Explanation |
On the specified doctype an index recreation is pending. The requested action cannot be executed. |
Action |
Execute the corresponding _admin request to continue or reset the index recreation. |
INOXRE8810 | Index recreation is running |
Explanation |
The requested action cannot be executed while an index recreation is running on the specified doctype. |
Action |
No action required. |
INOXRE8811 | Collection name not found |
Explanation |
The specified collection is unknown. |
Action |
Correct the collection name and repeat the request. |
INOXRE8814 | Element/attribute name not found |
Explanation |
The specified element or attribute is unknown. |
Action |
Correct the element or attribute name and repeat the request. |
INOXRE8815 | Internal error: mapping already defined |
Explanation |
Internal error: mapping already defined. |
Action |
Please contact your software supplier. |
INOXRE8816 | Internal error while inserting an implicit element or attribute |
Explanation |
An internal error occurred while inserting an implicit element or attribute. |
Action |
Please contact your software supplier. |
INOXRE8818 | Duplicate collection name |
Explanation |
There is already a collection with the specified name. |
Action |
Specify another collection name or undefine the existing collection. |
INOXRE8819 | Duplicate element/attribute name |
Explanation |
The element or attribute to be inserted is already defined. It is not allowed to specify a schema containing two or more elements or attributes with the same name and the same parent. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8821 | Internal error: invalid parent specification |
Explanation |
Internal error: invalid parent specification. |
Action |
Please contact your software supplier. |
INOXRE8822 | Invalid options specification |
Explanation |
The specified options are incorrect. Either unexpected options are specified or expected options are missing. |
Action |
Refer to the Tamino documentation, correct your schema definition and repeat the request. |
INOXRE8823 | Internal error: invalid object ID specification |
Explanation |
Internal error: an invalid ID was specified. |
Action |
Retry with an increased transaction timeout value. If that doesn't help restart the Tamino database. If the problem still occurs please contact your software supplier. |
INOXRE8824 | Internal error: invalid collection ID specification |
Explanation |
Internal error: an invalid ID was specified. |
Action |
Please contact your software supplier. |
INOXRE8825 | Invalid multiplicity specification |
Explanation |
The specified multiplicity is invalid. Either the multiplicity does not correspond with the mapping type, or a multiplicity of + or * is specified for attributes, or a multiplicity not equal to blank is specified for the root element. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8826 | Invalid search type specification |
Explanation |
The search type is invalid or does not match the specified mapping type. For an external document summary file the specified shortname may be invalid. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8827 | Internal error: invalid index ID specification |
Explanation |
Internal error: an invalid ID was specified. |
Action |
Please contact your software supplier. |
INOXRE8830 | Invalid schema structure: missing node definition |
Explanation |
An attempt was made to specify a node with a mapping type which requires at least one child with a specific other mapping type. This element is missing. (Example: Mapping to an SQL table requires at least one child mapped to an SQL column.) |
Action |
Correct the schema definition and repeat the request. |
INOXRE8831 | Deletion rejected because of depending objects |
Explanation |
The server extension object could not be deleted because at least one node references a server extensions function of the object to be deleted. |
Action |
Update the schema definitions containing referencing nodes and repeat the request. |
INOXRE8833 | Internal error: file structure/schema definition mismatch |
Explanation |
Internal error: file structure/schema definition mismatch. |
Action |
Please contact your software supplier. |
INOXRE8834 | Data map record could not be stored |
Explanation |
A Data Map record could not be stored. The definition of one node is too large. |
Action |
Modify the schema definition and repeat the request. Please inform your software supplier. |
INOXRE8835 | Data map record could not be updated |
Explanation |
A data map record could not be updated. The number of children for one collection or node is too large. |
Action |
Modify the schema definition and repeat the request. Please inform your software supplier. |
INOXRE8836 | Modifying or deleting of system collection/doctype rejected |
Explanation |
Collections and doctypes containing the Tamino namespace may not be modified or deleted. |
Action |
No action required. |
INOXRE8841 | Invalid mapping specification: invalid or unexpected primary key definition |
Explanation |
For a mapped SQL table at least one mapped SQL column must be indicated as the primary key using the keyword ino:sqlprimarykeys. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8842 | Invalid mapping specification: invalid or unexpected password specification |
Explanation |
The specified Adabas password is either too long (maximum length is 8 characters) or unexpected (for nodes not mapped to AdaFile). |
Action |
Correct the schema definition and repeat the request. |
INOXRE8843 | Invalid mapping specification: invalid parent - child relation |
Explanation |
The relation between parent node and child node is not allowed. This is mostly caused by the object type of either parent or child node. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8844 | Invalid mapping specification: invalid parent - child relation |
Explanation |
The relation between parent node and child node is not allowed. This is caused by either an unexpected mapping type of the child node or a node having a multiplicity of + or * between a node mapped to an SQL table or an Adabas file and the corresponding nodes mapped to an SQL column or Adabas field, multiple field or periodic group. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8845 | Invalid schema structure: missing elements |
Explanation |
The mapping of the node is invalid. It requires other mapping in parent nodes. This error is mostly caused by a node mapped to an SQL column without having a corresponding node mapped to an SQL table, or mapped to an Adabas field without having a corresponding node mapped to an Adabas file. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8847 | Invalid mapping specification: invalid or unexpected shortname specification |
Explanation |
The specification of a shortname is not allowed or does not conform to Adabas shortname rules. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8848 | Invalid mapping specification: invalid or unexpected Adabas file specification |
Explanation |
The specification of a database ID and or file number is missing or invalid (Adabas file mapping) or not allowed (other mappings). |
Action |
Correct the schema definition and repeat the request. |
INOXRE8854 | Invalid mapping specification: invalid object reference specification |
Explanation |
The specified object reference was unexpected or refers to an undefined object. An object reference may only be specified for nodes mapped to another node. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8856 | Invalid mapping specification: invalid or unexpected SQL specification |
Explanation |
For an SQL table mapping the table name was missing or a password was specified without userid. For an SQL column mapping the column was not specified. For other mappings SQL specific keywords are unexpected. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8859 | Invalid mapping specification: invalid or unexpected format specification |
Explanation |
A format specification is either invalid (for Adafield mappings) or unexpected (for other mappings). A list of all valid formats is specified in the Tamino documentation. |
Action |
Correct the schema an repeat the request. |
INOXRE8860 | Invalid mapping specification: invalid or unexpected length specification |
Explanation |
A length specification is either invalid (for Adafield mappings) or unexpected (for other mappings). The length specification must conform to the format specification as defined in Adabas. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8861 | Invalid mapping specification: invalid or unexpected precision specification |
Explanation |
A precision was either specified for a non-SQL column mapping, or is unexpected or out of range for the specified datatype. Dependencies between datatype and precision are described in the Tamino documentation. |
Action |
Correct the schema and repeat the request. |
INOXRE8862 | Invalid mapping specification: invalid or unexpected scale specification |
Explanation |
A scale was either specified for a non-SQL column mapping, or is unexpected or out of range for the specified datatype. Dependencies between datatype, precision and scale are described in the Tamino documentation. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8863 | Invalid mapping specification: invalid or unexpected data type specification |
Explanation |
The specification of a data type is not allowed or does not conform to the list of supported datatypes. Please refer to the Tamino documentation for a list of supported data types. |
Action |
Correct the schema definition and repeat the request. |
INOXRE8865 | Invalid mapping specification: invalid or unexpected encoding specification |
Explanation |
The value for an encoding may only be specified for nodes mapped to an Adabas file or mapped to an Adabas field that has an alphanumeric format. The encoding must be a valid encoding string. |
Action |
Correct the schema and repeat the request. |
INOXRE8873 | Server extensions: function not found |
Explanation |
There is no server extension function with the specified function name. |
Action |
Check the specified function name. Be aware that function names are case sensitive. |
INOXRE8887 | The request cannot be executed within a session context |
Explanation |
In a session context it is not possible to recreate indexes for ino:creationDate or ino:lastModified. |
Action |
Recreate the indexes in a session-less request. |
INOXRE8888 | Adding a new node definition with the specified attributes is not supported |
Explanation |
Adding a new node definition with the specified attributes is not supported because of already existing documents. |
Action |
Remove the affected documents and repeat the request. |
INOXRE8889 | Modifying an existing node definition with the specified attributes is not supported |
Explanation |
The requested parameter may not be changed after the schema definition. |
Action |
Undefine the schema and define the modified schema definition once again. |
INOXRE8890 | Internal error: unsupported request |
Explanation |
The internal data map was called for an unsupported request. |
Action |
Please contact your software supplier. |
INOXRE8891 | Internal error: Data Map function failed |
Explanation |
The internal data map encountered an unexpected situation. |
Action |
Please contact your software supplier. |
INOXRE8892 | Internal error: Data Map corrupted |
Explanation |
The internal data map found insufficient data. |
Action |
Please contact your software supplier. |
INOXRE8893 | Internal error: conversion services failed |
Explanation |
An error occurred while the internal data map used conversion services. |
Action |
Please contact your software supplier. |
INOXRE8894 | Internal error: invalid file specification |
Explanation |
An internal error occurred during access to an Infofile. |
Action |
Please contact your software supplier. |
INOXRF8899 | Index recreation could not be finished successfully for doctype DOCTYPE in collection COLLECTION |
Explanation |
An error occurred while finishing the index recreation. The collection is currently not usable. |
Action |
Restart the server and execute the _admin command to finish the index recreation. |
INOXRI8838 | Request to create the unique constraint CONSTRAINT for doctype DOCTYPE in collection COLLECTION has failed and will be backed out |
Explanation |
A request to create a unique constraint was running during server shutdown. The unique constraint is dropped during server start. |
Action |
Repeat the request to create the unique constraint. |
INOXRW8801 | Request to create indexes for doctype DOCTYPE in collection COLLECTION is pending |
Explanation |
A request to create indexes was aborted with an error or was running during server shutdown. |
Action |
Start the corresponding admin command to continue or reset the index creation. |
INOXSE8903 | Memory allocation failed |
Explanation |
There was not enough main memory available to perform the request. |
Action |
Possibly the machine is overloaded. Try again later. |
INOXSE8905 | The combination of index-shortname and the search-type and/or map-type is not valid |
Explanation |
The node with the search-type and/or map-type cannot contain a definition of index-shortname |
Action |
Check the map-type and the search-type. |
INOXSE8906 | XML parser failure for schema definition |
Explanation |
The supplied schema definition is not well-formed XML. |
Action |
Correct the schema definition. |
INOXSE8909 | Internal error during schema processing |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXSE8910 | Invalid element content in schema definition |
Explanation |
The schema definition contains elements with mixed content, or the ino:file-format attribute has an illegal value. |
Action |
Correct the schema definition. |
INOXSE8911 | The specified mapping parameter(s) (adadsfnr, adadsdbid, adavoc...) can only be specified in a node which has the mapping type AdaFile |
Explanation |
The specifications such as adadsfnr, adadsdbid, adavoc etc. cannot be used with a mapping type other than AdaFile |
Action |
Remove the mapping parameters or change the mapping type to AdaFile. |
INOXSE8913 | Invalid structure of schema definition, hierarchy has to be collection - doctype - node |
Explanation |
The structure of the schema definition is invalid. It should be defined with the hierarchy collection - doctype - node(s). |
Action |
Check the schema definition and fix the affected nodes. |
INOXSE8914 | Internal error: buffer overflow |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXSE8915 | The keywords index-shortname, adadsdbid, adadsfnr, adavocdbid and adavocfnr are not supported in the current version |
Explanation |
These keywords are not supported in the current version. |
Action |
Remove these keywords from the schema definition. |
INOXSE8917 | Internal error: doctype without root element |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXSE8918 | Internal error: unknown object type |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXSE8920 | Internal error: unknown mapping type |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXSE8921 | ino:format or ino:length specified with SQL mapping |
Explanation |
ino:format and ino:length must not be specified with SQL mapping. |
Action |
Correct the schema definition. |
INOXSE8922 | Value has to be a number |
Explanation |
The given value could not be converted to a number. |
Action |
Correct the schema definition. |
INOXSE8923 | Specified number larger than allowed maximum |
Explanation |
The specified number was too large. |
Action |
Correct the schema definition. |
INOXSE8924 | Invalid doctype option specified |
Explanation |
An illegal value was specified for ino:options in the <ino:doctype> element. |
Action |
Correct the schema definition. |
INOXSE8926 | Collection name missing or invalid |
Explanation |
The name supplied in the ino:name attribute of the <ino:collection> element was either illegal or missing. |
Action |
Check the schema document. |
INOXSE8927 | Doctype name missing or invalid |
Explanation |
The name supplied in the ino:name attribute of the <ino:doctype> element was either illegal or missing. |
Action |
Correct the schema definition. |
INOXSE8929 | The node name specified does not conform to the XML specification |
Explanation |
The name specified in the ino:name attribute of an <ino:node> element does not conform to the XML specification. |
Action |
Correct the schema definition. |
INOXSE8930 | Doctype specified without any nodes |
Explanation |
Each doctype must have at least a root node. |
Action |
Correct the schema definition. |
INOXSE8931 | Node key missing |
Explanation |
The required ino:key attribute was missing for a <ino:node> element. |
Action |
Correct the schema definition. |
INOXSE8932 | Node object type missing |
Explanation |
The required ino:obj-type attribute was missing for a <ino:node> element. |
Action |
Correct the schema definition. |
INOXSE8933 | Node parent missing |
Explanation |
The required ino:parent attribute was missing for a <ino:node> element. |
Action |
Correct the schema definition. |
INOXSE8934 | Doctype contains multiple root nodes |
Explanation |
Each doctype must contain exactly one root node. |
Action |
Correct the schema definition. |
INOXSE8935 | Doctype contains no root nodes |
Explanation |
Each doctype must contain exactly one root node. |
Action |
Correct the schema definition. |
INOXSE8937 | Invalid parent reference |
Explanation |
The ino:parent attribute of an <ino:node> element did not point to another node. |
Action |
Correct the schema definition. |
INOXSE8938 | Invalid node option specified |
Explanation |
An illegal value was specified for ino:options in an <ino:node> element. |
Action |
Correct the schema definition. |
INOXSE8939 | Adabas dbid value too large |
Explanation |
The value specified for an Adabas database ID was too large. |
Action |
Correct the schema definition. |
INOXSE8940 | Adabas fnr value too large |
Explanation |
The value specified for an Adabas file number was too large. |
Action |
Correct the schema definition. |
INOXSE8941 | Length value too large |
Explanation |
The length value specified for an Adabas field was too large. |
Action |
Correct the schema definition. |
INOXSE8942 | Internal error: invalid ID reference |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXSE8943 | Internal error: bad query |
Explanation |
An internal error has occurred. |
Action |
Please contact your software supplier. |
INOXSE8944 | Object definition missing in the new schema definition |
Explanation |
One or more objects are missing in the schema definition although they are already defined in the data map. The current version does not support object deletion. |
Action |
Complete the schema definition. |
INOXSE8945 | Invalid type change |
Explanation |
Modification of type is not supported if type is CDATA. |
Action |
Fix the schema definition. |
INOXSE8946 | Shortname specified for ADAFile without adadsdbid/fnr |
Explanation |
Shortname specified for ADAFile without adadsdbid/fnr. |
Action |
Complete the schema definition. |
INOXSE8947 | Bad value for structure-index |
Explanation |
The specified value for structure-index of doctype is not supported. |
Action |
Fix the schema definition. |
INOXSE8948 | Attribute already declared |
Explanation |
An attribute is specified more than once. |
Action |
Fix the schema definition. |
INOXSE8949 | Different doctype and root element name |
Explanation |
The doctype and root element must have the same name. |
Action |
Fix the schema definition. |
INOXSE8950 | Too many indexes in schema |
Explanation |
The schema defines more than the maximum possible number of indexes. |
Action |
Adapt the schema definition. For example, you may use multipath indexes in order to reduce the number of indexes being created. |
INOXSE8951 | Too many elements/attributes for "lite" mapping" |
Explanation |
The schema defines more than the maximum possible number of elements/attributes for "lite" mapping". |
Action |
Correct the schema definition. |
INOXSE8952 | No more indexes available |
Explanation |
Attempted to create too many standard or text indexes in the schema definition. |
Action |
Remove standard or text indexes or use multi-path indexes where applicable. |
INOXSE8953 | Invalid node search type specified |
Explanation |
An illegal value was specified for the ino:search-type attribute. |
Action |
Correct the schema definition. |
INOXSE8954 | Scale value too large |
Explanation |
An illegal value was specified for the ino:scale attribute. |
Action |
Correct the schema definition. |
INOXSE8955 | Attribute missing |
Explanation |
There is a required attribute missing. |
Action |
Fix a schema definition. |
INOXSE8956 | Required node attribute missing |
Explanation |
One of the required attributes for the <ino:node> element is missing. |
Action |
Correct the schema definition. |
INOXSE8957 | Required doctype attribute missing |
Explanation |
One of the required attributes for the <ino:doctype> element is missing. |
Action |
Correct the schema definition. |
INOXSE8958 | Required collection attribute missing |
Explanation |
One of the required attributes for the <ino:collection> element is missing. |
Action |
Correct the schema definition. |
INOXSE8959 | Unknown node attribute specified |
Explanation |
An illegal attribute was specified for an <ino:node> element. |
Action |
Correct the schema definition. |
INOXSE8960 | Unknown doctype attribute specified |
Explanation |
An illegal attribute was specified for the <ino:doctype> element. |
Action |
Correct the schema definition. |
INOXSE8961 | Unknown collection attribute specified |
Explanation |
An illegal attribute was specified for the <ino:collection> element. |
Action |
Correct the schema definition. |
INOXSE8962 | Invalid or missing dbid parameter |
Explanation |
The explanation text in the< ino:messageline> element gives more information about the cause of the error. |
Action |
Correct the schema definition. |
INOXSE8963 | Invalid format value |
Explanation |
An illegal value was supplied in the ino:format attribute. |
Action |
Correct the schema definition. |
INOXSE8964 | Invalid object type value |
Explanation |
An illegal value was specified for the ino:obj-type attribute. |
Action |
Correct the schema definition. |
INOXSE8965 | Invalid data type value |
Explanation |
An illegal value was specified for the ino:data-type attribute. |
Action |
Correct the schema definition. |
INOXSE8966 | Invalid multiplicity value |
Explanation |
An illegal value was specified for the ino:multiplicity attribute. |
Action |
Correct the schema definition. |
INOXSE8967 | Invalid mapping type value |
Explanation |
An illegal value was specified for the ino:map-type attribute. |
Action |
Correct the schema definition |
INOXSE8968 | Invalid shortname value |
Explanation |
An illegal value was specified for the ino:shortname attribute. |
Action |
Correct the schema definition. |
INOXSE8969 | Unknown element name in schema definition |
Explanation |
Only <ino:collection>, <ino:doctype>, and <ino:node> are allowed as elements in a schema definition. |
Action |
Correct the schema definition. |
INOXSE8970 | Duplicate key value in schema definition |
Explanation |
The ino:key values must be unique within a schema definition. |
Action |
Correct the schema definition. |
INOXSE8971 | Invalid primary key reference in schema definition |
Explanation |
Every column reference in a primary definition for SQL table mapping needs to be declared as an SQL column mapping for one node in a subtree of the SQL table mapped node. |
Action |
Correct the schema definition. |
INOXSE8978 | Bad value for compression |
Explanation |
The specified value for compression of the doctype is not supported. |
Action |
Fix the schema definition. |
INOXSE8979 | Collection is currently used by another user |
Explanation |
The request cannot be executed because at least one of the affected collections is currently held by another user. |
Action |
Repeat the request. |
INOXSE8980 | Server extensions: external name and module name / function name are mutually exclusive |
Explanation |
Do not specify both external name and module name/function name for a server extension. |
Action |
Correct the schema definition. |
INOXTE7400 | Internal error |
Explanation |
A text retrieval internal error has occurred. |
Action |
Please contact your software supplier. |
INOXTE7401 | Empty search term |
Explanation |
An empty-valued search term is specified. |
Action |
Please specify a non-empty search term in the query. |
INOXTE7402 | Empty search token(s) |
Explanation |
One or more empty search tokens are specified. |
Action |
Please specify non-empty search tokens in the query. |
INOXTE7403 | Empty search term in word function |
Explanation |
An empty-valued search term is specified in the word function. |
Action |
Please specify a non-empty search term in the word function. |
INOXTE7404 | Invalid search term |
Explanation |
An invalid search term is specified. |
Action |
Please specify a valid search term in the query. |
INOXTE7405 | Invalid search token |
Explanation |
One or more invalid search tokens are specified. |
Action |
Please specify valid search tokens in the query. |
INOXTE7406 | Invalid search term in word function |
Explanation |
An invalid search term is specified in the word function. |
Action |
Please specify a valid search term in the word function. |
INOXTE7407 | Maximum number of search tokens exceeded |
Explanation |
The derived search tokens from the search term or specified search tokens have exceeded the maximum number allowed. |
Action |
Please correct your search term/tokens in the query. |
INOXTE7408 | Invalid wildcard usage |
Explanation |
Invalid wildcards are specified in the query. |
Action |
Please refer to Tamino documentation for more details. |
INOXTE7409 | Word function nesting |
Explanation |
Nesting of word functions is not allowed. |
Action |
Please correct the query. |
INOXTE7410 | Invalid highlighting marker |
Explanation |
Highlighting marker does not conform to an NCName. |
Action |
Please correct the marker parameter for the highlighting function. |
INOXTE7411 | Fragmented document reference |
Explanation |
Highlighting of document fragments is not supported. |
Action |
Please correct the query for the highlighting function. |
INOXTE7412 | Invalid node addressing |
Explanation |
Invalid node addressing of the document has occurred during the highlighting process. |
Action |
Please correct the query for the highlighting function. |
INOXTE7413 | No valid document node |
Explanation |
No valid document node is found for highlighting. |
Action |
Please correct the query for the highlighting function. |
INOXTE7415 | Invalid distance for proximity function |
Explanation |
The distance for a proximity function must be a positive integer. |
Action |
Correct the distance and try again. |
INOXTE7416 | index nonXML tsd:onTextInsert shadow X-Tension function not defined |
Explanation |
A shadow X-Tension function for the insertion of a non-XML text document was expected in the schema. |
Action |
Define a shadow X-Tension function tsd:onTextInsert in the schema. |
INOXTE7417 | index nonXML tsd:onBinaryInsert shadow X-Tension function not defined |
Explanation |
A shadow X-Tension function for the insertion of a non-XML binary object was expected in the schema. |
Action |
Define a shadow X-Tension function tsd:onBinaryInsert in the schema. |
INOXTE7418 | illegal phonrule definition |
Explanation |
The number of replace characters must not be higher than the number of characters to be replaced. |
Action |
Correct the phonrule(s) in question. |
INOXTE7419 | illegal stemrule definition |
Explanation |
The number of replace characters must not be higher than the number of characters to be replaced. |
Action |
Correct the stemrule(s) in question. |
INOXXE8600 | The group with name ino:admin may not contain any aclref elements |
Explanation |
The group with name ino:admin may not contain any aclref elements. |
Action |
Make sure that the group ino:admin contains no aclref elements and try again. |
INOXXE8601 | Not enough memory for the requested security operation |
Explanation |
Not enough memory for the requested security operation. |
Action |
Free up some memory resources and try executing the operation again. |
INOXXE8602 | This operation is not allowed for the special 2-Phase-Commit user |
Explanation |
This operation is not allowed for the special 2-Phase-Commit user. |
Action |
Make sure you specify a user with the needed privileges for this operation. |
INOXXE8603 | Namespace prefixes specified in ino:ace paths need to be defined |
Explanation |
Namespace prefixes specified in ino:ace paths need to be defined. |
Action |
Please specify a namespace definition for each namespace prefix and try again. |
INOXXE8604 | The aclref attribute may only reference existing documents |
Explanation |
The aclref attribute may only reference existing documents. |
Action |
Please check that only valid references to existing documents are specified in the aclref attribute. |
INOXXE8610 | Definitions for ino:userid, ino:groupname, and ino:aclname in the collection ino:security need to be unique |
Explanation |
Definitions for ino:userid, ino:groupname, and ino:aclname in the collection ino:security need to be unique. |
Action |
First delete the existing entry before loading the new one with the same name into the database. |
INOXXE8611 | Invalid path specified in an ino:ace element |
Explanation |
Invalid path specified in an ino:ace element. The path must consist of names that are valid for XML element or attribute names, separated by slashes. |
Action |
Please correct the path specified in the ino:ace element and try loading the security definitions again. |
INOXXE8699 | Administration command is not available |
Explanation |
An administration command is not available. |
Action |
Please contact your software supplier. |
INOXYE9002 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9003 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9004 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9005 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9006 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9007 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9008 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9009 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9010 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9011 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9012 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9013 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9014 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9015 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9016 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9017 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9018 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9019 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9020 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9021 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9022 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9023 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9024 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9025 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9026 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9027 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9028 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9029 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9030 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9031 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9032 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9033 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9034 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9035 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9036 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9037 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9038 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9039 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9040 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9041 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9042 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9043 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9044 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9045 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9046 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9047 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9048 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9049 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9050 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9051 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9052 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9053 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9054 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9055 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9056 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9057 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9058 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9059 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9060 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9061 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9062 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9063 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9064 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9065 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9066 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9067 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9068 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9069 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9070 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9071 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9072 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9073 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9074 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9075 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9076 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9077 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9078 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9079 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9080 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9081 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9082 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9083 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9084 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9085 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9086 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9087 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9088 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9089 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9090 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9091 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9092 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9093 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9094 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9095 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9096 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9097 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9098 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9099 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9100 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9101 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9102 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9103 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9104 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9105 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9106 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9107 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9108 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9109 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9110 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9111 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9112 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9113 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9114 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9115 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9116 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9117 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9118 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9119 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9120 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9121 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9122 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9123 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9124 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9125 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9126 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9127 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9128 | Doctype storage limit exceeded |
Explanation |
The storage limit for a single doctype was exceeded with regard to any of the following: -total number of documents -total collected size of documents -total number of occurrences of elements with reference index. |
Action |
Please contact your database adminstrator. |
INOXYE9129 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9130 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9131 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9132 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9133 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9134 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9135 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9136 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9137 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9138 | Bufferpool too small |
Explanation |
The buffer pool is to small to keep all data to be processed. In most cases this is caused by large amount of lock data. |
Action |
Increase the value of database property "buffer pool size". |
INOXYE9139 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9140 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9141 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9142 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9143 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9144 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9145 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9146 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9147 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9148 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9149 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9150 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9151 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9152 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9153 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9154 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9155 | The requested document(s) could not be locked |
Explanation |
An _XQL request was issued with _LOCKWAIT=no and _ISOLATION=shared/protected. At least one of the requested documents was locked by another user, therefore the lock could not be granted immediately. |
Action |
Retry the query, or specify _LOCKWAIT=yes. |
INOXYE9156 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9157 | Locking conflict has occurred |
Explanation |
The concurrently active transactions have issued conflicting lock requests. |
Action |
No action required. |
INOXYE9158 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9159 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9160 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9161 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9162 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9163 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9164 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9165 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9166 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9167 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9168 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9169 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9170 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9171 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9172 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9173 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9174 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9175 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9176 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9177 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9178 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9179 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9180 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9181 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9182 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9183 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9184 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9185 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9186 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9187 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9188 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9189 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9190 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9191 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9192 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9193 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9194 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9195 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9196 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9197 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9198 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9199 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9200 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9201 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9202 | Unique constraint violated |
Explanation |
Tamino detected either a duplicate ino:docname or a duplicate value for a unique constraint. |
Action |
Either choose a unique ino:docname or modify the documents. |
INOXYE9203 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9204 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9205 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9206 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9207 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9208 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9209 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9210 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9211 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9212 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9213 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9214 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9215 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9216 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9217 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9218 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9219 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9220 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9221 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9222 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9223 | Failed to create an additional database container |
Explanation |
Tamino failed to create an additional database container. This might be caused for example by a full disk or if the auto-expand option is set to "no". |
Action |
Analyze and remove the cause of the error. Typically, the job log of the database session will provide more information. In the Tamino Manager, select the node "Job Monitor" below "Tamino", and view the job of the database session in the category "Running Jobs" or "Pending Alerts". |
INOXYE9224 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9225 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9226 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9227 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9228 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9229 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9230 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9231 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9232 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9233 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9234 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9235 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9236 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9237 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9238 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9239 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9240 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9241 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9242 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9243 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9244 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9245 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9246 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9247 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9248 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9249 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9250 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9251 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9252 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9253 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9254 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9255 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9256 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9257 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9258 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9259 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9260 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9261 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9262 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9263 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9264 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9265 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9266 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9267 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9268 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9269 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9270 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9271 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9272 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9273 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9274 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9275 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9276 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9277 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9278 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9279 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9280 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9281 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9282 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9283 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9284 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9285 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9286 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9287 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9288 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9289 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9290 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9291 | Transaction aborted because it has taken too long |
Explanation |
The duration of the transaction has exceeded the maximum transaction duration. This can be caused by several circumstances: 1) The transaction could have done too much work to complete in the given time frame. 2) The number of transactions running in parallel has caused considerable delays in transaction execution. 3) The transaction might have waited for a resource that was held by another transaction for a very long time. In particular, this can happen if the number of XML work threads is too low. In this case, the transactions waiting for a resource block the XML work threads, and no XML work thread is available for the transaction holding the resource. 4) The transaction had to wait for a free XML work thread for a long time |
Action |
The maximum transaction duration and the number of XML work threads can be configured using the Tamino Manager. |
INOXYE9292 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9293 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9294 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9295 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9296 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9297 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9298 | Internal database error has occurred |
Explanation |
An internal error occurred. This could result in incorrect data. |
Action |
Please contact your software supplier. |
INOXYE9484 | Marked corrupt index for subsequent repair: collection name = COLL_NAME, node = NODE_PATH |
Explanation |
A corrupt index has been found and has been marked for index repair. It will not be used for query processing until it has been repaired. |
Action |
Repair indexes in the corresponding doctype using _admin=ino:RepairIndex() - then retry the operation and recreate the index if necessary. |
INOXYE9485 | Failed to prepare index marked as corrupt for subsequent repair index: collection name = COLL_NAME, node = NODE_PATH, reason = REASON |
Explanation |
An error occurred when attempting to prepare a corrupt index for a subsequent index repair. |
Action |
Please contact your software supplier. |
INOXYE9486 | Failed to mark index as corrupt due to a pending recreate index operation: collection name = COLL_NAME, node = NODE_PATH |
Explanation |
A corrupt index cannot be marked as corrupt while a recreate index operation or schema update is pending. |
Action |
Repair the indexes in the corresponding doctype using _admin=ino:RepairIndex() - then retry the operation and recreate the index if necessary. |
INOXYE9487 | Failed to mark index as corrupt due to recreate index operation in progress: collection name = COLL_NAME, node = NODE_PATH |
Explanation |
A corrupt index cannot be marked while a recreate index operation or schema update is in progress. |
Action |
Wait until recreate index operation or schema update on the corresponding doctype is finished, then retry the operation or recreate the index. |
INOXYE9488 | Error during index or constraint access |
Explanation |
An index or constraint is corrupted and must be recreated. |
Action |
Recreate all indexes and constraints of the doctype via ino:RecreateIndex admin command. |
INOXYE9489 | Error during index or constraint access |
Explanation |
An index or constraint is corrupted. |
Action |
Please contact your software supplier. |
INOXYE9490 | Error during index or constraint access |
Explanation |
An index or constraint is corrupted and must be recreated. |
Action |
Recreate the indexes and constraints via the ino:RecreateIndex admin command or update define. |
INOXYE9491 | Transaction aborted due to non-activity timeout |
Explanation |
The transaction has been aborted because there was no activity for a long time. |
Action |
The time period for non-activity timeout can be configured using the Tamino Manager (Property "non-activity timeout"). |
INOXYE9492 | Transaction aborted due to administrator action |
Explanation |
The database administrator has cancelled this transaction. |
Action |
No action required. |
INOXYE9493 | Transaction aborted because journal space was too small |
Explanation |
The journal space could not accommodate all the information that was necessary to back out the update command. |
Action |
Enlarge the journal space. |
INOXYE9494 | Request terminated because it tried to modify a replication database |
Explanation |
The request was sent to a replication database. User requests are not allowed to modify a replication database; only the replication process can do this. |
Action |
Send your request to the master of this replication database. |
INOXYE9495 | Request terminated because the replication database is currently not up-to-date |
Explanation |
The database is set to replication type with 'Simultaneous Query', but the currently replicated log space of the server does not contain additional locking information. Therefore the database cannot process queries while it replicates updates of this log space. Simultaneous query will be enabled, however, when the log space of the current session of the master is replicated. |
Action |
Wait until the log space of a session is replicated that permits simultaneous queries. Alternatively, send your request to the master of this replication database. |
INOXYE9496 | Transaction aborted due to deadlock |
Explanation |
The lock requests of concurrent transactions have caused a deadlock. |
Action |
No action required. |
INOXYE9497 | Transaction terminated because of ongoing replication process |
Explanation |
There is a replication process in progress that does not allow simultaneous queries. Because the replication process always has top priority on a replication database, any user transactions that had been active were terminated. |
Action |
Wait until the replication process has finished or starts another session that allows simultaneous queries. Alternatively send your request to the master of this replication database. |
INOXYE9498 | Request terminated due to database shutdown |
Explanation |
The request has been terminated because the database is being shut down. |
Action |
No action required. |
INOXYE9499 | Transaction aborted due to non-activity timeout or administration intervention |
Explanation |
The transaction has been aborted because there was no activity for a long time or because it was stopped by the database administrator. |
Action |
The time period for non-activity timeout can be configured using the Tamino Manager (Property "non-activity timeout"). |
INOXYW9483 | Found indexes marked as corrupt which cannot be dropped - subsequent index repair with "continue" option required: collection name = COLL_NAME, doctype = DOCTYPE_NAME |
Explanation |
A Tamino doctype contains indexes which must not be dropped, e.g. because they are used to implement a unique constraint. |
Action |
Issue _admin=inoRepairIndex() with the "continue" option for the same doctype in order to fix the corrupt indexes. |