9000 - 9499

These error codes indicate backup, restore, and STORAGE 3.0 errors.

ERROR 9001 (HY000): URI error

• OceanBase error code: 9001

• Cause: The destination URL specified for backup and restore is invalid.

• Solution: Check and modify the backup and restore configurations.

ERROR 9002 (HY000): OSS file MD5 error

• OceanBase error code: 9002

• Cause: Data verification of Object Storage Service (OSS) objects failed due to a data error in OSS.

• Solution: Contact OSS Technical Support for troubleshooting.

ERROR 9003 (HY000): OSS error

• OceanBase error code: 9003

• Cause: An unknown OSS error occurred.

• Solution: Contact OSS Technical Support for troubleshooting.

ERROR 9004 (HY000): Init MD5 fail

• OceanBase error code: 9004

• Cause: OpenSSL encountered an error when initializing MD5.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9005 (HY000): Out of element

• OceanBase error code: 9005

• Cause: The number of shards exceeds the upper limit.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9006 (HY000): Update MD5 fail

• OceanBase error code: 9006

• Cause: The MD5 update failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9007 (HY000): Invalid OSS file length

• OceanBase error code: 9007

• Cause: The length of the OSS object is not supported because the OSS object is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9010 (HY000): OSS file MD5 not match

• OceanBase error code: 9010

• Cause: An OSS object checksum mismatch occurred due to an OSS data error or a backup and restore program bug.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9011 (HY000): cannot find backup file

• OceanBase error code: 9011

• Cause: The backup file is not found because the specified backup and restore configurations are invalid.

• Solution: Check and modify the backup and restore configurations.

ERROR 9012 (HY000): Can not get data version from timestamp

• OceanBase error code: 9012

• Cause: No data version is passed by the logically recovered parameter.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9013 (HY000): Write OSS file error

• OceanBase error code: 9013

• Cause: The system encountered an error when writing data to the OSS object due to an unknown failure of OSS.

• Solution: Contact OSS Technical Support for troubleshooting.

ERROR 9014 (HY000): Another restore is in progress

• OceanBase error code: 9014

• Cause: A tenant with the same name as that of the tenant to be restored exists.

• Solution: Check whether the name of the tenant to be restored is already used. If yes, specify another name.

ERROR 9016 (HY000): ob cluster name not equal

• OceanBase error code: 9016

• Cause: The cluster name and URL for the logical backup are inconsistent.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9017 (HY000): rs list invalid

• OceanBase error code: 9017

• Cause: The specified RootServer list is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9018 (HY000): agent has failed task

• OceanBase error code: 9018

• Cause: A logical backup task failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9019 (HY000): restore partition is complete

• OceanBase error code: 9019

• Cause: A restore task is scheduled for a partition that has been restored.

• Solution: Troubleshooting is not required.

ERROR 9020 (HY000): restore partition twice

• OceanBase error code: 9020

• Cause: A restore task is scheduled for a partition that has been restored.

• Solution: Troubleshooting is not required.

ERROR 9022 (HY000): physical backup switch is on

• OceanBase error code: 9022

• Cause: Table deletion is delayed during physical backup.

• Solution: Troubleshooting is not required. The table will be automatically deleted after a physical backup task is completed.

ERROR 9023 (HY000): cannot start log archive backup

• OceanBase error code: 9023

• Cause: The log archiving task cannot be initiated when another log archiving task is in progress.

• Solution: Do not repeatedly schedule the command that initiates the log archiving.

ERROR 9024 (HY000): log archive backup is already disabled

• OceanBase error code: 9024

• Cause: A log archiving task in the Stopped state cannot be stopped again.

• Solution: Do not attempt to stop a log archiving task in the Stopped state.

ERROR 9025 (HY000): log archive backup info not exists

• OceanBase error code: 9025

• Cause: The log archiving file does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9026 (HY000): %s is not a valid uri

• OceanBase error code: 9026

• Cause: The specified backup destination is invalid.

• Solution: Check the backup_dest parameter and make sure that the path specified for backup_dest is valid.

ERROR 9026 (HY000): %s is not a valid uri

