9000 ~ 9499

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

ERROR 9001 (HY000) : URI error

• OceanBase Error 9001:

• Cause: The link of the destination of the backup restore task is incorrect.

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

ERROR 9002 (HY000) : OSS file MD5 error

• OceanBase Database error code: 9002

• Reason for the error: The data of the object stored in Alibaba Cloud OSS is incorrect. This error may be caused by an abnormally large file.

• Solution: Contact Alibaba Cloud Technical Support to identify the specific cause of the error.

ERROR 9003 (HY000) : OSS error

• OceanBase error code: 9003

• The error is due to an unknown error in Object Storage Service (OSS).

• Solution: Contact Alibaba Cloud technical support to find out the cause.

Relevant case studies:

• Backup path failed to set. Error message: OSS error
• Backups failed, and the tenant remains in the restoring state

ERROR 9004 (HY000) : Init MD5 fail

• OceanBase Database error code: 9004

• Cause: OpenSSL initialization of MD5 failed.

• Resolution: Contact OceanBase Technical Support for assistance.

ERROR 9005 (HY000) : Out of element

• OceanBase Database error code: 9005

• The cause of the error: the number of shards exceeded the limit.

• Resolution: Contact OceanBase technical support for assistance.

ERROR 9006 (HY000) : Update MD5 fail

• OceanBase Database error code: 9006

• Reason: The MD5 checksum update failed.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 9007 (HY000) : Invalid OSS file length

• OceanBase error code: 9007

• Cause: Invalid OSS file length. The file may be invalid.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 9010 (HY000) : OSS file MD5 not match

• OceanBase error code: 9010

• Cause: The checksum of the file stored in Alibaba Cloud OSS does not match that of the restored or backup file, which might indicate an abnormal Alibaba Cloud OSS file or a bug in the backup and restore program.

• Solution: Contact OceanBase Technical Support to help troubleshoot the issue.

ERROR 9011 (HY000) : cannot find backup file

• OceanBase Database Error Code 9011:

• Cause: The backup file cannot be found, indicating an error in the backup recovery configuration.

• Resolution: Verify and modify the relevant backup and restore configuration.

Example of a related case:

• The backup object cannot be restored to a specified time point for a heterogeneous restore.

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

• OceanBase Database error code: 9012

• Cause: The parameter data version is not specified in the logical restore parameters.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9013 (HY000) : Write OSS file error

• OceanBase error code: 9013

• The error is caused by an unknown issue with OSS.

• Solution: Contact the technical support engineer at Alibaba Cloud.

ERROR 9014 (HY000) : Another restore is in progress

• OceanBase Database error code: 9014

• Cause: There exists a tenant with the same name to be restored.

• Fix: Check the username of the restored tenant. If there are duplicate usernames, use a non-duplicated tenant name.

ERROR 9016 (HY000) : ob cluster name not equal

• OceanBase Database error code: 9016

• The error occurred because the cluster name and URL are inconsistent in the logical backup.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 9017 (HY000) : rs list invalid

• OceanBase Database error code: 9017

• Error reason: Invalid list of RSs. This is usually because the specified RS list is incorrect.

• Solution: Contact OceanBase technical support for further assistance.

ERROR 9018 (HY000) : agent has failed task

• OceanBase error code: 9018

• The cause: A logical backup task failed.

• Resolution: Contact OceanBase Technical Support for assistance.

ERROR 9019 (HY000) : restore partition is complete

• OceanBase Database error code: 9019

• Cause: The recovered partitions are scheduled for recovery tasks.

• Resolution: No action is required.

ERROR 9020 (HY000 ) : restore partition twice

• OceanBase error code: 9020

• Cause: The restored partition has been scheduled for the restore task again.

• Solution: No action is required.

ERROR 9022 (HY000) : physical backup switch is on

• OceanBase error code: 9022

• Cause: Dropped tables in the physical backup.

• Solution: No action is required. These files will be automatically deleted after the physical backup completes.

ERROR 9023 (HY000) : cannot start log archive backup

• OceanBase error code: 9023

• Cause: During log archiving, log archiving cannot be restarted.

