Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

Versions available for this page: CUBRID 8.4.0 |  CUBRID 8.4.1 |  CUBRID 8.4.3 |  CUBRID 9.0.0 | 

Error Messages

Replication Log Copy Process (copylogdb)

The error messages from the replication log copy process are stored in $CUBRID/log/db-name@remote-node-name_copylogdb.err. The severity levels of error messages found in the replication log copy process are as follows: fatal, error, and notification. The default level is error. Therefore, to record notification error messages, it is necessary to change the value of error_log_level in the cubrid.conf file. For details, see Error Message-Related Parameters.

Initialization Error Messages

The error messages that can be found in initialization stage of replication log copy process are as follows:

Error Code

Error Message

Severity

Description

Solution

10

Cannot mount the disk volume ?.

error

Fails to open a replication log file.

Check if replication logs exist. For the location of replication logs, see Default Environment Configuration.

78

Internal error: an I/O error occurred while reading logical log page ? (physical page ?) of ?

fatal

Fails to read a replication log.

Check the replication log by using the cubrid applyinfo utility.

81

Internal error: logical log page ? may be corrupted.

fatal

A replication log page error, in which the replication log copy process has been copied from the connected database server process.

Check the error log of the database server process to which the replication log copy process is connected.
This error log can be found in $CUBRID/log/server.

1039

log writer: log writer has been started. mode: ?

error

The replication log copy process has been successfully initialized and started.

No action is required because this error message is recorded to display the start information of the replication log copy process.
Ignore any error messages which are displayed between the start of replication log copy process and output of this error message since there is a possibility that an error message is shown up even in normal situation.

Replication Log Request and Reception Error Messages

The replication log copy process requests a replication log from the connected database server and receives the corresponding replication log. Error messages that can be found in this stage are as follows:

Error Code

Error Message

Severity

Description

Solution

89

Log ? is not included in the given database.

error

The previously replicated log and the log to be replication do not match.

Check information of the database server/host to which the replication log copy process is connected. If you need to change the database server/host information, reinitialize it by deleting the existing replication log and then restarting.

186

Data receiver error from the server

error

Incorrect information has been received from the database server to which the replication log copy process is connected.

It will be internally recovered.

199

The server is not responding.

error

The connection to the database server has been terminated.

It will be internally recovered.

Replication Log Write Error Messages

The replication log copy process copies the replication log that was received from the connected database server process to the location (ha_copy_log_base) specified in the cubrid_ha.conf file. Error messages that can be found in this stage are as follows:

Error Code

Error Message

Severity

Description

Solution

10

Cannot mount the disk volume ?.

error

Fails to open a replication log file.

Check if replication logs exist.

79

Internal error: an I/O error occurred while writing logical log page ? (physical page ?) of ?.

fatal

Fails to write a replication log.

It will be internally recovered.

80

An error occurred due to insufficient space in operating system device while writing logical log page ? (physical page ?) of ?. Up to ? bytes in size are allowed.

fatal

Fails to write a replication log due to insufficient file system space.

Check if there is sufficient space left in the disk partition.

Replication Log Archive Error Messages

The replication log copy process periodically archives the replication logs that have been received from the connected database server process. Error messages that can be found in this stage are as follows:

Error Code

Error Message

Severity

Description

Solution

78

Internal error: an I/O error occurred while reading logical log page ? (physical page ?) of ?.

fatal

Fails to read a replication log during archiving.

Check the replication log by using the cubrid applyinfo utility.

79

Internal error: an I/O error occurred while writing logical log page ? (physical page ?) of ?.

fatal

Fails to write an archive log.

It will be internally recovered.

81

Internal error: logical log page ? may be corrupted.

fatal

Found an error on the replication log during archiving.

Check the replication log by using the cubrid applyinfo utility.

98

Cannot create an archive log ? to archive pages from ? to ?.

fatal

Fails to create an archive log file.

Check if there is sufficient space left in the disk partition.

974

An archive log ? to archive pages from ? to ? has been created.

notification

Information on an archive log file

No action is required because this error message is recorded to keep information on newly created archive.

Stop and Restart Error Messages

Error messages that can be found in this stage are as follows:

Error Code

Error Message

Severity

Description

Solution

1037

log writer: log writer is terminated by signal.

error

The copylogdb process has been terminated by a specified signal.

It will be internally recovered.

Replication Log Reflection Process (applylogdb)

The error messages from the replication log reflection process are stored in $CUBRID/log/db-name@local-node-name_applylogdb_db-name_remote-node-name.err. The severity levels of error message found in the replication log reflection process are as follow: fatal, error, and notification. The default level is error. Therefore, to record notification error messages, it is necessary to change the value of error_log_level in the cubrid.conf file. For details, see Error Message-Related Parameters.

Initialization Error Messages

The error messages that can be found in initialization stage of replication log reflection process are as follows:

Error Code

Error Message

Severity

Description

Solution

10

Cannot mount the disk volume ?.

error