• OceanBase error code: 9026

• Cause: The specified backup destination is invalid.

• Solution: Check the backup_dest parameter and make sure that the path specified for backup_dest is valid.

ERROR 9027 (HY000): ob log archive interrupted

• OceanBase error code: 9027

• Cause: Log archiving is interrupted.

• Solution: Check whether a large number of logs are being written. If not, contact OceanBase Technical Support for troubleshooting.

ERROR 9028 (HY000): ob log archive stat not match

• OceanBase error code: 9028

• Cause: The log archiving status is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9029 (HY000): log archive is not running

• OceanBase error code: 9029

• Cause: Log archiving is not running. Generally, this error is reported on the OBServer node when you stop backup.

• Solution: This code does not indicate an error. No manual intervention is required.

ERROR 9030 (HY000): log archive invalid round

• OceanBase error code: 9030

• Cause: The round information of the log archiving task is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9031 (HY000): Cannot backup ob replica

• OceanBase error code: 9031

• Cause: The replica is being migrated or replicated or is a log-only replica, and therefore cannot be used for data backup.

• Solution: OceanBase Database will automatically retry the operation, and no manual intervention is required.

ERROR 9032 (HY000): backup info not exists

• OceanBase error code: 9032

• Cause: The backup information does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9033 (HY000): Backup meta info stored in system dictionary does not match with current system status

• OceanBase error code: 9033

• Cause: A backup status inconsistency error occurred.

• Solution:

  • If this error is returned for OBServer node log archiving, it usually occurs when log archiving is started or stopped. In this case, no manual intervention is required.

  • If this error is returned for RootService log archiving, contact OceanBase Technical Support for troubleshooting.

ERROR 9035 (HY000): restore index failed

• OceanBase error code: 9035

• Cause: The index rebuild operation failed after the restore was completed.

• Solution: Find the table index in the error state under the restored tenant and rebuild the index.

ERROR 9036 (HY000): Backup is in progress

• OceanBase error code: 9036

• Cause: An operation mutually exclusive with backup was performed.

• Solution: Stop data backup and log archiving and perform the operation again.

ERROR 9037 (HY000): log archive status is not valid

• OceanBase error code: 9037

• Cause: The log archiving status is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9038 (HY000): Cannot add replica during set member list in restore

• OceanBase error code: 9038

• Cause: Replication is not supported in the set member list phase.

• Solution: Replicas cannot be replicated in the set member list phase during restore. If the majority of replicas exist, the restore task can continue. If the majority of replicas no longer exist, cancel the current restore task and schedule a new restore task.

ERROR 9039 (HY000): pg log archive leader changed

• OceanBase error code: 9039

• Cause: The leader for log archiving has been switched.

• Solution: This is an internal error code. A leader switchover interrupts the log archiving process of the current partition group. The new leader will automatically proceed with the backup without the need for manual intervention.

ERROR 9040 (HY000): backup can not start

• OceanBase error code: 9040

• Cause: The log archiving task is not in the DOING state, and data backup cannot be initiated.

• Solution: Wait until the log archiving task enters the DOING state. If the log archiving task remains in the BEGINNING state, contact OceanBase Technical Support for troubleshooting.

ERROR 9041 (HY000): cancel backup do not allow

• OceanBase error code: 9041

• Cause: The backup task cannot be repeatedly canceled.

• Solution: Do not repeatedly cancel a task that is being canceled.

ERROR 9042 (HY000): backup data version gap over limit

• OceanBase error code: 9042

• Cause: Data backup is not completed within 16 rounds of major compactions.

• Solution: Analyze the cause of slow data backup or check whether major compactions are performed too frequently.

ERROR 9044 (HY000): delete backup data is in progress

• OceanBase error code: 9044

• Cause: The backup cleanup task cannot be repeatedly scheduled.

• Solution: Do not repeatedly schedule the backup cleanup task.

ERROR 9045 (HY000): delete backup set do not allow

• OceanBase error code: 9045

• Cause: The backup set cannot be deleted.

• Solution: Do not enter the command to delete the backup set.

ERROR 9046 (HY000): backup set id is not valid