• Solution: Avoid running the command to enable log archiving multiple times.

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

• OceanBase error code: 9024

• Cause: You cannot close log archiving during the Stop stage twice.

• Solution: Avoid closing an already closed log archive.

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

• OceanBase error code: 9025

*Cause: The archived log file does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase Error Code: 9026

• Error: The backup destination is invalid.

• Solution: Check if the backup_dest is appropriate and provide a valid backup_dest path.

Relevant Case Study:

• backup destination is not valid

ERROR 9027 (HY000) : ob log archive interrupted

• OceanBase error code: 9027

• The error occurred because of a log archiving interruption.

• Solution: If there are no write operations, check whether the logs are archived and archived in time. If the logs are archived, you can contact OceanBase technical support for troubleshooting.

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

• OceanBase Database error code: 9028

• Error reason: The log archive status does not match.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 9029 (HY000) : log archive is not running

• OceanBase Database error code: 9029

• Error reason: The log archive is not running. This error is usually printed when you stop the backup on an OBServer node.

• Solution: No manual intervention is required. This is just an exit log for the log archive.

ERROR 9030 (HY000) : log archive invalid round

• OceanBase Database error code: 9030

• Error reason: The log archive round information is invalid.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 9031 (HY000) : Cannot backup ob replica

• OceanBase Database error code: 9031

• Error reason: The replica is being migrated or is a log replica and cannot provide data backup capabilities.

• Solution: OceanBase Database will retry internally. No manual intervention is required.

ERROR 9032 (HY000) : backup info not exists

• OceanBase Database error code: 9032

• Error reason: The backup information does not exist.

• Solution: Contact OceanBase Technical Support for assistance.

Related case:

• Backup process runs for a long time and logs show error 9032

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

• OceanBase Database error code: 9033

• Error reason: The backup status is inconsistent.

• Solution:

  • If this error is reported by the log archive of an OBServer node, it is usually generated when you start or stop the log archive. No manual intervention is required.

  • If this error is reported by the log of the Root Service, contact OceanBase Technical Support for assistance.

ERROR 9035 (HY000) : restore index failed

• OceanBase Database error code: 9035

• Error reason: The index cannot be rebuilt after the restore is completed.

• Solution: Check the indexes of the internal tables of the restored tenant whose index status is error, and then recreate the indexes.

ERROR 9036 (HY000) : Backup is in progress

• OceanBase Database error code: 9036

• Error reason: This error is usually generated when you perform an operation that is mutually exclusive with the backup.

• Solution: Stop the data backup and log archive, and then execute the operation.

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

• OceanBase Database error code: 9037

• Error reason: The log archive status is invalid.

• Solution: Contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 9038

• Error reason: The set member list phase does not support replication.

• Solution: The set member list step of the restore does not support replica replication. If a majority of replicas still exist, the restore can continue. If no majority of replicas exists, you must cancel the restore and reschedule the restore task.

ERROR 9039 (HY000) : pg log archive leader changed

• OceanBase Database error code: 9039

• Error reason: The leader of the log archive has changed.

• Solution: This is an internal error. After the leader change is detected, the current PG log archive process is interrupted. The new leader will automatically continue the backup process. No manual intervention is required.

ERROR 9040 (HY000) : backup can not start

• OceanBase Database error code: 9040

• Error reason: The log archive is not in the DOING state. Therefore, you cannot start the data backup.

• Solution: Wait until the log archive enters the DOING state. If the log archive remains in the BEGINNING state for a long time, contact OceanBase Technical Support for assistance.

ERROR 9041 (HY000) : cancel backup do not allow

• OceanBase Database error code: 9041

• Error reason: You cannot cancel a backup task multiple times.

• Solution: Avoid canceling a backup task multiple times.

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

• OceanBase Database error code: 9042

• Error reason: If the data backup does not complete within 16 Major Merge operations, it will fail automatically.

• Solution: Check the reason for the slow data backup or confirm whether the Major Merge operations are too frequent.

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

• OceanBase Database error code: 9044

• Error reason: You cannot schedule the cleanup of the backup data multiple times.

