4. RP Error Code#
FATAL#
0x60002 ( 393218) rpERR_FATAL_RP_MEMORY_ALLOCATION Unable to allocate memory
Cause: The system failed to allocate sufficient memory.
Action: Verify that sufficient memory is available.
0x60006 ( 393222) rpERR_FATAL_RP_SENDER_INVALID_OPTION Internal error
Cause: An invalid replication option was set for the replication Sender.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x60071 ( 393329) rpERR_FATAL_ThrCondInit Failed to invoke the cond_init() system function
Cause: The system failed to invoke the cond_init() function.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x600A2 ( 393378) rpERR_FATAL_ThrCondBroadcast Failed to invoke a system function, cond_broadcast(), errno is (<0%d>).
Cause: The system failed to invoke the cond_broadcast() function.
Action: Please send a bug report to the vendor.
0x600B4 ( 393396) rpERR_FATAL_ThrMutexInit Unable to initialize a mutex.
Cause: The system failed to initialize a mutex.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x600B5 ( 393397) rpERR_FATAL_ThrMutexDestroy Failed to invoke the mutex_destroy() system function
Cause: The system failed to remove a mutex.
Action: Please send a bug report to the vendor.
0x60125 ( 393509) rpERR_FATAL_RPD_REPL_META_CRASH A replication meta table crashed.
Cause: A replication meta table crashed.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x60167 ( 393575) rpERR_FATAL_ThrLatchInit Unable to initialize a latch.
Cause: The system failed to initialize a latch.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
ABORT#
0x61003 ( 397315) rpERR_ABORT_RP_READ_SOCKET Unable to read from a socket
Cause: The connection to replication has been disconnected or failed to receive data within the specified time.
Action: Increase the replication-related timeout or check the local and remote altibase_rp.log file to find out why the connection is broken.
0x61004 ( 397316) rpERR_ABORT_RP_WRITE_SOCKET Unable to write to a socket
Cause: Network error
Action: Check the network.
0x61008 ( 397320) rpERR_ABORT_RP_META_NO_SUCH_DATA Unable to find meta information.
Cause: Failed to find information from the replication metadata either because the database crashed or an error occurred.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61009 ( 397321) rpERR_ABORT_RP_JOIN_THREAD Unable to join the sender thread
Cause: The system failed to join the sender thread.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6100A ( 397322) rpERR_ABORT_RP_ALREADY_STARTED The sender has already been started.
Cause: The sender has already been started.
Action: Check whether the sender has already been started.
0x6100B ( 397323) rpERR_ABORT_RP_MAXIMUM_THREADS_REACHED Out of replication threads ( replication thread count > <0%d>)
Cause: The number of replications currently running on the system has exceeded the maximum limit.
Action: Check the maximum number of replication threads.
0x6100C ( 397324) rpERR_ABORT_RP_RECEIVER_NOT_FOUND The receiver does not exist.
Cause: Internal server error
Action: Please send a bug report to the vendor.
0x6100D ( 397325) rpERR_ABORT_RP_SENDER_HANDSHAKE [Sender] Failed to handshake with the peer server (<0%s>)
Cause: Network or server error. The replication definition might contain an error.
Action: Check the network. Verify that the replication definition is the same on the corresponding server.
0x6100E ( 397326) rpERR_ABORT_RP_PEER_WAKEUP Failed to wake up peer sender
Cause: When the server started, it attempted to connect to the remote database, but failed.
Action: Start the remote database.
0x61010 ( 397328) rpERR_ABORT_RP_SENDER_START [Sender] Failed to start the sender thread
Cause: The communication or handshaking failed.
Action: Check the network, the server, and the replication definition.
0x61011 ( 397329) rpERR_ABORT_RP_SENDER_SYNCSTART [Sender] Failed to start sync
Cause: The communication or handshaking failed.
Action: Check the network, the server, and the replication definition.
0x61012 ( 397330) rpERR_ABORT_RP_SENDER_CONNECT_PEER [Sender] Failed to connect to the peer server
Cause:
- Peer server is not running.
- IP address or Port number is invalid.
- Network is not working.
Action:
- Confirm peer server is running.
- Verify both IP address and port number are correctly entered.
- Ensure that network is working normally.
0x61013 ( 397331) rpERR_ABORT_RP_SENDER_DO_REPLICATION [Sender] Replication failed
Cause: The replication Sender failed during replication.
Action: Check the error number from the altibase_rp.log file and take appropriate action.
0x61014 ( 397332) rpERR_ABORT_RP_SENDER_MAKE_XLOG_IN_LOGFILE [Sender] Failed to make XLOG in a log file at SN[<0%lu>]
Cause: The replication Sender failed to convert the log of the corresponding SN in the log file to an XLog.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61015 ( 397333) rpERR_ABORT_RP_SENDER_CHECK_LOG [Sender] Failed to check a physical log at SN[<0%lu>]
Cause: The replication Sender cannot read the log of the corresponding SN.
Action: The replication Sender that sends logs to the Altibase Log Analyzer must specify the SN to another position.
0x6101D ( 397341) rpERR_ABORT_RP_SENDER_SYNC_TABLE [Sender] Failed to sync a table
Cause: The replication Sender failed to synchronize the table.
Action: Check the network status or the status of the corresponding server, and take appropriate action.
0x61021 ( 397345) rpERR_ABORT_RP_SENDER_ADD_INSERT_SYNC_XLOG [Sender] Failed to add the insert SYNC XLOG
Cause: The replication Sender failed to send data to the corresponding server.
Action: Please send a bug report to the vendor.
0x61022 ( 397346) rpERR_ABORT_RP_SENDER_SLEEP [Sender] Sender Sleep : <0%d> seconds
Cause: The sender is in sleep.
Action: This message is for information only.
0x61023 ( 397347) rpERR_ABORT_RP_REPLICATION_DISABLED Replication is disabled
Cause: The replication feature of Altibase could not be used. Replication was not initialized on startup because the port is not set correctly.
Action: Set the port correctly.
0x61025 ( 397349) rpERR_ABORT_RP_REPLICATION_DENY Replication denied (<0%s>)
Cause: Replication access was denied because the corresponding server has not yet started.
Action: Restart replication after a brief delay. If replication has already started, wait for the corresponding server to start.
0x61026 ( 397350) rpERR_ABORT_RP_REPLICATION_NOK Unable to process the replication (<0%s>)
Cause: Replication was not possible because some conditions were not satisfied.
Action: Try again later.
0x61027 ( 397351) rpERR_ABORT_RP_REPLICATION_NOT_STARTED Replication did not start.
Cause: The replication did not start.
Action: Verify that replication was started.
0x61028 ( 397352) rpERR_ABORT_RP_REPLICATION_SELF_REPLICATION A case of self-replication has been detected. (Peer=<0%s>:<1%u>)
Cause: The IP address and port for replication are the same as those of the local server.
Action: Check the IP address and port for replication.
0x61029 ( 397353) rpERR_ABORT_RP_ENTRY_EXIST [Sender] Entry already exists in insert()
Cause: The same transaction table slot is being used.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6102A ( 397354) rpERR_ABORT_BIND Bind failure
Cause: Network error
Action: Check the network.
0x6102C ( 397356) rpERR_ABORT_START_RECEIVER [Receiver] Failed to start the receiver
Cause: The replication Receiver has failed to start either because the versions are different or there is a network error.
Action: Check the replication version between the two nodes, or check the network.
0x6102D ( 397357) rpERR_ABORT_LISTEN [Receiver] Failed to listen to a replication socket (Port No:<0%d>)
Cause: REPLICATION_PORT_NO port is occupied by other application or not yet released.
Action: Use other port number or terminate the application using the REPLICATION_PORT_NO port.
0x61030 ( 397360) rpERR_ABORT_META_BUILD [Receiver] Failed to build meta information
Cause: The system failed to create metadata.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61031 ( 397361) rpERR_ABORT_META_MISMATCH [Receiver] Meta information does not match
Cause: The receiver's meta information does not match the sender's meta information.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61032 ( 397362) rpERR_ABORT_SEND_ACK [Receiver] Failed to send ACK
Cause: Failed to send a handshake ACK to the replication Sender.
Action: Check the network.
0x61033 ( 397363) rpERR_ABORT_TX_BEGIN [Receiver] Transaction begin failure
Cause: The replication Receiver failed to start an internal transaction.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61034 ( 397364) rpERR_ABORT_TX_COMMIT [Receiver] Transaction commit failure
Cause: The replication Receiver failed to commit an internal transaction.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61035 ( 397365) rpERR_ABORT_UPDATE_CONFLICT [Receiver] An update conflict occurred.
Cause: An update conflict occurred while the replication was in process.
Action: You may safely ignore this message if you have restarted replication.
0x61037 ( 397367) rpERR_ABORT_NOT_EXIST_TABLE_DEL [Receiver] err_not_exist_table in deleteXLog()
Cause: The table does not exist.
Action: Check the altibase_rp.log file.
0x61038 ( 397368) rpERR_ABORT_NOT_EXIST_TABLE_INS [Receiver] err_not_exist_table in insertXLog()
Cause: The table does not exist.
Action: Check the altibase_rp.log file.
0x61039 ( 397369) rpERR_ABORT_NOT_EXIST_TABLE_UPT [Receiver] err_not_exist_table in updateXLog()
Cause: The table does not exist.
Action: Check the altibase_rp.log file.
0x61042 ( 397378) rpERR_ABORT_TX_COMMIT2 [Receiver] err_tx in commit()
Cause: The replication Receiver failed to commit a replicated transaction.
Action: Check the error code from the altibase_rp.log file and take appropriate action. If the maximum number of rows has been set for creating tables, commit can fail.
0x61043 ( 397379) rpERR_ABORT_TX_ERROR [Receiver] err_tx in err_tx()
Cause: The replication Receiver failed to roll back a committed transaction.
Action: Check the error code from the altibase_rp.log file and take appropriate action.
0x61046 ( 397382) rpERR_ABORT_PROTOCOL_RUN [Receiver] protocol error in run()
Cause: The replication Receiver received an unexpected protocol from the replication Sender.
Action: Check the replication protocol version between the two nodes. If the versions are different, change it to the same version. If the versions are the same, check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61047 ( 397383) rpERR_ABORT_ERROR_RECVXLOG2 [Receiver] <0%s> receiver has error in recvXLog()
Cause: Unable to read data from the network connection.
Action: Check the network connection.
0x61048 ( 397384) rpERR_ABORT_RECVXLOG_RUN [Receiver] <0%s> receiver has recvXLog error in run()
Cause: Unable to read data from the network connection.
Action: Check the network connection.
0x6104B ( 397387) rpERR_ABORT_END_THREAD [Receiver] <0%s> receiver is ended (by thr_exit)
Cause: Unable to read data from the network connection.
Action: Check the network connection.
0x6104D ( 397389) rpERR_ABORT_CLOSE_LOG_FILE [Sender] Failed to close log file logfile<0%d>.log
Cause: Internal server error
Action: Please send a bug report to the vendor.
0x6104E ( 397390) rpERR_ABORT_GET_ACK [Sender] Failed to get ACK
Cause: Internal server error
Action: Please send a bug report to the vendor.
0x6104F ( 397391) rpERR_ABORT_RP_SENDER_INIT [Sender] Failed to initialize
Cause: The replication Sender failed to initialize.
Action: Restart the replication Sender. If the replication Sender repeatedly fails to start, check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61050 ( 397392) rpERR_ABORT_OPEN_LOG_FILE [Sender] Failed to open log file logfile<0%d>.log
Cause: Internal server error
Action: Please send a bug report to the vendor.
0x61053 ( 397395) rpERR_ABORT_INVALID_PARAM [Sender] Invalid parameter
Cause: Internal server error
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61055 ( 397397) rpERR_ABORT_MEMORY_ALLOC Memory allocation failure [Function=<0%s>, Variable=<1%s>]
Cause: The system failed to allocate memory.
Action: Check the status of the memory available for allocation and retry.
0x61056 ( 397398) rpERR_ABORT_ALREADY_FINAL [Receiver] to be ended (already finalized by manager)
Cause: The replication Receiver terminated abnormally. This error mainly occurs due to a network error or a rollback of a long-running transaction.
Action: Check the error number from the altibase_rp.log file and take appropriate action. If the replication Receiver has rolled back a long-running transaction, increase the value of replication_receive_timeout on both nodes.
0x61057 ( 397399) rpERR_ABORT_PROTOCOL_ERROR [Receiver] rp_x_b protocol error in run()
Cause: The receiver thread tried to start a transaction that has already been started.
Action: N/A
0x6105A ( 397402) rpERR_ABORT_BEGIN_ERROR_IN_RUN [Receiver] begin error in run()
Cause: The replication Receiver failed to add a new transaction.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6105B ( 397403) rpERR_ABORT_ABORT_ERROR_IN_RUN [Receiver] abort error in run()
Cause: The replication Receiver failed to roll back a transaction.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6105C ( 397404) rpERR_ABORT_COMMIT_ERROR_IN_RUN [Receiver] commit error in run()
Cause: The replication Receiver failed to commit a replicated transaction.
Action: Check the error number from the altibase_rp.log file and take appropriate action.
0x61069 ( 397417) rpERR_ABORT_RP_INTERNAL_ARG Internal server error in replication module (<0%s>).
Cause: Program eror.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6106B ( 397419) rpERR_ABORT_RP_SENDER_SEND_ERROR [Sender] Failed to send XLog to peer network
Cause: The peer network has a problem.
Action: The system will retry automatically.
0x6106C ( 397420) rpERR_ABORT_RP_SENDER_RECV_ERROR [Sender] Failed to receive XLog from peer network
Cause: The peer network has a problem or is offline.
Action: The system will retry automatically.
0x6106D ( 397421) rpERR_ABORT_RP_SET_SAVEPOINT_ERROR_IN_RUN [Receiver] smiTrans set(savepoint) error in run()
Cause: The replication Receiver failed to create a savepoint.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6106E ( 397422) rpERR_ABORT_RP_ABORT_SAVEPOINT_ERROR_IN_RUN [Receiver] smiTrans abort(savepoint) error in run()
Cause: The replication Receiver failed to roll back to a savepoint.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6106F ( 397423) rpERR_ABORT_RP_NOT_DROP_ONE_TABLE You cannot drop only one replicated table.
Cause: You cannot drop a table when only one replicated table is remaining.
Action: Drop the replication object, or insert another table and drop the table.
0x61075 ( 397429) rpERR_ABORT_TIMEOUT_EXCEED Timeout exceed.
Cause: A timeout occurred while the replication Sender and Receiver were communicating.
Action: : Set a larger value for the REPLICATION_RECEIVE_TIMEOUT property.
0x61076 ( 397430) rpERR_ABORT_INVALID_XSN [Sender] Invalid XSN[<0%ld>] > Current[<1%ld>] occurred
Cause: The restart SN value of the replication Sender is invalid.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61077 ( 397431) rpERR_ABORT_RP_SENDER_UPDATE_XSN [Sender] Failed to update XSN
Cause: The replication Sender failed to update the restart SN value.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61078 ( 397432) rpERR_ABORT_RP_TRANSACTION_TABLE_IN_INSERT [Receiver] replication transaction table error during insert() operation
Cause: The replication Receiver failed to insert data into the transaction table.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61079 ( 397433) rpERR_ABORT_RP_FIND_IN_TRANSTABLE_REMOVE [Receiver] find error in transaction table during remove() operation
Cause: Internal server error
Action: Please send a bug report to the vendor.
0x6107A ( 397434) rpERR_ABORT_NOT_HAVE_HOST Invalid Host [<0%s>, <1%d>]
Cause: Host Information (IP, Port) doesn't belong to this replication.
Action: Attempt this operation again using the correct host information.
0x6107B ( 397435) rpERR_ABORT_COLUMN_COUNT_MISMATCH <0%s> column count mismatch of <1%s> table. ( column count of received XLog is <2%d> and column count of meta is <3%d>)
Cause: The sender and receiver table column counts do not match.
Action: Reorganize replicated tables and recreate the replication after checking both the sender and receiver table meta information.
0x6107C ( 397436) rpERR_ABORT_COLUMN_ID_MISMATCH <0%s> <1%d>'th column ID mismatch of <2%s> table. ( column ID of received XLog is <3%d> and column ID of meta is <4%d>)
Cause: The sender and receiver table column IDs do not match.
Action: Reorganize replicated tables and recreate the replication after checking both the sender and receiver table meta information.
0x61082 ( 397442) rpERR_ABORT_INDEX_COUNT_IS_NOT_AVAILABLE [Meta] Index Count isn't available [<0%u>]
Cause: Index count mismatch
Action: Check the number of table indexes.
0x61083 ( 397443) rpERR_ABORT_ADD_SESSION [Network] Add Session operation failed
Cause: cmiAddSession() returned an error
Action: Please send a bug report to the vendor.
0x61084 ( 397444) rpERR_ABORT_SET_LINK [Network] Set link to session failed
Cause: The session already has another link.
Action: Please send a bug report to the vendor.
0x61085 ( 397445) rpERR_ABORT_FREE_LINK [Network] Free link operation failed
Cause: Failed to free network memory resources.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61086 ( 397446) rpERR_ABORT_FREE_DISPATCHER [Network] Free dispatcher operation failed
Cause: Failed to free network dispatcher resources.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61087 ( 397447) rpERR_ABORT_SHUTDOWN_LINK [Network] Shutdown link operation failed
Cause: Failed to shut down the network because the corresponding party has terminated first.
Action: You may safely ignore this message.
0x61088 ( 397448) rpERR_ABORT_CLOSE_LINK [Network] Close link operation failed
Cause: Failed to close a network socket.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61089 ( 397449) rpERR_ABORT_ALLOC_LINK [Network] Alloc link operation failed
Cause: Failed to allocate network resources.
Action: Check the state of system resources. If they are insufficient, take appropriate action.
0x6108A ( 397450) rpERR_ABORT_CONNECT_FAIL [Network] Connection failed
Cause: The system failed to invoke connect() function.
Action: Verify that the corresponding server is alive, or check the network.
0x6108B ( 397451) rpERR_ABORT_SEND_FAIL [Network] Send operation failed
Cause: The replication Sender failed to send data to the corresponding server.
Action: Verify that the corresponding server is alive, or check the network status.
0x6108C ( 397452) rpERR_ABORT_OPEN_LOB_CURSOR [SmExec] A failure occurred while opening LOB Cursor
Cause: The replication Receiver tried to open a LOB cursor to apply LOB data, but failed.
Action: Check whether the LOB data of the replication target table is the same and take appropriate action.
0x6108D ( 397453) rpERR_ABORT_CLOSE_LOB_CURSOR [SmExec] A failure occurred while closing the LOB Cursor
Cause: The replication Receiver tried to close a LOB cursor to finish applying LOB data, but failed.
Action: Check whether the LOB data of the replication target table is the same and take appropriate action.
0x6108E ( 397454) rpERR_ABORT_LOB_PREPARE_WRITE [SmExec] A failure occurred while preparing for LOB writing
Cause: The replication Receiver tried to prepare to write the LOB cursor to finish applying LOB data, but failed.
Action: Check whether the LOB data of the replication target table is the same and take appropriate action.
0x6108F ( 397455) rpERR_ABORT_LOB_FINISH_WRITE [SmExec] A failure occurred while finishing LOB writing
Cause: The replication Receiver tried to finish writing to the LOB cursor to finish applying LOB data, but failed.
Action: Check whether the LOB data of the replication target table is the same and take appropriate action.
0x61090 ( 397456) rpERR_ABORT_LOB_PARTIAL_WRITE [SmExec] A failure occurred while writing the LOB piece
Cause: The replication Receiver tried to partially write to the LOB cursor to finish applying LOB data, but failed.
Action: Check whether the LOB data of the replication target table is the same and take appropriate action.
0x61091 ( 397457) rpERR_ABORT_LOB_GET_LENGTH [SmExec] A failure occurred while getting the LOB piece length
Cause: The replication Receiver tried to get the length of the LOB cursor to finish applying LOB data, but failed.
Action: Check whether the LOB data of the replication target table is the same and take appropriate action.
0x61092 ( 397458) rpERR_ABORT_LOB_READ [SmExec] A failure occurred while reading an LOB piece
Cause: The replication Receiver tried to read the LOB cursor to finish applying LOB data, but failed.
Action: Check whether the LOB data of the replication target table is the same and take appropriate action.
0x61093 ( 397459) rpERR_ABORT_NOT_FOUND_LOCATOR [SmExec] Locator [<0%lu>] not found
Cause:A LOB locator was not found.
Action: Please send a bug report to the vendor.
0x61094 ( 397460) rpERR_ABORT_RP_SENDER_NOT_FOUND_TABLE The given table isn't found in the meta.
Cause: Unable to find the table in the meta.
Action: Check the altibase_rp.log file and replication definition.
0x61095 ( 397461) rpERR_ABORT_RP_RECEIVER_NOT_FOUND_TABLE The given table isn't found in the meta.
Cause: Unable to find the table in the meta.
Action: Check the altibase_rp.log file and replication definition.
0x61096 ( 397462) rpERR_ABORT_RP_RECEIVER_NOT_FOUND_COLUMN The given column isn't found in the meta information.
Cause: Unable to find the column in the meta information.
Action: Check the altibase_rp.log file and replication definition.
0x61097 ( 397463) rpERR_ABORT_GET_MODULE The module couldn't be found on the server using the module ID.
Cause: Unable to find the module pointer on the server.
Action: Verify the altibase_rp.log file and replication definition.
0x61098 ( 397464) rpERR_ABORT_SENDER_INVALID_XLOG_TYPE [Sender] Invalid XLog type [<0%u>] in sender analysis
Cause: The XSN read and created by the replication Sender is invalid.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61099 ( 397465) rpERR_ABORT_RECEIVER_INVALID_XLOG_TYPE [Receiver] Invalid XLog type [<0%u>] in receiver analysis
Cause: The replication Receiver received an invalid XLog.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6109A ( 397466) rpERR_ABORT_ITEM_NOT_EXIST [Meta] Replication meta item doesn't exist [Replication Name:<0%s>]
Cause: The replication metadata item does not exist due to a database error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6109C ( 397468) rpERR_ABORT_CONVERT_ENDIAN Endian conversion operation failed
Cause: A server with different Endians failed to convert the Endians during replication.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6109E ( 397470) rpERR_ABORT_NOT_EXIST_TABLE [Receiver] The specified table doesn't exist.
Cause: The table does not exist.
Action: Check the altibase_rp.log file.
0x6109F ( 397471) rpERR_ABORT_RP_ALREADY_STARTED_RECEIVER The receiver has already been started.
Cause: The receiver has already been started.
Action: Check whether the receiver has already been started.
0x610A0 ( 397472) rpERR_ABORT_GIVEUP_SENDER_STOP [Sender] Stopping <0%s> sender thread (sender read = SN[<1%ld>], current = SN[<2%ld>], distance from checkpoint = <3%ld>)
Cause: The system tried to restart the sender thread with the current log file as specified by the REPLICATION_MAX_LOGFILE property.
Action: Check the status of the replication object, then synchronize the replication data and then restart replication.
0x610A1 ( 397473) rpERR_ABORT_GIVEUP_SENDER_RESET [Sender] Resetting <0%s> sender XSN (sender XSN = SN[<1%ld>], current = SN[<2%ld>], distance from checkpoint = <3%ld>)
Cause: The system tried to change the current log file as specified by the REPLICATION_MAX_LOGFILE property.
Action: Check the status of the replication object, then synchronize the replication data and then restart replication.
0x610A3 ( 397475) rpERR_ABORT_ROLE_NOT_SUPPORT_RECEIVER [Receiver] The receiver is not supported in this role.
Cause: The replication receiver is not supported in this role.
Action: Check the role of the replication.
0x610A4 ( 397476) rpERR_ABORT_RECEIVER_UNEXPECTED_PROTOCOL [Receiver] Unexpected replication protocol [<0%u>]
Cause: The replication Receiver received an undefined protocol for replication.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610A5 ( 397477) rpERR_ABORT_RECEIVER_TX_NOT_BEGIN [Receiver] Transaction has not begun. Received XLog [Type:<0%d>, TID:<1%u>, SN:<2%ld>]
Cause: The replication Receiver received the XLog of a transaction that has not yet started.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610A6 ( 397478) rpERR_ABORT_LOGBUFFER_ALLOC Replication log buffer memory allocation failed.
Cause: The system failed to allocate memory.
Action: Verify that sufficient memory is available.
0x610A7 ( 397479) rpERR_ABORT_RP_SENDER_UPDATE_INVALID_MAX_SN [Sender] Failed to update INVALID MAX SN
Cause: Failed to update replication metadata (INVALID MAX SN) due to a database error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610A8 ( 397480) rpERR_ABORT_RECOVERY_INFO_EXIST Recovery information already exists.
Cause: Adding a table into or deleting a table from the replication is prohibited if the recovery option is enabled.
Action: Disable the recovery option or create another replication and try again.
0x610A9 ( 397481) rpERR_ABORT_RECOVERY_ALREADY_STARTED The recovery sender has already been started.
Cause: The recovery sender has already been started.
Action: Wait for complete recovery or cancel the recovery.
0x610AA ( 397482) rpERR_ABORT_RP_MAXIMUM_RECOVERYITEM_REACHED Irreplicable recovery information
Cause: The amount of available recovery information on the system exceeds the maximum limit.
Action: Retry after
- 1. Increase value of the REPLICATION_MAX_COUNT property. - 2. Remove the replication which enables other RECOVERY option. - 3. Disable RECOVERY option.
0x610AC ( 397484) rpERR_ABORT_GIVEUP_RECOVERY_DESTROY [Receiver] Destroy <0%s> recovery information (recovery info min sn = SN[<1%ld>], distance from checkpoint = <2%ld>)
Cause: The number of logs that the replication Receiver stored for replication recovery has exceeded REPLICATION_MAX_LOGFILE. Recovery data and log files necessary for replication recovery have been dropped.
Action: To use the replication recovery option, increase the value of the REPLICATION_MAX_LOGFILE property.
0x610AD ( 397485) rpERR_ABORT_RP_RECOVERY_REQUEST Failed to send <0%s> recovery request
Cause: Failed to request replication recovery either because the corresponding server has not started or there is a network error.
Action: - Replication recovery is impossible if the corresponding server has been terminated. - To disable this option, set REPLICATION_RECOVERY_MAX_TIME to 0, and restart. - If a network error has occurred, increase REPLICATION_RECOVERY_REQUEST_TIMEOUT, and restart replication. - If connection fails, check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610B0 ( 397488) rpERR_ABORT_MISMATCH_OLD_ITEMS_COUNT Old items count mismatch (<0%d>:<1%d>)
Cause: The number of rows selected from SYS_REPL_OLD_ITEMS_ is invalid due to a database error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610B2 ( 397490) rpERR_ABORT_CONDITION_COLUMN_IS_NOT_FOUND Condition column not found.
Cause: The condition column could not be found.
Action: Check the existence of a condition column.
0x610B3 ( 397491) rpERR_ABORT_ART Error generated by Automatic Recovery Test(ART)
Cause: Ignore.
Action: Ignore.
0x610B6 ( 397494) rpERR_ABORT_RECEIVER_NOT_FOUND_TABLE Table not found in the meta [SN=<0%ld>, Table OID=<1%ld>]
Cause: Failed to find the table with the table OID from replication Receiver metadata due to a database error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610B7 ( 397495) rpERR_ABORT_RECEIVER_NOT_FOUND_PK_COLUMN PK Column not found in the meta [SN=<0%ld>, Table OID=<1%ld>, PK Column Seq=<2%d>]
Cause: Failed to find the primary key column from metadata due to a database error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610B8 ( 397496) rpERR_ABORT_RECEIVER_NOT_FOUND_COLUMN Column not found in the meta [SN=<0%ld>, Table OID=<1%ld>, Column ID=<2%d>]
Cause: Failed to find the column from metadata due to a database error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610B9 ( 397497) rpERR_ABORT_RP_NOT_DROP_ONE_HOST You cannot drop only one host.
Cause: Replication cannot be dropped when only one host is remaining.
Action: Drop the replication object, or insert another host and drop the host.
0x610BA ( 397498) rpERR_ABORT_RP_ABORT_PSM_SVP [Receiver] smiTrans abort PSM savepoint error in run()
Cause: The replication receiver failed to abort to the savepoint.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610BB ( 397499) rpERR_ABORT_MISMATCH_OFFLINE_LOG_LFGCOUNT Offline log LFG counts do not match.
Cause: The sender and receiver offline log LFG counts do not match.
Action: Check the LFG counts.
0x610BC ( 397500) rpERR_ABORT_MISMATCH_OFFLINE_LOG_OSVERSION Offline log system OS versions do not match.
Cause: The sender and receiver offline log system OS versions do not match.
Action: Confirm that the operating systems of Active and Standby server are the same or unset OFFLINE option.
0x610BD ( 397501) rpERR_ABORT_MISMATCH_OFFLINE_LOG_SMVERSION Offline log SM versions do not match.
Cause: The sender and receiver offline log SM versions do not match.
Action: Confirm that the database versions of Active and Standby server are the same or unset OFFLINE option.
0x610BE ( 397502) rpERR_ABORT_MISMATCH_OFFLINE_LOG_COMPILEBIT Offline log compile bits do not match.
Cause: The sender and receiver offline log compile bits do not match.
Action: Confirm that the compile bit versions of Active and Standby server are the same or unset OFFLINE option.
0x610BF ( 397503) rpERR_ABORT_SENDER_NOT_FOUND_COLUMN Column not found in the meta.
Cause: Failed to find the column from metadata due to a database error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610C0 ( 397504) rpERR_ABORT_MISMATCH_OFFLINE_LOG_FILESIZE Offline log file size does not match.
Cause: The sender and receiver offline log file sizes do not match.
Action: Check the log file size.
0x610C1 ( 397505) rpERR_ABORT_INVALID_CM_VARIABLE_SIZE Invalid CM variable size [<0%s>]
Cause: Internal communication logic error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610C2 ( 397506) rpERR_ABORT_RP_NOT_FOUND_OFFMETA The meta information for the offline sender cannot be found in memory.
Cause: The remote sender has not been started since the local server was started.
Action: Start the replication in the remote server.
0x610C3 ( 397507) rpERR_ABORT_INVALID_OFFLINE_RESTARTSN [Offline Sender] Failed to get valid XSN
Cause: The replication stopped before XSN update.
Action: In this case, you cannot use the offline sender.
0x610C4 ( 397508) rpERR_ABORT_NOT_EXIST_REPL_ITEM Replication items not found.
Cause:
-
When the ALTER REPLICATION DROP TABLE statement is executed, the table is not in the replication.
-
When the ALTER REPLICATION REP START statement is executed, the table on the sender (Active) side is not in the receiver (standby).
Action: Ensure that the replication table exists on both sides or that the table is included in the replication.
0x610C5 ( 397509) rpERR_ABORT_TX_ALLOC_TIMEOUT [Receiver] Transaction allocation exceeds timeout.
Cause: The transaction allocation failed because it timed out.
Action: Check transaction table status.
0x610C6 ( 397510) rpERR_ABORT_INVALID_CONT_LOG Invalid log exists before current analyzing log [SN:<0%lu>].
Cause: The previously analyzed log has an invalid continue flag.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610C7 ( 397511) rpERR_ABORT_RP_OFFLINE_SENDER_ABNORMALLY_EXIT Offline sender exits without finishing some jobs.
Cause: An offline replication Sender has exited without finishing some jobs.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610C8 ( 397512) rpERR_ABORT_RP_WRONG_OPERATION_TYPE Invalid Operation type [<0%u>] of replication protocol.
Cause: The replication protocol's operation type is invalid.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610C9 ( 397513) rpERR_ABORT_RP_OVERFLOW Size of log record is greater than size of replication log buffer.
Cause: Replication is delayed or replication log buffer size is too small.
Action:
-
Increase REPLICATION_LOG_BUFFER_SIZE and restart the system.
-
Find and resolve cause of the delay.
0x610CB ( 397515) rpERR_ABORT_REPLICATION_NAME_MISMATCH The replication name does not match [<0%s>:<1%s>].
Cause: The replication name does not match.
Action: Check the replication's name.
0x610CC ( 397516) rpERR_ABORT_CONFLICT_RESOLUTION Master/Slave conflict resolution of the replication is not allowed [<0%d>:<1%d>].
Cause: The master/slave conflict resolution scheme for this replication object is not allowed.
Action: Check the conflict resolution scheme of the replication object.
0x610CD ( 397517) rpERR_ABORT_REPLICATION_ITEM_COUNT_MISMATCH The replication's item count does not match [<0%d>:<1%d>].
Cause: The replication item count mismatch.
Action: Check the replication items.
0x610CE ( 397518) rpERR_ABORT_ROLE_MISMATCH The replication's role does not match [<0%d>:<1%d>].
Cause: The replication role mismatch.
Action: Check the replication role.
0x610CF ( 397519) rpERR_ABORT_TRANSACTION_TABLE_SIZE_MISMATCH The transaction table size of the replication does not match [<0%u>:<1%u>].
Cause: Replication transaction table size mismatch.
Action: Check the transaction table size.
0x610D0 ( 397520) rpERR_ABORT_OPTION_MISMATCH The replication's option does not match [<0%d>:<1%d>].
Cause: The replication's option mismatch.
Action: Check the replication's option.
0x610D1 ( 397521) rpERR_ABORT_CHARACTER_SET_MISMATCH The character set of the database does not match. (DB=[<0%s>:<1%s>], National=[<2%s>:<3%s>]).
Cause: Database character set mismatch.
Action: Check the character set of the database.
0x610D2 ( 397522) rpERR_ABORT_PRIMARY_KEY_COUNT_MISMATCH The primary key column count of the replicated table does not match [<0%s>(<1%d>):<2%s>(<3%d>)].
Cause: The primary key column count of the replicated table mismatch.
Action: Check the primary key of the replicated table.
0x610D3 ( 397523) rpERR_ABORT_USER_NAME_MISMATCH The user name of the replicated table's owner does not match [<0%s>(<1%s>):<2%s>(<3%s>)].
Cause: Replicated table's owner user name mismatch.
Action: Check the user name of the replicated table's owner.
0x610D4 ( 397524) rpERR_ABORT_TABLE_NAME_MISMATCH The replicated table name does not match [<0%s>:<1%s>].
Cause: Replicated table name mismatch.
Action: Check the replicated table name.
0x610D5 ( 397525) rpERR_ABORT_PARTITION_NAME_MISMATCH The partition name of the replicated table does not match [<0%s>:<1%s>].
Cause: Replicated table partition name mismatch.
Action: Check the partition name of the replicated table.
0x610D6 ( 397526) rpERR_ABORT_PARTITION_METHOD_MISMATCH The partition method of the replicated table does not match [<0%s>(<1%d>):<2%s>(<3%d>)].
Cause: Replicated table partition method mismatch.
Action: Check the partition method of the replicated table.
0x610D7 ( 397527) rpERR_ABORT_PARTITION_ORDER_MISMATCH The partition order of the replicated table does not match [<0%s>(<1%d>):<2%s>(<3%d>)].
Cause: Replicated table partition order mismatch.
Action: Check the partition order of the replicated table.
0x610D8 ( 397528) rpERR_ABORT_UNIQUE_INDEX_COUNT_MISMATCH The unique index count of the replicated table does not match [<0%s>:<1%s>].
Cause: Replicated table unique index count mismatch.
Action: Check the unique index count of the replicated table.
0x610D9 ( 397529) rpERR_ABORT_NON_REPLICATION_COLUMN_NOT_NULL The non-replicated column of the replicated table has NOT NULL constraint. [<0%s>:<1%s>(<2%s>)].
Cause: The replicated table's non-replicated column has a NOT NULL constraint.
Action: Check the non-replicated column of the replicated table.
0x610DA ( 397530) rpERR_ABORT_COLUMN_TYPE_MISMATCH The column type of the replicated table does not match. [<0%s>.<1%s>(<2%u>):<3%s>.<4%s>(<5%u>)].
Cause: Replicated table column type mismatch.
Action: Check the column type of the replicated table.
0x610DB ( 397531) rpERR_ABORT_COLUMN_SIZE_MISMATCH The column size of the replicated table does not match. [<0%s>(Name:<1%s>, Size:<2%d>, Precision:<3%d>, Scale:<4%d>):<5%s>(Name:<6%s>, Size:<7%d>, Precision: <8%d>, Scale: <9%d>)].
Cause: Replicated table column size mismatch.
Action: Check the column size of the replicated table.
0x610DC ( 397532) rpERR_ABORT_ENCRYPT_PRECISION_MISMATCH The encrypt precision of the replicated table's column does not match. [<0%s>(Name:<1%s>, Precision:<2%d>):<3%s>(Name:<4%s>, Precision: <5%d>)].
Cause: Replicated table's column encryption precision mismatch.
Action: Check the the encrypt precision of the replicated table's column.
0x610DD ( 397533) rpERR_ABORT_COLUMN_CHARACTER_SET_MISMATCH The column character set of the replicated table does not match. [<0%s>.<1%s>(<2%u>):<3%s>.<4%s>(<5%u>)].
Cause: Replicated table's column character set mismatch.
Action: Check the column character set of the replicated table.
0x610DE ( 397534) rpERR_ABORT_COLUMN_CONSTRAINT_MISMATCH NOT NULL constraints of the replicated table's column does not match. [<0%s>.<1%s>(<2%d>):<3%s>.<4%s>(<5%d>)].
Cause: Replicated table's NOT NULL constraints mismatch.
Action: Check the column's constraint of the replicated table.
0x610DF ( 397535) rpERR_ABORT_POLICY_MISMATCH The encrypt policy name of the replicated table's column does not match. [<0%s>(Name:<1%s>, Policy:<2%s>):<3%s>(Name:<4%s>, Policy:<5%s>)].
Cause: Replicated table's column encryption policy name mismatch.
Action: Check the encrpyt policy name of the replicated table's column.
0x610E0 ( 397536) rpERR_ABORT_POLICY_CODE_MISMATCH The encrypt policy code of the replicated table's column does not match. [<0%s>(Name:<1%s>, Policy:<2%s>):<3%s>(Name:<4%s>, Policy:<5%s>)].
Cause: Replicated table's column encryption policy code mismatch.
Action: Check the encryption policy name of the replicated table's column.
0x610E1 ( 397537) rpERR_ABORT_ECC_POLICY_MISMATCH The encrypted comparision code policy name of the replicated table's column does not match. [<0%s>(Name:<1%s>, ECC Policy:<2%s>):<3%s>(Name:<4%s>, ECC Policy:<5%s>)].
Cause: The replicated table's column encryption comparison code policy name mismatch.
Action: Check the encrypted comparison code policy name of the replicated table's column.
0x610E2 ( 397538) rpERR_ABORT_ECC_POLICY_CODE_MISMATCH The encrypted comparison policy code of the replicated table's column does not match. [<0%s>(Name:<1%s>, ECC Policy:<2%s>):<3%s>(Name:<4%s>, ECC Policy:<5%s>)].
Cause: Replicated table's column encryption comparison code mismatch.
Action: Check the encrypted comparison code of the replicated table's column.
0x610E3 ( 397539) rpERR_ABORT_INDEX_NAME_MISMATCH The index name of the replicated table does not match. [<0%s>(Name:<1%s>):<2%s>(Name:<3%s>)].
Cause: Replicated table index name mismatch.
Action: Check the index name of the replicated table.
0x610E4 ( 397540) rpERR_ABORT_INDEX_TYPE_MISMATCH The index type of the replicated table does not match. [<0%s>(Name:<1%s>, Type:<2%u>):<3%s>(Name:<4%s>, Type:<5%u>)].
Cause: Replicated table index name mismatch.
Action: Check the index name of the replicated table.
0x610E5 ( 397541) rpERR_ABORT_INDEX_UNIQUENESS_MISMATCH The index uniqueness of the replicated table does not match. [<0%s>(Name:<1%s>, Uniqueness:<2%d>):<3%s>(Name:<4%s>, Uniqueness:<5%d>)].
Cause: Replicated table index uniqueness mismatch.
Action: Check the index uniqueness of the replicated table.
0x610E6 ( 397542) rpERR_ABORT_LOCAL_INDEX_UNIQUENESS_MISMATCH The local index uniqueness of the replicated table does not match. [<0%s>(Name:<1%s>, Uniqueness:<2%d>):<3%s>(Name:<4%s>, Uniqueness:<5%d>)].
Cause: Replicated table local index uniqueness mismatch.
Action: Check the local index uniqueness of the replicated table.
0x610E7 ( 397543) rpERR_ABORT_INDEX_COLUMN_COUNT_MISMATCH The index column count of the replicated table does not match. [<0%s>(Name:<1%s>, Count:<2%u>):<3%s>(Name:<4%s>, Count:<5%u>)].
Cause: Replicated table index column count mismatch.
Action: Check the index column count of the replicated table.
0x610E8 ( 397544) rpERR_ABORT_INDEX_COLUMN_ID_MISMATCH The index column ID of the replicated table does not match. [<0%s>(Name:<1%s>, ID:<2%u>):<3%s>(Name:<4%s>, ID:<5%u>)].
Cause: Replicated table index column ID mismatch.
Action: Check the index column ID of the replicated table.
0x610E9 ( 397545) rpERR_ABORT_INDEX_COLUMN_ORDER_MISMATCH The index column order of the replicated table does not match. [<0%s>(Name:<1%s>, ID:<2%d>, Flag:<3%d>):<4%s>(Name:<5%s>, ID:<6%d>, Flag:<7%d>)].
Cause: Replicated table index column order mismatch.
Action: Check the index column order of the replicated table.
0x610EA ( 397546) rpERR_ABORT_MIXED_UNIQUE_INDEX_COLUMN The unique index of the replicated table is composed of replication column and non-replication column [<0%s>(<1%s>)].
Cause: The unique index of the replicated table is composed of a replication column and a non-replication column.
Action: Check the unique index of the replicated table.
0x610ED ( 397549) rpERR_ABORT_CANCEL_COMMIT_BY_REPL Transaction's commit was canceled by replication conflict.
Cause: Replication conflict occurred in the standby host.
Action: Execute rollback and check your application update logic.
0x610EF ( 397551) rpERR_ABORT_ABNORMAL_TYPE [<0%s>:<1%u>] sender have abnormal type.
Cause: The replication Sender type is set to an invalid value.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610F1 ( 397553) rpERR_ABORT_RP_SENDER_UPDATE_REMOTE_FAULT_DETECT_TIME [Sender] Failed to update REMOTE_FAULT_DETECT_TIME
Cause: Failed to update the REMOTE_FAULT_DETECT_TIME column in the SYS_REPLICATIONS_ meta table due to a database error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610F2 ( 397554) rpERR_ABORT_SENDER_APPLY_ABNORMAL_EXIT [Sender] The apply thread exits abnormally.
Cause: While the replication Sender was terminating, a related thread terminated abnormally due to a network error.
Action: Some data may have been unsent. Restart the replication Sender and then stop it, to terminate it normally.
0x610F3 ( 397555) rpERR_ABORT_FAILBACK_SENDER_NOT_EXIST [Receiver] Failback sender does not exist.
Cause: Failback sender does not exist.
Action: Check the status of the replication sender.
0x610F4 ( 397556) rpERR_ABORT_FAILBACK_PK_QUEUE_TIMEOUT_EXCEED [Receiver] The queue for failback is full.
Cause: The queue for failback is full.
Action: Check status of the replication sender.
0x610F5 ( 397557) rpERR_ABORT_FAILBACK_INCREMENTAL_SYNC_MISMATCH The REPLICATION_FAILBACK_INCREMENTAL_SYNC property mismatch. [<0%u>:<1%u>]
Cause: The REPLICATION_FAILBACK_INCREMENTAL_SYNC property mismatch.
Action: Check the REPLICATION_FAILBACK_INCREMENTAL_SYNC property.
0x610F6 ( 397558) rpERR_ABORT_RP_LOG_BUFFER_PROPERTY_CONFLICT The replication log buffer cannot be used when the REPLICATION_SYNC_LOG property is 1.
Cause: The REPLICATION_LOG_BUFFER_SIZE property is greater than 0 and the REPLICATION_SYNC_LOG property is 1.
Action: Check the REPLICATION_LOG_BUFFER_SIZE and REPLICATION_SYNC_LOG properties.
0x610F7 ( 397559) rpERR_ABORT_NOT_FOUND_RECORD [Receiver] Unable to find record in <0%s> function
Cause: The record does not exist.
Action:
-
Find the conflicted record in altibase_rp.log or altibase_rp_conflict.log file and match the data or find and resolve the cause of the conflict (such as app logic).
-
In case that there is no primary key information for the log about conflict in altibase_rp.log or altibase_rp_conflict.log file, set the third bit of RP_MSGLOG_FLAG or the RP_CONFLICT_MSGLOG_FLAG to output the primary key information into the log.
-
It is possible to match the data using tools such as AltiComp if conflict has already occurred.
0x610F8 ( 397560) rpERR_ABORT_RP_SENDER_ADD_XLOG [Sender] Failed to add a XLog [TID:<0%u>, SN:<1%lu>, Type:<2%d>, Log Type:<3%d>, Change Log Type:<4%d>]
Cause: The replication Sender failed to create an XLog from a log.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610FB ( 397563) rpERR_ABORT_UNEXPECTED_HANDSHAKE_ACK Unexpected replication handshake ACK [Result:<0%u>]
Cause: The replication Sender received an unexpected ACK while handshaking the replication Receiver.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610FC ( 397564) rpERR_ABORT_HANDSHAKE_DISCONNECT Disconnection during handshaking [<0%s>]
Cause: A network error has occurred.
Action: Check the network status and ensure that all systems are connected to the network.
0x610FD ( 397565) rpERR_ABORT_SENDER_INFO_NOT_EXIST No Sender information for replication <0%s>.
Cause: There is no information about the replication Sender.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x610FE ( 397566) rpERR_ABORT_RPC_REPLICATION_ALREADY_STARTED Replication has already started.
Cause: Replication is currently underway.
Action: Stop the current replication to start again.
0x610FF ( 397567) rpERR_ABORT_RPC_NOT_SUPPORT_REPLICATION_DDL This replication DDL is no longer supported.
Cause: An attempt to use a deprecated DDL statement was made.
Action: Refer to the Replication User's Manual.
0x61100 ( 397568) rpERR_ABORT_RPC_DUPLICATE_REPLICATION Duplicate replication names. The replication name already exists in the database.
Cause: The replication name already exists in the database. The IP address and the port number must be unique.
Action: Use another replication name. Consult the meta tables in order to find replications that use the same IP address and port number.
0x61101 ( 397569) rpERR_ABORT_RPC_DUPLICATE_REPL_OPTION Duplicate option names.
Cause: Duplicate option names exist.
Action: Check option names for duplicates.
0x61102 ( 397570) rpERR_ABORT_RPC_MAX_REPLICATION_COUNT No more replications may be created. A database cannot have more than the maximum number of replications.
Cause: A database cannot have more than the maximum number of replications.
Action: Decrease the number of replications or increase the value of REPLICATION_MAX_COUNT property.
0x61103 ( 397571) rpERR_ABORT_RPC_ROLE_NOT_SUPPORT_UNIX_DOMAIN UNIX domain socket is not supported in this role.
Cause: This role does not support UNIX_DOMAIN in the 'WITH' clause.
Action: Check the role of the replication.
0x61104 ( 397572) rpERR_ABORT_RPC_ROLE_SUPPORT_ONE_SOCKET_TYPE One socket type is supported in this role.
Cause: This role supports one socket type.
Action: Check the role of the replication.
0x61105 ( 397573) rpERR_ABORT_RPC_ROLE_SUPPORT_ONE_UNIX_DOMAIN Only one UNIX domain socket is supported in this role.
Cause: This role supports one UNIX domain socket.
Action: Check the role of the replication.
0x61106 ( 397574) rpERR_ABORT_RPC_ROLE_NOT_SUPPORT_REPL_RECOVERY Recovery option not supported in this role.
Cause: This role does not support the recovery option.
Action: Check the options or the role of the replication.
0x61107 ( 397575) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_OFFLINE_AND_RECOVERY Offline option is not supported with recovery option.
Cause: Offline option is not supported with the recovery option.
Action: Check the replication options.
0x61108 ( 397576) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_OFFLINE_AND_EAGER The offline option is not supported with eager mode.
Cause: Simultaneous use of eager mode and the offline option is not supported.
Action: Change the option or mode of the replication.
0x61109 ( 397577) rpERR_ABORT_RPC_ROLE_NOT_SUPPORT_REPL_OFFLINE Offline option not supported in this role.
Cause: This role does not support the offline option.
Action: Check the options or the role of the replication.
0x6110A ( 397578) rpERR_ABORT_RPC_ROLE_NOT_SUPPORT_DEFAULT_REPL_MODE The default replication mode is not supported in this role.
Cause: This role does not support the default replication mode.
Action: Check the role of the replication.
0x6110B ( 397579) rpERR_ABORT_RPC_INVALID_HOST_IP_PORT The host IP address or port number is invalid.
Cause: Invalid host IP address or port number.
Action: Check the host IP address and port number.
0x6110C ( 397580) rpERR_ABORT_RPC_ALREADY_EXIST_REPL_HOST Replication hosts already exist.
Cause: Replication hosts already exist.
Action: Check the meta tables.
0x6110D ( 397581) rpERR_ABORT_RPC_REPLICATED_OBJECT_TYPE The replicated object type must be a table. <0%s>
Cause: Only a table may be replicated.
Action: Check the object type.
0x6110E ( 397582) rpERR_ABORT_RPC_NOT_EXIST_USER User not found
Cause: The user is not in the meta database.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6110F ( 397583) rpERR_ABORT_RPC_NOT_EXISTS_USER User not found : <0%s>
Cause: The name of the specified user was not found in the database.
Action: Verify that the user exists in the database.
0x61110 ( 397584) rpERR_ABORT_RPC_NOT_EXIST_TABLE Table not found
Cause: The table is not in the meta database.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61111 ( 397585) rpERR_ABORT_RPC_NOT_EXISTS_TABLE Table not found : <0%s>
Cause: The name of the specified table was not found in the database.
Action: Verify that the table exists in the database. Verify that there are no typos in the table name.
0x61112 ( 397586) rpERR_ABORT_RPC_REPLICATE_TABLE_WITH_REFERENCE Replication is not allowed on tables that have referential constraints. (<0%s>.<1%s>)
Cause: The user tried to replicate a table that has referential constraints.
Action: Verify that the table to be replicated does not have any referential constraints.
0x61113 ( 397587) rpERR_ABORT_RPC_NOT_EXISTS_PRIMARY_KEY A replicated table must have a primary key. (<0%s>.<1%s>)
Cause: No primary key was found in the table to be replicated. For replication, specify a table having a primary key.
Action: Create a primary key for the table to be replicated.
0x61114 ( 397588) rpERR_ABORT_RPC_REPL_RECOVERY_COUNT A table can recover only one replication.
Cause: Table recovery already supported by another replication.
Action: Check the replication recovery count.
0x61115 ( 397589) rpERR_ABORT_RPC_NOT_APPLICABLE_POLICY This column policy is not compatible with replication. [<0%s>]
Cause: This column policy is not compatible with replication.
Action: Check the column policy.
0x61116 ( 397590) rpERR_ABORT_RPC_CANNOT_USE_VOLATILE_TABLE Replication not allowed on volatile tables.
Cause: A volatile table cannot be replicated.
Action: Verify that the table to be replicated is not a volatile table.
0x61117 ( 397591) rpERR_ABORT_RPC_CANNOT_USE_TEMPORARY_TABLE Temporary tables cannot be replicated.
Cause: An attempt was made to add a temporary table to a replication object.
Action: Verify that none of the tables to be replicated are temporary tables.
0x61118 ( 397592) rpERR_ABORT_RPC_NOT_SUPPORT_MAX_ROWS_AND_EAGER Replication in eager mode is not supported with the MAX ROWS table option.
Cause: A table with the MAX_ROWS option specified cannot be replicated in eager mode.
Action: Check the replication mode.
0x61119 ( 397593) rpERR_ABORT_RPC_NOT_ALLOW_ADD_TABLE An ADD TABLE statement is not allowed in recovery support replication.
Cause: An ADD TABLE statement is not allowed in a recovery support replication.
Action: Check the replication options.
0x6111A ( 397594) rpERR_ABORT_RPC_NOT_EXIST_REPL_ITEM No replication items found.
Cause: No replication items were found.
Action: Check the meta tables.
0x6111B ( 397595) rpERR_ABORT_RPC_NOT_EXIST_REPLICATION Undefined replication name. The replication name was not found in the database.
Cause: The replication name was not found in the database. The name is incorrect or the replication has not been created yet.
Action: Verify that the replication name is typed correctly. Consult meta tables to see if the same replication name exists in the database.
0x6111C ( 397596) rpERR_ABORT_RPC_ALREADY_RECOVERY_SET Recovery option already set.
Cause: The replication recovery option has already been set.
Action: Check the replication options.
0x6111D ( 397597) rpERR_ABORT_RPC_ALREADY_RECOVERY_UNSET The recovery option was already unset.
Cause: The replication recovery option was already unset.
Action: Check the replication options.
0x6111E ( 397598) rpERR_ABORT_RPC_NOT_ALLOW_DROP_TABLE An DROP TABLE statement is not allowed in recovery support replication.
Cause: A DROP TABLE statement is not allowed in recovery support replication.
Action: Check the replication options.
0x6111F ( 397599) rpERR_ABORT_RPC_NOT_EXIST_REPL_HOST Replication hosts not found.
Cause: No replication hosts were found.
Action: Check the meta tables.
0x61120 ( 397600) rpERR_ABORT_RPC_NOT_SUPPORT_AT_SN_CLAUSE Replication cannot start from a specific SN unless it is used with the Log Analyzer.
Cause: The AT SN clause was specified, but the role of the replication object is not "Log Analyzer".
Action: Either specify the FOR ANALYSIS clause in the CREATE REPLICATION statement, or do not use the AT SN clause in the ALTER REPLICATION statement.
0x61121 ( 397601) rpERR_ABORT_RPC_NOT_SUPPORT_RETRY_AND_EAGER The retry option is not supported when replication is running in eager mode.
Cause: The retry option is not supported in eager mode.
Action: Either remove the retry option or change the replication mode.
0x61122 ( 397602) rpERR_ABORT_RPC_ROLE_NOT_SUPPORT_SYNC Replication SYNC is not supported in this role.
Cause: This role does not support SYNC.
Action: Check the role of the replication.
0x61123 ( 397603) rpERR_ABORT_RPC_ALREADY_OFFLINE_SET Offline option already set.
Cause: The replication offline option was already set.
Action: Check the replication options.
0x61124 ( 397604) rpERR_ABORT_RPC_ALREADY_OFFLINE_UNSET Offline option already unset.
Cause: The replication offline option was already unset.
Action: Check the replication options.
0x61126 ( 397606) rpERR_ABORT_RPD_REPL_NOT_FOUND Replication not found
Cause: The specified replication has not been created yet.
Action: Create the replication first. Verify that the replication name is valid.
0x61127 ( 397607) rpERR_ABORT_RPD_INTERNAL_ARG Internal server error in meta module (<0%s>).
Cause: Failed to execute DML on replication metadata due to a database error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61128 ( 397608) rpERR_ABORT_RPD_TOO_MANY_REPLICATION_OLD_ITEMS Internal server error. There are too many old item metas for replication. (<0%s>)
Cause: A larger number of rows than those existing were returned from SYS_REPL_OLD_ITEMS_. This is an internal server error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61129 ( 397609) rpERR_ABORT_RPD_NOT_ENOUGH_REPLICATION_OLD_ITEMS Internal server error. There are too few old item metas for replication. (<0%s>)
Cause: A smaller number of rows than those existing were returned from SYS_REPL_OLD_ITEMS_. This is an internal server error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6112A ( 397610) rpERR_ABORT_RPD_NOT_EXIST_REPL_OFFLINE_DIR_PATH Replication offline log dir not found.
Cause: No replication offline log directory path was found.
Action: Check the meta tables.
0x6112B ( 397611) rpERR_ABORT_RPD_TOO_MANY_REPLICATION_OFFLINE_DIR_PATH Internal server error. Too many offline log dir paths for replication.
Cause: Too many directories were specified for offline replication.
Action: Specify only one directory.
0x6112C ( 397612) rpERR_ABORT_RPD_NOT_ENOUGH_REPLICATION_OFFLINE_DIR_PATH Internal server error. Too few offline log dir paths for replication.
Cause: A directory has not been specified for offline replication.
Action: Specify a directory.
0x6112D ( 397613) rpERR_ABORT_RPD_MAX_REPLICATION Internal server error.
Cause: This is an internal error related to metadata of the replication object.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6112E ( 397614) rpERR_ABORT_RPD_TOO_MANY_REPLICATION_HOSTS Internal server error. There are too many hosts for replication.
Cause: This is an internal error related to metadata of replication hosts.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6112F ( 397615) rpERR_ABORT_RPD_NOT_ENOUGH_REPLICATION_HOSTS Internal server error. There are too few hosts for replication.
Cause: This is an internal error related to metadata of replication hosts.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61130 ( 397616) rpERR_ABORT_RPD_TOO_MANY_REPLICATION_ITEMS Internal server error. There are too many tables for replication.
Cause: This is an internal error related to SYS_REPL_ITEMS_ .
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61131 ( 397617) rpERR_ABORT_RPD_NOT_ENOUGH_REPLICATION_ITEMS Internal server error. There are too few tables for replication.
Cause: This is an internal error related to SYS_REPL_ITEMS_.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61132 ( 397618) rpERR_ABORT_RPD_MAXIMUM_OBJECT_NUMBER_EXCEED The number of elements <0%s> exceeds the maximum limit (<1%ld>).
Cause: The specified number of elements exceeds the maximum limit.
Action: Reduce the specified number of elements.
0x61133 ( 397619) rpERR_ABORT_RPD_TOO_MANY_REPLICATION_OLD_COLUMNS Internal server error. There are too many old column metas for replication. (<0%s>, <1%lu>)
Cause: This is an internal error related to SYS_REPL_ITEMS_.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61134 ( 397620) rpERR_ABORT_RPD_NOT_ENOUGH_REPLICATION_OLD_COLUMNS Internal server error. There are too few old column metas for replication. (<0%s>, <1%lu>)
Cause: This is an internal error related to SYS_REPL_ITEMS_.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61135 ( 397621) rpERR_ABORT_RPD_TOO_MANY_REPLICATION_OLD_INDICES Internal server error. There are too many old index metas for replication. (<0%s>, <1%lu>)
Cause: This is an internal error related to SYS_REPL_ITEMS_.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61136 ( 397622) rpERR_ABORT_RPD_NOT_ENOUGH_REPLICATION_OLD_INDICES Internal server error. There are too few old index metas for replication. (<0%s>, <1%lu>)
Cause: This is an internal error related to SYS_REPL_ITEMS_.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61137 ( 397623) rpERR_ABORT_RPD_TOO_MANY_REPLICATION_OLD_INDEX_COLS Internal server error. There are too many old index column metas for replication. (<0%s>, <1%lu>, <2%u>)
Cause: This is an internal error related to SYS_REPL_ITEMS_.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61138 ( 397624) rpERR_ABORT_RPD_NOT_ENOUGH_REPLICATION_OLD_INDEX_COLS Internal server error. There are too few old index column metas for replication. (<0%s>, <1%lu>, <2%u>)
Cause: This is an internal error related to SYS_REPL_ITEMS_.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61139 ( 397625) rpERR_ABORT_RPD_ALREADY_SUPPORT_RECOVERY The table recovery is already supported by another replication <0%s>
Cause: The recovery of this table is already supported by an existing replication.
Action: Check the replication item.
0x6113A ( 397626) rpERR_ABORT_NOT_EXIST_SYNC_TABLE A table to be synchronized does not exist.
Cause: The table is not a replication target object.
Action: Check whether the table is a replication target object.
0x6113B ( 397627) rpERR_ABORT_SEND_SYNC_TABLES Failed to send information about a table to synchronize.
Cause: A network error has occurred.
Action: Check the network status and ensure that all systems are connected to the network.
0x6113C ( 397628) rpERR_ABORT_INVALID_SYNC_TABLE_NUMBER The number of tables to be synchronized is invalid.
Cause: The number of tables to be synchronized is invalid.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6113D ( 397629) rpERR_ABORT_REBUILD_INDEX Failed to rebuild indexes after synchronization operation.
Cause: The table may be locked, or meta information may be corrupted.
Action: Wait for the lock to be released and then try again.
0x6113E ( 397630) rpERR_ABORT_RP_SYNC Synchronization failed. Indexes on the remote server may have been inconsistent.
Cause: Check the log files on the remote server to determine the cause of failure.
Action: Identify and rectify the cause of synchronization failure. Additionally, check whether indexes on the remote server have been inconsistent, and rebuild the indexes if necessary.
0x6113F ( 397631) rpERR_ABORT_SEND_SYNC_START Failed to send signal starting replication synchronization.
Cause: A network error has most likely occurred.
Action: Check the network status and ensure that all systems are connected to the network.
0x61140 ( 397632) rpERR_ABORT_LOCK_TABLE Failed to lock table for replication synchronization.
Cause: A lock conflict occurred.
Action: Wait for the lock to be released or manually release the lock.
0x61141 ( 397633) rpERR_ABORT_SEND_SYNC_TABLES_NUMBER Failed to send information about the number of tables to synchronize.
Cause: A network error has most likely occurred.
Action: Check the network status and ensure that all systems are connected to the network.
0x61142 ( 397634) rpERR_ABORT_ALLOC_CM_BLOCK [Network] Allocate communication block failed
Cause: Failed to allocate network resources.
Action: Check the state of system resources. If they are insufficient, take appropriate action.
0x61143 ( 397635) rpERR_ABORT_FREE_CM_BLOCK [Network] Free communication block failed
Cause: Failed to free network memory resources.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61144 ( 397636) rpERR_ABORT_LOB_TRIM [SmExec] A failure occurred while trimming LOB type data
Cause: Failed to trim LOB data.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61145 ( 397637) rpERR_ABORT_RPC_CANNOT_REPLICATE_TABLE_WITH_COMPRESSED_COLUMN Replication is not allowed on tables that have compressed column.
Cause: A table with a compressed column cannot be replicated.0x110E9
Action: Verify that the table to be replicated does not have any compressed columns.
0x61146 ( 397638) rpERR_ABORT_INVALID_PACKET_TYPE Invalid communication packet type
Cause: An invalid communication packet type has been detected.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61147 ( 397639) rpERR_ABORT_CHECK_NAME_NOT_FOUND Check constraint name of the replicated table does not exist. [<0%s>(Name: <1%s>)]
Cause: The check constraint name of the replicated table does not match.
Action: Check the check constraint name.
0x61148 ( 397640) rpERR_ABORT_CHECK_CONDITION_MISMATCH Check constraint condition string of the replicated table mismatch. [<0%s>(Condition String: <1%s>):<2%s>(Condition String: <3%s>)]
Cause: The check constraint condition string for both tables does not match.
Action: Check the condition string in check constraint.
0x61149 ( 397641) rpERR_ABORT_CHECK_COLUMN_NOT_REPL Check Constraint is composed of replication column and non-replication column [<0%s>(<1%s>)]
Cause: The check constraint column composition does not match.
Action: Check the column in check constraint.
0x6114A ( 397642) rpERR_ABORT_FUNC_BASED_INDEX_EXPRESSION_MISMATCH Function-based index expression string of the replicated table mismatch. [<0%s>(Name:<1%s>, Expression String:<2%s>:<3%s>(Name:<4%s>, Expression String:<5%s>)]
Cause: The function-based index expression string is not the same as the corresponding table.
Action: Check the expression string in the function-based index.
0x6114B ( 397643) rpERR_ABORT_FUNC_BASED_INDEX_COUNT_MISMATCH Function-based index count of the replicated table does not equal. [<0%s>:<1%s>]
Cause: The function-based index count of the replicated table does not match.
Action: Check the function-based index.
0x6114C ( 397644) rpERR_ABORT_COLUMN_HIDDEN_MISMATCH Hidden columns mismatch.[<0%s>.<1%s>(<2%u>):<3%s>.<4%s>(<5%u>)]
Cause: The hidden column names and the regular column names are identical for the replication target tables.
Action: Check whether the hidden column names and the regular column names are identical.
0x6114D ( 397645) rpERR_ABORT_FUNC_BASED_INDEX_COLUMN_NOT_REPL Function-based index is composed of replication column and non-replication column [<%0s>(<%1s>)]
Cause: The function based index is composed of a replicated column and a non-replicated column.
Action: Check the composition of the function based index.
0x6114E ( 397646) rpERR_ABORT_COMPATIBILITY_BETWEEN_TABLE_AND_PARTITION The replication units mismatch: <0%s>
Cause: The replication unit (table or partition) to be dropped or synced is not the same as the existing replication unit.
Action: Check whether the specified replication unit exists in the partition_unit column of the SYS_REPL_IMTES_ meta table.
0x6114F ( 397647) rpERR_ABORT_RPC_NOT_EXISTS_PARTITION Partition not found : <0%s>
Cause: The name of the specified partition was not found in the specified table.
Action: Verify that the partition exists in the database. Verify that there are no typos in the partition name.
0x61150 ( 397648) rpERR_ABORT_RPC_EXISTS_OFFLINE_OPTION_COMPRESSED_COLUMN Offline replication cannot be performed on a compressed table. [<0%s>.<1%s>]
Cause: Offline replication cannot be performed on a compressed table.
Action: Check whether the specified table is compressed or not.
0x61151 ( 397649) rpERR_ABORT_RPC_NOT_SUPPORT_OFFLINE_REPLICATE_TABLE_WITH_COMPRESSED_COLUMN Compressed tables do not support offline replication.
Cause: Compressed tables do not support offline replication.
Action: Check whether the specified table is compressed or not.
0x61152 ( 397650) rpERR_ABORT_RP_SYNC_WITH_INDEX_CAUTION Replication synchronization failed. Check whether the index on the remote server is consistent.
Cause: Check logs on the local and remote servers for the cause of failure.
Action: Check whether the index on the remote server is inconsistent and rebuild it, if necessary.
0x61153 ( 397651) rpERR_ABORT_RP_SYNC_WITHOUT_INDEX_CAUTION Replication synchronization failed.
Cause: Check logs on the local and remote servers for the cause of failure.
Action: Check the cause for synchronization failure and fix it.
0x61154 ( 397652) rpERR_ABORT_INSERT_GLOBAL_INDEX_TABLE Failed to insert the record to the global index table.
Cause: Inserting data into a partition and a global index failed while duplicating a partition with a global index.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61155 ( 397653) rpERR_ABORT_UPDATE_GLOBAL_INDEX_TABLE Failed to update the record to the global index table.
Cause: Updating data on a partition and a global index failed while duplicating a partition with a global index.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61156 ( 397654) rpERR_ABORT_DELETE_GLOBAL_INDEX_TABLE Failed to delete the record from the global index table.
Cause: Deleting data from a partition and a global index failed while duplicating a partition with a global index.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61157 ( 397655) rpERR_ABORT_RPD_OVERFLOW_COUNT_REPL_OFFLINE_DIR_PATH Exceeds the maximum number of log directory paths allowed to be specified.
Cause: Only one log directory path can be specified with the replication offline option.
Action: Check the log directory path of the Active server.
0x61158 ( 397656) rpERR_ABORT_DATA_STILL_REMAIN_IN_BUFFER If receive buffer has been processed, no data should remain in the receive buffer.
Cause: Already processed data remains in the replication receive buffer.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61159 ( 397657) rpERR_ABORT_REPLICATION_MODE_MISMATCH The replication mode does not match. [<0%u>:<1%u>]
Cause: The mode of the replicated table mismatch.
Action: Please check the mode of the replicated table.
0x6115A ( 397658) rpERR_ABORT_PARTITION_CONDITION_MISMATCH The partition condition of the replicated table does not match. [<0%s>:<1%s>]
Cause: The partition condition of the replicated table mismatch.
Action: Please check the partition condition of the replicated table.
0x6115B ( 397659) rpERR_ABORT_NOT_SUPPORT_FEATURE_WITH_V6_PROTOCOL This feature is not supported with __REPLICATION_USE_V6_PROTOCOL property. (<0%s>)
Cause: When using A5 protocol, this feature is not surpported.
Action: Check the __REPLICATION_USE_V6_PROTOCOL property or table schemes.
0x6115C ( 397660) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_GAPLESS_AND_EAGER The gap control option is not supported with eager mode.
Cause: Simultaneous use of eager mode and the gap control option is not supported.
Action: Change the option or mode of the replication.
0x6115D ( 397661) rpERR_ABORT_RPC_ALREADY_GAPLESS_SET The gapless option already set.
Cause: The replication gapless option has already been set.
Action: Check the replication options.
0x6115E ( 397662) rpERR_ABORT_RPC_ALREADY_GAPLESS_UNSET The gapless option was already unset.
Cause: The replication gapless option was already unset.
Action: Check the replication options.
0x6115F ( 397663) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_PARALLEL_OPTION_AND_EAGER The parallel option is not supported with eager mode.
Cause: Simultaneous use of eager mode and the parallel option is not supported.
Action: Change the option or mode of the replication.
0x61160 ( 397664) rpERR_ABORT_RPC_NOT_PROPER_VALUE_FOR_PARALLEL_COUNT Invalid the parallel count value. Valid value range = 0 ~ 512
Cause: The value of parallel count is invalid.
Action: Spcify the value of parallel count whthin valid range.
0x61161 ( 397665) rpERR_ABORT_RPC_ALREADY_PARALLEL_SET The parallel option already set.
Cause: The replication parallel option has already been set.
Action: Check the replication options.
0x61162 ( 397666) rpERR_ABORT_RPC_ALREADY_PARALLEL_UNSET The parallel option was already unset.
Cause: The replication parallel option was already unset.
Action: Check the replication options.
0x61163 ( 397667) rpERR_ABORT_RPC_ALREADY_GROUPING_SET The grouping option already set.
Cause: The grouping option has already been set.
Action: Check the replication options.
0x61164 ( 397668) rpERR_ABORT_RPC_ALREADY_GROUPING_UNSET The grouping option was already unset.
Cause: The grouping option was already unset.
Action: Check the replication options.
0x61165 ( 397669) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_GROUPING_AND_EAGER The grouping option is not supported with eager mode.
Cause: Simultaneous use of eager mode and the grouping option is not supported.
Action: Change the option or mode of the replication.
0x61166 ( 397670) rpERR_ABORT_AHEAD_ANALYZER_TIMED_WAIT_ERROR Internal server error. ( system call ( timedwait ) got error )
Cause: cond_timedwait() returned false while the Ahead Analyzer for grouping transaction was waiting after finishing the analysis in the replication with the grouping option enabled.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61168 ( 397672) rpERR_ABORT_TRANSACTION_NOT_ACTIVE Transaction is not active.
Cause: A transaction is not active.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61169 ( 397673) rpERR_ABORT_SOCKET_OPEN_ERROR Socket Can not be openned.
Cause: An error occurred while opening the socket.
Action: Please check system resources
0x6116A ( 397674) rpERR_ABORT_SOCKET_SET_BLOCK_MODE Socket can not be set as block mode.
Cause: An error occurred while setting a block mode to socket.
Action: Please check network status.
0x6116B ( 397675) rpERR_ABORT_SOCKET_GET_OPTION Socket can not be gotten option value.
Cause: An error occurred while getting socket option.
Action: Please check system resource (file descriptor) or network resources.
0x6116C ( 397676) rpERR_ABORT_POLL_REMOVE_SOCK Socket can not be removed from the poll.
Cause: An error occurred while removing socket from the poll.
Action: Please check system (file descriptor) or network resources.
0x6116D ( 397677) rpERR_ABORT_POLL_DISPATCH_TIMEOUT There is no network event in time.
Cause: There is no network I/O in time.
Action: Please check network interface controller.
0x6116E ( 397678) rpERR_ABORT_POLL_DISPATCH_ERROR Fail to invoke the dispatcher system function.
Cause: This is a system call error.
Action: Please check system resources (file descriptor or memory).
0x6116F ( 397679) rpERR_ABORT_POLL_CREATE_ERROR Dispatcher can not be created.
Cause: An error occurred while creating dispatcher was being created.
Action: Please check system resources (file descriptor or memory).
0x61170 ( 397680) rpERR_ABORT_SOCK_GET_ADDR_INFO_ERROR Fail to invoke getAddrInfo system function. (IP = <0%s>, PORT = <1%d>)
Cause: IP address and port number are wrong, or There is not enough memory.
Action: Please check IP address and port Number, or system resources(memory).
0x61171 ( 397681) rpERR_ABORT_REPLICATION_HAS_RECOVERY_OPTION_IN_SPLIT_PARTITION Replication option is set to recovery.(Replcation Name:<0%s>, User:<1%s>, Table:<2%s>, Partition:<3%s>)
Cause: The partition split cannot be performed in recovery option.
Action: Check the replication options
0x61172 ( 397682) rpERR_ABORT_REPLICATION_HAS_RECOVERY_OPTION_IN_MERGE_PARTITION Replication option is set to recovery.(Replcation Name:<0%s>, User:<1%s>, Table:<2%s>, Partition:<3%s>, Partition:<4%s>)
Cause: The partition merge cannot be performed in recovery option.
Action: Check the replication options
0x61173 ( 397683) rpERR_ABORT_TABLE_PARTITIONS_ARE_NOT_SAME_REPLICATION Replicated partitions are not included same replication.(User:<0%s>, Table:<1%s>, Partition:<2%s>, Partition:<3%s>)
Cause: The partition merge cannot be performed in other replicated partition.
Action: Check the partition name of the replicated table.
0x61174 ( 397684) rpERR_ABORT_PARTITION_NAME_DIFF The partition name of local table must be same with remote one.( Replication name: <0%s> Local (User:<1%s>, Table:<2%s>, Partition:<3%s>), Remote (User:<4%s>, Table:<5%s>, Partition:<6%s>) )
Cause: The partition name of local table is not same with remote one.
Action: Modify the partition name of local table.
0x61175 ( 397685) rpERR_ABORT_TABLE_NAME_DIFF The name of local table must be same with remote one.(Replication name: <0%s> Local (User:<1%s>, Table:<2%s>, Partition:<3%s>), Remote (User:<4%s>, Table:<5%s>, Partition:<6%s>) )
Cause: The name of local table must be same with remote one.
Action: Verify that the name of local table is same with remote table.
0x61176 ( 397686) rpERR_ABORT_REPLICATION_HAS_RECOVERY_OPTION_IN_DROP_PARTITION Replication option is set to recovery.(Replcation Name:<0%s>, User:<1%s>, Table:<2%s>, Partition:<3%s>)
Cause: Cannot perform a DDL(DROP PARTITION) in recovery option.
Action: Remove the recovery option.
0x61177 ( 397687) rpERR_ABORT_POLL_ADD_SOCK A Socket cannot be added to the poll.
Cause: An error occurred while adding a socket to the poll.
Action: Check the system or network resources; in particular, verify the file descriptor.
0x61178 ( 397688) rpERR_ABORT_RPC_NOT_PROPER_VALUE Invalid <0%s> value : <1%s>. Valid value range = <2%lu> ~ <3%lu> <4%s>
Cause: The value is out of range.
Action: Spcify the value whthin valid range.
0x6117B ( 397691) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_LOCAL_AND_EAGER It is unable to use eager mode when local replication option used.
Cause: Eager mode does not support local replication option.
Action: Change replication mode or remove LOCAL option.
0x6117C ( 397692) rpERR_ABORT_SELF_REPLICATION_TABLE Self-replication has been detected due to duplicate table name. [<0%s>.<1%s>.<2%s>:<3%s>.<4%s>.<5%s>]
Cause: The same name is used in the source and target tables.
Action: Set a different name for the source and target tables.
0x6117D ( 397693) rpERR_ABORT_SELF_REPLICATION_NAME Self-replication has been detected due to duplicate replication name. [<0%s>]
Cause: Same replication name used for itself and peer replicaiton.
Action: Use different peer replication name from its replication name.
0x6117E ( 397694) rpERR_ABORT_RP_NOT_SUPPORT_CONVERT_APPLY_DATA_TYPE The table(<0%s>.<1%s>:<2%s>.<3%s>) containing <4%s> does not support sql apply feature.
Cause: The table containing specific data type does not support sql apply feature.
Action: Please drop specific data type from the table.
0x6117F ( 397695) rpERR_ABORT_REPLICATION_DDL_ENABLE_LEVEL Cannot execute this DDL on a replicated table when the system property REPLICATION_DDL_ENABLE_LEVEL is <0%u>.
Cause: System property REPLICATION_DDL_ENABLE_LEVEL is not appropriate for this DDL.
Action: Check the system property REPLICATION_DDL_ENABLE_LEVEL.
0x61180 ( 397696) rpERR_ABORT_RPC_DDL_NOT_SUPPORTED_REPLICATED_TABLE This DDL is not supported on replicated table.(Cause : <0%s>)
Cause: This DDL is not supported on replicated table.
Action: Identify the cause and take appropriate action.
0x61181 ( 397697) rpERR_ABORT_RP_ALREADY_DDL_SYNC Can not perform a DDL synchronization because it is currently in progress (Replication name : <0%s>).
Cause: Can not perform a DDL synchronization because it is currently in progress.
Action: Retry after finishing the DDL synchronization.
0x61182 ( 397698) rpERR_ABORT_RP_DDL_SYNC_NOT_SUPPORT_EAGER Can not execute a DDL synchronization on a table using eager mode replication.
Cause: Can not execute a DDL synchronization for a table using eager mode replication.
Action: Change the replication mode in eager mode replication or remove the table in eager mode replication.
0x61183 ( 397699) rpERR_ABORT_RP_DDL_SYNC_NOT_SUPPORT_GLOBAL_NON_PARTITION_INDEX A DDL synchronization is not support on a table with global non-partitioned index.
Cause: A DDL synchronization is not support on a table with global non-partitioned index.
Action: Verify that the table with a global non-paritited index.
0x61184 ( 397700) rpERR_ABORT_RP_DDL_SYNC_DISABLE Can not perform the DDL synchronization when the value of the REPLICATION_DDL_SYNC property is 0.
Cause: Can not perform the DDL synchronization when the value of the REPLICATION_DDL_SYNC property is 0.
Action: Verify and change the value of the REPLICATION_DDL_SYNC property is 1.
0x61185 ( 397701) rpERR_ABORT_RP_DDL_SYNC_ERROR_AFTER_COMMIT_MSG A DDL synchronization is failed after sending commit message. The table schema of the remote server may have been inconsistent.
Cause: A DDL synchronization is failed after sending commit message.
Action: Verify that the replication actually commits
0x61186 ( 397702) rpERR_ABORT_RP_DDL_SYNC_RECEIVE_ERROR A DDL synchronization receives the error message from the remote server (<0%s>).
Cause: Receive the error message from the remote server.
Action: Perform a DDL synchronization after troubleshooting the remote server.
0x61187 ( 397703) rpERR_ABORT_RP_SENDER_NOT_RUNNING The sender of replication <0%s> is not running.
Cause: The sender of replication is not running.
Action: Restart replication or wait for the replication sender to run.
0x61188 ( 397704) rpERR_ABORT_RP_DDL_SYNC_SQL_LENGTH_ERROR The length of the SQL query exceeds the maximum limit (<0%u>).
Cause: The length of the SQL query exceeds the maximum limit.
Action: Refer to the Replication Manaual for the maximum possible length allowed for the DDL synchronization query.
0x61189 ( 397705) rpERR_ABORT_PARENT_AND_CHILD_CONNECT_DIFFERENT Failed to connected by the parallel senders. The parallel senders get different IP address from DNS server.
Cause: The parallel senders must be connected by the same IP.
Action: Verify the DNS server or restart the replication sender. (When you restart the replication, the parallel senders have been connected by the same IP.)
0x6118A ( 397706) rpERR_ABORT_RPC_ROLE_NOT_SUPPORT_IB InfiniBand(IB) can not be used with 'FOR ANALYSIS' syntax.
Cause: InfiniBand(IB) can not be used with 'FOR ANALYSIS' syntax.
Action: Check the role of the replication. Do not use the InfiniBand(IB).
0x6118B ( 397707) rpERR_ABORT_RPC_NOT_DEFAULT_SRID Only the default SRID can be replicated.
Cause: The SRID of the geometry column is not the default.
Action: Check the SRID of the geometry column.
0x6118C ( 397708) rpERR_ABORT_RP_DDL_SYNC_WITH_PROPAGATION The propagation option(FOR PROPAGABLE LOGGING/ FOR PROPAGATION) does not support DDL synchronization.
Cause: The propagation option(FOR PROPAGABLE LOGGING/ FOR PROPAGATION) does not support DDL synchronization.
Action: Remove the propagation option.
0x6118D ( 397709) rpERR_ABORT_HBT_DETECT_PEER_SERVER_ERROR The HeartBeat thread(HBT) detects peer server or network error.
Cause:
- Peer server is not running.
- Network is not working.
Action:
- Confirm peer server is running.
- Ensure that network is working normally.
0x6118E ( 397710) rpERR_ABORT_SEND_TIMEOUT_EXCEED Timeout exceed while the replication Sender and Receiver were communicating.
Cause: A timeout occurred while the replication Sender and Receiver were communicating.
Cause:
-
Set a larger value for the REPLICATION_SENDER_SEND_TIMEOUT property.
-
Check the peer server or network connection.
0x6118F ( 397711) rpERR_ABORT_FAULT_TOLERATED Failed to work because an internal exception occurred from an OS.[Contact Altibase's Support Center]
Cause: An internal exception occurred from an OS.
Action: Check the error number from the trace log for more detailed information. And contact Altibase's Support Center (http://support.altibase.com).
0x61190 ( 397712) rpERR_ABORT_PARTITION_COUNT_MISMATCH The partition count of the replicated table does not match [<0%s>(<1%d>):<2%s>(<3%d>)].
Cause: Replicated table partition count mismatch.
Action: Check the partition count of the replicated table.
0x61191 ( 397713) rpERR_ABORT_SYNC_FAILED_BY_BULK_INSERT Replication synchronization failed by replication bulk insert.
Cause: Bulk insert error has been occurred while executing the received record.
Action: Check the altibase_rp.log file.
0x61192 ( 397714) rpERR_ABORT_SRID_MISMATCH The geometry SRID of the replicated table's column does not match. [<0%s>(Name:<1%s>, SRID:<2%d>):<3%s>(Name:<4%s>, SRID: <5%d>)].
Cause: Replicated table's column geometry SRID mismatch.
Action: Check the geometry SRID of the replicated table's column.
0x61193 ( 397715) rpERR_ABORT_NOT_SUPPORT_SRID_REMOTE The geometry SRID of <0%s> table's column is not supported on the remote server;
Cause: The remote server is a version that does not support geometry SRID.
Action: Check the error number from the trace log for more detailed information. And contact Altibase's Support Center (http://support.altibase.com).
0x61194 ( 397716) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_CONDITIONAL_START_AND_EAGER SYNC CONDITIONAL and START CONDITIONAL clauses are not supported with replication eager mode.
Cause: It's unable to execute the statement, becuase SYNC CONDITIONAL and START CONDITIONAL clauses are not supported with replication eager mode.
Action: Check the replication mode.
0x61195 ( 397717) rpERR_ABORT_DDL_SYNC_WITH_LOCK_UNTIL_NEXT_DDL You cannot execute DDL for the replicated table after performing LOCK.. UNTIL NEXT DDL on REPLICATION_DDL_SYNC enable mode.
Cause: You cannot use the property REPLICATION_DDL_SYNC enable and LOCK.. UNTIL NEX DDL statement on the replicated table.
Action: Change the property REPLICATION_DDL_SYNC to 0(disable) or close a transaction.
0x61196 ( 397718) rpERR_ABORT_RPD_TOO_LONG_MUTEX_NAME A mutex name is too long. (<0%s>)
Cause: The Internal mutex name is over 64 characters.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x61197 ( 397719) rpERR_ABORT_RPD_TOO_LONG_FILE_PATH A xlogfile full-path is too long. (<0%s>)
Cause: A xlogfile full-path is over 1024 characters.
Action: Modify XLOGFILE_DIR property to short full-path.
0x61198 ( 397720) rpERR_ABORT_RPD_FAILURE_UNLINK_FILE Failed to delete xlogfile. [path=(<0%s>), errcode=<1%d>]
Cause: The system failed to remove a file, because the file is busy.
Action: Terminate unnecessary processes.
0x61199 ( 397721) rpERR_ABORT_RPD_CREATER_THREAD_NOT_ALIVE <0%s> xlogfile creater thread has beed terminated.
Cause: The xlogfile creater thread has been terminated.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6119A ( 397722) rpERR_ABORT_RPD_FLUSHER_THREAD_NOT_ALIVE <0%s> xlogfile flusher thread has been terminated.
Cause: The xlogfile flusher thread has been terminated.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6119B ( 397723) rpERR_ABORT_RPN_UNABLE_READ_CONTEXT Invalid read context.
Cause: Internal error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6119C ( 397724) rpERR_ABORT_RPX_FAIL_WRITE_XLOG_IN_XLOGFILE Failed to write xlog into xlogfile.
Cause: Internal error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x6119D ( 397725) rpERR_ABORT_RPC_CONSISTENT_MODE_MUST_HAVE_PARALLEL syntax error : PARALLEL APPLIER Option is missing on CREATE CONSISTENT REPLICATION statement.
Cause: Consistent replication should be made with parallel applier option.
Action: Check the syntax of CREATE CONSISTENT REPLICATION statement.
0x6119E ( 397726) rpERR_ABORT_RPC_NOT_COMPATIBLE_ROLE_OPTION_IN_CONSISTENT_MODE Unable to use the role option in consistent replication.
Cause: Cannot create consistent replication with role option, except for parallel applier option.
Action: Check the constraint for consistent replication.
0x6119F ( 397727) rpERR_ABORT_RPC_CONSISTENT_DO_NOT_HAVE_ANY_OTHER_OPTIONS Unable to use the option in consistent replication.
Cause: Unable to use any option in consistent replication, except for parallel applier option.
Action: Check the constraint for consistent replication.
0x611A0 ( 397728) rpERR_ABORT_RPC_FLUSH_XLOGFILE_STATEMENT_CAN_ONLY_RUN_IN_CONSISTENT ALTER REPLICATION ... FLUSH FROM XLOGFILE statement can be executed only in a consistent mode replication.
Cause: This statement can be executed only in a consistent mode replication.
Action: Check if the replication mode is consistent or not.
0x611A1 ( 397729) rpERR_ABORT_RPC_FAILED_FLUSH_XLOGFILE Failed to flush xlog files.
Cause: Internal error.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x611A2 ( 397730) rpERR_ABORT_RPC_CANNOT_FIND_REMOTE_META Cannot find the replication remote metadata.
Cause: Xlogfile recovery receiver must have a replication remote metadata.
Action:
-
Check if the replication has started after Altibase server startup.
-
A replication remote metadata is generated when the replication starts after Altibase server startup.
0x611A3 ( 397731) rpERR_ABORT_RPC_RECEIVER_IS_WORKING_ON_IT Xlogfile recovery cannot run while another receiver is working on synchronization or recovery.
Cause: Another receiver with same replication name is processing on synchronization or recovery.
Action: Check whether another receiver with same replication name is processing on synchronization or recovery.
0x611A4 ( 397732) rpERR_ABORT_RP_CANNOT_FIND_XLOGFILE Unable to find a xlogfile related with the replication name. (<0%s>)
Cause: If the replication has been started once in consistent mode, the xlogfile should exist as "xlogfile_repName_fileno". But the file cannot be found.
Action: Check the replication's name and verify that the xlogfile exists in XLOGFILE_DIR.
0x611A5 ( 397733) rpERR_ABORT_RPC_NOT_SUPPORT_FAILBACK_THIS_MODE Failback is not supported in this replication mode.
Cause: Failback is supported only in the consistent mode.
Action: Verify whether the replication mode is the consistent mode.
0x611A6 ( 397734) rpERR_ABORT_RPC_NOT_SUPPORT_RETRY_AND_CONSISTENT The retry option is not supported when a replication is running in the consistent mode.
Cause: The retry option is not supported in the consistent mode.
Action: Either remove the retry option or change the replication mode.
0x611A9 ( 397737) rpERR_ABORT_RP_RECEIVER_INITIALIZE_FAIL The receiver(%s) has not started, because the replication meta information has been changed.
Cause: The receiver has not started, because the replication meta has been changed.
Action: Restart the replication sender.
0x611AA ( 397738) rpERR_ABORT_RP_XLOG_FILE_FAILBACK_MASTER_SENDER_INITIALIZE_FAIL Failed to perform a failback, because the replication meta information has been changed.
Cause: Failed to perform a failback, because the replication meta information has been changed.
Action: Retry 'ALTER REPLICATION repl_name FAILBACK';
0x611AD ( 397741) rpERR_ABORT_OFFLINE_OPTION_IS_NOT_SET Offline option is not set.
Cause: Replication is created without the offline option.
Action: Check the options of the replication.
0x611AE ( 397742) rpERR_ABORT_OFFLINE_META_ROLE_NOT_SUPPORT Offline meta is supported only ANALYSIS.
Cause: This role does not support offline meta.
Action: Check the role of the replication.
0x611AF ( 397743) rpERR_ABORT_RPC_ROLE_NOT_SUPPORT_REPL_META_LOGGING Meta Logging option is supported only ANALYSIS.
Cause: This role does not support the Meta Logging option.
Action: Check the options or the role of the replication.
0x611B0 ( 397744) rpERR_ABORT_RP_REMOTE_META_EXIST BUILD OFFLINE META is already run.
Cause: Remote meta already exists.
Action: run 'ALTER REPLICATION replication_name RESET OFFLINE META;'
0x611B1 ( 397745) rpERR_ABORT_RP_REMOTE_META_FILE_IS_CORRUPTED Remote meta file is corrupt. (Meta End SN : <0%ld>, Restart SN : <1%ld>)
Cause: The 'replication_name_META_NEW.bin' file is corrupt. Restart SN is more than Meta End SN of 'replication_name_META_OLD.bin' file.
Action: Run 'ALTER REPLICATION replication_name BUILD OFFLINE META AT SN(sn)' with a value less than Meta End SN.
0x611B2 ( 397746) rpERR_ABORT_RP_ERR_REMOTE_META_NOT_BUILD_OFFLINE_META Remote meta is not from building offline meta.
Cause: Remote meta is not from building offline meta.
Action: Check the role of the replication.
0x611B3 ( 397747) rpERR_ABORT_ERR_NO_VALID_METAFILE Invalid sender meta files. (Replication name: <0%s>, File name: <1%s>_META_NEW.bin, <2%s>_META_OLD.bin )
Cause: Sender meta files do not exist or are invalid.
Action: 'BUILD OFFLINE META' failed. Verify the altibase_rp.log.
0x611B4 ( 397748) rpERR_ABORT_ERR_NO_VALID_SNFILE Invalid Restart SN files. (Replication name: <0%s>, File name: <1%s>_SN_NEW.bin, <2%s>_SN_OLD.bin )
Cause: Restart SN files do not exist or are invalid.
Action: 'BUILD OFFLINE META' failed. Verify the altibase_rp.log.
0x611B5 ( 397749) rpERR_ABORT_FAIL_TO_CREATE_DIRECTORY Failed to create meta directory (Dir Name :<0%s> )
Cause: The specified directory could not be created.
Action: Check the directory path or permission.
0x611B6 ( 397750) rpERR_ABORT_RP_OFFLINE_ALA_SENDER_PROCESS_DDL Offline ALA Sender read DDL log.
Cause: Offline ALA Sender read DDL log.
Action: After executing DDL on the target DB, Offline Adapter should be executed again.
0x611B8 ( 397752) rpERR_ABORT_TX_SEGMENT_ENTRY_ALLOC [Receiver] Transaction updating disk table data failed due to transaction segment allocation failure.
Cause: The number of transaction segments exceeds TRANSACTION_SEGMENT_COUNT
Action:
- 1. Increase the value of TRANSACTION_SEGMENT_COUNT property. - 2. Check the status of the replication receiver.
0x611B9 ( 397753) rpERR_ABORT_RP_DDL_SYNC_RETRY_ERROR Retry due to DDL Sync failure
Cause: Retry due to DDL Sync failure
Action: Wait until the success or stop DDL Sync.
0x611BA ( 397754) rpERR_ABORT_RP_DDL_SYNC_NOT_SUPPORT_GROUPING DDL Sync does not support replication's grouping option.
Cause: DDL Sync does not support replication's grouping option.
Action: Remove replication's grouping option.
0x611BF ( 397759) rpERR_ABORT_ERR_INVALID_METAFILE Invalid sender meta file. (Replication name: <0%s>, File name: <1%s>)
Cause: Sender meta file does not exist or is invalid.
Action: Verify the altibase_rp.log.
0x611C0 ( 397760) rpERR_ABORT_ERR_INVALID_SNFILE Invalid Restart SN file. (Replication name: <0%s>, File name: <1%s>)
Cause: Restart SN file does not exist or is invalid.
Action: Verify the altibase_rp.log.
0x611C1 ( 397761) rpERR_ABORT_INVALID_REPLICATION_SENDER_IP The value of REPLICATION_SENDER_IP is not valid. (<0%s>)
Cause: The value of REPLICATION_SENDER_IP must be an IP address.
Action: Change the value of REPLICATION_SENDER_IP in the altibase.properties file or ALTIBASE_REPLICATION_SENDER_IP environment variable and try again.
0x611C2 ( 397762) rpERR_ABORT_CANNOT_BE_EXEC_SENDER Unable to start the replication, when RECEIVE_ONLY option is set. Cause: RECEIVE_ONLY option is set.
Action: To start the replication, turn off the RECEIVE_ONLY option or recreate the replication.
0x611C3 ( 397763) rpERR_ABORT_CANNOT_MODIFY_RECEIVE_ONLY RECEIVE_ONLY option cannot be used since the replication has been started before.
Cause: Cannot change to the RECEIVE_ONLY option, because the replication has been started before.
Action: Reset or recreate the replication and try again.
0x611C4 ( 397764) rpERR_ABORT_RPC_ALREADY_RECEIVE_ONLY_UNSET RECEIVE_ONLY option is already unset.
Cause: RECEIVE_ONLY option is already unset.
Action: Check if RECEIVE_ONLY option is unset.
0x611C5 ( 397765) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_RECEIVE_ONLY_AND_EAGER RECEIVE_ONLY option cannot be used with eager mode.
Cause: RECEIVE_ONLY option is not supported with eager mode.
Action: Do not use RECEIVE_ONLY option in eager mode replication.
0x611C6 ( 397766) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_RECEIVE_ONLY_AND_GROUPING RECEIVE_ONLY option cannot be used with GROUPING option.
Cause: RECEIVE_ONLY option is not supported with GROUPING option.
Action: Do not use RECEIVE_ONLY option with GROUPING option.
0x611C7 ( 397767) rpERR_ABORT_RPC_ROLE_NOT_SUPPORT_RECEIVE_ONLY RECEIVE_ONLY option cannot be used with the clause for replication role.
Cause: RECEIVE_ONLY option is not supported with the clause for replication role.
Action: Do not use RECEIVE_ONLY option with the clause for replication role.
0x611C8 ( 397768) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_RECEIVE_ONLY_AND_DDLREPL RECEIVE_ONLY option cannot be used with DDL_REPLICATION.
Cause: RECEIVE_ONLY option is not supported with DDL_REPLICATION.
Action: Do not use RECEIVE_ONLY option with DDL_REPLICATION.
0x611C9 ( 397769) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_RECEIVE_ONLY_AND_GAPLESS RECEIVE_ONLY option cannot be used with GAPLESS option.
Cause: RECEIVE_ONLY option is not supported with GAPLESS option.
Action: Do not use RECEIVE_ONLY option with GAPLESS option.
0x611CA ( 397770) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_RECEIVE_ONLY_AND_RECOVERY RECEIVE_ONLY option cannot be used with REOCVERY option.
Cause: RECEIVE_ONLY option is not supported with REOCVERY option.
Action: Do not use RECEIVE_ONLY option with REOCVERY option.
0x611CB ( 397771) rpERR_ABORT_RPC_ALREADY_RECEIVE_ONLY_SET RECEIVE_ONLY option is already set.
Cause: RECEIVE_ONLY option is already set.
Action: Check if RECEIVE_ONLY option is set.
0x611CC ( 397772) rpERR_ABORT_CANNOT_CONNECT The host information of replication is invalid.
Cause: Unable to connect to the remote server due to the invalid host information.
Action: Check the host information of replication and retry.
0x611CD ( 397773) rpERR_ABORT_NOT_EXIST_HOSTS There is no host information in the replication.
Cause: The host of the replication do not exists. Unable to start the replication because host information of the replication does not exist.
Action: Add replication host in the replication and try again.
0x611CE ( 397774) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_RECEIVE_ONLY_AND_HOSTS RECEIVE_ONLY option cannot be used when host information of the replication exists.
Cause: RECEIVE_ONLY option cannot be used when host information of the replication exists.
Action: Check if host information of the replication exists.
0x611CF ( 397775) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_RECEIVE_ONLY_AND_MASTER RECEIVE_ONLY option cannot be used on master server.
Cause: RECEIVE_ONLY option is not supported with master server.
Action: Do not use RECEIVE_ONLY option on master server. If you want to use RECEIVE_ONLY option, check the restrictions of it from the Replication Manual.
0x611D0 ( 397776) rpERR_ABORT_RPC_NOT_SUPPORT_REPL_RECEIVE_ONLY_AND_METALOGGING RECEIVE_ONLY option cannot be used with META_LOGGING option.
Cause: RECEIVE_ONLY option is not supported with META_LOGGING option.
Action: Do not use RECEIVE_ONLY option with META_LOGGING option.
0x611D1 ( 397777) rpERR_ABORT_RP_DDL_SYNC_NOT_SUPPORT_RECEIVE_ONLY Unable to execute DDL for DDL synchronization, when RECEIVE_ONLY option is set.
Cause: DDL synchronization does not support when RECEIVE_ONLY option is set.
Action: To perform DDL Synchronization, turn off the replication RECEIVE_ONLY option and restart the replication.
0x611D2 ( 397778) rpERR_ABORT_RP_ABORT_SVP_WITHOUT_STMT [Receiver] smiTrans abort savepoint without statement error in run()
Cause: The replication receiver failed to abort to the savepoint.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
IGNORE#
0x62024 ( 401444) rpERR_IGNORE_RP_SENDER_HASH_INIT [Sender] Failed to initialize the hash table
Cause:
-
The replication feature of Altibase could not be used.
-
Replication was not initialized on startup because the port is not set correctly.
Action: Set the port correctly.
0x6204A ( 401482) rpERR_IGNORE_RECEIVER_START [Receiver] started ...
Cause: The receiver thread has already been started.
Action: You can safely ignore this message.
0x6204C ( 401484) rpERR_IGNORE_START_SENDER [Sender] Replication <0%s> Start... at [<1%ld>]
Cause: The replication started up correctly.
Action: N/A
0x62068 ( 401512) rpERR_IGNORE_RP_INIT_SOCK Unable to initialize a socket
Cause: Not enough memory. Unable to connect to a remote server.
Action: Check whether the remote server is running and online.
0x62070 ( 401520) rpERR_IGNORE_RP_PROTOCOL_DIFF Different replication protocols
Cause: The replication protocol is different from that on the peer server.
Action: Check the replication protocol version, endian, and 32/64 bit.
0x6209B ( 401563) rpERR_IGNORE_RP_META_DIFF Replication meta is different
Cause: The replication meta is different from that on the peer server.
Action: Check the Altibase version and the replication protocol version.
0x620CA ( 401610) rpERR_IGNORE_RP_NO_SPACE There is not available space for replication log buffer.
Cause: Replication is delayed or replication log buffer size is too small.
Action:
-
Increase REPLICATION_LOG_BUFFER_SIZE and restart the system.
-
Find and resolve cause of the delay.
0x620EB ( 401643) rpERR_IGNORE_EXIT_FLAG_SET Exit flag is set.
Cause: The exit flag has been set.
Action: Check the error number from the trace log and contact Altibase's Support Center (http://support.altibase.com).
0x620EE ( 401646) rpERR_IGNORE_NOT_ACITVE_TX The transaction does not exist in transaction table of the sender.
Cause: The Sender of the replication is not alone. Another Sender of the replication is processing the transaction.
Action: This is not an error of Altibase.
0x620F0 ( 401648) rpERR_IGNORE_RP_SENDER_STOP [Sender] Stop sender thread <0%s>:<1%u> at [<2%ld>], Restart SN[<3%ld>]
Cause: This error occurs when the replication Sender stops.
Action: You may safely ignore this message.
0x620F9 ( 401657) rpERR_IGNORE_TIMESTAMP_INSERT_CONFLICT [Receiver] An insert conflict occurred during timestamp conflict resolution.
Cause: The timestamp value of an XLog is older than an existing one.
Action: This behavior is normal and can be expected from time to time.
0x620FA ( 401658) rpERR_IGNORE_TIMESTAMP_UPDATE_CONFLICT [Receiver] An update conflict occurred during timestamp conflict resolution.
Cause: The timestamp value of an XLog is older than an existing one.
Action: This behavior is normal and can be expected from time to time.
RETRY#
0x631A8 ( 405928) rpERR_REBUILD_RPD_MISS_MATCH_LOCK_TABLE_AND_META The replication meta information has been changed.
Cause: The replication meta information has been changed.
Action: You may safely ignore this message.