• OceanBase error code: 9046

• Cause: The specified backup set ID is invalid.

• Solution: Specify a valid backup_set_id value and try again.

ERROR 9047 (HY000): invalid password for backup

• OceanBase error code: 9047

• Cause: The entered password is invalid.

• Solution: Enter the valid password and try again.

ERROR 9048 (HY000): backup set is isolated by two log archive round

• OceanBase error code: 9048

• Cause: Data backup and log archiving are discontinuous.

• Solution: Check whether log archiving is interrupted.

ERROR 9049 (HY000): backup status is stopped, can not cancel

• OceanBase error code: 9049

• Cause: The backup task has been stopped and cannot be canceled again.

• Solution: Troubleshooting is not required.

ERROR 9050 (HY000): no backup data to be backuped up

• OceanBase error code: 9050

• Cause: No data needs to be backed up by the scheduled backup task.

• Solution: This error usually occurs during backup. Troubleshooting is not required.

ERROR 9051 (HY000): backup mount file is not valid

• OceanBase error code: 9051

• Cause: The network file system (NFS) is not mounted to some OBServer nodes.

• Solution: Make sure that the NFS is mounted to all OBServer nodes.

ERROR 9052 (HY000): backup clean info not match

• OceanBase error code: 9052

• Cause: The backup cleanup task encountered a metadata inconsistency error.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9053 (HY000): cancel delete backup do not allow

• OceanBase error code: 9053

• Cause: The cancel operation is initiated when no cleanup task is available.

• Solution: Do not initiate the cancel operation when no cleanup task is available.

ERROR 9054 (HY000): backup clean info not exists

• OceanBase error code: 9054

• Cause: The metadata of the backup cleanup task does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9057 (HY000): can not set backup region, because %s

• OceanBase error code: 9057

• Cause: The backup region cannot be modified.

• Solution: Record the error message and contact OceanBase Technical Support for troubleshooting.

ERROR 9058 (HY000): can not set backup zone, because %s

• OceanBase error code: 9058

• Cause: The backup zone cannot be modified.

• Solution: Record the error message and contact OceanBase Technical Support for troubleshooting.

ERROR 9059 (HY000): backup backup has reached max backup times

• OceanBase error code: 9059

• Cause: An internal error occurred. This code is returned if all the existing backup sets or backup pieces have reached the threshold of backup times during secondary backup scheduling.

• Solution: Troubleshooting is not required.

ERROR 9060 (HY000): COS error

• OceanBase error code: 9060

• Cause: The module to adapt to Cloud Object Storage (COS) of Tencent Cloud encountered an error.

• Solution: This code is returned if a logic error occurs in the adaptation between OceanBase Database and COS. Contact OceanBase Technical Support for troubleshooting.

ERROR 9061 (HY000): IO limit

• OceanBase error code: 9061

• Cause: Throttling is triggered on I/O operations. Currently, this code is returned only for the List operation of COS.

• Solution: Contact COS Technical Support to increase or remove the throttling threshold for the List operation.

ERROR 9062 (HY000): reach backup backup copy limit

• OceanBase error code: 9062

• Cause: When the system schedules secondary backup tasks based on the specified backup times, all backup sets and backup pieces have reached the threshold of backup times, and no backup set or backup piece requires secondary backup.

• Solution: Troubleshooting is not required.

ERROR 9063 (HY000): backup io is prohibited

• OceanBase error code: 9063

• Cause: Throttling is triggered on the List operation performed during backup and restore in the COS-based environment.

• Solution:

  • If this error occurs occasionally, troubleshooting is not required.

  • If this error occurs frequently, contact COS Technical Support to increase or remove the throttling threshold for the List operation.

ERROR 9064 (HY000): the archive log and backup data are not continuous

• OceanBase error code: 9064

• Cause: The archived log data and original backup data are discontinuous.

• Solution:

  • For OceanBase Database V2.2.X, initiate a new major compaction and then a new data backup task.

  • For OceanBase Database V3.1.X and later versions, initiate a new data backup task.

ERROR 9065 (HY000): agent has suspended

• OceanBase error code: 9065