• Solution: Avoid scheduling the cleanup of the backup data multiple times.

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

• OceanBase Database error code: 9045

• Error reason: You cannot delete a backup set.

• Solution: Check whether you entered an incorrect command.

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

• OceanBase Database error code: 9046

• Error reason: The backup set ID is invalid. This is usually because you specified an invalid backup_set_id.

• Solution: Check whether the backup_set_id is correct and retry the operation.

ERROR 9047 (HY000) : invalid password for backup

• OceanBase Database error code: 9047

• Error reason: The password is invalid.

• Solution: Check whether the password is correct and retry the operation.

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

• OceanBase Database error code: 9048

• Error reason: The data backup and log archive are not continuous.

• Solution: Check whether the log archive has been interrupted.

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

• OceanBase Database error code: 9049

• Error reason: The backup has been stopped and cannot be canceled again.

• Solution: No additional processing is required. The backup has been stopped.

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

• OceanBase Database error code: 9050

• Error reason: The scheduled backup task has no data to be backed up.

• Solution: This error usually appears in the backup scenario. No processing is required.

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

• OceanBase Database error code: 9051

• Error reason: An OBServer node does not mount the NFS.

• Solution: Make sure that all nodes are mounted with the NFS.

ERROR 9052 (HY000) : backup clean info not match

• OceanBase error code: 9052

• Error reason: The metadata of the backup cleanup is inconsistent.

• Solution: Contact OceanBase Technical Support.

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

• OceanBase error code: 9053

• Error reason: The Cancel operation was initiated without a cleanup task.

• Solution: Avoid initiating the Cancel operation without a cleanup task.

ERROR 9054 (HY000) : backup clean info not exists

• OceanBase error code: 9054

• Error reason: The metadata of the backup cleanup does not exist.

• Solution: Contact OceanBase Technical Support.

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

• OceanBase error code: 9057

• Error reason: The backup region cannot be modified.

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

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

• OceanBase error code: 9058

• Error reason: The backup zone cannot be modified.

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

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

• OceanBase error code: 9059

• Error reason: Internal error code. It is mainly used when scheduling backups for internal backup, and the Backup Set or Backup Piece meets the maximum backup times requirement.

• Solution: No action is required.

ERROR 9060 (HY000) : COS error

• OceanBase error code: 9060

• Error reason: An error occurred in the module responsible for Tencent Cloud COS adaptation.

• Solution: This is usually a logic error in OceanBase Database's adaptation of COS. Contact OceanBase Technical Support.

ERROR 9061 (HY000) : IO limit

• OceanBase error code: 9061

• Error reason: This error is caused by I/O limitations. Currently, only the List operation in the Tencent Cloud COS module returns this error code.

• Solution: Contact Tencent Cloud COS customer support to increase or remove the List throttling limit.

ERROR 9062 (HY000) : reach backup backup copy limit

• OceanBase error code: 9062

• Error reason: When scheduling backups for the specified number of backup copies, all backup sets and backup pieces already meet the backup copy requirements, and no backup set or backup piece is found to be backed up.

• Solution: No action is required.

ERROR 9063 (HY000) : backup io is prohibited

• OceanBase error code: 9063

• Error reason: The backup and restore operation in the COS environment is throttled during the List operation.

• Solution:

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

  • If this error frequently occurs, contact the COS customer support to increase or remove the List operation frequency limit.

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

• OceanBase error code: 9064

• Error reason: The data in the archive logs and the original backup data are not continuous.

• Solution:

  • V2.2.X: Perform a major compaction and 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

• Error reason: When the logical backup and restore feature is paused, the ongoing task returns this error code.

• Solution: This error code does not affect the feature. The logical backup will be paused and can be restarted later.

ERROR 9066 (HY000) : %.*s is conflict with %.*s

• OceanBase error code: 9066

• Error reason: There are conflicting values.

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

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

• OceanBase error code: 9069

• Error reason: Deleting a backup log shard is not allowed.

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

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

• OceanBase error code: 9070

• Error reason: The OBServer node is not connected to the backup medium, such as when the NFS is not mounted or the object storage does not have access permissions.

