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 specified in the backup and restore settings may be incorrect.
Solution: Check the backup and restore configurations and modify them as needed.
ERROR 9004 (HY000) : Init MD5 fail
OceanBase error code: 9004
Cause: An OpenSSL initialization MD5 error occurred.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9005 (HY000) : Out of element
OceanBase error code: 9005
Cause: The limit on shards has been exceeded.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9006 (HY000) : Update MD5 fail
OceanBase error code: 9006
Cause: MD5 update failed.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9011 (HY000) : cannot find backup file
OceanBase error code: 9011
Cause: The backup file could not be found. The specified backup and restore configuration may be incorrect.
Solution: Check the backup and restore configurations and modify them as needed.
ERROR 9012 (HY000) : Can not get data version from timestamp
OceanBase error code: 9012
Cause: The
data versionparameter was not passed in the logical restore parameters.Solution: Contact OceanBase Technical Support for assistance.
ERROR 9014 (HY000) : Another restore is in progress
OceanBase error code: 9014
Cause: A tenant with the same name already exists for the tenant to be restored.
Solution: Check whether the username of the tenant to be restored is duplicated. If so, use a unique tenant name.
ERROR 9016 (HY000) : ob cluster name not equal
OceanBase error code: 9016
Cause: The cluster name and URL do not match for the logical backup.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9017 (HY000) : rs list invalid
OceanBase error code: 9017
Cause: The RS list is invalid, possibly due to an incorrect specified RS list.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9018 (HY000) : agent has failed task
OceanBase error code: 9018
Cause: There are failed tasks in the logical backup.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9019 (HY000) : restore partition is complete
OceanBase error code: 9019
Cause: A restore task has been repeatedly scheduled for a partition that has already been restored.
Solution: No action required.
ERROR 9020 (HY000) : restore partition twice
OceanBase error code: 9020
Cause: A restore task has been repeatedly scheduled for a partition that has already been restored.
Solution: No action required.
ERROR 9022 (HY000) : physical backup switch is on
OceanBase error code: 9022
Cause: Tables are delayed during physical backup.
Solution: No action required. Tables will be automatically deleted after physical backup is completed.
ERROR 9023 (HY000) : cannot start log archive backup
OceanBase error code: 9023
Cause: Log archiving cannot be restarted during log archiving.
Solution: Avoid repeatedly scheduling commands to restart log archiving.
ERROR 9024 (HY000) : log archive backup is already disabled
OceanBase error code: 9024
Cause: Log archiving cannot be disabled during the Stop phase.
Solution: Avoid repeatedly disabling log archiving that has already been disabled.
ERROR 9025 (HY000) : log archive backup info not exists
OceanBase error code: 9025
Cause: The file containing log archive information does not exist.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9026 (HY000) : %s is not a valid uri
OceanBase error code: 9026
Cause: The backup destination URI is invalid.
Solution: Check whether the
backup_destparameter is valid and provide a validbackup_destpath.
ERROR 9027 (HY000) : ob log archive interrupted
OceanBase error code: 9027
Cause: Log archiving was interrupted.
Solution: Check whether a large volume of writes caused log archiving to be overwhelmed. If not, contact OceanBase Technical Support for assistance.
ERROR 9028 (HY000) : ob log archive stat not match
OceanBase error code: 9028
Cause: The status of log archiving does not match.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9029 (HY000) : log archive is not running
OceanBase error code: 9029
Cause: Log archiving is not running. This error is typically printed on the OBServer node when you stop backup.
Solution: No manual intervention is required. Just exit the error log of log archiving normally.
ERROR 9030 (HY000) : log archive invalid round
OceanBase error code: 9030
Cause: The round information of log archiving is incorrect.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9031 (HY000) : Cannot backup ob replica
OceanBase error code: 9031
Cause: The replica is currently migrating replication or log replicas and cannot provide data backup capability.
Solution: OceanBase AI Database will retry internally. No manual intervention is required.
ERROR 9032 (HY000) : backup info not exists
OceanBase error code: 9032
Cause: Backup information does not exist.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9033 (HY000) : Backup meta info stored in system dictionary does not match with current system status
OceanBase error code: 9033
Cause: The backup status is inconsistent.
Solution:
If this error occurs during log archiving on an OBServer node, which usually happens when starting or stopping log archiving, no manual intervention is required.
If this error occurs in the root service log, contact OceanBase Technical Support to investigate the specific cause.
ERROR 9035 (HY000) : restore index failed
OceanBase error code: 9035
Cause: Index rebuilding failed after restore completion.
Solution: Check for indexes with a lock status of
erroron internal tables within the restored tenant, and recreate those indexes.
ERROR 9036 (HY000) : Backup is in progress
OceanBase error code: 9036
Cause: Generally, an operation that is mutually exclusive to backup was performed.
Solution: Stop data backup and log archiving before executing this command.
ERROR 9037 (HY000) : log archive status is not valid
OceanBase error code: 9037
Cause: The log archive status is invalid.
Solution: Contact OceanBase Technical Support for assistance in troubleshooting.
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 listphase.Solution: The
set member liststep of restore does not support replica replication. If a majority of replicas still exist at this point, the restore can continue; if no majority replicas remain, you need to 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: An internal error code. Detection of a leader switch will interrupt the current PostgreSQL log archive process. The new leader will automatically resume backup work without requiring operational intervention.
ERROR 9040 (HY000) : backup can not start
OceanBase error code: 9040
Cause: Log archive is not in the
DOINGstate, so data backup cannot be started.Solution: Wait for log archive to enter the
DOINGstate. If it remains in theBEGINNINGstate for a long time, contact OceanBase Technical Support to investigate the specific cause.
ERROR 9041 (HY000) : cancel backup do not allow
OceanBase error code: 9041
Cause: Repeated cancellation of a backup task is not allowed.
Solution: Avoid repeatedly canceling tasks that are already being canceled.
ERROR 9042 (HY000) : backup data version gap over limit
OceanBase error code: 9042
Cause: Data backup will fail automatically if it is not completed during more than 16
Major Merges.Solution: Investigate the cause of the slow data backup or confirm whether
Major Mergesare occurring too frequently.
ERROR 9044 (HY000) : delete backup data is in progress
OceanBase error code: 9044
Cause: Scheduling a cleanup task for backups repeatedly is not allowed.
Solution: Avoid repeatedly scheduling cleanup tasks for backups.
ERROR 9045 (HY000) : delete backup set do not allow
OceanBase error code: 9045
Cause: Deleting a 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. You may have specified an invalid
backup_set_id.Solution: Check whether the input
backup_set_idis 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 discontinuous.
Solution: Check whether the 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 further action is required. The backup has already stopped.
ERROR 9050 (HY000) : no backup data to be backed up
OceanBase error code: 9050
Cause: The scheduled backup task has no data to back up.
Solution: This typically occurs in a backup scenario and does not require handling.
ERROR 9051 (HY000) : backup mount file is not valid
OceanBase error code: 9051
Cause: There are OBServer nodes that have not mounted NFS.
Solution: Ensure that all nodes have mounted NFS.
ERROR 9052 (HY000) : backup clean info not match
OceanBase error code: 9052
Cause: The cleaned-up metadata for the backup is inconsistent.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9053 (HY000) : cancel delete backup do not allow
OceanBase error code: 9053
Cause: A
Canceloperation was initiated when no cleanup tasks were pending.Solution: Avoid initiating a
Canceloperation when no cleanup tasks are pending.
ERROR 9054 (HY000) : backup clean info not exists
OceanBase error code: 9054
Cause: The cleaned-up metadata does not exist.
Solution: Contact OceanBase Technical Support for assistance.
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 assistance.
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 assistance.
ERROR 9059 (HY000) : backup backup has reached max backup times
OceanBase error code: 9059
Cause: Internal error code. This code is primarily used internally during backup scheduling when it is found that neither the Backup Set nor any Backup Piece meets the maximum Backup Times requirement.
Solution: No action required.
ERROR 9060 (HY000) : COS error
OceanBase error code: 9060
Cause: An error occurred in the module responsible for Tencent Cloud COS adaptation.
Solution: This is usually a logical error in the OceanBase AI Database's adaptation to COS. You need to contact OceanBase Technical Support.
ERROR 9061 (HY000) : IO limit
OceanBase error code: 9061
Cause: This is caused by an I/O limitation. Currently, only the List operation of the Tencent Cloud COS module returns this error code.
Solution: You need to contact COS customer support to increase or remove the List throttling.
ERROR 9062 (HY000) : reach backup backup copy limit
OceanBase error code: 9062
Cause: When scheduling backups for specified Backup Times, it is found that all backup_sets and backup_pieces already meet the Backup Times requirements, and no backup_set or backup_piece to back up is found.
Solution: No action is required.
ERROR 9063 (HY000) : backup io is prohibited
OceanBase error code: 9063
Cause: The execution of List operations for backup and restore is throttled in a COS environment.
Solution:
If this issue occurs occasionally, no action is required.
If this issue occurs frequently, you need to contact the backup COS customer support to increase or remove the frequency limit for List operations.
ERROR 9064 (HY000) : the archive log and backup data are not continuous
OceanBase error code: 9064
Cause: The archived log data and the original backup data are discontinuous.
Solution:
Rerun the data backup.
ERROR 9065 (HY000) : agent has suspended
OceanBase error code: 9065
Cause: This error code is returned for tasks being performed when the backup feature is paused via logical backup and restore.
Solution: This error code does not affect functionality. Logical backup will be paused and can be restarted later.
ERROR 9066 (HY000) : %.*s is conflict with %.*s
OceanBase error code: 9066
Cause: Conflicting values exist.
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
Cause: Deleting a backup log shard is not allowed.
Solution: Check if an incorrect delete command was entered.
ERROR 9070 (HY000) : can not connect to backup destination
OceanBase error code: 9070
Cause: There is an OBServer node that is not connected to the backup medium, for example, NFS is not mounted, or there is no access permission for object storage.
Solution: Mount NFS correctly, or set the correct authorization information for object storage or grant the necessary operational permissions.
ERROR 9071 (HY000) : no I/O operation permission at the backup destination
OceanBase error code: 9071
Cause: The OBServer node does not have operational permission on the backup medium.
Solution: Grant the permission for the operation that lacks permission.
ERROR 9072 (HY000) : obesi process session conflicts
OceanBase error code: 9072
Cause: Session conflict for the independent backup I/O sub-process.
Solution: No action required.
ERROR 9073 (HY000) : external storage OBS error
OceanBase error code: 9073
Cause: An error may have occurred at the storage medium level when the backup medium is Huawei Cloud OBS.
Solution: You need to check whether Huawei Cloud OBS is connected normally and writes data normally.
ERROR 9075 (HY000) : obesi process io error
OceanBase error code: 9075
Cause: I/O failure during backup or restore due to abnormal OBSESI process status.
Solution: No action required.
ERROR 9076 (HY000) : backup meta index does not exist
OceanBase error code: 9076
Cause: The backup data's meta-information index does not exist.
Solution: Contact technical support for assistance.
ERROR 9077 (HY000) : log discontinuous between two archive rounds
OceanBase error code: 9077
Cause: When continuously reading archived logs, the logs of two consecutive rounds are discontinuous, making it impossible to read them continuously.
Solution: Contact technical support for assistance.
ERROR 9078 (HY000) : archive log is to end
OceanBase error code: 9078
Cause: Continuous reading of archived logs has reached the end.
Solution: No action required.
ERROR 9079 (HY000) : archive log had been recycled
OceanBase error code: 9079
Cause: When continuously reading archived logs, it was found that the log had been recycled.
Solution: Contact technical support for assistance.
ERROR 9080 (HY000) : format file does not exist%s
OceanBase error code: 9080
Cause: The format file does not exist.
Solution: Check whether the format file exists in the target location. If not, create the format file.
ERROR 9081 (HY000) : format file does not match%s
OceanBase error code: 9081
Cause: The format file in the target location does not match the expected one.
Solution: Ensure that the format file in the target location matches the expected content.
ERROR 9082 (HY000) : backup device out of space
OceanBase error code: 9082
Cause: The backup disk has insufficient storage space.
Solution: Expand the backup storage space.
ERROR 9083 (HY000) : the pwrite offset of the object storage is inconsistent
OceanBase error code: 9083
Cause: The offset for appending data to the backup or restore file does not match the file length.
Solution: No action required.
ERROR 9084 (HY000) : the contents of pwrite are inconsistent
OceanBase error code: 9084
Cause: The content of the file appended during backup or restore does not match the existing file content.
Solution: No action required.
ERROR 9085 (HY000) : backup major SSTable range not cover minor SSTable
OceanBase error code: 9085
Cause: The range of the major SSTable backed up does not cover the minor SSTable.
Solution: No action is required. The backup will be retried internally.
ERROR 9086 (HY000) : backup advance checkpoint by flush timeout
OceanBase error code: 9086
Cause: The backup log stream advancement checkpoint timed out.
Solution: Contact technical support for assistance.
ERROR 9087 (HY000) : observer clog is recycled before archive
- OceanBase error code: 9087
- Cause: The archived file has been recycled during consumption and archiving.
ERROR 9088 (HY000) : log restore source tenant state not match, switchover to primary not allowed
- OceanBase error code: 9088
- Cause: The states of the source tenant and log stream for log restore do not match, preventing the current tenant from switching to primary.
- Solution:
- Check whether the states of the source tenant and target tenant for backup and restore match.
- Check whether the primary-standby replication configuration is correct.
- 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 error code: 9089
- Cause: The states of the source tenant and log stream for log restore do not match, preventing the current tenant from switching to primary.
- Solution:
- Check whether the states of the source log and target log for restore match.
- Check whether the primary-standby replication configuration is correct.
- Check whether the backup of the source log is complete and the restore of the target log 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 restart automatically and does not require manual intervention.
ERROR 9091 (HY000) : Already in ARCHIVELOG mode
OceanBase error code: 9091
Cause: The database is already in ARCHIVELOG mode.
Solution: This status message indicates 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 status message indicates no action is required.
ERROR 9094 (HY000) : Restore log stream failed
OceanBase error code: 9094
Cause: Log stream restore failed. The log stream data to be restored may be corrupted.
Solution: Contact technical support for assistance.
ERROR 9095 (HY000) : No tablet need backup
OceanBase error code: 9095
Cause: No tablets require backup.
Solution: Contact technical support for assistance.
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. Wait for the standby database to complete the version upgrade.
ERROR 9097 (HY000) : primary tenant has been dropped
- OceanBase error code: 9097
- Cause: The primary tenant was dropped during primary-standby synchronization.
- Solution: Check the tenant information in the primary database to confirm whether a 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 while attempting to append content to a regular object in object storage.
- Solution: Check the object storage type to ensure it supports appending content to regular objects.
ERROR 9099 (HY000) : %s restore failed, %s
OceanBase error code: 9099
Cause: The restore operation failed.
Solution: Check the restore configuration and parameter settings to ensure they meet the requirements and expectations of the restore target.
ERROR 9100 (HY000) : no such file or directory
OceanBase error code: 9100
Cause: The storage layer cannot find the corresponding directory or file, possibly due to an issue with the configured storage directory.
Solution: Contact technical support for assistance in troubleshooting.
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 assistance in troubleshooting.
ERROR 9102 (HY000) : file or directory permission denied
OceanBase error code: 9102
Cause: No permission to access the file or directory.
Solution: Contact OceanBase Technical Support for assistance in troubleshooting.
ERROR 9103 (HY000) : too many open files
OceanBase error code: 9103
Cause: The number of File Descriptors (FDs) opened by the file system has reached the limit.
Solution: The internal logic will retry; no manual intervention is required.
ERROR 9104 (HY000) : fail to commit direct load
OceanBase error code: 9104
Cause: The
COMMIToperation failed during direct load, possibly due to a leader switchover.Solution: If direct load fails, you can try importing again.
ERROR 9105 (HY000) : S3 error
OceanBase error code: 9105
Cause:
- The input bucket is incorrect.
- The object storage endpoint is invalid.
- An unknown error occurred in S3.
Solution:
- Check whether the input bucket exists.
- Please check whether the object storage endpoint configuration is correct. Ensure that the endpoint is correctly configured and the object storage service is accessible.
- If the possibility of a bucket error is ruled out, contact the technical support personnel of OceanBase AI Database for assistance in troubleshooting.
ERROR 9106 (HY000) : Tenant snapshot '%.*s' does not exist
OceanBase error code: 9106
Cause: The specified tenant snapshot does not exist.
Solution: Verify whether the specified tenant snapshot is correct. If the snapshot does not exist, you may need to create a new snapshot or perform subsequent processing based on the actual situation.
ERROR 9107 (HY000) : Tenant snapshot '%.*s' already exist
OceanBase error code: 9107
Cause: The specified tenant snapshot already exists.
Solution: Verify whether the specified tenant snapshot already exists. If the snapshot already exists, you may need to perform other operations or proceed with subsequent handling based on the actual circumstances.
ERROR 9108 (HY000) : Tenant snapshot task timeout. %.*s
OceanBase error code: 9108
Cause: The tenant snapshot task timed out.
Solution: Check whether the execution time of the snapshot task is excessively long. You may need to increase the timeout period or optimize the task execution process.
ERROR 9111 (HY000) : Tenant snapshot task failed", "%.*s
OceanBase error code: 9111
Cause: The tenant snapshot task failed.
Solution: Check the cause of the snapshot task failure and handle it accordingly.
ERROR 9112 (HY000) : Tenant snapshot lock conflict", "%s
OceanBase error code: 9112
Cause: A lock conflict occurred during the tenant snapshot operation.
Solution: Check the specific details of the snapshot lock conflict. You may need to release the conflicting snapshot lock or adjust the lock usage.
ERROR 9113 (HY000) : checksum type %s is not supported for the input destination
OceanBase error code: 9113
Cause: The input destination does not support the checksum type %s.
Solution: Check the checksum type of the input destination and ensure a supported type is used.
ERROR 9114 (HY000) : storage destination is not valid
OceanBase error code: 9114
Cause: The object storage destination is invalid.
Solution: Check whether the object storage destination is correct and ensure it is a valid destination. You may need to correct the configuration or settings of the object storage destination.
ERROR 9115 (HY000) : can not connect to storage destination
OceanBase error code: 9115
Cause: Unable to connect to the object storage destination.
Solution: Check the connection configuration for the object storage destination and ensure the network connection is normal. You may need to correct the connection configuration, access the object storage key, or resolve the network connection issue.
ERROR 9116 (HY000) : no I/O operation permission of the object storage
OceanBase error code: 9116
Cause: No I/O operation permissions for the object storage.
Solution: Check the permission settings for the object storage and ensure the correct I/O operation permissions are granted. You may need to adjust the object storage permission settings or contact the administrator to obtain the appropriate permissions.
ERROR 9117 (HY000) : the specified s3_region does not match the endpoint
OceanBase error code: 9117
Cause: The
s3_regionis not specified, or the specifieds3_regiondoes not match the endpoint.Solution: Check whether the specified
s3_regionmatches the endpoint correctly. Ensure the corrects3_regionand corresponding endpoint are used in the configuration.
ERROR 9118 (HY000) : object storage endpoint is invalid
OceanBase error code: 9118
Cause: The object storage endpoint is invalid.
Solution: Check whether the endpoint configuration for the object storage is correct. Ensure the endpoint configuration is correct and the object storage service is accessible.
ERROR 9119 (HY000) : %s
OceanBase error code: 9119
Cause: Insufficient data (log archive or data backup) is available to restore to the specified point during data recovery. Possible causes include:
- The data backup set is incomplete, with missing or corrupted backup files.
- Archival logs are missing, causing the required logs for restoring to the specified point to be discontinuous.
- The restore point exceeds the range that can be recovered from the backup set and log archive, attempting to restore to a point without backup or logs.
Solution:
- Verify the restore point.
- Check the integrity and time range of the backup set.
- Confirm the continuity of the archived logs.
ERROR 9120 (HY000) : cannot find object on object storage
OceanBase error code: 9120
Cause: The specified object (file) cannot be found in object storage. Possible causes include:
- The accessed object does not exist.
- The specified path is incorrect.
- Insufficient permissions to access object storage.
Solution:
- Check whether the accessed object or file exists.
- Confirm whether the object storage path is correctly configured.
- Confirm whether the current user has access permissions for object storage.
ERROR 9129 (HY000) : object storage io error
- OceanBase error code: 9129
- Cause: An object storage error code. Common causes include object storage connectivity and compatibility issues.
- Solution: Please check the connectivity of object storage. If no connectivity issues are confirmed, contact technical support for assistance in troubleshooting.
ERROR 9130 (HY000) : the pwrite offset of the object storage is inconsistent
OceanBase error code: 9130
Cause: In object storage, the provided offset during an Append operation is inconsistent with the length of the current object.
Solution: Contact technical support for assistance.
ERROR 9131 (HY000) : the contents of pwrite are inconsistent
OceanBase error code: 9131
Cause: When performing an append operation in object storage, if the provided offset is smaller than the current object length for some reason, a GET request is initiated to read the overlapping content. An error is reported if the content is inconsistent.
Solution: Contact technical support for assistance.
ERROR 9132 (HY000) : object storage data checksum error
OceanBase error code: 9132
Cause: An object storage data checksum error occurred.
Solution: This is an internal error code. Contact technical support for troubleshooting.
ERROR 9133 (HY000) : Backup zone or backup idc or backup region invalid
OceanBase error code: 9133
Cause: The source zone/IDC/region specified for the backup or archive path does not exist (for example, if the cluster only has zones1 and zone2, but you set backup zone to zone=zone3,zone4, and then check shows zones3 and zone4 do not exist).
Solution: Query the
DBA_OB_ZONESview to confirm whether the entered locality exists. Correct it and reset the setting.
ERROR 9134 (HY000) : tmp file has already sealed
OceanBase error code: 9134
Cause: The temporary file has already been sealed.
Solution: Retry the SQL. If the issue persists, contact technical support for assistance.
ERROR 9135 (HY000) : tmp file exceeds disk quota
OceanBase error code: 9135
Cause: The amount of data from the temporary files that has been persisted to disk exceeds the set limit.
Solution: Check whether the SQL causing the error currently generates more data than expected (for example, if the expected maximum data size for persistent temporary files is 500 GB). If so, adjust the parameter
temporary_file_max_disk_sizeto an appropriate value.
ERROR 9136 (HY000) : Backup missing mview dependent tablet sstable, sstable maybe recycled
OceanBase error code: 9136
Cause: During backup, multi-version major SSTables were recycled.
Solution: Re-initiate the data backup.
ERROR 9138 (HY000) : No suitable replica found to perform backup
OceanBase error code: 9138
Cause: No suitable replica was found to perform the backup operation.
Solution: Check the replica status. After confirming it is normal, re-initiate the backup.
ERROR 9139 (HY000) : kms destination is not valid
OceanBase error code: 9139
Cause: When transparent encryption is enabled for the backup tenant, the key address was not specified or was specified incorrectly during tenant restore.
Solution: Specify the correct key address in the restore command, or specify the correct key address by setting the Session variable
SET @kms_encrypt_infobefore restore.
ERROR 9140 (HY000) : the object is locked by worm
OceanBase error code: 9140
Cause: Attempt to delete or modify an object in object storage that is in the retention period.
Solution: Check if a retention policy is configured for the backup or archive path. If a retention policy is configured, contact OceanBase Technical Support for assistance.
ERROR 9141 (HY000) : the resource has been released
OceanBase error code: 9141
Cause: A temporary file macroblock was unexpectedly released during use.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9142 (HY000) : the object cannot be overwritten with different content
OceanBase error code: 9142
Cause: Write a non-idempotent file with the same name to object storage configured with a retention policy.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9144 (HY000) : Unexpected macro cache file
OceanBase error code: 9144
Cause: An unexpected file appeared in the macroblock cache directory, possibly a file created by the user.
Solution: Contact OceanBase Technical Support for assistance.
ERROR 9147 (HY000) : can not access backup set file
OceanBase error code: 9147
Cause: During physical restore execution, the OBServer node cannot access the backup set file in the specified backup medium.
Solution: Check the connectivity of object storage. After confirming no connectivity issues, contact Technical Support for assistance.
ERROR 9148 (HY000) : disk quota is exceeded
OceanBase error code: 9148
Cause: The disk quota has been exceeded.
Solution: Clean up files or adjust the disk quota.
ERROR 9149 (HY000) : backup dest is not allowed to set when log_only policy exists
OceanBase error code: 9149
Cause: The
log_onlycleanup policy applies only to scenarios where only log archiving is enabled and no data backup is performed. When alog_onlycleanup policy exists, configuring a data backup path is not allowed.Solution: First, delete the
log_onlycleanup policy, then configure the data backup path.
ERROR 9150 (HY000) : log_only policy is not allowed to set when backup dest exists
OceanBase error code: 9150
Cause: The
log_onlycleanup policy applies only to scenarios where only log archiving is enabled and no data backup is performed. In scenarios where a data backup path is already configured, the cleanup policy cannot be set tolog_only.Solution: To use the
log_onlycleanup policy, you must first delete the configured data backup path.
ERROR 9151 (HY000) : backup clean can not start, because %s
OceanBase error code: 9151
Cause: Data backup and archiving cleanup cannot proceed. Possible reasons include the tenant's status being non-
NORMAL(for example,CREATING,RESTORE, etc.) or the tenant not having a cleanup policy configured (for expiration cleanup scenarios).Solution: Check the tenant status. For expiration cleanup scenarios, confirm whether the relevant tenant has a cleanup policy correctly configured.
ERROR 9152 (HY000) : backup device may be not mounted, %s did not read any data written by %s
OceanBase error code: 9152
Cause: The backup medium is not properly mounted.
Solution: Mount the backup medium correctly to ensure all OBServer nodes of the tenant initiating the archiving/backup/restoration operation can access the same backup medium.
ERROR 9153 (HY000) : backup device is not read and write strongly consistent. %s did not read the latest data written by %s.
OceanBase error code: 9153
Cause: The read and write operations on the backup medium are not strongly consistent.
Solution: If the backup medium is NFS, refer to the deployment instructions for mounting it in the specified manner; if the backup medium is object storage, contact the corresponding service provider.
ERROR 9155 (HY000) : micro block is too large and rejected from micro cache
OceanBase error code: 9155
Cause: The size of the microblock to be cached exceeds the upper limit allowed by the microblock cache (default: 128 KB), and the system refuses to write this microblock to the microblock cache.
Solution: This error is a normal internal stream control behavior of the system, which does not affect data correctness or business availability. Generally, no action is required. If it occurs frequently and significantly impacts read performance, contact technical support for assistance.
ERROR 9156 (HY000) : ss ls is in gc status
OceanBase error code: 9156
Cause: The log stream is in GC status and no longer accepts new write or operation requests.
Solution: Retry may succeed. If failures persist, contact OceanBase technical support for assistance.
ERROR 9158 (HY000) : the object type is invalid
OceanBase error code: 9158
Cause: An unexpected object type was encountered during data write to object storage. For example, a Put operation was performed on an Append-type object, or an Append operation was performed on a normal-type object.
Solution: Contact Technical Support for assistance.
ERROR 9159 (HY000) : available data backup set is not found
OceanBase error code: 9159
Cause: No backup set is available to restore to the specified time.
Solution: Select a different restore point or specify another backup set path.
ERROR 9200 (HY000) : Extend ssblock file to smaller is not allowed
OceanBase error code: 9200
Cause: SSBlock files cannot be reduced in size.
Solution: Check whether the size specified by
ALTER SYSTEM SET datafile_sizeis greater than the current SSBlock file. If so, contact Technical Support for assistance.
ERROR 9201 (HY000) : Mark blocks timeout(5s) in auto extend process when alloc block fail
OceanBase error code: 9201
Cause: Macroblock marking failed after automatic SSBlock file extension.
Solution: Contact Technical Support for assistance.
ERROR 9202 (HY000) : Auto extend param is not ready to start extending file
OceanBase error code: 9202
Cause: Automatic extension may not have started due to configuration issues, or the preset disk usage of
datafilehas reached its limit.Solution: Check if the
free_sizefield in the__all_virtual_disk_stattable is 0. If it is, disk space is exhausted. You need to increase thedatafilethreshold or perform disk expansion.