• Cause: This error code is returned when the backup process is suspended during a logical backup and restore task.

• Solution: This error does not affect the system functionality. You can restart the logical backup later.

ERROR 9069 (HY000): deleting backup piece is not allowed

• OceanBase error code: 9069

• Cause: The backup piece cannot be deleted.

• Solution: Do not enter the command to delete the backup set.

ERROR 9070 (HY000): can not connect to backup destination

• OceanBase error code: 9070

• Cause: The OBServer node is not connected to the backup media. For example, the NFS is not mounted, or OSS does not have access privilege.

• Solution: Correctly mount the NFS, specify the correct authorization information for the OSS, or grant the necessary operation privileges.

ERROR 9071 (HY000): no I/O operation permission at the backup destination

• OceanBase error code: 9071

• Cause: The OBServer node does not have privileges to perform operations on the backup media.

• Solution: Grant privileges for operations that were unauthorized.

ERROR 9072 (HY000): obesi process session conflicts

• OceanBase error code: 9072

• Cause: The sessions of the independent backup I/O subprocesses conflict.

• Solution: Troubleshooting is not required.

ERROR 9073 (HY000): external storage OBS error

• OceanBase error code: 9073

• Cause: An error occurred to the storage media when the backup media is Object Storage Service (OBS) of HUAWEI CLOUD.

• Solution: Check whether the connection and data writes to the HUAWEI CLOUD OBS are normal.

ERROR 9074 (HY000): backup validation task skipped

• OceanBase error code: 9074

• Cause: The backup verification of the deleted tenant is skipped.

• Solution: Troubleshooting is not required.

ERROR 9075 (HY000): obesi process io error

• OceanBase error code: 9075

• Cause: The backup and restore I/O failed due to the unusual status of the obesi process.

• Solution: Troubleshooting is not required.

ERROR 9076 (HY000): backup meta index does not exist

• OceanBase error code: 9076

• Cause: The metadata index of the backup data does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9077 (HY000): log discontinuous between two archive rounds

• OceanBase error code: 9077

• Cause: The rounds of two consecutively read archived logs are not continuous.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9078 (HY000): archive log is to end

• OceanBase error code: 9078

• Cause: The continuous read of the archived logs has reached the end.

• Solution: Troubleshooting is not required.

ERROR 9079 (HY000): archive log had been recycled

• OceanBase error code: 9079

• Cause: The archived logs are already recycled when the continuous log read is performed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9080 (HY000): the format file does not exist under the destination

• OceanBase error code: 9080

• Cause: The format file does not exist in the backup destination. Possible scenarios:

  • The format file is removed from the destination before the backup task.
  • The specified destination is not empty but does not contain the format file.

• Solution: Check whether the format file exists in the backup destination. If not, the destination is invalid. When you specify a new destination directory, you must clear the directory before writing the backup to the destination.

ERROR 9081 (HY000): the content of the format file at the destination does not match

• OceanBase error code: 9081

• Cause: The backup destination specified in the format file does not match the actual backup destination. Possible scenarios:

  • You have specified the destination of another cluster, tenant, or backup type.
  • The format file in the backup destination is damaged.

• Solution: Make sure that the specified backup information matches the actual cluster, tenant, or backup type to be backed up.

ERROR 9082 (HY000): backup device out of space

• OceanBase error code: 9082

• Cause: The storage space of the backup disk is insufficient.

• Solution: Scale out the storage space for the backup.

ERROR 9083 (HY000): the pwrite offset of the object storage is inconsistent

• OceanBase error code: 9083

• Cause: The offset for file appending during backup and restore does not match the file size.

• Solution: Troubleshooting is not required.

ERROR 9084 (HY000): the contents of pwrite are inconsistent

• OceanBase error code: 9084

• Cause: The appended file content during backup and restore does not match the existing file content.

• Solution: Troubleshooting is not required.

ERROR 9085 (HY000): backup major SSTable range not cover minor SSTable

• OceanBase error code: 9085

• Cause: The backup scope of the major SSTables does not cover the minor SSTables.

• Solution: Troubleshooting is not required. The system will retry during the backup.