• Solution: Correctly mount the NFS or set the correct authorization information for the object storage or enable the necessary operation permissions.

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

• OceanBase error code: 9071

• Error reason: The OBServer node does not have operation permissions on the backup medium.

• Solution: Enable the permissions for the operations that lack permissions.

ERROR 9072 (HY000) : obesi process session conflicts

• OceanBase error code: 9072

• Error reason: Session conflicts occur in the backup I/O independent sub-process.

• Solution: No action is required.

ERROR 9073 (HY000) : external storage OBS error

• OceanBase error code: 9073

• Error reason: When the backup medium is Huawei Cloud OBS, a storage-level error may have occurred.

• Solution: Check whether Huawei Cloud OBS is connected and can write data.

ERROR 9074 (HY000) : backup validation task skipped

• OceanBase error code: 9074

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

• Solution: No action is required.

ERROR 9075 (HY000) : obesi process io error

• OceanBase Database error code: 9075

• Error reason: The backup and restore I/O failed because the obesi process was in an abnormal state.

• Solution: No action is required.

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

• OceanBase Database error code: 9076

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

• Solution: Contact OceanBase Technical Support.

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

• OceanBase Database error code: 9077

• Error reason: The logs of two consecutive archive rounds are not continuous. Therefore, the logs cannot be continuously read.

• Solution: Contact OceanBase Technical Support.

ERROR 9078 (HY000) : archive log is to end

• OceanBase Database error code: 9078

• Error reason: The continuous reading of the archive logs has reached the end.

• Solution: No action is required.

ERROR 9079 (HY000) : archive log had been recycled

• OceanBase Database error code: 9079

• Error reason: The archive logs to be continuously read have been recycled.

• Solution: Contact OceanBase Technical Support.

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

• OceanBase Database error code: 9080

• Error reason: The format file does not exist.

• Solution: Check whether the format file exists in the destination. If not, create the format file.

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

• OceanBase Database error code: 9081

• Error reason: The content of the format file in the destination does not match the expected content.

• Solution: Ensure that the content of the format file in the destination matches the expected content.

ERROR 9082 (HY000) : backup device out of space

• OceanBase Database error code: 9082

• Error reason: The backup device has insufficient storage space.

• Solution: Expand the storage space of the backup device.

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

• OceanBase Database error code: 9083

• Error reason: The offset of the pwrite file in the object storage is inconsistent with the file length.

• Solution: No action is required.

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

• OceanBase Database error code: 9084

• Error reason: The content of the pwrite file is inconsistent with the existing content of the file.

• Solution: No action is required.

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

• OceanBase Database error code: 9085

• Error reason: The range of the major SSTable in the backup does not cover the minor SSTable.

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

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

• OceanBase Database error code: 9086

• Error reason: The backup log stream checkpoint is timed out.

• Solution: Contact OceanBase Technical Support.

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

• OceanBase Database error code: 9087
• Error reason: The archive file has been recycled before it is consumed.

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

• OceanBase Database error code: 9088
• Error reason: The source tenant and log stream states do not match. Therefore, the current tenant cannot be switched to the primary tenant.
• Solution:
  1. Check whether the source tenant and target tenant states match.
  2. Check whether the master-slave replication configuration is correct.
  3. Check whether the backup of the source tenant is complete and the restore of the target tenant is correct.

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

• OceanBase Database error code: 9089
• Error reason: The log restore source tenant or log stream state does not match. The current tenant cannot be switched to the primary tenant.
• Solution:
  1. Check whether the backup restore source log state matches the target log state.
  2. Check whether the primary-standby replication configuration is correct.
  3. Check whether the backup of the source log is complete and whether the restore of the target log is correct.

ERROR 9090 (HY000) : obesi process session not exist

• OceanBase Database error code: 9090

• Error reason: The obesi process session does not exist.

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

ERROR 9091 (HY000) : Already in ARCHIVELOG mode

• OceanBase Database error code: 9091

• Error reason: The database is already in the ARCHIVELOG mode.

• Solution: This is a current state prompt. No action is required.

ERROR 9092 (HY000) : Already in NOARCHIVELOG mode

