solidDB Help : solidDB reference : Error codes : solidDB database (DBE) errors and messages
  
solidDB database (DBE) errors and messages
The solidDB database (DBE) error and message codes are described in the following table:
 
Code
Class
Type
Description
1004
Database
Warning
Database headers are inconsistent.
1005
Database
Warning
Database is crashed.
1012
Database
Warning
BLOB size overflow.
1013
Database
Warning
BLOB size underflow.
1019
Database
Return Code
Operation canceled.
1022
Database
Warning
The database you are using has been originally created with a different database block size setting than your current setting.
To suppress this warning, edit the solid.ini file to contain the following parameter setting:
Indexfile.BlockSize=required_blocksize
10001
Database
Error
Key value is not found.
Internal error: a key value cannot be found from the database index.
10002
Database
Error
Operation failed.
This is an internal error indicating that the index of the table accessed is in inconsistent state. Try to drop and create the index again to recover from the error.
You might also receive this error if you try to SET TRANSACTION READ ONLY when the transaction already contains some write operations.
10004
Database
Error
Redefinition.
Unexpected failure occurred in the database engine.
This error can also occur during recovery: either an index or a view has been redefined during recovery. The server is not able to do the recovery. Delete log files and start the server again.
10005
Database
Error
Unique constraint violation.
You have violated a unique constraint. This happens when you have tried to insert or update a column which has a unique constraint and the value inserted or updated is not unique.
This error message applies not only to user tables, but also to the system tables. For example, if you try to create a table that has the same name as an existing table, you might see this message. The same applies to other database object names, such as names of users, roles, and triggers.
10006
Database
Error
Concurrency conflict, two transactions updated or deleted the same row.
Two separate transactions have modified a same row in the database simultaneously. This has resulted in a concurrency conflict.
The error is returned when the tables are set with optimistic concurrency control and two or more concurrent connections attempt to obtain a exclusive lock on the same row/or set of rows at the same time (same row in the database is being modified simultaneously).
To diagnose the problem:
1 Enable monitoring.
2 Check soltrace.out for error 10006.
Resolving the problem:
The transaction that has been committed first is allowed to make the modifications to the database. The latter transactions is rolled back and this error message is returned to the application. To handle this update conflict, for example, the application could try to re-read the data and try the update again.
You can also switch to pessimistic locking method where row-level locking is used to avoid update conflicts. The pessimistic locking mode is suggested for tables that are modified frequently. To turn the pessimistic locking on for a table, use the ALTER TABLE statement.
10007
Database
Error
Transaction is not serializable.
The transaction committed is not serializable.
10008
Database
Error
Snapshot does not exist.
10009
Database
Error
Snapshot is newest.
10010
Database
Fatal Error
No checkpoint exists in database.
Possible causes for this error include:
Most likely the creation of a new database had failed. To recover, delete the database and log files and try to create the database again.
The database has been irrevocably corrupted. revert to the latest backup.
This error occurs when the server has crashed in the middle of creating a new database. Delete the database and log files and try to create the database again.
10011
Database
Fatal Error
Database headers are corrupted.
This can be due to a disk error or other system failure. Restore the database from a backup.
10012
Database
Fatal Error
Node split failed.
This error is given if the node split of the in-memory database (B+ tree) fails.
10013
Database
Error
Transaction is read-only.
You tried to do one of the following actions:
Execute conflicting SET TRANSACTION statements, for example, you executed SET TRANSACTION READ WRITE after you already SET TRANSACTION READ ONLY within the same transaction.
Write on a HotStandby database server that is in a SECONDARY state.
Write inside a transaction that is set read-only. Remove the write operation or unset the read-only mode in the transaction.
If you see this message in the first transaction that you try to execute after connecting to a server, and if you have not done anything to set the transaction or server to read-only mode, then try simply executing a COMMIT WORK statement and then re-executing the statement that caused the 10013 error.
10014
Database
Error
Resource is locked.
This error occurs when you are trying to use a key value in an index which has been concurrently dropped.
10016
Database
Error
Log file is corrupted.
One of the log files of the database is corrupted. You can not use these log files. Delete them and start the server again.
10017
Database
Error
Too long key value.
The maximum length of the key value has been exceeded. The maximum value is one third of the size of the index leaf.
If there are blobs (long varchars or long varbinaries) among the columns, the capacity requirements for a row can be reduced by storing the blob separately in the blob storage. However, when storing data in the blob storage, the first 254 bytes are also stored on the actual row. Therefore, with 8K block size, only 11 varchar columns with 254 characters of data is sufficient to exceed the key value limitation and cause this error message.
You can try to:
Increase the value of the IndexFile.BlockSize parameter to increase the key value limit
Redesign your database to reduce space requirements. Design alternatives include:
Break columns with big VARCHAR strings to several rows in separate tables. Implement a view to represent the data accordingly.
Define columns with big VARCHAR strings to be concatenated inside one long VARCHAR to be processed as a blob. Implement a view to represent the data accordingly.
Define the table to be stored in the main memory. Since main memory storage uses a different algorithm, where the row size limitation is defined the by disk block size (minus overhead in the range of tens of bytes per row and few bytes per column), the
limit is higher than with disk based tables. If the key value limit is exceeded in main memory tables, the error message is 16501.
10019
Database
Error
Backup is active
You have tried to start a backup when a backup process is already in progress.
10020
Database
Error
Checkpoint creation is active.
You have tried to start a checkpoint when a checkpoint creation is already in progress.
10021
Database
Error
Failed to delete log file log_file (errno = operating_system_error_code).
The deletion of a log file in making a backup has failed.
Reasons for the failure can be:
The log file has already been deleted from the operating system.
The log file has a read-only attribute.
10023
Database
Fatal Error
Wrong log file, maybe the log file is from another database.
The log file in the database directory is from another solidDB database. Copy the correct log files to the database directory.
10024
Database
Error
Illegal backup directory.
The backup directory is either an empty string or a dot indicating that the backup will be created in the current directory.
10026
Database
Error
Transaction is timed out.
An idle transaction has exceeded the maximum idle transaction time. The transaction has been aborted.
The maximum value is set in parameter AbortTimeOut in SRV section. The default value is 120 minutes.
10027
Database
Error
No active search.
This error is given during the UPDATE or DELETE operation if it is found that the active search identifying the data in the database to be updated or deleted does not exist.
10028
Database
Error
Referential integrity violation, foreign key values exist.
You tried to delete a row that is referenced from a foreign key.
10029
Database
Error
Referential integrity violation, referenced column values do not exist.
The definition of a foreign key does not uniquely identify a row in the referenced table.
10030
Database
Error
Backup directory directory name does not exist.
Backup directory is not found. Check the name of the backup directory.
10031
Database
Error
Transaction detected a deadlock or a lock wait timeout, transaction is rolled back.
To avoid lock timeouts, adjust the lock wait timeout settings.
To avoid deadlocks, adjust the data access order in concurrent transactions.
If necessary, begin transaction again.
10032
Database
Fatal Error
Wrong database block size specified.
The block size of the database file differs from the block size given in the configuration file solid.ini.
10033
Database
Error
Primary key unique constraint violation. Your primary key definition is not unique.
10034
Database
Error
Sequence name sequence conflicts with an existing entity.
Choose a unique name for a sequence. The specified name is already used.
10035
Database
Error
Sequence does not exist.
Check the name of the sequence.
10036
Database
Error
Data dictionary operation is active for accessed sequence.
A create or drop operation is active for the accessed sequence. Finish the current transaction and then try again.
10037
Database
Error
Can not store sequence value, the target data type is illegal. The valid target data types are BIGINT, INTEGER, and BINARY.
10038
Database
Error
Illegal column value for descending index.
Corrupted data found in descending index. Drop the index and create it again.
10039
Database
Error
INTERNAL: Assertion failure
For more information, contact solidDB Support.
10040
Database
Error
Log file write failure, probably the disk containing the log files is full. Shut down the server and reserve more disk space for log files.
10041
Database
Error
Database is read-only.
Server has run out of disk space and automatically switched to read-only mode. Free disk space, move the database file to another disk or divide the database into multiple files and disks with IndexFile.FileSpec parameter.
You can query the read-only mode of the database by using the ADMIN COMMAND 'getreadonlyflag' command.
10042
Database
Error
Database index check failed, the database file is corrupted.
10043
Database
Error
Database free block list corrupted, same block twice in free list.
10044
Database
Error
Primary key can not contain blob attributes.
10045
Database
Error
This database is a HotStandby secondary server, the database is read only.
10046
Database
Error
Operation failed, data dictionary operation is active. Wait and try again.
10047
Database
Error
Replicated transaction is aborted.
10048
Database
Error
Replicated transaction contains schema changes, operation failed.
10049
Database
Error
Secondary server not available any more, transaction aborted
10050
Database
Error
Replicated row contains BLOB columns that cannot be replicated.
10051
Database
Error
Log file is corrupted.
10052
Database
Fatal Error
Cannot convert an abnormally closed database. Use the old solidDB database version to recover the database first.
10053
Database
Error
Table is read only.
10054
Database
Fatal Error
Opening the database file failed.
Probably another solidDB process is already running in the same directory.
10055
Database
Fatal Error
Too little cache memory has been specified for the solidDB process.
10056
Database
Fatal Error
Cannot open database file. Error text (number). Most likely the solidDB process does not have correct access rights to the database file.
10057
Database
Fatal Error
The database is irrevocably corrupted. Revert to the latest backup.
10058
Database
Fatal Error
The internal database file format version (number) does not match with the solidDB version. Possible causes for this error include:
a version of solidDB that is too old is used with this database
the database has been corrupted
10059
Database
Fatal Error
The internal header version (number) does not match with the solidDB version.
Possible causes for this error include:
a version of solidDB that is too old is used with this database
the database has been corrupted
10060
Database
Fatal Error
Cannot perform roll-forward recovery in read-only mode.
If General.Readonly is set to no (default), the server has run out of disk space and automatically switched to read-only mode. To free disk space, move the database file to another disk or divide the database into multiple files and disks with IndexFile.FileSpec parameter.
10061
Database
Fatal Error
Out of database cache memory blocks.
solidDB process cannot continue because there is too little cache memory allocated for the solidDB process. Typical cause for this problem is a heavy load from several concurrent users. To allocate more cache memory, set the following solid.ini parameter to a higher value:
[IndexFile]
CacheSize=cache_size_in_bytes
Note Allocated cache memory size should not exceed the amount of physical memory.
10062
Database
Fatal Error
Failed to write to log filename at offset.
Verify that the disk containing the log files is not full and is functioning properly. Also, log files should not be stored on shared disks over the network.
10063
Database
Fatal Error
Cannot create new logfile file_name because such a file already exists in the log file directory.
Probably your log file directory also contains logs from some other database. solidDB process cannot continue until invalid log files are removed from the log file directory.
To recover:
Remove log filename and all other log files with greater sequence numbers.
Change the value of the Logging.FileNameTemplate parameter to point to a directory that does not contain any solidDB transaction log files.
10064
Database
Fatal Error
Illegal log file name template.
Most likely, the log file name template specified in Logging.FileNameTemplate contains too few or too many sequence number digit positions. There should be at least 4 and at most 10 digit positions.
10065
Database
Fatal Error
Unknown log write mode. Recheck the configuration parameter.
10066
Database
Fatal Error
Cannot open log filename. Check the following log file name template in solid.ini:
[Logging]
FileNameTemplate=name
and verify that:
it can be expanded into a valid file name in this environment
solidDB process has appropriate privileges to the log files directory.
10067
Database
Fatal Error
Cannot create database because old log filename exists in the log files directory.
Possibly the database has been deleted without deleting the log files or there are log files from some other database in the log files directory of the database to be created.
10068
Database
Fatal Error
Roll-forward recovery cannot be performed because the configured log file block size number does not match with block size number of existing filename.
To enable recovery, edit solid.ini to include parameter setting:
[Logging]
BlockSize=blocksize in bytes
and restart the solidDB process. After successful recovery, you can change the log file block size by performing these steps:
3 Shut down the solidDB process.
4 Remove old log files.
5 Edit new block size into solid.ini.
6 Restart solidDB.
10069
Database
Fatal Error
Roll-forward recovery failed because relation id number was not found. Database has been irrevocably corrupted. Restore the database from the last backup.
10070
Database
Fatal Error
Roll-forward failed because relation id number was not found. Database has been irrevocably corrupted. Restore the database from the latest backup.
10071
Database
Fatal Error
Restore the database from the latest backup.
10072
Database
Fatal Error
Database operation failed because of the file I/O problem.
10073
Database
Fatal Error
Database is inconsistent. Illegal index block type size, address, routine, reachmode. Restore the database from the latest backup.
10074
Database
Fatal Error
Roll-forward recovery failed. Revert to the latest backup.
10075
Database
Fatal Error
The database you are trying to use has been originally created with different database block size settings than your current settings.
Edit the solid.ini file to contain the following parameter setting:
[IndexFile]
BlockSize=blocksize in bytes
10076
Database
Fatal Error
Roll-forward recovery failed because tablename or viewname is redefined in the log filename.
Possible causes for this error include:
another solidDB process is using the same log file directory
old log files are present in the log file directory
solidDB process cannot use this corrupted log file to recover. In order to continue, you have the following alternatives:
Revert to the last backup.
Revert to the last checkpoint.
Revert to the last committed transaction within the last valid log file.
10077
Database
Fatal Error
No base catalog given for database conversion (use -C catalogname )
The base catalog must be provided when converting the database to a new format.
10078
Database
Error
User rolled back the transaction.
10079
Database
Error
Cannot remove filespec. File is already in use.
10080
Database
Error
HotStandby secondary server can not execute operation received from primary server.
A possible cause for this error is that the database did not originate from the primary server using HotStandby copy or netcopy command.
10081
Database
Error
The database file is incomplete or corrupt.
If the file is on a HotStandby secondary server, use the HotStandby copy or netcopy command to send the file from the primary server again.
10082
Database
Error
Backup aborted.
10083
Database
Error
Failed to abort HSB transaction because commit is already sent to secondary.
10084
Database
Error
Table is not locked.
10085
Database
Error
Checkpointing is disabled.
10086
Database
Error
Deleted row not found.
A key value being deleted cannot be found in the b-tree. This is an internal error.
10087
Database
Error
HotStandby not allowed for main memory tables.
10088
Database
Error
Specified lock timeout is too large.
10089
Database
Error
Operation failed, server is in HSB primary uncertain mode.
10090
Database
Error
Data dictionary operation in a newer transaction.
This error is returned when a transaction tries to access a table whose schema has been altered by a later transaction. The recommended action is to try the failing SQL command in a new transaction.
10091
Database
Error
Backup detected a log file with wrong block size, backup aborted.
10092
Database
Fatal Error
HotStandby cannot operate when logging is disabled.
10093
Database
Fatal Error
HotStandby migration is not possible if Hotstandby is not configured.
10094
Database
Fatal Error
Only amount cache pages configured for M-table usage, at least amount needed.
10095
Database
Error
Cursor is closed after isolation change.
The current cursor is closed, because its isolation level has been changed.
10096
Database
Fatal Error
Only kilobytes kilobytes configured for M-table checkpointing, at least kilobytes KB needed.
Not enough memory has been configured for the M-table.
10098
Database
Error
Incrementing sequence sequence_name failed.
10099
Database
Fatal Error
Encryption password has not been given for encrypted database.
10100
Database
Fatal Error
Incorrect password has been given for encrypted database.
10101
Database
Fatal Error
Unknown encryption algorithm.
10104
Database
Fatal Error
Database is not created using solidDB Storage Engine for MySQL Prototype. Cannot open database.
10105
Database
Error
Cache size for hash table specified with value parameter is smaller than actual cache size.
10106
Database
Fatal Error
Too big cache memory has been specified for the SOLID process. Edit the solid.ini file to change this parameter value not to exceed system limit and restart the SOLID process.
This is a fatal error.
10107
Database
Error
Cursor is closed after Logreader partition change.
10108
Database
Error
Search is aborted because of concurrent data dictionary operation on table.
10109
Database
Error
Transaction is already in prepared state, operation failed.
10110
Database
Error
XA transaction has not yet ended, operation failed.
10111
Database
Error
XA transaction has ended, operation failed.
10112
Database
Error
XA transaction is from a different connection, operation failed.
10113
Database
Error
Duplicate XID.
10114
Database
Error
XA transaction cannot have any DDL statements, operation failed.
10115
Database
Error
Operation is not supported with XA transaction.
10116
Database
Error
Failed to set internal trxid counter, trxid %164u, max new trxid %164u, counter trxid %164u.
10117
Database
Error
Transaction is too large.
10118
Database
Error
Database index tree is corrupted, cannot create new checkpoint.
10119
Database
Error
This interface cannot be used when Audit Info is collected.
10120
Database
Error
Logreader catchup position unreachable.
10121
Database
Error
Roll-forward recovery failed. There is a wrong file file in log file directory with wrong checkpoint information. Recovery checkpoint number is value, found checkpoint number value at position.
Possible causes for this error include:
log file directory contains log files from different databases.
some old log files are present in the log file directory.
solidDB process cannot use this invalid log file to recover.
10122
Database
Error
Database index tree migrate to a new format failed. Error error at position.
10123
Database
Error
Stack overflow, stack size size KB.
10124
Database
Error
Logreader cursor timed out while waiting for client to read data.
10126
Database
Error
Invalid HSB state in transaction commit, trx state state, hsb state state, trxid trxid.
10127
Database
Error
Logreader cursor queue size overflow, too long queue length.
16004
Database
Message
M-table operations now have enough memory for normal service.
16005
Database
Message
M-table operations now have enough memory for updates, inserts still disallowed.
16006
Database
Message
Memory for M-tables is now back below the warning level.
16501
Database
Error
New row value too large for M-table.
16502
Database
Error
Row size exceeds the allowed value for M-tables.
You might receive this error, for example, after you have upgraded to a new version of solidDB that uses in-memory tables as a default table type, and the previous version of your database used disk-based tables by default.
If you want to continue using disk-based tables, set the General.DefaultStoreIsMemory parameter to no.
16503
Database
Error
Serializable isolation level is not supported in M-tables.
16504
Database
Error
Memory for M-tables is running low, inserts to M-tables disallowed.
16505
Database
Error
Ran out of memory for M-tables, updates and inserts to M-tables disallowed.
16506
Database
Fatal Error
Too small configured MME.ImdbMemoryLimit to start server.
16507
Database
Error
Memory for M-tables is above the warning level.
16509
Database
Error
MME transaction maximum size exceeded
The maximum transaction size is set with the MME.MaxTransactionSize parameter.
30200
DBE
Message
Creating a new database.
30201
DBE
Message
Database converted successfully.
30202
DBE
Message
Database already exists.
30203
DBE
Message
Converting database ...
30204
DBE
Message
This database is from an older Solid version. To convert database for use with this version, start server with option -x convert. Note that after conversion, the database cannot be used with older versions of server anymore.
30205
DBE
Message
New database was not created.
30206
DBE
Message
Database does not exist. Cannot create a new database because the server is not running as a foreground process. To create a new database, start the server as a foreground process with -f option.
30207
DBE
Message
Failed to open the database. Exiting from server_name.
30208
DBE
Message
Merge not started; denied by user callback.
30209
DBE
Message
Idle merge started value keys to remove.
30210
DBE
Message
Merge started, value keys to remove.
30211
DBE
Message
Idle quick merge started.
30212
DBE
Message
Quick merge started.
30213
DBE
Message
Merge stopped, all keys merged.
30214
DBE
Message
Merge stopped, value keys merged.
30215
DBE
Message
Merge task started, value tasks active.
30216
DBE
Message
User merging enabled.
30217
DBE
Message
Error when converting procedures procedure procedure_name.
30218
DBE
Message
Quick merge stopped.
30220
DBE
Message
Checking database index.
30221
DBE
Message
Database index is ok.
30222
DBE
Message
Database is in backup server mode. Cannot check the index.
30223
DBE
Message
Testing the database index.
30224
DBE
Message
Database index has been tested successfully. Database index is ok.
30225
DBE
Message
ERROR! Database index is NOT ok! Check errors from file ssdebug.log.
30226
DBE
Message
SOLID Fatal Error: Failed to open the database for testing.
30227
DBE
Message
SOLID Fatal Error: Failed to connect to the database for testing.
30228
DBE
Message
Database file has been reorganized successfully.
30229
DBE
Message
ERROR! Failed to reorganize the database file! Check errors from file ssdebug.log.
30230
DBE
Message
Starting roll-forward recovery, wait ...
30231
DBE
Message
Recovery of value transactions successfully completed.
30232
DBE
Message
Recovery successfully completed.
30233
DBE
Message
Writing IMDB pages to disk. Pages: value.
30234
DBE
Message
Finished writing IMDB pages to disk. Pages: value.
30235
DBE
Message
Loading IMDB. Pages: value.
30236
DBE
Message
Finished loading IMDB. Pages: value.
30237
DBE
Message
Starting to reorganize and compact the database file.
30240
DBE
Message
Failed to create a new database.
30241
DBE
Message
Failed to log on to the database.
30242
DBE
Message
Failed to connect, script not executed.
30243
DBE
Message
Failed to open SQL input file.
30244
DBE
Message
Script script_name failed.
30245
DBE
Message
Table table_name not found.
30246
DBE
Message
Converting table table_name...
30247
DBE
Message
Table table_name converted.
30248
DBE
Message
No need to convert table table_name.
30249
DBE
Message
There is a problem opening the database because not all db files defined in the solid.ini were found. Check the configuration. Note that only the file(s) defined with the largest FileSpec_n definition(s) should be missing.
30250
DBE
Message
Using SplitMerge.
30251
DBE
Message
Starting to re-create the database (delete old database and create a new one).
30252
DBE
Message
Successfully deleted database and logs.
30253
DBE
Message
Failed to delete database and/or logs check file permissions.
30254
DBE
Message
Database is a broken HSB copy or netcopy database.
30255
DBE
Fatal Error
Exiting from server (FAKE_DBE_CRASHAFTERCPMARK).
30256
DBE
Fatal Error
Database must exist
30257
DBE
Fatal Error
Database creation date is already reset
30258
DBE
Fatal Error
Database creation time can be reset only one time
30259
DBE
Fatal Error
Error test in file file_name line value
30260
DBE
Message
Database version does not match with SOLID version.
30261
DBE
Message
Database file format does not match with SOLID version.
30262
DBE
Message
Maximum number of users reached.
30263
DBE
Message
Maximum number of old HSB states value reached.
30264
DBE
Message
Fixing bad B-tree node reference at address address.
30265
DBE
Message
Fixing B-tree key range errors at address address.
30266
DBE
Message
Running autofix.
30267
DBE
Message
Autofix completed successfully.
30268
DBE
Message
Autofix failed, check ssdebug.log for errors.
30269
DBE
Message
Maximum number of Logreader operations reached.
30270
DBE
Message
Maximum number of abort operations reached.
30271
DBE
Message
Failed to set Logging.ThreadPriority, value not changed.
30272
DBE
Message
Checkpoint integrity check started.
30273
DBE
Message
Checkpoint integrity check stopped.
30274
DBE
Message
Free list error, address address, status value.
30275
DBE
Message
Change list error, address address, status value.
30320
DBE
Message
Logreader using default transaction batch size value.
30321
DBE
Message
Logreader transaction batch size value.
30322
DBE
Message
Logreader read full statements.
30323
DBE
Message
Logreader catchup init.
30324
DBE
Message
Logreader catchup error.
30325
DBE
Message
Logreader catchup scan open.
30326
DBE
Message
Logreader catchup active.
30327
DBE
Message
Logreader catchup completed.
30328
DBE
Message
Logreader live data.
Go up to
Error codes