ERROR 9086 (HY000): backup advance checkpoint by flush timeout

• OceanBase error code: 9086

• Cause: The push of the log stream checkpoint timed out during the backup.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9087(HY000): observer clog is recycled before archive

• OceanBase error code: 9087
• Cause: The archived files have been recycled when they are consumed.

ERROR 9088 (HY000): log restore source tenant state not match, switchover to primary not allowed

• OceanBase error code: 9088
• Cause: The status of the source tenant for log restoration or the log stream does not match that of the destination tenant. The current tenant cannot be switched to the primary tenant.
• Solution:
  1. Make sure that the status of the source tenant for backup and restoration matches that of the destination tenant.
  2. Make sure that the leader-follower replication settings are correct.
  3. Make sure that the backup of the source tenant is complete and the restoration of the destination tenant is correct.

ERROR 9089 (HY000): log restore source ls state not match, switchover to primary not allowed

• OceanBase error code: 9089
• Cause: The status of the source tenant for log restoration or the log stream does not match that of the destination tenant. The current tenant cannot be switched to the primary tenant.
• Solution:
  1. Make sure that the status of the source logs for backup and restoration matches that of the destination logs.
  2. Make sure that the leader-follower replication settings are correct.
  3. Make sure that the backup of the source logs is complete and the restoration of the destination logs is correct.

ERROR 9090 (HY000): obesi process session not exist

• OceanBase error code: 9090

• Cause: The obesi process session does not exist.

• Solution: The obesi process restarts automatically. No manual intervention is required.

ERROR 9091 (HY000): Already in ARCHIVELOG mode

• OceanBase error code: 9091

• Cause: The status is already ARCHIVELOG.

• Solution: This is a status prompt. No manual intervention is required.

ERROR 9092 (HY000): Already in NOARCHIVELOG mode

• OceanBase error code: 9092

• Cause: The status is already NOARCHIVELOG.

• Solution: This is a status prompt. No manual intervention is required.

ERROR 9096 (HY000): standby binary version is lower than primary data version, standby need upgrade

• OceanBase error code: 9096
• Cause: The version of the standby cluster is earlier than that of the primary cluster.
• Solution: Upgrade the version of the standby cluster to that of the primary cluster.

ERROR 9097 (HY000): primary tenant has been dropped

• OceanBase error code: 9097
• Cause: The primary tenant is deleted during the primary/standby cluster synchronization.
• Solution: Check the tenant information of the primary cluster and make sure that the primary tenant exists.

ERROR 9098 (HY000): normal object in object_storage(oss,cos,etc.) can't be appended content

• OceanBase error code: 9098
• Cause: An error occurred during the attempt to append content to a normal object in an object storage instance, such as an Alibaba Cloud OSS bucket or a COS instance.
• Solution: Make sure that the object storage instance type in use supports appending content to a normal object.

ERROR 9100 (HY000): no such file or directory

• OceanBase error code: 9100

• Cause: The specified directory or file is not found in the storage layer. This may be because the configuration is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9101 (HY000): file or directory already exist

• OceanBase error code: 9101

• Cause: The specified file or directory already exists.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

ERROR 9200 (HY000): Extend ssblock file to smaller is not allowed

• OceanBase error code: 9200

• Cause: The size of the SSBlock file cannot be reduced.

• Solution: Make sure that the value specified by ALTER SYSTEM SET datafile_size is larger than the current SSBlock file size, or contact OceanBase Technical Support for troubleshooting.

ERROR 9201 (HY000): Mark blocks timeout(5s) in auto extend process when alloc block fail

• OceanBase error code: 9201

• Cause: After the automatic scaling of the SSBlock file, the macroblocks cannot be labeled.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9202 (HY000): Auto extend param is not ready to start extending file

• OceanBase error code: 9202

• Cause: The automatic disk scaling does not start due to possible configuration issues or because the disk usage has reached the upper limit specified by datafile.

• Solution: Check whether the value of the free_size field in the __all_virtual_disk_stat table is 0. If yes, the disk space is exhausted. You must increase the datafile threshold or disk size.