This error code range indicates Root Service error codes.
ERROR 4507 (42000) : Convert error
OceanBase error code: 4507
Cause: An IP address was printed to a string.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 4512 (HY000) : RootServer state error
OceanBase error code: 4512
Cause: The current state of the RootServer does not allow the operation.
Solution: Check the current state of the RootServer. You can query the
__all_virtual_core_meta_tableto determine if any RootServer is online.
ERROR 4515 (HY000) : No replica is valid
OceanBase error code: 4515
Cause: The replica status is incorrect.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 4519 (HY000) : Iteration was stopped
OceanBase error code: 4519
Cause: This is not an error code; it indicates that the MemTable iteration has ended.
Solution: No action required.
ERROR 4530 (HY000) : Zone info \'%s\' not exist
OceanBase error code: 4530
Cause: The zone does not exist. This usually occurs during a major compaction in a specified zone or when reporting a leader switchover error.
Solution: Check if the specified zone exists. You can query the
DBA_OB_ZONEStable to resolve this.
ERROR 4544 (42000) : Root not integrated
OceanBase error code: 4544
Cause: During the rotation major compaction, this error is reported if the number of replicas for a partition does not reach a majority. It is reported for partitions with fewer than a majority of replicas.
Solution: Immediate manual intervention is required to check the reason why the majority was lost for that partition.
ERROR 4547 (HY000) : global merge not started
OceanBase error code: 4547
Cause: Pre-check before manual major compaction rotation. If the cluster has not initiated a major freeze, manual compaction cannot be initiated.
Solution: Check whether the cluster has initiated a major freeze.
ERROR 4548 (HY000) : merge already started
OceanBase error code: 4548
Cause: Pre-check before manual major compaction rotation. If a zone has already initiated manual compaction, manual compaction cannot be initiated for that zone again.
Solution: Check whether manual compaction has already been initiated for that zone.
ERROR 4549 (HY000) : rootservice already exist
OceanBase error code: 4549
Cause: Self-check during the startup of the current RS. If another replica is already the RS, the current RS abandons the role.
Solution: This is a self-check before RS startup and does not require handling.
ERROR 4550 (HY000) : rootservice is shutdown
OceanBase error code: 4550
Cause: The RS replica to which the request was sent is not in the working state. This may be because the RS is currently leaderless, or the request was sent to a standby replica of the RS.
Solution: Usually, retrying the request resolves the issue. When the RS is leaderless, further investigation is required.
ERROR 4551 (HY000) : server migrate in denied
OceanBase error code: 4551
Cause: During the execution of a
balance task, an OBServer node may fail if the disk is full or there are too many partitions. In this case, the OBServer node returns a packet to the RS indicating the failure of thebalance taskand reports this error code.Solution: The RS stops scheduling tasks to the server and retries after a specified period. If the server continuously reports this error code, manual intervention is required to check for disk overload or excessive partitions.
ERROR 4552 (HY000) : rebalance task can not executing now
OceanBase error code: 4552
Cause: Before executing a
balance task, the RS performs a series of checks, such as whether the leader switchover succeeded, whether the target machine already has the replica, and whether the replica schema exists. If these checks indicate thebalance taskcannot be executed, the task ends and this error code is reported.Solution: Check the pre-execution conditions of the
balance taskand troubleshoot based on the specific error. For example, if the leader switchover failed before migrating the leader, further investigation is needed to determine the cause of the leader switchover failure.
ERROR 4554 (HY000) : rebalance task not in progress on observer
OceanBase error code: 4554
Cause: The RS periodically sends an RPC to the OBServer node to check whether each
balance taskexists. If abalance taskno longer exists, the RS marks thebalance taskas completed and returns this error code.Solution: This error is usually caused by a delay in reporting from the meta_table or packet loss when the
balance taskreturns a packet to the RS. Generally, no action is required.
ERROR 4605 (HY000) : Data source timeout
OceanBase error code: 4605
Cause: An RPC timed out during storage layer migration replication.
Solution: Check the cause of the long duration or increase the timeout period.
ERROR 4615 (HY000) : tablegroup is not empty
OceanBase error code: 4615
Cause: This error is reported when deleting a table group if any of the following conditions exist:
Tables are present in the table group.
The table group is the database's
default_tablegroup_id.The table group is the tenant's
default_tablegroup_id.
Solution: Delete the tables in the table group but do not delete the
default_tablegroup_idtable group.
ERROR 4620 (HY000) : server status is not valid
OceanBase error code: 4620
Cause: This error is reported when the server value is invalid.
Solution: Change the invalid server value.
ERROR 4621 (HY000) : wait elect partition leader timeout
OceanBase error code: 4621
Cause: Timeout occurred while waiting for leader election.
Solution: Check the cause of the long duration or increase the timeout period.
ERROR 4622 (HY000) : wait all rs online timeout
OceanBase error code: 4622
Cause:
Used during bootstrap to check whether the server where the RS resides is
ALIVE. If it is notALIVE, this error is reported.Used during Bootstrap to check whether the server where the RS resides is
in_serviceor whether itsstart_service_timeis0. If it is notin_serviceorstart_service_timeis0, this error is reported.
Solution: Investigate the cause of the long duration or increase the timeout period.
ERROR 4624 (HY000) : zone '%s' server '%s' %s resource is not enough to hold a new unit
OceanBase error code: 4624
Cause:
When allocating resources (including scenarios such as resource pool creation and modification, unit migration, and replica replenishment), checks are performed to ensure sufficient resources are available. If resources are insufficient, this error is reported.
When creating a table, checks are performed to ensure sufficient resources are available. If resources are insufficient, this error is reported.
Solution: Adjust the resource allocation based on the specific cause.
ERROR 4626 (HY000) : resource pool \'%s\' has already been granted to a tenant
OceanBase error code: 4626
Cause: A tenant is already using this resource pool.
Solution: Check
__all_resource_poolto obtain the tenant ID (tenant_id) that references this resource pool. You can use the following solutions:Delete the corresponding tenant.
Scale down the tenant to reduce its resource pool usage.
Create another resource pool that does not consume this resource pool.
ERROR 4628 (HY000) : server has already been deleted
OceanBase error code: 4628
Cause: The server is already in the Deleting state and cannot be deleted again with the
delete servercommand.Solution: A defensive error message; no need to execute the
delete servercommand again.
ERROR 4629 (HY000) : server is not in deleting status
OceanBase error code: 4629
Cause: An internal error. A defensive error message to terminate the
delete servertask.Solution: An internal error code. Please contact technical support for assistance.
ERROR 4630 (HY000) : server not in server white list
OceanBase error code: 4630
Cause: Internal error. The server is not in the current cluster. Common scenarios include:
A brief error message is displayed before service is provided after an RS switchover.
A brief error message is displayed during the cluster Bootstrap process.
A newly added machine has not been added using the
add servercommand.Database migration from another cluster.
Solution:
For the scenarios where no service is provided after an RS switchover or during the cluster Bootstrap process, if the error persists for only a short time, no action is required.
For the scenario where a newly added machine has not been added using the
add servercommand, confirm whether theadd serveroperation was missed.For the scenario of database migration from another cluster, confirm whether database migration has occurred. If so, contact technical support for assistance in troubleshooting.
ERROR 4631 (HY000) : server zone not match
OceanBase error code: 4631
Cause: Defensive validation. The Server and Zone information specified during
start server,delete server, orstop serverdoes not match.Solution: In cases where a Zone is specified, confirm whether the Server and Zone in
__all_servermatch.
ERROR 4632 (HY000) : zone num has reach max zone num
OceanBase error code: 4632
Cause: Defensive error during
add zone. The number of Zones exceeds the maximum limit of 64.Solution: Remove unnecessary Zone information using the
delete zonecommand.
ERROR 4633 (HY000) : zone status not match
OceanBase error code: 4633
Cause: A defensive error of the
delete/start zonecommand. When you execute theDELETE ZONEstatement, the zone status must beinactive. When you execute theSTART ZONEstatement, the zone status must be other thanactive.Solution: Query the content of the
DBA_OB_ZONEStable to confirm the zone status. If the status does not meet expectations, contact technical support for assistance.
ERROR 4634 (HY000) : resource unit \'%s\' is referenced by some resource pool
OceanBase error code: 4634
Cause: When you delete or use a resource unit, it is found that the resource unit is referenced by a resource pool.
Solution:
Check the
__all_unit_configor__all_resource_pooltable to see which resource pool references the resource unit.Execute the
ALTER RESOURCE POOLstatement to modify the resource units referenced by the resource pool so that it no longer references this resource unit. Alternatively, execute theDROP RESOURCE POOLstatement to directly drop the resource pool.Execute the
DROP RESOURCE UNITorALTER RESOURCE POOLstatement to delete or use the resource unit.
ERROR 4636 (HY000) : table schema primary zone different with other table in same tablegroup
OceanBase error code: 4636
Cause: A defensive error. The
primary_zoneof the table does not match that of the other tables in the same tablegroup.Solution: The
primary_zoneof all tables in the same tablegroup must match.
ERROR 4637 (HY000) : server is not active
OceanBase error code: 4637
Cause: An internal error. The server is in the
inactivestate.Solution: Generally, no action is required. For details, contact technical support for assistance.
ERROR 4638 (HY000) : The RootServer is not the master
OceanBase error code: 4638
Cause: The root server is undergoing a leader switchover or the RS service is restarting.
Solution: Generally, you can try again after a while. If the error persists for a long time, contact technical support for assistance.
ERROR 4640 (HY000) : The chosen partition servers belong to same zone
OceanBase error code: 4640
Cause: The Bootstrap command specifies servers with identical zone information in
rs_list.Solution: Currently, for the same partition, a zone can have only one Paxos member. You need to adjust the zone information of the servers in the
rs_listparameter of the Bootstrap command.
ERROR 4641 (HY000) : Duplicated zone \'%s\' in zone list %s
OceanBase error code: 4641
Cause: Zone information is duplicated in
zone_list.Solution: Remove duplicate zone information from
zone_list.
ERROR 4646 (HY000) : tenant name \'%s\' over max_tenant_name_length %ld
OceanBase error code: 4646
Cause: The
tenant_nameis invalid (empty or exceeds 64 characters).Solution: Adjust the
tenant_name.
ERROR 4647 (HY000) : resource pool list is empty
OceanBase error code: 4647
Cause: No corresponding resource pool was specified when creating the tenant.
Solution: Specify a resource pool when creating the tenant.
ERROR 4648 (HY000) : resource unit \'%s\' not exist
OceanBase error code: 4648
Cause: The specified unit type does not exist.
Solution: Verify whether the specified resource pool exists.
ERROR 4649 (HY000) : resource unit \'%s\' already exist
OceanBase error code: 4649
Cause: The created unit type already exists.
Solution: Modify the unit type name and create it again.
ERROR 4650 (HY000) : resource pool \'%s\' not exist
OceanBase error code: 4650
Cause: The specified resource pool does not exist.
Solution: Check whether the resource pool exists.
ERROR 4651 (HY000) : resource pool \'%s\' exist
OceanBase error code: 4651
Cause: The resource pool already exists.
Solution: Rename the resource pool and then create it again.
ERROR 4652 (HY000) : wait leader switch timeout
OceanBase error code: 4652
Cause: When stopping a zone or server, the operation failed due to a timeout caused by an excessively long leader switchover time.
Solution: Increase the timeout period or contact technical support for assistance.
ERROR 4653 (HY000) : location not exist
OceanBase error code: 4653
Cause: During SQL execution, the Location information was found to be non-existent.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 4654 (HY000) : location leader not exist
OceanBase error code: 4654
Cause: During SQL execution, the Leader was found to be non-existent in the Location information.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 4655 (HY000) : zone not active
OceanBase error code: 4655
Cause: The specified zone has been decommissioned.
Solution: Wait until the zone is reactivated before proceeding.
ERROR 4656 (HY000) : resource pool unit num is bigger than zone server count
OceanBase error code: 4656
Cause: The number of units in a zone of a resource pool exceeds the number of servers in that zone.
Solution: Ensure the number of units in a zone is less than the number of servers in that zone.
ERROR 4657 (HY000) : resource pool list %s unit servers intersect
OceanBase error code: 4657
Cause: Zones exist in all resource pools belonging to the same tenant that intersect.
Solution: Ensure no zones exist in all resource pools belonging to the same tenant that intersect.
ERROR 4659 (HY000) : invalid %s value, min value is %s
OceanBase error code: 4659
Cause: Invalid unit size.
Solution: Change the unit size to be between
min_valandmax_val.
ERROR 4660 (HY000) : Can not stop server in multiple zones, there are already servers stopped in zone:%s
OceanBase error code: 4660
Cause: Servers across zones cannot be stopped at once.
Solution: Ensure only servers in one zone are stopped at a time.
ERROR 4661 (HY000) : Session already exist
OceanBase error code: 4661
Cause: Conflict with an existing session when creating a session.
Solution: This error generally does not occur. If it does, contact technical support for assistance.
ERROR (HY000) : Timeout OB_GET_LOCATION_TIME_OUT
OceanBase error code: 4664
Cause: Obtaining
locationcachetimed out during SQL execution.Solution: Increase the timeout period or contact technical support for assistance.
ERROR 4666 (HY000) : cluster name does not match to \'%s\'
OceanBase error code: 4666
Cause: The
cluster namespecified in the command is incorrect.Solution: Execute
show parameters where name ='cluster'to obtain the correctcluster name.
ERROR 4667 (HY000) : Please check new zone in zone_merge_order. You can show parameters like 'zone_merge_order'
OceanBase error code: 4667
Cause: If
zone_merge_orderwas set duringadd zone, you need to adjust thezone_merge_orderparameter accordingly.Solution: Run
show parameters like 'zone_merge_order'to view and adjust thezone_merge_orderparameter.
ERROR 4668 (HY000) : The zone is not empty and cannot be deleted. You should delete the servers of the zone. There are %ld servers alive and %ld not alive
OceanBase error code: 4668
Cause: A non-empty zone cannot be deleted.
Solution: Delete the servers in the zone first, then delete the zone.
ERROR 4671 (HY000) : full replica num not enough
OceanBase error code: 4671
Cause: A
FULLreplica was not created when the partition was created.Solution: For details, contact technical support for assistance.
ERROR 4672 (HY000) : replica num not enough
OceanBase error code: 4672
Cause: The number of replicas does not reach a majority.
Solution: Check the number of replicas for the corresponding partition.
ERROR 4674 (HY000) : run job not success yet
OceanBase error code: 4674
Cause: In OFS block interface mode, the next task is scheduled before the previous block recycling task is accepted.
Solution: Generally no action is required. For details, contact technical support for assistance.
ERROR 4675 (HY000) : no need to rebuild
OceanBase error code: 4675
Cause: The replica that triggered a rebuild may have caught up with its upstream logs.
Solution: No rebuild is needed.
ERROR 4676 (HY000) : need remove unneed table
OceanBase error code: 4676
Cause: A MemTable has been flushed but not released, and it is encountered again during the next minor compaction.
Solution: Generally no action is required. For details, contact technical support for assistance.
ERROR 4677 (HY000) : no need to merge
OceanBase error code: 4677
Cause: No MemTable or SSTable meeting minor compaction criteria was found in this minor compaction scheduling.
Solution: Generally no action is required. For details, contact technical support for assistance.
ERROR 4681 (HY000) : rpc need reconnect
OceanBase error code: 4681
Cause: This is an error code from logical migration, which is no longer used.
ERROR 4683 (HY000) : src do not allow migrate
OceanBase error code: 4683
Cause: Migration is not allowed at the source. This might occur if the source is being deleted.
Solution: Please try again.
ERROR 4684 (HY000) : Too many partitions were defined for this tenant
OceanBase error code: 4684
Cause: The partition quota for the tenant has been reached, and no more partitions can be created for the tenant.
Solution: Check if any partitions remain in the recycle bin.
If so, execute
purge recyclebinunder the tenant connection. After the partition is cleaned up by the garbage collector, some partition space will be freed up.If none remain, it means the tenant has reached the maximum number of partitions allowed. You need to allocate more memory for the tenant to create more partitions.
ERROR 4685 (HY000) : active memtable not exist
OceanBase error code: 4685
Cause: The active MemTable does not exist.
Solution: This is an internal error code. Please contact technical support for confirmation.
ERROR 4686 (HY000) : Should use leader replica for duplicate table after DML operator
OceanBase error code: 4686
Cause: A write operation has already been performed on a replicated table partition. Subsequent read operations should be routed to the leader replica of the replicated table partition.
Solution: This is an internal error code. If returned, please contact technical support for confirmation.
ERROR 4688 (HY000) : standby tenant is read only
OceanBase error code: 4688
Cause: The standby cluster supports only read operations.
Solution: To modify the standby cluster, you need to perform a role switch to convert it into the primary cluster.
ERROR 4690 (HY000) : other primary cluster already exist, can not start as primary
OceanBase error code: 4690
Cause: Another primary cluster is detected, preventing this cluster from taking over as the primary.
Solution: This is an internal error code. If returned, please contact technical support for confirmation.
ERROR 4691 (HY000) : array binding needs to switch iterator
OceanBase error code: 4691
Cause: An internal error occurred, marking the end of the iterator.
Solution: This is an internal error code. If returned, please contact technical support for confirmation.
ERROR 4692 (HY000) : standby cluster not empty
OceanBase error code: 4692
Cause: The standby cluster is not empty and cannot be added.
Solution: Clear the standby cluster, perform a new bootstrap, and then add the standby cluster.
ERROR 4693 (HY000) : not primary cluster
OceanBase error code: 4693
Cause: The current cluster is not the primary cluster.
Solution: Confirm the role of the current cluster.
ERROR 4694 (HY000) : check drop column failed
OceanBase error code: 4694
Cause: The check to determine whether
drop columnis allowed failed. This usually occurs when the database is in a major compaction state, which does not allowdrop column.Solution: Wait for all partition major compactions to complete. If the error persists after major compaction is complete, contact technical support for confirmation.
ERROR 4695 (HY000) : not standby cluster
OceanBase error code: 4695
Cause: The target cluster role is not a standby cluster, and adding it is not allowed.
Solution: Check the role of the target cluster to be added. A standby cluster can only be added to a primary cluster.
ERROR 4696 (HY000) : cluster version not compatible
OceanBase error code: 4696
Cause: The version number of the standby cluster to be added does not match the primary cluster version number, and adding it is not allowed.
Solution: In the primary-standby deployment configuration, the roles of the primary and standby clusters must be the same.
ERROR 4697 (HY000) : wait trans table merge finish timeout
OceanBase error code: 4697
Cause: Transaction status table minor compaction timed out.
Solution: An internal error code. If this error is returned, contact technical support for confirmation.
ERROR 4698 (HY000) : skip renew location by rpc
OceanBase error code: 4698
Cause: Internal RPC failed to refresh the location cache.
Solution: This is an internal error code. If it is returned, contact technical support for confirmation.
ERROR 4699 (HY000) : renew location by rpc failed
OceanBase error code: 4699
Cause: Internal RPC failed to refresh the location cache.
Solution: This is an internal error code. If it is returned, contact technical support for confirmation.
ERROR 4700 (HY000) : cluster id does not match
OceanBase error code: 4700
Cause: The
cluster iddoes not match the current cluster ID.Solution: Query the current cluster ID and reconfirm the
cluster idparameter.
ERROR 4701 (HY000) : parameter cannot be modified because specified value is invalid
OceanBase error code: 4701
Cause: The specified parameter value is invalid.
Solution: Check the given parameter value and re-execute the related command.
ERROR 4702 (HY000) : %s %.*s already exists
OceanBase error code: 4702
Cause: The resource object already exists and cannot be created repeatedly.
Solution: Change the resource object name and re-execute the related command.
ERROR 4703 (HY000) : resource plan %.*s does not exist
OceanBase error code: 4703
Cause: The resource plan does not exist.
Solution: Specify the correct resource plan name and retry the related command.
ERROR 4704 (HY000) : value %ld for %s is outside valid range of 0 to 100
OceanBase error code: 4704
Cause: The resource usage range is incorrect; it must be between
[0,100].Solution: Specify the correct range value.
ERROR 4705 (HY000) : plan directive %.*s, %.*s does not exist
OceanBase error code: 4705
Cause: The plan directive does not exist.
Solution: Specify the correct plan directive.
ERROR 4706 (HY000) : plan directive %.*s, %.*s already exists
OceanBase error code: 4706
Cause: The plan directive already exists.
Solution: Specify a different plan directive name.
ERROR 4707 (HY000) : plan directive name '%.*s' not supported
OceanBase error code: 4707
Cause: The specified plan directive name does not exist when creating a user resource group mapping.
Solution: Specify a valid directive name.
ERROR 4708 (HY000) : Failover is not allowed
OceanBase error code: 4708
Cause: Failover operation is not allowed.
Solution: Troubleshoot the reason why failover is not allowed based on the error message.
ERROR 4709 (HY000) : Add cluster not allowed. Actions: %s
OceanBase error code: 4709
Cause: Adding a standby cluster is not allowed.
Actionsprovides the corresponding reason and solution.Solution: Resolve the issue indicated in
Actionsand then perform the failover operation.
ERROR 4710 (HY000) : consumer group %.*s does not exist
OceanBase error code: 4710
Cause: The user resource group does not exist.
Solution: Specify the correct user resource group name.
ERROR 4711 (HY000) : cluster is not accessible, cluster_id: %ld
OceanBase error code: 4711
Cause: The specified cluster is inaccessible.
Solution: Verify that the
cluster_idis correct. If it is correct, check whether the cluster is accessible and whether the Root Service is running normally.
ERROR 4712 (HY000) : rebuild global index:'%.*s' failed when drop/truncate partitions
OceanBase error code: 4712
Cause: A partition drop or truncate operation succeeded, but the corresponding global index rebuilding task failed.
Solution:
Check for invalid indexes.
Drop these invalid indexes.
Recreate the indexes.
ERROR 4713 (HY000) : unique/primary keys in table referenced by enabled foreign keys
OceanBase error code: 4713
Cause: The operation conflicts with a foreign key.
Solution: Disassociate the foreign key, then perform the operation.
ERROR 4719 (HY000) : log stream does not exist
OceanBase error code: 4719
Cause: The corresponding log stream does not exist on the current OBServer node.
Solution: This is an internal error code. If it is returned, contact technical support to confirm.
ERROR 4720 (HY000) : too many log streams were defined for this tenant
OceanBase error code: 4720
Cause: A single OBServer node supports a maximum of 100 log streams per tenant. If too many log streams are created, this error is reported.
Solution: Reduce the number of log streams for the tenant on a single OBServer node.
ERROR 4721 (HY000) : log stream location does not exist
OceanBase error code: 4721
Cause: The location information for the corresponding log stream was not found in the internal table.
Solution: Retry automatically. If the error persists after retrying, check whether the corresponding log stream exists and has been reported successfully.
ERROR 4722 (HY000) : log stream location leader does not exist
OceanBase error code: 4722
Cause: No leader was found in the location information, which may be caused by the absence of a leader replica for the log stream.
Solution: Check whether the corresponding log stream has a leader replica.
ERROR 4723 (HY000) : mapping between tablet and log stream does not exist
OceanBase error code: 4723
Cause: The log stream information for the Tablet was not found in the internal table.
Solution: Retry automatically. If the error persists after retrying, check whether the corresponding Tablet exists and has been reported successfully.
ERROR 4724 (HY000) : unexpected tablet existence
OceanBase error code: 4724
Cause: An internal error occurred. An unexpected tablet exists, possibly because a duplicate tablet was created.
Solution: Contact technical support for confirmation.
ERROR 4725 (HY000) : tablet does not exist
OceanBase error code: 4725
Cause: An internal error occurred. An non-existent tablet was accessed. For example, during an SQL query, if a Truncate or Drop operation is performed on a table or partition that is undergoing minor compaction, the query may indicate the tablet does not exist.
Solution: Contact technical support for confirmation.
ERROR 4727 (HY000) : ls need revoke
OceanBase error code: 4727
Cause: During an active leader switchover, the sub-module that registers and senses leader and standby switchover failed and could not roll back to the original state.
Solution: The kernel automatically handles this by executing a forced removal logic.
ERROR 4732 (HY000) : check cluster status", "%s
OceanBase error code: 4732
Cause: The cluster status is incorrect.
Solution: Check the
__all_cluster_infotable to see if there are any abnormalities in thecluster_roleorswitchover_statusfields of the cluster.
ERROR 4733 (HY000) : zone '%s' resource not enough to hold %ld new unit. You can check resource info by views: DBA_OB_UNITS, GV$OB_UNITS, GV$OB_SERVERS.\n%s
OceanBase error code: 4733
Cause: The remaining resources in the ZONE are insufficient to create all units. This error occurs mainly in the following scenarios:
- Creating a resource pool.
- Adjusting the number of units in a resource pool.
- Adjusting unit specifications.
Solution: Check the allocated resources and adjust the required resources appropriately.
ERROR 4734 (HY000) : zone '%s' server not enough to hold %ld new unit, please check zone valid servers
OceanBase error code: 4734
Cause: The number of valid OBServer nodes in the ZONE is insufficient to create all units. This error occurs mainly in the following scenarios:
- Creating a resource pool.
- Adjusting the number of units in a resource pool.
- Adjust the unit specifications.
Solution: Check the number of valid OBServer nodes and adjust the required resources accordingly.
ERROR 4735 (HY000) : sstable not exist
OceanBase error code: 4735
Cause: During migration, the corresponding SSTable cannot be found when multiple SSTables on the source side are merged into one.
Solution: Generally, you only need to retry after a while. If the error persists for a long time, contact technical support for assistance.
ERROR 4736 (HY000) : resource unit value is invalid
OceanBase error code: 4736
Cause: The unit specification value is invalid.
Solution: Adjust it to a valid unit specification.
ERROR 4737 (HY000) : log stream already exist
OceanBase error code: 4737
Cause: The log stream at the destination end of the migration replication already exists.
Solution: Generally, no action is required. The destination will wait for the local log stream to be GCed and then retry successfully. If the error persists for a long time, contact technical support for assistance.
ERROR 4740 (HY000) : log stream replica task result is uncertain
OceanBase error code: 4740
Cause: The disaster recovery task liveness detection mechanism has found that the log stream replica has an invalid task, and the task execution result is uncertain.
Solution: No action is required.
ERROR 4741 (HY000) : log stream wait log replay timeout
OceanBase error code: 4741
Cause: Timeout waiting for clog replay at the destination end of migration replication.
Solution: Generally, no action is required. Migration will retry. If the error persists for a long time, contact technical support for assistance.
ERROR 4742 (HY000) : log stream wait tablet ready timeout
OceanBase error code: 4742
Cause: Timeout occurred while the destination end of migration waited for all tablets to become ready.
Solution: Generally no action is required as the migration will be retried. If the error persists for a long time, contact technical support for assistance.
ERROR 4743 (HY000) : freeze service epoch is not expected
OceanBase error code: 4743
Cause: This error commonly occurs when the epoch of the major compaction service is inconsistent due to logstream leader switchover.
Solution: An internal error code of the major compaction feature. Contact technical support for assistance.
ERROR 4744 (HY000) : already exist larger frozen_scn in __all_freeze_info", "%s
OceanBase error code: 4744
Cause: Major freeze was executed again before the previous major compaction completed.
Solution: Wait for the previous major compaction to finish before initiating a major freeze.
ERROR 4745 (HY000) : delete server not allowed
OceanBase error code: 4745
Cause: No other server in the same zone can host the data from the server to be deleted. This mainly includes two scenarios:
- No idle server is available in the same zone.
- An idle server exists, but its resources are insufficient to host the units from the server to be deleted.
Solution: Add an idle server to the same zone or scale up the existing idle server.
ERROR 4746 (HY000) : Network error and packet status unknown. Abort auto retry
- OceanBase error code: 4746
- Cause: During the execution of a distributed plan, network instability or node downtime causes scheduling failure.
- Solution: Rerun the SQL statement.
ERROR 4747 (HY000) : arbitration service does not exist, %s
OceanBase error code: 4747
Cause: The arbitration service address has not been configured for the cluster.
Solution: Arbitration-related operations are not supported when the arbitration service address is not configured. You can add an arbitration service address for the cluster by using OCP or executing the SQL command
alter system add arbitration service '$svr_ip:$svr_port';.
ERROR 4748 (HY000) : arbitration service already exist, %s
OceanBase error code: 4748
Cause: The cluster already has a valid arbitration service address.
Solution: A cluster does not support configuring multiple arbitration services simultaneously.
ERROR 4751 (HY000) : wait degration finished timeout
OceanBase error code: 4751
Cause: Timeout occurred while waiting for tenant downgrade during server stop.
Solution: Reissue the Stop Server command until it succeeds.
ERROR 4752 (HY000) : rootservice start process has failure
- OceanBase error code: 4752
- Cause: The Root Service startup process failed.
- Solution: Contact technical support for assistance.
ERROR 4753 (HY000) : rootservice stop process has failure
- OceanBase error code: 4753
- Cause: The Root Service stop process failed.
- Solution: Contact technical support for assistance.
ERROR 4754 (HY000) : root inspection is not passed
- OceanBase error code: 4754
- Cause: Root check failed.
- Solution: Contact technical support for assistance.
ERROR 4755 (HY000) : rootservice background thread may be hung
- OceanBase error code: 4755
- Cause: A background thread of Root Service may be hung.
- Solution: Contact technical support for assistance.
ERROR 4756 (HY000) : Migration src and dest version is not compatible
- OceanBase error code: 4756
- Cause: The source and destination versions are incompatible.
- Solution: No action is required. The migration replication kernel will implement a retry.
ERROR 4757 (HY000) : Cluster info may remain on arbitration server '%.*s', please make sure whether to use ob_admin to clean it.
- OceanBase error code: 4757
- Cause: When replacing or deleting a cluster's arbitration service, it is detected that cluster information may still exist on the arbitration server. You need to use the ob_admin tool to clear the cluster information.
- Solution: Before using the ob_admin tool to clear the information, confirm whether you need to clear the cluster information. If you are certain you need to clear it, you can use the ob_admin tool; if not, do not perform the clearance operation.
ERROR 4758 (HY000) : the arbitration service may be unavailable, please check and retry
- OceanBase error code: 4758
- Cause: It is detected that the arbitration service may be unavailable. You need to check and retry.
- Solution: Check the status of the arbitration service or check the network connection.
ERROR 4759 (HY000) : An error was ignored when accessing virtual table, actual error code: %d
- OceanBase error code: 4759
- Cause: An error occurred when accessing the virtual table, but the error was ignored. For example, the error code that occurred was 1305.
- Solution: Check the error logs for error code 1305 to find the error message that occurred when accessing the virtual table. Based on the information in the error logs, fix the error that occurred when accessing the virtual table.
ERROR 4760 (HY000) : log stream is offline
- OceanBase error code: 4760
- Cause: The log stream is going offline from this machine and cannot be read correctly.
- Solution: Please re-execute the SQL statement.
ERROR 4762 (HY000) : This operation has been finished without checking ls status
- OceanBase error code: 4762
- Cause: The tenant parameter
enable_rebalanceis disabled, causing log streams not to be balanced. Therefore, some operations require checking whether log streams are balanced, but this step is skipped and the operation ends directly. - Solution: No action is required.
ERROR 4763 (HY000) : invalid user.table.column, table.column, or column specification
- OceanBase error code: 4763
- Cause: The user, table, or column name specified in the SQL statement is incorrect or invalid.
- Solution: Check whether the user, table, or column specified in the SQL statement is correct, ensuring no spelling or syntax errors.
ERROR 4764 (HY000) : unknown SET option '%s'
- OceanBase error code: 4764
- Cause: An unknown SET option was specified when setting a parameter.
- Solution: Check whether the option specified in the SET command is correct, ensuring no spelling or syntax errors.
ERROR 4765 (HY000) : create standby tenant may fail, %s
- OceanBase error code: 4765
- Cause: The standby tenant could not be created for some reason.
- Solution: Check the recovery status of the system log stream in the
V$OB_LS_LOG_RESTORE_STATUStable.
ERROR 4766 (HY000) : ls waiting safe destory, %s
- OceanBase error code: 4766
- Cause: Indicates that the log stream is waiting to be safely destroyed.
- Solution: No action required.
ERROR 4767 (HY000) : log stream is not leader log stream
OceanBase error code: 4767
Cause: The log stream is not the Paxos leader.
Solution: The background thread will attempt to execute on the leader after detecting this error.
ERROR 4768 (HY000) : ls lock conflict, %s
OceanBase error code: 4768
Cause: Log stream lock conflict.
Solution: Resolve the log stream lock conflict or wait for the lock to release.
ERROR 4769 (HY000) : invalid root key", "%s
OceanBase error code: 4769
Cause: Invalid root key.
ERROR 4780 (HY000) : This service_name is not found in the tenant
OceanBase error code: 4780
Cause: The specified service_name does not exist.
Solution: Check if there is an issue with the service_name specified in the connection string, or check the connectivity between the Proxy and OCP.
ERROR 4781 (HY000) : The service has not started on all servers
OceanBase error code: 4781
Cause: When performing service_name-related maintenance operations (for example, creating or deleting a service_name), and notifying each OBServer node for effect, some servers failed.
Solution: Wait for a while. Normally, the background thread refreshes periodically, with a default refresh interval of about 10 seconds.
ERROR 4782 (HY000) : The tenant is not PRIMARY
OceanBase error code: 4782
Cause: When service_name and failover_mode are specified, the tenant must be the primary tenant. If the current tenant is not the primary tenant, it is a proxy routing error.
Solution: The proxy cache or OCP cache is incorrect. If both the proxy and OCP caches are normal, the system will retry and refresh. You can then re-execute the SQL, which will be routed to the correct primary tenant.
ERROR 4783 (HY000) : The service has stopped
OceanBase error code: 4783
Cause: The specified service_name has been stopped by the user.
Solution: You need to start the service_name using the O&M command:
ALTER SYSTEM START SERVICE service_name TENANT = tenant_name;.
ERROR 4784 (HY000) : Server '%s' connection error
OceanBase error code: 4784
Cause: The Root Service failed to connect to the target OBServer node when adding an OBServer.
Solution:
- Check the network connectivity between the Root Service and the target OBServer.
- Check whether the target OBServer process is started and initialized.
- Check whether the target OBServer has been added to other clusters, and whether the data directory and configuration file directory are empty before the process starts.