9000 to 9499

This range indicates backup and restore error codes and STORAGE 3.0 error codes.

ERROR 9001 (HY000): URI error

• OceanBase error code: 9001

• Cause: The destination link for backup and restore is incorrect.

• Solution: Check the backup and restore configurations and make the necessary modifications.

ERROR 9002 (HY000): OSS file MD5 error

• OceanBase error code: 9002

• Cause: The data of the OSS file is corrupted, or the data on OSS is abnormal.

• Solution: Contact OSS technical support for troubleshooting.

ERROR 9003 (HY000): OSS error

• OceanBase error code: 9003

• Cause: An unknown error occurred on OSS.

• Solution: Contact OSS technical support for troubleshooting.

ERROR 9004 (HY000): Init MD5 fail

• OceanBase error code: 9004

• Cause: An error occurred while initializing MD5 by OpenSSL.

• Solution: Contact OceanBase technical support for troubleshooting.

ERROR 9005 (HY000): Out of element

• OceanBase error code: 9005

• Cause: The number of shards exceeds the limit.

• Solution: Contact OceanBase technical support for troubleshooting.

ERROR 9006 (HY000): Update MD5 fail

• OceanBase error code: 9006

• Cause: An error occurred while updating MD5.

• Solution: Contact OceanBase technical support for troubleshooting.

ERROR 9007 (HY000): Invalid OSS file length

• OceanBase error code: 9007

• Cause: The OSS file length is invalid. The OSS file may be incorrect.

• Solution: Contact OceanBase technical support for troubleshooting.

ERROR 9010 (HY000): OSS file MD5 not match

• OceanBase error code: 9010

• Cause: The checksum of the OSS file does not match, which means that the data on OSS is abnormal or there is a bug in the backup and restore program.

• Solution: Contact OceanBase technical support for troubleshooting.

ERROR 9011 (HY000): cannot find backup file

• OceanBase error code: 9011

• Cause: The backup file cannot be found, which means that the specified backup and restore configurations are incorrect.

• Solution: Check the backup and restore configurations and make the necessary modifications.

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

• OceanBase error code: 9012

• Cause: The parameter data version is not passed in the logic restore method.

• Solution: Contact OceanBase technical support for troubleshooting.

ERROR 9013 (HY000): Write OSS file error

• OceanBase error code: 9013

• Cause: An unexpected error occurred while writing to the OSS file, which means that an unknown issue occurred on 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 the one being restored exists.

• Solution: Check whether the username of the restoring tenant is duplicated. If yes, use a non-duplicate username.

ERROR 9016 (HY000): ob cluster name not equal

• OceanBase error code: 9016

• Cause: The cluster name in the logic backup does not match the URL.

• Solution: Contact OceanBase technical support for troubleshooting.

ERROR 9017 (HY000): rs list invalid

• OceanBase error code: 9017

• Cause: The RS list is invalid. The specified RS list may be incorrect.

• Solution: Contact OceanBase technical support for troubleshooting.

ERROR 9018 (HY000): agent has failed task

• OceanBase error code: 9018

• Cause: The logic backup has failed tasks.

• Solution: Contact OceanBase technical support for troubleshooting.

ERROR 9019 (HY000): restore partition is complete

• OceanBase error code: 9019

• Cause: A restore task was scheduled again for a partition that has already been restored.

• Solution: No action is required.

ERROR 9020 (HY000): restore partition twice

• OceanBase error code: 9020

• Cause: A restore task was scheduled again for a partition that has already been restored.

• Solution: No action is required.

ERROR 9022 (HY000): physical backup switch is on

• OceanBase error code: 9022

• Cause: The delayed deletion of tables is performed during physical backup.

• Solution: No action is required. The table is deleted automatically after physical backup completes.

ERROR 9023 (HY000): cannot start log archive backup

• OceanBase error code: 9023

• Cause: Log archiving cannot be started again while log archiving is in progress.

• Solution: Avoid scheduling the log archiving start command repeatedly.

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

• OceanBase error code: 9024

