High Availability Guide : Error codes for HotStandby : HotStandby errors and status codes
  
HotStandby errors and status codes
solidDB® HotStandby errors (14009 - 147xx, 307xx) occur when using the HotStandby commands.
solidDB® server errors for HotStandby
This section lists the solidDB® server errors that are related to HotStandby. A full list of the errors in the Server class is available in section “solidDB® server errors” in the solidDB® Administrator Guide.
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.
Meaning: The operation failed and the server is shutting down. Failure may be due to issuing the command to a non-HotStandby server, or to either a Primary or Secondary server in which the command does not apply.
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 cominfo'
ADMIN COMMAND 'hotstandby connect'
ADMIN COMMAND 'hotstandby status switch'
ADMIN COMMAND 'hotstandby set standalone'
ADMIN COMMAND 'hotstandby copy'
ADMIN COMMAND 'hotstandby netcopy'
14502
Server
Error
RPC parameter is invalid
Meaning: some of the connection info provided in the HSB connect string is erroneous and the connection to another server failed.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby status connect'
14503
Server
Error
Communication error, connection lost.
Meaning: There was a communication error and the other server was not found. There was a failure to connect to the other server.
ADMIN COMMANDs that may return this status in the result set of the command:
ADMIN COMMAND 'hotstandby status connect'
14520
Server
Error
Server is HotStandby secondary server, no connections are allowed.
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 might need to start one of the database servers (the one that you intend to become the Secondary) with the command-line option -x backupserver and then netcopy the Primary’s database to the Secondary.
For more information about how to resynchronize the primary and secondary servers after receiving error 14525, see How to resync HotStandby primary and secondary servers if hsb netcopy takes such a long time that hsb connect fails with error 14525?
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'
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.
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.
solidDB® HotStandby errors
Code
Class
Type
Description
14700
HotStandby
Error
Rejected connection, both servers in PRIMARY role.
Meaning: Command 'hsb connect' returns this error if both nodes are in same role.
14701
HotStandby
Error
Rejected connection, both servers in SECONDARY role.
Meaning: Command 'hsb connect' returns this error if both nodes are in same role.
14702
HotStandby
Error
Operation failed, catchup is active.
Meaning: While the servers are performing catchup, you will get this error if you issue any of the following commands on the Primary:
'hsb switch secondary'
'hsb set secondary alone'
'hsb set standalone'
'hsb connect'
'hsb copy'
'hsb netcopy'
While the servers are performing catchup, you will get this error if you issue any of the following commands on the Secondary:
'hsb switch primary'
'hsb set secondary alone'
'hsb set primary alone'
'hsb set standalone'
'hsb connect'
14703
HotStandby
Error
Operation failed, copy is active.
Meaning: While the Primary is doing copy or netcopy, the following commands returns this error:
'hsb switch secondary'
'hsb set secondary alone'
'hsb set standalone'
'hsb connect'
'hsb disconnect'
'hsb copy'
'hsb netcopy'
14704
HotStandby
Error
HotStandby copy or netcopy is only allowed when primary is in alone state.
Meaning: This error is returned if the server is in PRIMARY ACTIVE state and the command 'hsb copy' or 'hsb netcopy' is issued.
14705
HotStandby
Error
Setting to STANDALONE is not allowed in this state.
Meaning: If the server is in PRIMARY ACTIVE state and you issue the command 'hsb set standalone', then you will get this message.
14706
HotStandby
Error
Invalid read thread mode for HotStandby, only mode 2 is supported.
14707
HotStandby
Error
Operation not allowed in the STANDALONE state.
14708
HotStandby
Error
Catchup failed, catchup position was not found from log files.
14709
HotStandby
Error
Hot Standby enabled, but connection string is not defined.
14710
HotStandby
Error
Hot Standby admin command conflict with an incoming admin command.
14711
HotStandby
Error
Failed because server is shutting down.
14712
HotStandby
Error
Server is secondary. Use primary server for this operation.
solidDB® HSB errors and messages
Code
Class
Type
Description
14007
HSB
Message
CONNECTING
14008
HSB
Message
CATCHUP
14009
HSB
Message
No role switches since the server startup
14010
HSB
Message
DISCONNECTING
14522
HSB
Message
HotStandby copy directory not specified.
14537
HSB
Message
BROKEN
14704
HSB
Error
HotStandby copy or netcopy is only allowed when primary is in alone state
14712
HSB
Error
Server is secondary. Use primary server for this operation
30500
HSB
Message
Started as a HotStandby primary
30501
HSB
Message
Started as a HotStandby secondary
30502
HSB
Message
The database was not shut down properly the last time that it was used starting as a HotStandby secondary
30503
HSB
Message
Forcing HotStandby primary to start as a secondary
30504
HSB
Message
HotStandby role switched to secondary
30505
HSB
Message
HotStandby role switched to primary
30506
HSB
Message
Primary server must be set to PRIMARY ALONE or switched to the secondary role.
30507
HSB
Message
HotStandby server set to PRIMARY ALONE.
30508
HSB
Message
HotStandby server set to SECONDARY ALONE
30509
HSB
Message
HotStandby switch to primary failed, error error_code
30510
HSB
Message
HotStandby switch to secondary failed, error error_code
30511
HSB
Message
Failed to start HotStandby to server_name, error error_code
30512
HSB
Message
Failed to switch HotStandby role to primary, error error_code
30513
HSB
Message
Failed to switch HotStandby role to secondary, error error_code
30514
HSB
Message
Both databases are primary servers starting as a secondary
30515
HSB
Message
Both HotStandby databases are primaries
30516
HSB
Message
Failed to start HotStandby to server_name, other server rejected with error error_code
30517
HSB
Message
HotStandby role in secondary switched
30518
HSB
Message
HotStandby role switched to standalone
30530
HSB
Message
Starting to send HotStandby catchup data to secondary server
30531
HSB
Message
HotStandby catchup completed successfully
30532
HSB
Message
HotStandby catchup ended abnormally
30533
HSB
Message
HotStandby catchup can not be started. Secondary is not properly synchronized with primary full synchronization is required
30534
HSB
Message
HotStandby catchup ended abnormally, status error_code
30535
HSB
Message
HotStandby catchup ended abnormally, error error_code
30536
HSB
Message
HotStandby catchup ended abnormally due to a communication error
30537
HSB
Message
HotStandby catchup ended abnormally, secondary returned error error_code
30538
HSB
Message
HotStandby catchup size <value> greater than configured maximum size value, stopping HotStandby
30539
HSB
Message
File error in HotStandby catchup, stopping HotStandby
30540
HSB
Message
Starting to receive HotStandby catchup data from primary server
30541
HSB
Message
Secondary is not properly synchronized with primary due to a log file corruption. Restart secondary and execute a HSB netcopy.
30550
HSB
Message
Connection broken to HotStandby secondary server
30551
HSB
Message
Connected to HotStandby
30552
HSB
Message
HotStandby secondary connected
30553
HSB
Message
HotStandby primary connected
30554
HSB
Message
Hot Standby connection broken to Secondary server with an open transaction waiting for the operator to resolve transaction status. Primary server must be set to alone mode or switched to secondary mode.
30555
HSB
Message
HotStandby ping timeout
30556
HSB
Message
Connection broken to HotStandby secondary
30557
HSB
Message
HotStandby databases are not properly synchronized
30558
HSB
Message
HotStandby connection to secondary timed out
30559
HSB
Message
HotStandby connection broken
30560
HSB
Message
HotStandby: HotStandby_error_message
30561
HSB
Message
Started connecting to HotStandby
30562
HSB
Message
Connection broken to HotStandby primary server
30570
HSB
Message
Network backup completed.
30571
HSB
Message
Started to receive network backup.
30572
HSB
Message
Database started using a HotStandby copy/netcopy.
30573
HSB
Message
Network backup failed.
30574
HSB
Message
Hot Standby forcing threads to 1
30575
HSB
Message
Hot Standby replication configured but no active license found replication not started
30577
HSB
Message
HotStandby connect operation failed
30579
HSB
Message
HotStandby connection is already active.
30581
HSB
Message
Invalid event event
30582
HSB
Message
HotStandby cannot set the server to PRIMARY ALONE.
30583
HSB
Message
HotStandby copy failed.
30585
HSB
Message
Database starts to listen for netcopy.
30586
HSB
Message
HotStandby catchup, catchup_phase logpos: log_position
catchup_phase can be:
HSB waitdurable
HSB catchup start
HSB write catchup
HSB write switch
30750
HSB
Message
HotStandby connection is already active.
30752
HSB
Message
Operation failed disconnect is active.
30757
HSB
Message
CONNECTED
30758
HSB
Message
Bad Hot Standby command.
30759
HSB
Message
HotStandby server is set to STANDALONE.
30760
HSB
Message
Started the process of disconnecting the servers.
30761
HSB
Message
Started the process of switching the role to primary.
30762
HSB
Message
Started the process of switching the role to secondary.
30763
HSB
Message
Started the process of connecting the servers.
30764
HSB
Message
Copy started.
30765
HSB
Message
Parameter AutoPrimaryAlone is set to Yes.
30766
HSB
Message
Parameter AutoPrimaryAlone is set to No.
30767
HSB
Message
Parameter Connect is set to value.
30768
HSB
Message
HotStandby connection is already broken.
30769
HSB
Message
Operation failed because connection between the servers is active.
30772
HSB
Message
Hot Standby node identifier must be defined in the ini file.
30774
HSB
Message
Server is already STANDALONE.
30775
HSB
Message
Parameter CopyDirectory is set to value.
30776
HSB
Message
Parameter ConnectTimeout is set to value.
30777
HSB
Message
Parameter PingTimeout is set to value milliseconds.
30779
HSB
Message
Hot Standby migration is active
30782
HSB
Message
Server is already set to primary alone.
30783
HSB
Message
Server is already set to secondary alone.
30784
HSB
Message
Parameter parameter_name is set to value.
30785
HSB
Message
Parameter parameter_name is set to value.
30786
HSB
Message
Parameter parameter_name is set to value.
30787
HSB
Fatal Error
pri_dologskip:bad type, log pos, log size
This error refers to a failed operation on the HSB primary server. The error returns the failed operation and its location in the log, and the log size. Operations in the replication log are skipped.
30788
HSB
Fatal Error
pri_hsblogcopy_write:bad type, log pos, log size
This error refers to a failed operation on the HSB primary server. The write to the replication log file fails. The error returns the failed operation and its location in the log, and the log size.
30789
HSB
Fatal Error
Failed to open hot standby replication log file.
30790
HSB
Fatal Error
Failed to allocate memory for HotStandby log. Max Log size is logsize.
This error concerns a diskless database using HotStandby. In these systems, the HotStandby log is written to memory. This error is given if allocating more memory for the log file fails.
30791
HSB
Fatal Error
HotStandby:solhsby:bad type type, log pos log_pos, log size log_size
30792
HSB
Message
Both servers are secondary.
30793
HSB
Message
Maximum number of secondary tasks value reached.
The queue at the secondary server for incoming log operations is growing faster than the operations can be executed and acknowledged to the primary server.
The queue can be monitored with the performance counter HSB secondary queues.
30794
HSB
Message
Invalid HotStandby.Connect option -z. -z option is not supported.
See also
Error codes for HotStandby