|
Code
|
Class
|
Type
|
Description
|
|---|---|---|---|
|
14003
|
Server
|
Return Code
|
ACTIVE
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby status switch'
ADMIN COMMAND 'hotstandby status catchup'
ADMIN COMMAND 'hotstandby status copy'
Meaning: The switch process, catchup process, copy or netcopy process is still active.
|
|
14007
|
Server
|
Return Code
|
CONNECTING
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby status connect'
Meaning: The Primary and Secondary servers are in the process of connecting.
|
|
14008
|
Server
|
Return Code
|
CATCHUP
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby status connect'
Meaning: The Primary server is connected to the Secondary server, but the transaction log is not yet fully copied. This message is returned only from the Primary server.
|
|
14009
|
Server
|
Return Code
|
No server switch occurred before.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby status switch'
Meaning: The switch process has never happened between the servers.
|
|
14501
|
Server
|
Error
|
Operation failed.
This error occurs when a timed command fails. Check the arguments of timed commands.
This error number is also used for certain HotStandby errors. See solidDB® High Availability User Guide for details.
|
|
14502
|
Server
|
Error
|
RPC parameter is invalid.
A network error has occurred.
|
|
14503
|
Server
|
Error
|
Communication error.
A communication error has occurred.
|
|
14504
|
Server
|
Error
|
Duplicate cursor name cursor.
You have tried to declare a cursor with a cursor name which is already in use. Use another name.
|
|
14505
|
Server
|
Error
|
Connect failed, illegal user name or password.
You have entered either a user name or a password that is not valid.
|
|
14506
|
Server
|
Error
|
The server is closed, no new connections allowed.
You have tried to connect to a closed server. Connecting was aborted.
|
|
14507
|
Server
|
Error
|
Maximum number of licensed user connections exceeded.
You have tried to connect to a server which has all licenses currently in use. Connecting was aborted.
|
|
14508
|
Server
|
Error
|
The operation has timed out.
You have launched an operation that has been aborted.
|
|
14509
|
Server
|
Error
|
Version mismatch.
A version mismatch has occurred. The client and server are different versions. Use same versions in the client and the server.
|
|
14510
|
Server
|
Error
|
Communication write operation failed.
A write operation failed. This indicates a network problem. Check your network settings.
|
|
14511
|
Server
|
Error
|
Communication read operation failed.
A read operation failed. This indicates a network problem. Check your network settings.
|
|
14512
|
Server
|
Error
|
There are users logged to the server.
You can not shutdown the server now. There are users connected to the server.
|
|
14513
|
Server
|
Error
|
Backup process is active.
You cannot shut down the server now. The backup process is active
|
|
14514
|
Server
|
Error
|
Checkpoint creation is active.
You cannot shut down the server now. The checkpoint creation is active.
|
|
14515
|
Server
|
Error
|
Invalid user id.
You tried to drop a user, but the user id is not logged in to the server.
|
|
14516
|
Server
|
Error
|
Invalid user name.
You tried to drop a user, but the user name is not logged in to the server.
|
|
14517
|
Server
|
Error
|
Someone has updated the at commands at the same time, changes not saved.
You tried to update timed commands at the same time another user was doing the same. Your changes will not be saved.
|
|
14518
|
Server
|
Error
|
Connection to the server is broken, connection lost. Possible network error. Reconnect to the server.
|
|
14519
|
Server
|
Error
|
The user was thrown out from the server, connection lost. Possible network error.
|
|
14520
|
Server
|
Error
|
Server is HotStandby secondary server, no connections are allowed.
|
|
14521
|
Server
|
Error
|
Failed to create a new thread for the client.
|
|
14522
|
Server
|
Error
|
HotStandby copy directory not specified.
Meaning: No copy directory is specified.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby copy'
To solve this problem, either specify the directory as part of the command, for example:
ADMIN COMMAND 'hotstandby copy \Secondary\dbfiles\'
or else set the CopyDirectory parameter in the solid.ini configuration file.
|
|
14523
|
Server
|
Error
|
Switch process is already active.
Meaning: The switch process is already active in the HotStandby server. If you only need to complete the current switch, then wait. If you are trying to switch a second time (that is, switch back to the original configuration), then you must wait for the first switch to complete before you can start the second switch.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby switch primary'
ADMIN COMMAND 'hotstandby switch secondary'
ADMIN COMMAND 'hotstandby status switch'
|
|
14524
|
Server
|
Error
|
HotStandby databases have a different base database, database time stamps are different.
Meaning: Databases are from a different seed database. You must synchronize databases. You may need to perform netcopy of the Primary’s database to the Secondary.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby connect'
ADMIN COMMAND 'hotstandby status switch'
|
|
14525
|
Server
|
Error
|
HotStandby databases are not properly synchronized.
Meaning: Databases are not properly synchronized. You must synchronize the databases. You may need to start one of the database servers (the one that you intend to become the Secondary) with the command line parameter -x backupserver and then netcopy the Primary’s database to the Secondary.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby connect'
ADMIN COMMAND 'hotstandby status switch'
|
|
14526
|
Server
|
Error
|
Invalid argument.
Meaning: An argument used in the HotStandby ADMIN COMMAND is unknown or invalid.
All HotStandby commands can return this error in the result set of the ADMIN COMMAND.
Note In the following HotStandby commands, the invalid argument error is a syntax error when the specified Primary or Secondary server can not apply to the switch:
ADMIN COMMAND 'hotstandby switch primary'
ADMIN COMMAND 'hotstandby switch secondary'
|
|
14527
|
Server
|
Error
|
This is a non-HotStandby server.
Meaning: The command was executed on a server that is not configured for HotStandby.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby connect'
ADMIN COMMAND 'hotstandby status switch'
ADMIN COMMAND 'hotstandby switch primary'
ADMIN COMMAND 'hotstandby switch secondary'
ADMIN COMMAND 'hotstandby state'
|
|
14528
|
Server
|
Error
|
Both HotStandby databases are primary databases.
Meaning: Both databases are Primary. This is a fatal error because there may be conflicting changes. Both databases are automatically dropped to Secondary state by the system. You must decide which database is the real Primary database and then synchronize the databases.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby connect'
ADMIN COMMAND 'hotstandby status switch'
|
|
14529
|
Server
|
Error
|
The operation timed out.
|
|
14530
|
Server
|
Error
|
The connected client does not support UNICODE data types.
Connected client is an old version client that does not support UNICODE data types. UNICODE data type columns cannot be used with old clients.
|
|
14531
|
Server
|
Error
|
Too many open cursor, max limit is value.
There are too many open cursors for one client; maximum number of open cursors for one connection is 1000. The value can be changed using the parameter Srv.MaxOpenCursors=n.
|
|
14532
|
Server
|
Error
|
Internal error: cursor synchronization between client and server failed. Contact technical support for more information.
|
|
14533
|
Server
|
Error
|
Operation cancelled
Operation was cancelled because client application called ODBC or JDBC cancel function.
|
|
14534
|
Server
|
Error
|
Server process size has exceeded the limit set with parameter Srv.ProcessMemoryLimit. Only ADMIN COMMANDs are allowed.
Increase the value of Srv.ProcessMemoryLimit or disable the process memory size checking by setting Srv.ProcessMemoryCheckInterval to 0.
Tip: You can modify the Srv.ProcessMemoryLimit and Srv.ProcessMemoryCheckInterval parameters dynamically with ADMIN COMMAND 'parameter'.
ADMIN COMMANDs are allowed so that you can increase the process size limit.
|
|
14535
|
Server
|
Error
|
Server is already a primary server.
Meaning: The server you are trying to switch to Primary is already in one of the PRIMARY states.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby switch primary'
|
|
14536
|
Server
|
Error
|
Server is already a secondary server.
Meaning: The server you are trying to switch to Secondary is already in one of the SECONDARY states.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby switch secondary'
|
|
14537
|
Server
|
Error
|
HotStandby connection is broken.
Meaning: This command is returned from both the Primary and Secondary server.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby status connect'
ADMIN COMMAND 'hotstandby connect'
One possible cause of this problem is an incorrect Connect string in the Secondary's solid.ini file. If the netcopy operation succeeds but the connect command fails, check the Connect string. (Netcopy does not require the Secondary to open a separate connection to the Primary, and thus may succeed even if the Connect string on the Secondary is wrong.)
|
|
14538
|
Server
|
Error
|
Server is not HotStandby primary server.
Meaning: To issue this command, the server must be a HotStandby Primary server.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby copy copy_directory'
ADMIN COMMAND 'hotstandby netcopy'
ADMIN COMMAND 'hotstandby connect'
ADMIN COMMAND 'hotstandby set primary alone'
ADMIN COMMAND 'hotstandby set standalone'
|
|
14539
|
Server
|
Error
|
Operation Refused.
This error code is given when one of the following situations occurs:
The user issued a netcopy command to a Primary server, but the server that should be Secondary is not actually in a Secondary state, or is not in “netcopy listening mode”. (Both the Primary and the Secondary server are probably in PRIMARY ALONE state.)
To solve the problem, restart the Secondary with the -x backupserver command-line option, then try again to issue the netcopy command to the Primary.
Attention: If both servers were in PRIMARY ALONE state, and if both servers executed transactions while those servers were in PRIMARY ALONE state, then they probably each have data that the other one does not. This is a serious error, and doing a netcopy to put them back in sync would result in writing over some transactions that have already been committed in the Secondary server.
This message can be generated when you use a callback function and the callback function refuses to shut down or accept a backup or netcopy command.
When you use linked library access, you can provide “callback” functions by using the SSCSetNotifier function. Your callback functions will be notified when the server has been commanded to shut down or to do a netcopy operation. If for some reason your application does not want the command to be followed, then your callback can return a value that cancels the command. In this situation, you will see error 14539.
To solve the problem, wait until the client code finishes the operation that it does not want to interrupt, then retry the command (for example, the shutdown or netcopy).
|
|
14540
|
Server
|
Error
|
Server is already a non-HotStandby server.
|
|
14541
|
Server
|
Error
|
HotStandby configuration in solid.ini conflicts with ADMIN COMMAND 'HSB SET STANDALONE'.
|
|
14542
|
Server
|
Error
|
Server in backupserver mode. Operation refused.
|
|
14543
|
Server
|
Error
|
Invalid command. The database is a HotStandby database but, HotStandby section not found in solid.ini configuration file.
|
|
14544
|
Server
|
Error
|
Operation failed. This command is not supported on diskless server.
|
|
14545
|
Server
|
Error
|
Primary can only be set to primary alone when its role is primary broken.
|
|
14546
|
Server
|
Error
|
Switch failed. The server or the remote server cannot switch from primary alone to secondary server. Catchup should be done first before switch.
Meaning: This command is returned when a state switch to SECONDARY is executed from a local or remote Primary server that is in the PRIMARY ALONE state and it is detected that the Primary and Secondary server are not in sync. You must connect the Primary server to the Secondary server and wait for the catchup process to complete before switching the Secondary to the Primary.
HotStandby commands that return this error:
ADMIN COMMAND 'hotstandby switch secondary'
|
|
14547
|
Server
|
Error
|
The value for the -R option (Read Timeout) was missing or invalid.
|
|
14548
|
Server
|
Error
|
Switch failed. The server in Standalone cannot be switched to a secondary.
Meaning: This command is returned when a state switch to SECONDARY is executed from a local or remote Primary server that is in the STANDALONE state and it is detected that the Primary and Secondary server are not in sync. You must connect the Primary server to the Secondary server and wait for the catchup to complete before switching the Secondary to the Primary.
HotStandby commands that return this error:
ADMIN COMMAND 'hotstandby switch secondary'
|
|
14549
|
Server
|
Error
|
HotStandby transaction is active.
Meaning: If the HotStandby connection is broken, Primary server must be set to alone mode or switched to secondary mode before shutdown.
|
|
14550
|
Server
|
Error
|
Hotstandby connect parameter can be changed only when the primary is not connected to secondary.
|
|
14551
|
Server
|
Error
|
Maximum number of START AFTER COMMIT statements reached.
|
|
14552
|
Server
|
Error
|
Server is in backup server mode, no connections are allowed.
Error 14552 is returned when a client attempts to establish a connection to a solidDB® server which is in a backup server mode (also called netcopy listening mode). The backup server mode is a special server mode where the solidDB® instance has been started with the command line option -xbackupserver. This mode indicates that the solidDB® instance is a Secondary server that is either waiting for or in the process of receiving the database file from the Primary server due to a netcopy command issued at the Primary server.
|
|
14553
|
Server
|
Error
|
Backup process is not active
This error is given if ADMIN COMMAND 'abort backup' is issued and no backup is active.
|
|
14554
|
Server
|
Error
|
The server does not support the required Transparent Failover level.
Reserved for future. This error will be reported when the server does not implement the Transparent Failover (TF) level requested by the application. Currently, there is only one level.
|
|
14555
|
Server
|
Error
|
Netbackup: Conflicting usage of backup directory %s.
|
|
14556
|
Server
|
Error
|
Netbackup: No server connection string specified.
|
|
14557
|
Server
|
Error
|
Netbackup: A server configured for HotStandby cannot act as a netbackup server.
|
|
14558
|
Server
|
Error
|
Operation not allowed when delete capture is off.
|
|
14559
|
Server
|
Error
|
Exceeded maximum number of allowed connections for user. Close existing connections or contact administrator to increase the limit.
Users with administrative privileges can define the maximum number of connections with the ALTER USER statement.
|
|
14570
|
Server
|
Error
|
XID not found.
|
|
14571
|
Server
|
Error
|
XID has not been prepared. Cannot execute two phase commit.
|
|
14572
|
Server
|
Error
|
XID has been prepared. Cannot execute one phase commit.
|
|
14600
|
Server
|
Error
|
Command is ambiguous in cluster session.
|
|
14706
|
Server
|
Error
|
Invalid read thread mode for HotStandby, only mode 2 is supported.
|
|
30135
|
Server
|
Fatal Error
|
SMA application has failed while processing the solidDB® server code. Server cannot continue and is executing emergency shutdown. Failed process id is process_id.
|