• Cause: Log archiving in the STOP phase cannot be disabled again.

• Solution: Avoid disabling log archiving that has already been disabled.

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

• OceanBase error code: 9025

• Cause: The log archive information 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 backup destination is invalid.

• Solution: Check whether backup_dest is valid and provide an available backup_dest path.

ERROR 9027 (HY000): ob log archive interrupted

• OceanBase error code: 9027

• Cause: Log archiving was interrupted.

• Solution: Check whether heavy writes prevent log archiving from keeping up. If not, contact OceanBase technical support for troubleshooting.

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

• OceanBase error code: 9028

• Cause: The log archive status does not match.

• 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. This error is usually logged by an OBServer node when backup is being stopped.

• Solution: No manual intervention is required. This is a normal error log when log archiving exits.

ERROR 9030 (HY000): log archive invalid round

• OceanBase error code: 9030

• Cause: The log archive round information is incorrect.

• 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 is a log replica, and therefore cannot provide data backup services.

• Solution: OceanBase Database will internally retry the request. No manual intervention is needed.

ERROR 9032 (HY000): backup info not exists

• OceanBase error code: 9032

• Cause: The backup information does not exist.

• Solution: Contact OceanBase technical support for help.

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

• OceanBase error code: 9033

• Cause: The status of the backup is inconsistent.

• Solution:

  • If the error occurred during log archive of an OBServer node, it is generally caused by the start or stop of log archive. In this case, no manual intervention is needed.

  • If the error occurred during log archive of the RootService, contact OceanBase technical support for help.

ERROR 9035 (HY000): restore index failed

• OceanBase error code: 9035

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

• Solution: Check the indexes with the error state in the internal tables of the restore tenant and recreate the indexes.

ERROR 9036 (HY000): Backup is in progress

• OceanBase error code: 9036

• Cause: Generally, this error occurs when you perform an operation that conflicts with a backup.

• Solution: Run the command again after the data backup and log archive are stopped.

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

• OceanBase error code: 9037

• Cause: The status of the log archive is illegal.

• Solution: Contact OceanBase technical support for help.

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

• OceanBase error code: 9038

• Cause: Replication is not supported during the set member list phase of the restore.

• Solution: Replication is not supported during the set member list step of restore. If a majority of replicas still exists, restore can continue; if not, cancel the restore and reschedule the restore task.

ERROR 9039 (HY000): pg log archive leader changed

• OceanBase error code: 9039

• Cause: The log archive leader has switched.

• Solution: Internal error code. After detecting a leader switchover, the current PG will be interrupted. The new leader will automatically continue the backup work without O&M intervention.

ERROR 9040 (HY000): backup can not start

• OceanBase error code: 9040

• Cause: The log archive is not in the DOING state, and therefore data backup cannot be started.

• Solution: Wait for the log archive to enter the DOING state. If it stays in the BEGINNING state for a long time, contact OceanBase technical support for help.

ERROR 9041 (HY000): cancel backup do not allow

• OceanBase error code: 9041

• Cause: You cannot cancel a backup task that is being canceled.

• Solution: Make sure that you do not cancel a task that is being canceled.

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

• OceanBase error code: 9042

• Cause: Data backup fails automatically if it is not completed within 16 major compactions.

• Solution: Identify why data backup is slow or whether major compaction occurs too frequently.

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

• OceanBase error code: 9044

• Cause: Scheduling a backup cleanup task repeatedly is not allowed.

• Solution: Avoid scheduling backup cleanup tasks repeatedly.

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

• OceanBase error code: 9045

• Cause: Deleting the backup set is not allowed.

• Solution: Check whether an incorrect delete command was entered.

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

• OceanBase error code: 9046

• Cause: The backup set ID is invalid. An invalid backup_set_id may have been specified.

• Solution: Check whether the entered backup_set_id is correct and try again.

ERROR 9047 (HY000): invalid password for backup

• OceanBase error code: 9047

• Cause: The password is invalid.

• Solution: Check whether the password is correct 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 not continuous.

• Solution: Check whether log archiving has been interrupted.

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