• OceanBase Database error code: 9092

• Error reason: The database is already in the NOARCHIVELOG mode.

• Solution: This is a current state prompt. No action is required.

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

• OceanBase Database error code: 9096
• Error reason: The standby database version is behind the primary database version.
• Solution: Check the versions of the standby and primary databases. Wait for the standby database to be upgraded.

ERROR 9097 (HY000) : primary tenant has been dropped

• OceanBase Database error code: 9097
• Error reason: The primary tenant was deleted during the primary-standby synchronization process.
• Solution: Check the tenant information of the primary database to confirm whether the primary tenant exists.

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

• OceanBase Database error code: 9098
• Error reason: An error occurred while attempting to append content to a normal object in object storage (such as OSS or COS).
• Solution: Check the object storage type and ensure that the object storage type being used supports appending content to normal objects.

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

• OceanBase Database error code: 9099

• Error reason: The restore operation failed.

• Solution: Check the configuration and parameter settings for the restore operation to ensure they meet the requirements and expectations of the restore target.

ERROR 9100 (HY000) : no such file or directory

• OceanBase Database error code: 9100

• Error reason: The storage layer cannot find the corresponding directory or file. The issue may be related to the configured storage directory.

• Solution: Contact technical support for assistance.

ERROR 9101 (HY000) : file or directory already exist

• OceanBase Database error code: 9101

• Error reason: The corresponding file or directory already exists.

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

ERROR 9105 (HY000) : S3 error

• OceanBase Database error code: 9105

• Error reason:

  1. The input bucket is incorrect.
  2. The endpoint of the object storage is invalid.
  3. An unknown error occurred with S3.

• Solution:

  1. Check whether the input bucket exists.
  2. Check whether the endpoint configuration for the object storage is correct. Ensure that the endpoint is correctly configured and accessible.
  3. If the bucket error is ruled out, contact OceanBase Database technical support for assistance.

ERROR 9106 (HY000) : Tenant snapshot '%.*s' does not exist

• OceanBase Database error code: 9106

• Error reason: The specified tenant snapshot does not exist.

• Solution: Confirm whether the specified tenant snapshot is correct. If the snapshot does not exist, you may need to create a new snapshot or take other actions based on the situation.

ERROR 9107 (HY000) : Tenant snapshot '%.*s' already exist

• OceanBase Database error code: 9107

• Error reason: The specified tenant snapshot already exists.

• Solution: Confirm whether the specified tenant snapshot already exists. If the snapshot already exists, you may need to take other actions based on the situation.

ERROR 9108 (HY000) : Tenant snapshot task timeout. %.*s

• OceanBase Database error code: 9108

• Error reason: The tenant snapshot task timed out.

• Solution: Check whether the snapshot task execution time is too long. You may need to extend the timeout period or optimize the task execution process.

ERROR 9109 (HY000) : Clone tenant timeout. %.*s

• OceanBase Database error code: 9109

• Error reason: The clone tenant operation times out.

• Solution: Check whether the execution time of the clone tenant operation is too long. If so, you can extend the timeout period or optimize the clone process.

ERROR 9110 (HY000) : Tenant clone job failed", "%.*s

• OceanBase Database error code: 9110

• Error reason: The tenant clone job failed.

• Solution: Check the cause of the failure of the tenant clone job and handle it accordingly.

ERROR 9111 (HY000) : Tenant snapshot task failed", "%.*s

• OceanBase Database error code: 9111

• Error reason: The tenant snapshot task failed.

• Solution: Check the cause of the failure of the tenant snapshot task and handle it accordingly.

ERROR 9112 (HY000) : Tenant snapshot lock conflict", "%s

• OceanBase Database error code: 9112

• Error reason: A tenant snapshot lock conflict occurs.

• Solution: Check the specific situation of the snapshot lock conflict. You can release the conflicting snapshot lock or adjust the lock usage method.

ERROR 9113 (HY000) : checksum type %s is not supported for the input destination

• OceanBase Database error code: 9113

• Error reason: The input destination does not support the %s checksum type.

• Solution: Check the checksum type of the input destination and ensure that a supported checksum type is used.

