Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

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

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 more information, 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 Name

Severity

Description

Solution

10

ER_IO_MOUNT_FAIL

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

ER_HA_LA_STARTED

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 Name

Severity

Description

Solution

13

ER_IO_READ

error

Reading the log page to be reflected has failed.

Check the replication log by using the cubrid applyinfo utility.

17

ER_PB_BAD_PAGEID

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

ER_LOG_PAGE_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

ER_LOG_MOUNT_FAIL

error

No replication log file

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

97

ER_LOG_NOTIN_ARCHIVE

error

The log page does not exist in the replication log.

Check the replication log by using the cubrid applyinfo utility.

897

ER_IO_LZO_DECOMPRESS_FAIL

error

Decompressing the log record has failed.

Check the replication log by using the cubrid applyinfo utility.

1028

ER_HA_LA_UNEXPECTED_EOF_IN_ARCHIVE_LOG

error

An incorrect log record exists in the archive log.

Check the replication log by using the cubrid applyinfo utility.

1029

ER_HA_LA_INVALID_REPL_LOG_PAGEID_OFFSET

error

An incorrect log record has been included.

Check the replication log by using the cubrid applyinfo utility.

1030

ER_HA_LA_INVALID_REPL_LOG_RECORD

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 Name

Severity

Description

Solution

72

ER_LK_UNILATERALLY_ABORTED

error

Replication reflection has been failed due to deadlock, etc.

This is recovered internally.

111

ER_TM_SERVER_DOWN_UNILATERALLY_ABORTED

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

ER_NET_CANT_CONNECT_SERVER

error

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

This is recovered internally.

195

ER_NET_SERVER_COMM_ERROR

error

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

This is recovered internally.

224

ER_OBJ_NO_CONNECT

error

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

This is recovered internally.

1027

ER_HA_LA_FAILED_TO_CHANGE_STATE

error

The status change of replication reflection has been failed.

This is recovered internally.

1031

ER_HA_LA_FAILED_TO_APPLY_SCHEMA

error

SCHEMA replication reflection has been failed.

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

1032

ER_HA_LA_FAILED_TO_APPLY_INSERT

error

INSERT replication reflection has been failed.

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

1033

ER_HA_LA_FAILED_TO_APPLY_UPDATE

error

UPDATE replication reflection has been failed.

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

1034

ER_HA_LA_FAILED_TO_APPLY_DELETE

error

DELETE replication reflection has been failed.

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

1040

ER_HA_GENERIC_ERROR

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 Name

Severity

Description

Solution

1035

ER_HA_LA_EXCEED_MAX_MEM_SIZE

error

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

This is recovered internally.

1036

ER_HA_LA_STOPPED_BY_SIGNAL

error

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

This is recovered internally.