|
Code
|
Class
|
Type
|
Description
|
|---|---|---|---|
|
14007
|
HSB
|
Message
|
CONNECTING
ADMIN COMMANDs that might 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
|
HSB
|
Message
|
CATCHUP
ADMIN COMMANDs that might 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
|
HSB
|
Message
|
No server switch occurred before.
ADMIN COMMANDs that might 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.
|
|
14010
|
HSB
|
Message
|
DISCONNECTING
ADMIN COMMANDs that might 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 disconnecting.
|
|
14522
|
HSB
|
Message
|
HotStandby copy directory not specified.
|
|
14537
|
HSB
|
Message
|
BROKEN
|
|
14700
|
HSB
|
Error
|
Rejected connection, both servers in PRIMARY role.
Meaning: Command 'hsb connect' returns this error if both nodes are in same role.
|
|
14701
|
HSB
|
Error
|
Rejected connection, both servers in SECONDARY role.
Meaning: Command 'hsb connect' returns this error if both nodes are in same role.
|
|
14702
|
HSB
|
Error
|
Operation failed, catchup is active.
Meaning: While the servers are performing catchup, you will get this error if you run any of the following commands on the primary server:
'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 run any of the following commands on the secondary server:
'hsb switch primary'
'hsb set secondary alone' 'hsb set primary alone' 'hsb set standalone' 'hsb connect' |
|
14703
|
HSB
|
Error
|
Operation failed, copy is active.
Meaning: While the primary server is executing a copy or netcopy command, 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
|
HSB
|
Error
|
HotStandby copy or netcopy commands are allowed only when the primary server is in PRIMARY ALONE state.
Meaning: This error is returned if the server is in PRIMARY ACTIVE state and the command 'hsb copy' or 'hsb netcopy' is run.
|
|
14705
|
HSB
|
Error
|
Setting to STANDALONE is not allowed in this state.
Meaning: If the server is in PRIMARY ACTIVE state and you run the command 'hsb set standalone', then you will get this message.
|
|
14706
|
HSB
|
Error
|
Invalid read thread mode for HotStandby, only mode 2 is supported.
|
|
14707
|
HSB
|
Error
|
Operation not allowed in the STANDALONE state.
|
|
14708
|
HSB
|
Error
|
Catchup failed, catchup position was not found from log files.
|
|
14709
|
HSB
|
Error
|
Hot Standby enabled, but connection string is not defined.
|
|
14710
|
HSB
|
Error
|
Hot Standby admin command conflict with an incoming admin command.
|
|
14711
|
HSB
|
Error
|
Failed because server is shutting down.
|
|
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 server is not properly synchronized with primary server. 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 server is not properly synchronized with primary server 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 to secondary server is broken with an open transaction waiting for the operator to resolve transaction status. Primary server must be switched to PRIMARY ALONE or SECONDARY ALONE state.
|
|
30555
|
HSB
|
Message
|
HotStandby ping timeout.
|
|
30556
|
HSB
|
Message
|
Connection to HotStandby secondary server is broken.
|
|
30557
|
HSB
|
Message
|
HotStandby databases are not properly synchronized.
|
|
30558
|
HSB
|
Message
|
HotStandby connection to secondary server 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 to HotStandby primary server is broken.
|
|
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
|
|
30587
|
HSB
|
Message
|
Failed to set %s.%s, value not changed.
|
|
30588
|
HSB
|
Message
|
Hotstandby action: action.
|
|
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.
|