|
Code
|
Class
|
Type
|
Description
|
|---|---|---|---|
|
11000
|
System
|
Error
|
File open failure.
The server is unable to open the database file. Reason for the failure can be:
▪The database file has been set to read-only.
▪You do not have rights to open the database file in write mode.
▪Another solidDB® is using the database file.
Correct the error and try again.
|
|
11001
|
System
|
Fatal Error
|
File write failure.
The server is unable to write to the disk. The database files may have a read-only attribute set or you may not have rights to write to the disk. Add rights or unset read-only attribute and try again.
|
|
11002
|
System
|
Fatal Error
|
File write failed, disk full.
The server failed to write to the disk, because the disk is full. Free disk space or move the database file to another disk. You can also split the database file to several disks using the IndexFile.FileSpec parameter.
|
|
11003
|
System
|
Fatal Error
|
File write failed, configuration exceeded.
Writing to the database file failed because the maximum database file size set with IndexFile.FileSpec parameter has been exceeded.
Increase the maximum file size limit or divide the database into multiple files.
See Troubleshooting database file size (file write fails) for more details.
|
|
11004
|
System
|
Fatal Error
|
File read failure.
An error occurred reading a file. This may indicate a disk error in your system.
|
|
11005
|
System
|
Fatal Error
|
File read beyond end of file.
This error is given, if the file EOF is reached during the read operation.
|
|
11006
|
System
|
Fatal Error
|
File read failed, illegal file address.
An error occurred reading a file. This may indicate a disk error in your system, or insufficient file read or write permissions.
With this error, the following type of error message can be written to the solmsg.out file:
SsBOpenLocal failed,
file '/home/solid/sol00001.log', error = 13, retries = 0, open files = 1 The error 13 refers to an operating system error code 13 which is defined as:
#define EACCES 13 /* Permission denied */
This means that the solid process does not have operating system permissions to read or create the file.
|
|
11007
|
System
|
Fatal Error
|
File lock failure.
The server failed to lock the database file.
|
|
11008
|
System
|
Fatal Error
|
File unlock failure.
The server failed to unlock a file.
|
|
11009
|
System
|
Fatal Error
|
File free block list corrupted.
This error is given when reading data from disk to memory, but the memory space is already allocated for another purpose.
|
|
11010
|
System
|
Error
|
Too long file name.
Filename specified in parameter IndexFile.FileSpec is too long. Change the name to a proper file name.
|
|
11011
|
System
|
Error
|
Duplicate file name specification.
Filename specified in parameter IndexFile.FileSpec is not unique. Change the name to a proper file name.
|
|
11012
|
System
|
Fatal Error
|
License information not found, exiting from solidDB Check the existence of your solid.lic file.
|
|
11013
|
System
|
Fatal Error
|
License information is corrupted. Your solid.lic file has been corrupted.
|
|
11014
|
System
|
Fatal Error
|
Database age limit of evaluation license expired.
|
|
11015
|
System
|
Fatal Error
|
Evaluation license expired.
|
|
11016
|
System
|
Fatal Error
|
License is for different CPU architecture.
|
|
11017
|
System
|
Fatal Error
|
License is for different OS environment.
|
|
11018
|
System
|
Fatal Error
|
License is for different version of this OS.
|
|
11019
|
System
|
Fatal Error
|
License is not valid for this server version.
|
|
11020
|
System
|
Fatal Error
|
License information is corrupted.
|
|
11021
|
System
|
Fatal Error
|
Problem with your license, please contact solidDB support.
|
|
11022
|
System
|
Error
|
Desktop license is only for local protocol communication, cannot use protocol for listening.
|
|
11023
|
System
|
Error
|
Internal binary stream error.
This error is given if read or write fails when handling a binary stream object.
|
|
11024
|
System
|
Error
|
Desktop license is only for local communication, cannot use name for listening.
|
|
11025
|
System
|
Error
|
License file filename is not compatible with this server executable.
The server has been started with an incompatible license file. You need to update your license file to match the server version.
|
|
11026
|
System
|
Error
|
Backup directory contains a file which could not be removed.
Some file could not be removed from the backup directory. The backup directory may point to a wrong location.
|
|
11027
|
System
|
Error
|
No such parameter section section.
Parameter was not found from the specified section in the solid.ini file.
|
|
11028
|
System
|
Error
|
No such parameter section.name. Parameter does not exist.
|
|
11029
|
System
|
Error
|
Not allowed to set parameter value.
User is not allowed to set the parameter value.
|
|
11030
|
System
|
Error
|
Cannot set values to multiple parameters. Only one parameter can be set at one time.
|
|
11031
|
System
|
Error
|
Illegal type for parameter. Parameter type is illegal.
|
|
11032
|
System
|
Error
|
Cannot set new value for parameter section.name. A new value cannot be set for the parameter.
|
|
11033
|
System
|
Error
|
Parameter is read-only.
|
|
11034
|
System
|
Error
|
File remove failure.
|
|
11035
|
System
|
Error
|
Value for parameter is smaller than minimum value.
|
|
11036
|
System
|
Error
|
Value for parameter is bigger than maximum value.
|
|
11037
|
System
|
Error
|
Value for parameter is invalid.
|
|
11038
|
System
|
Error
|
File specification exceeds the database address space.
|
|
11039
|
System
|
Error
|
File specification exceeds the database address space.
This error is given if solidDB® attempts to use a file, whose given size is larger that the size that solidDB® can use.
|
|
11040
|
System
|
Error
|
Password file cannot be opened.
This error is given if solidDB® cannot find the database password file.
|
|
11041
|
System
|
Error
|
No password found in password file.
This error is given if the database password is not in the password file.
|
|
11042
|
System
|
Error
|
Internal error: Empty diagnostic record. Contact solidDB® Support for more information.
|
|
11045
|
System
|
Fatal Error
|
Call to system function munmap failed with errno 12 (ENOMEM). System has run out of memory, or the process’s maximum number of mappings has been exceeded.
In Linux environments, you might be able to recover from the error by increasing the value of the kernel parameter vm.max_map_count. For instructions how to modify the value of vm.max_map_count, see the documentation provided with your operating system.
|