• OceanBase error code: 9049

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

• Solution: No additional action is required. The backup has already stopped.

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

• OceanBase error code: 9050

• Cause: The scheduled backup task has no data to back up.

• Solution: This usually occurs in backup scenarios. No action is required.

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

• OceanBase error code: 9051

• Cause: One or more OBServer nodes have not mounted NFS.

• Solution: Make sure that NFS is mounted on all nodes.

ERROR 9052 (HY000): backup clean info not match

• OceanBase error code: 9052

• Cause: The backup cleanup metadata is inconsistent.

• Solution: Contact OceanBase technical support for troubleshooting.

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

• OceanBase error code: 9053

• Cause: Cancel was issued when no cleanup task was running.

• Solution: Avoid issuing Cancel when no cleanup task is running.

ERROR 9054 (HY000): backup clean info not exists

• OceanBase error code: 9054

• Cause: The cleanup metadata 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: Internal error code. Returned during internal backup scheduling when both the backup set and backup piece have reached the maximum backup times.

• Solution: No action is required.

ERROR 9060 (HY000): COS error

• OceanBase error code: 9060

• Cause: An error occurred in the Tencent Cloud COS module.

• Solution: This error is usually caused by logic errors in the process of adapting OceanBase Database to COS. Contact OceanBase Technical Support.

ERROR 9061 (HY000): IO limit

• OceanBase error code: 9061

• Cause: This is an IO restriction. Currently, only the List operation in the Tencent Cloud COS module returns this error code.

• Solution: Contact the customer support team of COS to increase or remove the IO restriction on the List operation.

ERROR 9062 (HY000): reach backup backup copy limit

• OceanBase error code: 9062

• Cause: The backup task cannot find any backup set or backup piece that meets the backup requirements of the specified backup time. In other words, all backup sets and backup pieces have met the backup requirements of the specified backup time.

• Solution: No action is required.

ERROR 9063 (HY000): backup io is prohibited

• OceanBase error code: 9063

• Cause: The List operation in the COS environment is being rate-limited during backup or restore.

• Solution:

  • If this error occurs occasionally, no action is required.

  • If this error frequently occurs, contact the customer support team of the backup COS to increase or remove the rate limit on the List operation.

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

• OceanBase error code: 9064

• Cause: The archived logs or backup data are discontinuous.

• Solution:

  • V2.2.X: Perform a major compaction and then initiate a data backup again.

  • V3.1.X and later: Initiate a data backup again.

ERROR 9065 (HY000): agent has suspended

• OceanBase error code: 9065

• Cause: This error code is returned when the backup suspension feature of the logic backup and restore is enabled during the execution of a task.

• Solution: This error code does not affect the feature. The logic backup will be suspended. After the suspension is enabled, it can be disabled again.

ERROR 9066 (HY000): %.*s conflicts with %.*s

• OceanBase error code: 9066

• Cause: Conflicting values are detected.

• Solution: Check the conflicting values and ensure that they do not conflict with other values.

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

• OceanBase error code: 9069

• Cause: Deleting a backup log shard is not allowed.

• Solution: Check whether you have entered the correct delete command.

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

• OceanBase error code: 9070

• Cause: Some OBServer nodes cannot communicate with the backup media. For example, NFS is not mounted or the object storage does not have access permissions.

• Solution: Mount NFS correctly, or set the correct authorization information for object storage or grant the necessary operation permissions.

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

• OceanBase error code: 9071

• Cause: The OBServer node does not have the permissions to operate on the backup media.

• Solution: Grant the required permissions to the operation.

ERROR 9072 (HY000): obesi process session conflicts

• OceanBase error code: 9072

• Cause: A session conflict occurred between the backup I/O independent sub-process and another process.

• Solution: No action is required.

ERROR 9073 (HY000): external storage OBS error

• OceanBase error code: 9073

• Cause: When the backup media is Huawei Cloud OBS, a storage media-level error occurred.

• Solution: Check whether Huawei Cloud OBS is connected and write-enabled. If the problem persists, contact technical support.

