Replication Log Reflection Process

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 of error messages found in the replication log reflection process can be as follows: fatal, error, and notification. The default severity is error. Therefore, to store notification error messages, it is necessary to change the value of error_log_level in cubrid.conf. For details, see Error Message-Related Parameters.

Initialization Error Message

The error messages that may be stored in the initialization stage of the replication log reflection process are as follows:

Error Code

Error Message

Severity

Description

Solution

10

Unable to mount disk volume ?

error

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

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

1038

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

error

Starts normally once the initialization of applylogdb is successful.

No action is required, because this error message has been stored to display the starting information of the replication log reflection process.

Log Analysis Error Message

The replication log reflection process reads, analyzes, and reflects the replication logs that have been copied by the replication log copy process. The error messages that may occur during a replication log analysis are as follows:

Error Code

Error Message

Severity

Description

Solution

13

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

error

Reading the log page to be reflected has failed.

Check the replication log by using the cubrid applyinfo utility.

17

Internal error: fetching deallocated pageid ? of volume ?.

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

Unable to mount log disk volume/file ?.

error

No replication log file

Check if there is a replication log.
Check the replication log by using the cubrid applyinfo utility.

97

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

error

The log page does not exist in the replication log.

Check the replication log by using the cubrid applyinfo utility.

897

Decompression failed.

error

Decompressing the log record has failed.

Check the replication log by using the cubrid applyinfo utility.

1028

log applier: unexpected EOF record in archive log. LSA: ?|?.

error

An incorrect log record exists in the archive log.

Check the replication log by using the cubrid applyinfo utility.

1029

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

error

An incorrect log record has been included.

Check the replication log by using the cubrid applyinfo utility.

1030

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

error

A log record header error

Check the replication log by using the cubrid applyinfo utility.

Replication Log Reflection Error Message

The replication log reflection process reads, analyzes, and reflects the replication logs that have been copied by the replication log copy process. The error messages that may occur when reflecting a replication log analysis are as follows:

Error Code

Error Message

Severity

Description

Solution

72

Your transaction (index ?, ?@?|?) has been unilaterally aborted by the system.

error

Replication reflection has been failed due to deadlock, etc.

This is recovered internally.

111

Your transaction has been aborted by the system due to server failure or mode change.

error

Replication reflection is failed because the database server process for replication reflection has been terminated, or its mode has been changed.

This is recovered internally.

191

Cannot connect to server ? on ?.

error

The connection to the database server process for replication reflection has been terminated.

This is recovered internally.

195

Server communications error: ?.

error

The connection to the database server process for replication reflection has been terminated.

This is recovered internally.

224

A database has not been restarted.

error

The connection to the database server process for replication reflection has been terminated.

This is recovered internally.

1027

log applier: failed to change apply state from ? to ?.

error

The status change of replication reflection has been failed.

This is recovered internally.

1031

log applier: failed to apply schema replication log. class: ?, schema: ?, internal error: ?.

error

SCHEMA replication reflection has been failed.

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

1032

log applier: failed to apply insert replication log. class: ?, key: ?, internal error: ?.

error

INSERT replication reflection has been failed.

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

1033

log applier: failed to apply update replication log. class: ?, key: ?, internal error: ?.

error

UPDATE replication reflection has been failed.

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

1034

log applier: failed to apply delete replication log. class: ?, key: ?, internal error: ?.

error

DELETE replication reflection has been failed.

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

1040

HA generic: ?.

notification

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

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

Stop and Restart Error Message

The error messages that may occur at the beginning and the end of the replication log reflection process are as follows:

Error Code

Error Message

Severity

Description

Solution

1035

log applier: mem size(? MB) of log applier is greater than max mem size (? MB) or has been grow more than 2 times (? MB). required LSA: ?|? last committed LSA: ?|?.

error

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

This is recovered internally.

1036

log applier: log applier shut itself down by signal.

error

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

This is recovered internally.