ERROR 9114 (HY000) : storage destination is not valid

• OceanBase Database error code: 9114

• Error reason: The object storage destination is invalid.

• Solution: Check whether the object storage destination is correctly configured and ensure that it is a valid destination. You may need to correct the object storage destination configuration or settings.

ERROR 9115 (HY000) : can not connect to storage destination

• OceanBase Database error code: 9115

• Error reason: The connection to the object storage destination fails.

• Solution: Check the connection configuration to the object storage destination and ensure that the network connection is normal. You may need to correct the connection configuration, access key, or fix the network connection issue.

ERROR 9116 (HY000) : no I/O operation permission of the object storage

• OceanBase Database error code: 9116

• Error reason: No I/O operation permission is granted for the object storage.

• Solution: Check the permission settings for the object storage and ensure that you have the correct I/O operation permissions. You may need to adjust the object storage permission settings or contact an administrator to obtain the appropriate permissions.

ERROR 9117 (HY000) : the specified s3_region does not match the endpoint

• OceanBase Database error code: 9117

• Error reason: The s3_region parameter is not specified or the specified s3_region does not match the endpoint.

• Solution: Check whether the specified s3_region and endpoint are correctly matched. Ensure that the correct s3_region and corresponding endpoint are used for configuration.

ERROR 9118 (HY000) : object storage endpoint is invalid

• OceanBase Database error code: 9118

• Error reason: The object storage endpoint is invalid.

• Solution: Check whether the object storage endpoint configuration is correct. Ensure that the endpoint configuration is correct and can access the object storage service.

ERROR 9129 (HY000) : object storage io error

• OceanBase Database error code: 9129
• Error reason: An object storage error occurs. Common causes include object storage connectivity and compatibility issues.
• Solution: Check the object storage connectivity and contact technical support after confirming that no connectivity issues exist.

ERROR 9133 (HY000) : Backup zone or backup idc or backup region invalid

• OceanBase Database error code: 9133

• Error reason: The backup path or archive path source zone, IDC, or region does not exist. For example, if the cluster has only zone1 and zone2, but you set the backup zone to zone3 and zone4, an error will be returned because zone3 and zone4 do not exist.

• Solution: Query the DBA_OB_ZONES view to confirm whether the specified locality exists. Then, correct the configuration.

ERROR 9135 (HY000) :tmp file exceeds disk quota

• OceanBase Database error code: 9135

• Error reason: The data size of the temporary file exceeds the set limit.

• Solution: Check whether the SQL statement that caused the current error generates more data than expected. For example, if the maximum data size of the temporary file is expected to be 500 GB, you can adjust the temporary_file_max_disk_size parameter to an appropriate value.

ERROR 9136 (HY000) : Backup missing mview dependent tablet sstable, sstable maybe recycled

• OceanBase Database error code: 9136

• Error reason: The major sstable of a multi-version table is recycled during backup.

• Solution: Initiate data backup again.

ERROR 9139 (HY000) : kms destination is not valid

• OceanBase Database error code: 9139

• Error reason: When transparent encryption is enabled for a backup tenant, the key address is not specified or the specified key address is invalid when you restore the tenant.

• Solution: Specify the correct key address in the restore command or set the @kms_encrypt_info session variable to the correct key address before restore.

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

• OceanBase Database error code: 9140

• Error reason: You attempt to delete or modify an object 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 set. If the enable_worm parameter is correctly set, contact OceanBase Technical Support for further assistance.

ERROR 9141 (HY000) : the resource has been released

• OceanBase Database error code: 9141

• Error reason: A temporary file macroblock is unexpectedly released during use.

• Solution: Contact OceanBase Technical Support for further assistance.

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

• OceanBase Database error code: 9142

• Error reason: You attempt to write a non-idempotent file with the same name to an object storage service that is configured with a retention policy.

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 9144 (HY000) : Unexpected macro cache file

• OceanBase Database error code: 9144

• Error reason: An unexpected file is found in the macroblock cache directory. This file is likely created by you.

• Solution: Contact OceanBase Technical Support for further assistance.

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