ERROR 9074 (HY000): backup validation task skipped

• OceanBase error code: 9074

• Cause: The backup validation task is skipped after the tenant is deleted.

• Solution: No action is required.

ERROR 9075 (HY000): obesi process io error

• OceanBase error code: 9075

• Cause: An I/O failure occurred during backup and restore because the obesi process encountered an abnormal state.

• Solution: No action is 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 technical support for help.

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

• OceanBase error code: 9077

• Cause: A discontinuity was found between two rounds of continuous logs when they were being read.

• Solution: Contact technical support for help.

ERROR 9078 (HY000): archive log is to end

• OceanBase error code: 9078

• Cause: The reading of archive logs has reached the end.

• Solution: No action is required.

ERROR 9079 (HY000): archive log had been recycled

• OceanBase error code: 9079

• Cause: The archive log that is being read has been recycled.

• Solution: Contact technical support for help.

ERROR 9080 (HY000): format file does not exist%s

• OceanBase error code: 9080

• Cause: The format file at the backup destination does not exist. The possible causes are as follows:

  • The format file is removed before the destination participates in a backup task.
  • The specified destination is not empty, and it does not contain a format file.

• Solution: Check whether the format file exists at the backup destination. If it does not, the destination is no longer valid. When you set a new destination, clear all files in the destination before adding it to backup.

ERROR 9081 (HY000): format file does not match%s

• OceanBase error code: 9081

• Cause: The format file information at the backup destination does not match. The possible causes are as follows:

  • When you set the destination, you use a destination that belongs to another cluster, tenant, or backup type.
  • The format file at the destination is corrupted.

• Solution: Verify that the cluster, tenant, and backup type of the destination match those of the backup task. If they do not match, use the correct destination.

ERROR 9082 (HY000): backup device out of space

• OceanBase error code: 9082

• Cause: The backup disk is full.

• Solution: Expand the backup disk space.

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

• OceanBase error code: 9083

• Cause: The offset of the pwrite file in object storage does not match the file length.

• Solution: No action is required.

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

• OceanBase error code: 9084

• Cause: The content of the pwrite file in object storage does not match the existing file content.

• Solution: No action is required.

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

• OceanBase error code: 9085

• Cause: The range of the major SSTable does not cover that of the minor SSTable.

• Solution: No action is required. The backup system will retry internally.

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

• OceanBase error code: 9086

• Cause: Advancing the log stream checkpoint timed out during backup.

• Solution: Contact the technical support team for help.

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

• OceanBase error code: 9087
• Cause: The archive file was recycled while archive consumption was in progress.

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

• OceanBase error code: 9088
• Cause: The log restore source tenant/log stream state does not match. Switching the current tenant to primary is not allowed.
• Solution:
  1. Check whether the source and target tenant states for backup and restore match.
  2. Check whether the primary/standby replication configuration is correct.
  3. Check whether the source tenant backup is complete and whether the target tenant restore is correct.

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

• OceanBase error code: 9089
• Cause: The log restore source tenant/log stream state does not match. Switching the current tenant to primary is not allowed.
• Solution:
  1. Check whether the source and target log states for backup and restore match.
  2. Check whether the primary/standby replication configuration is correct.
  3. Check whether the source log backup is complete and whether the target log restore 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 will automatically restart. No manual intervention is required.

ERROR 9091 (HY000): Already in ARCHIVELOG mode

• OceanBase error code: 9091

• Cause: The database is already in ARCHIVELOG mode.

• Solution: This is a status notification. No action is required.

ERROR 9092 (HY000): Already in NOARCHIVELOG mode

• OceanBase error code: 9092

• Cause: The database is already in NOARCHIVELOG mode.

• Solution: This is a status notification. No action is required.

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

• OceanBase error code: 9096
• Cause: The standby database version is behind the primary database version.
• Solution: Check the standby and primary database versions and wait for the standby upgrade to complete.

ERROR 9097 (HY000): primary tenant has been dropped

• OceanBase error code: 9097
• Cause: The primary tenant is deleted during primary/standby synchronization.
• Solution: Check whether the primary tenant exists in the primary database.

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

