The error messages from the replication log copy process are stored in $CUBRID/log/db-name@remote-node-name_copylogdb.err. The severity of error messages found in the replication log copy process are 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.
The error messages that may be stored in the initialization stage of replication log copy process are as follows:
Error Code |
Error Message |
Severity |
Description |
Solution |
---|---|---|---|---|
10 |
Unable to mount disk volume ?. |
error |
Opening a replication log file has failed. |
Check if there is a replication log. For the location of replicated logs, see Default Environment Configuration. |
78 |
Internal error: an I/O error occurred while reading logical log page ? (physical page ?) of ?. |
fatal |
Reading a replication log has failed. |
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. |
1039 |
log writer: log writer started. mode: ? |
error |
The replication log copy process has been successfully initialized and started. |
No action is required, because this error message has been stored to display the starting information of the replication log copy process. |
The replication log copy process requests a replication log from the connected database server, and receives the corresponding replication log. The error messages that may occur during this process are as follows:
Error Code |
Error Message |
Severity |
Description |
Solution |
---|---|---|---|---|
89 |
Log ? does not belong to the given database. |
error |
The previously replicated log and the log to be replicated do not match. |
Check the 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 |
Error receiving data from server. |
error |
Incorrect information has been received from the database server to which the replication log copy process is connected. |
This is recovered internally. |
199 |
Server no longer responding. |
error |
The connection to the database server has been terminated. |
This is recovered internally. |
The replication log copy process copies the replication log (ha_copy_base) that was received from the connected database server process to the location specified in cubrid_ha.conf. The error messages that may occur during this process are as follows:
Error Code |
Error Message |
Severity |
Description |
Solution |
---|---|---|---|---|
10 |
Unable to mount disk volume ?. |
error |
Opening a replication log file has failed. |
Check if the replication log exists. |
79 |
Internal error: an I/O error occurred while writing logical log page ? (physical page ?) of ?. |
fatal |
Writing a replication log has failed. |
This is recovered internally. |
80 |
Insufficient space in operating system device when writing logical log page ? (physical page ?) of ?. Could not write more than ? bytes. |
fatal |
Writing a replication log has failed due to insufficient file system space. |
Check if there is sufficient space left in the disk partition. |
The replication log copy process periodically archives the replication log that has been received from the connected database server process. The error messages that may occur during this process 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 |
Reading a replication log has failed 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 |
Writing the archive log has failed. |
This is recovered internally. |
81 |
Internal error: logical log page ? may be corrupted. |
fatal |
A replication log error has been found during archiving. |
Check the replication log by using the cubrid applyinfo utility. |
98 |
Unable to create archive log ? to archive pages from ? to ?. |
fatal |
Creating the archive log file has failed. |
Check if there is sufficient space left in the disk partition. |
974 |
Archive log ? is created to archive pages from ? to ?. |
notification |
Archive log file information |
No action is required, because this error message is recorded for the log information of the newly created archive. |
The error messages that may occur at the beginning and the end of the replication log copy process are as follows:
Error Code |
Error Message |
Severity |
Description |
Solution |
---|---|---|---|---|
1037 |
log writer: log writer shut itself down by signal. |
error |
The copylogdb process has been terminated by a specific signal. |
This is recovered internally. |