• OceanBase Database error code: 9147

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

• Solution: Check the connectivity of the object storage service. If no connectivity issues are found, contact OceanBase Technical Support for further assistance.

ERROR 9148 (HY000): disk quota is exceeded

• OceanBase Database error code: 9148

• Error reason: The disk quota is exceeded.

• Solution: Clear the files or adjust the disk quota.

ERROR 9149 (HY000) : backup dest is not allowed to set when log_only policy exists

• OceanBase Database error code: 9149

• Error reason: The log_only cleanup policy applies to a scenario where only log archiving is enabled and no data backup is performed. When the log_only cleanup policy exists, you cannot configure a data backup path.

• Solution: Delete the log_only cleanup policy first, and then configure a data backup path.

ERROR 9150 (HY000) : log_only policy is not allowed to set when backup dest exists

• OceanBase Database error code: 9150

• Error reason: The log_only cleanup policy applies to a scenario where only log archiving is enabled and no data backup is performed. In a scenario where a data backup path is configured, you cannot set the cleanup policy to log_only.

• Solution: If you want to use the log_only cleanup policy, you must delete the configured data backup path first.

ERROR 9151 (HY000) : backup clean can not start, because %s

• OceanBase Database error code: 9151

• Error reason: Data backup and archive cleanup cannot be performed. The reason may be that the status of the related tenant is not NORMAL (for example, the tenant is in the CREATING or RESTORE state) or the related tenant is not configured with a cleanup policy (for an expiration cleanup scenario).

• Solution: Check the tenant status. For an expiration cleanup scenario, confirm whether the related tenant is correctly configured with a cleanup policy.

ERROR 9152 (HY000) : backup device may be not mounted, %s did not read any data written by %s

• OceanBase Database error code: 9152

• Error reason: The backup media is not correctly mounted.

• Solution: Correctly mount the backup media and ensure that all OBServer nodes of the tenant that initiates the archive, backup, or restore operation can access the same backup media. For more information about how to mount an NFS, see Deploy NFS.

ERROR 9153 (HY000) : backup device is not read and write strongly consistent. %s did not read the latest data written by %s.

• OceanBase Database error code: 9153

• Error reason: The backup device does not have strong consistency for read and write operations.

• Solution: If the backup device is an NFS file system, see Mount an NFS file system for more information. If the backup device is an object storage service, contact the service provider.

ERROR 9155 (HY000) : micro block is too large and rejected from micro cache

• OceanBase Database error code: 9155

• Error reason: In shared storage mode, the size of the microblock to be cached exceeds the maximum allowed size of the microblock cache (default 128KB). The system rejects writing the microblock to the microblock cache.

• Solution: This error is a normal system flow control behavior and does not affect data correctness or business availability. Generally, no action is required. If this error frequently occurs and significantly impacts read performance, please contact technical support for assistance.

ERROR 9158 (HY000) : the object type is invalid

• OceanBase Database error code: 9158

• Error reason: An unexpected object type is encountered when data is written to the object storage service. For example, a Put operation is performed on an Append object, or an Append operation is performed on a normal object.

• Solution: Contact Technical Support for assistance.

ERROR 9159 (HY000) : available data backup set is not found

• OceanBase error code: 9159

• Error reason: No backup set is available to restore to the specified point in time.

• Solution: Select a different restore point or specify a different backup set path.

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

• OceanBase Database error code: 9200

• Error reason: The SSBlock file cannot be reduced in size.

• Solution: Check whether the value specified for ALTER SYSTEM SET datafile_size is greater than the size of the current SSBlock file. If not, contact Technical Support for assistance.

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

• OceanBase Database error code: 9201

• Error reason: The macroblock marking fails after the SSBlock file is automatically extended.

• Solution: Contact Technical Support for assistance.

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

• OceanBase Database error code: 9202

• Error reason: The auto-extend feature is not enabled, or the disk space occupied by the datafile parameter has reached the upper limit.

• Solution: Check whether the free_size field in the __all_virtual_disk_stat table is 0. If yes, the disk space is exhausted. In this case, you need to increase the threshold of datafile or expand the disk.