An applylogdb that is trying to reflect the same replication log is already running.

Check if there is an applylogdb process that is trying to reflect the same replication log.

1038

log applier: log applier has been started. required LSA: ?|?. last committed LSA: ?|?.

error

It will be started normally after initialization of applylogdb succeeds.

No action is required because this error is recorded to display the start information of the replication log reflection process.

Log Analysis Error Messages

The replication log reflection process reads, analyzes, and reflects the replications logs that have been copied by the replication log copy process. The error message that can be found in this stage are as follows:

Error Code

Error Message

Severity

Description

Solution

13

An I/O error occurred while reading page ? in volume ?.

error

Fails to read a log page to be reflected.

Check the replication log by using the cubrid applyinfo utility.

17

Internal error: Trying to read page ? of the volume ? which has been already released.

fatal

Trying to read a log page that does not exist in the replication log.

Check the replication log by using the cubrid applyinfo utility.

81

Internal error: logical log page ? may be corrupted.

fatal

There is an inconsistency between an old log under replication reflection and the current log, or there is a replication log record error.

Check the replication log by using the cubrid applyinfo utility.

82

Cannot mount the disk volume/file ?.

error

No replication log file exists.

Check if replication logs exist.
Check the replication log by using the cubrid applyinfo utility.

97

Internal error: unable to find log page ? in log archives.

error

No log page exists in the replication log.

Check the replication log by using the cubrid applyinfo utility.

897

Decompression failure

error

Fails to decompress the log record.

Check the replication log by using the cubrid applyinfo utility.

1028

log applier: Unexpected EOF log record exists in the Archive log. LSA: ?|?.

error

Incorrect log record exists in the archive log.

Check the replication log by using the cubrid applyinfo utility.

1029

log applier: Incorrect log page/offset. page HDR: ?|?, final: ?|?, append LSA: ?|?, EOF LSA: ?|?, ha file status: ?, is end-of-log: ?.

error

Incorrect log record exists.

Check the replication log by using the cubrid applyinfo utility.

1030

log applier: Incorrect log record. LSA: ?|?, forw LSA: ?|?, backw LSA: ?|?, Trid: ?, prev tran LSA: ?|?, type: ?.

error

Log record header error

Check the replication log by using the cubrid applyinfo utility.

Replication Log Reflection Error Messages

The replication log reflection process reads, analyzes, and reflects the replication logs that have been copied by the replication log copy process. Error messages that can be found in this stage are as follows:

Error Code

Error Message

Severity

Description

Solution

72

The transaction (index ?, ?@?|?) has been cancelled by system.

error

Fails to reflect replication due to deadlock, etc.

It will be recovered internally.

111

Your transaction has been cancelled due to server failure or a mode change.

error

Fails to reflect replication because the database server process in which replication is supposed to be reflected has been terminated or its mode has been changed.

It will be recovered internally.

191

Cannot connect to server ? on ?.

error

The connection to the database server process in which replication is supposed to be reflected has been terminated.

It will be recovered internally.

195

Server communication error: ?.

error

The connection to the database server process in which replication is supposed to be reflected has been terminated.

It will be recovered internally.

224

The database has not been resumed.

error

The connection to the database server process in which replication is supposed to be reflected has been terminated.

It will be recovered internally.

1027

log applier: Failed to change the reflection status from ? to ?.

error

Fails to change of replication reflection.

It will be recovered internally.

1031

log applier: Failed to reflect the Schema replication log. class: ?, schema: ?, internal error: ?.

error

Fails to reflect SCHEMA replication.

Check the consistency of the replication. If it is inconsistent, reconfigure the HA replication.

1032

log applier: Failed to reflect the Insert replication log. class: ?, key: ?, internal error: ?.

error

Fails to reflect INSERT replication.

Check the consistency of the replication. If it is inconsistent, reconfigure the HA replication.

1033

log applier: Failed to reflect the Update replication log. class: ?, key: ?, internal error: ?.

error

Fails to reflect UPDATE replication.

Check the consistency of the replication. If it is inconsistent, reconfigure the HA replication.

1034

log applier: Failed to reflect the Delete replication log. class: ?, key: ?, internal error: ?.

error

Fails to reflect DELETE replication.

Check the consistency of the replication. If it is inconsistent, reconfigure the HA replication.

1040

HA generic: ?.

notification

Changes the last record of the archive log or replication reflection status.

No action is required because this error message is recorded to provide general information.

Stop and Restart Error Messages

The error messages that can be found in this stage are as follows:

Error Code

Error Message

Severity

Description

Solution

1035

log applier: The memory size (? MB) of the log applier is larger than the maximum memory size (? MB), or is doubled the starting memory size (? MB) or more. required LSA: ?|?. last committed LSA: ?|?.

error

The replication log reflection process has been restarted due to reaching the maximum memory size limit.

It will be recovered internally.

1036

log applier: log applier is terminated by signal.

error

The replication log reflection process has been terminated by a specified signal.

It will be recovered internally.