• OceanBase error code: 9098
• Cause: An error occurred while attempting to append content to a normal object in object storage (OSS, COS, etc.).
• Solution: Check the type of object storage. Make sure that the type supports appending content to a normal object.

ERROR 9099 (HY000): %s restore failed, %s

• OceanBase error code: 9099

• Cause: The restore operation failed.

• Solution: Check the restore configuration and parameters to ensure that they meet the requirements and expectations of the restore destination.

ERROR 9100 (HY000): no such file or directory

• OceanBase error code: 9100

• Cause: The storage layer cannot find the corresponding directory or file. The configuration of the storage directory may be incorrect.

• Solution: Contact technical support for help.

ERROR 9101 (HY000): file or directory already exist

• OceanBase error code: 9101

• Cause: The corresponding file or directory already exists.

• Solution: This is an internal error code. Contact technical support for help.

ERROR 9132 (HY000): object storage data checksum error

• OceanBase error code: 9132

• Cause: The object storage data checksum is incorrect.

• Solution: This is an internal error code. Contact technical support for help.

ERROR 9135 (HY000): tmp file exceeds disk quota

• OceanBase error code: 9135

• Cause: The temporary file size exceeds the disk quota limit.

• Solution: Check disk space usage and investigate slow SQL to identify what is generating large temporary files. If the data volume is expected, increase the temporary_file_max_disk_size parameter to adjust the temporary file limit.

ERROR 9140 (HY000): the object is locked by worm

• OceanBase error code: 9140

• Cause: An attempt is made to delete or modify an object in object storage that is in the retention period.

• Solution: Check whether the backup or archive path is configured with a retention policy and whether the enable_worm parameter is correctly configured when you set the backup or archive path. If enable_worm is correctly configured, contact OceanBase technical support for help.

ERROR 9142 (HY000): the object can not be overwritten with different content

• OceanBase error code: 9142

• Cause: A non-idempotent file with the same name is written to object storage that is configured with a retention policy.

• Solution: Contact OceanBase technical support for help.

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

• OceanBase error code: 9200

• Cause: SSBlock files cannot be shrunk.

• Solution: Check whether the size specified in ALTER SYSTEM SET datafile_size is greater than the current SSBlock file size. If not, contact technical support for help.

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

• OceanBase error code: 9201

• Cause: Macroblocks cannot be marked after the SSBlock file is automatically expanded.

• Solution: Contact technical support for help.

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

• OceanBase error code: 9202

• Cause: Automatic expansion may not be enabled due to configuration issues, or the preset disk usage of datafile has reached its upper limit.

• Solution: Check whether the free_size field in the __all_virtual_disk_stat table is 0. If yes, disk space is exhausted. Increase the datafile threshold or expand the disk.

ERROR 9129 (HY000): object storage io error

• OceanBase error code: 9129

• Cause: An object storage error occurred. Common causes include connectivity and compatibility issues with object storage.

• Solution: Check object storage connectivity. After confirming that connectivity is normal, contact technical support for help.

ERROR 9133 (HY000): locality do not exist in locality list. can not set:

• OceanBase error code: 9133

• Cause: The source endpoint specified for the backup or archive path does not exist.

• Solution: Query the DBA_OB_ZONES view to verify whether the specified locality exists. Correct the locality and try again.

ERROR 9135 (HY000): tmp file exceeds disk quota

• OceanBase error code: 9135

• Cause: The amount of data written to disk by temporary files exceeds the configured upper limit.

• Solution: Check whether the SQL statement that triggered the error produces more data than expected (for example, whether the maximum temporary file data written to disk is expected to be 500 GB). If the data volume is as expected, adjust the temporary_file_max_disk_size parameter to an appropriate value.

ERROR 9147 (HY000): can not access backup set file

• OceanBase error code: 9147

• Cause: During physical restore, an OBServer node cannot access the backup set file in the specified backup media.

• Solution: Check object storage connectivity. After confirming that connectivity is normal, contact technical support for help.