ORA-00000 to ORA-00999

ORA-00000: PX DOP downgrade from %ld to %ld

• OceanBase error code: 5780

• SQLSTATE: HY000

• Cause: Normal exit.

ORA-00000: parallel_max_servers downgrade due to insufficent cpu resource from %ld to %ld. deprecated

• OceanBase error code: 5781

• SQLSTATE: HY000

• Cause: Normal exit.

  Note

  This error code is no longer used in the current version.

ORA-00001: unique constraint \'%s\' for key \'%.*s\' violated

• OceanBase error code: 5024

• SQLSTATE: 23000

• Cause: The UPDATE or INSERT statement attempts to insert duplicate keys.

• Solution: Remove the UNIQUE constraint or do not insert the key.

ORA-00001: unique constraint (%.*s) violated

• OceanBase error code: 5595

• SQLSTATE: 23000

• Cause: The UPDATE or INSERT statement attempts to insert duplicate keys.

• Solution: Remove the UNIQUE constraint or do not insert the key.

ORA-00001: unique constraint violated, column '%.*s' with value '%.*s' in %s

• OceanBase error code: 5334

• SQLSTATE: HY000

• Cause: The UPDATE or INSERT statement attempts to insert duplicate keys.

• Solution: Remove the UNIQUE constraint or do not insert the key.

ORA-00001: unique constraint (%.*s) violated

• OceanBase error code: 5562

• SQLSTATE: HY000

• Cause: The UPDATE or INSERT statement attempts to insert duplicate keys.

• Solution: Remove the UNIQUE constraint or do not insert the key.

ORA-00036: maximum number of recursive SQL levels (%ld) exceeded

• OceanBase error code: 9697

• SQLSTATE: HY000

• Cause: The number of recursive SQL levels exceeds the specified value.

• Solution: Delete the recursive SQL statement or recursive trigger.

ORA-00051: timeout occurred while waiting for a resource

• OceanBase error code: 5848

• SQLSTATE: HY000

• Cause: This error is usually caused by a dead instance.

• Solution: Check whether there are dead or unrecovered instances. If there are, recover them.

ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired

• OceanBase error code: 6006

• SQLSTATE: HY000

• Cause: The resource is busy.

• Solution: Retry the operation or increase the timeout period.

ORA-00185: invalid argument for %s call

• OceanBase error code: 5488
• SQLSTATE: HY000
• Cause: The arguments of the %s call are invalid.

ORA-00324: cursor attribute may not be applied to non-cursor %.*s

• OceanBase error code: 9784
• SQLSTATE: HY000
• Cause: A cursor-specific attribute was applied to a variable or identifier that is not a cursor.
• Solution: Locate the incorrect identifier and make sure it is a valid cursor.

ORA-00060: deadlock detected while waiting for resource

• OceanBase error code: 4101

• SQLSTATE: HY000

• Cause: A deadlock was detected while waiting for a resource.

• Solution: View the trace file and check the transactions and resources involved. If necessary, retry.

OBE-00060: Migrate tx data not continues

• OceanBase error code: 4408

• SQLSTATE: HY000

• Cause: The source transaction data table was recycled during migration, and the destination copy found that the transaction data table was not continuous, resulting in a failure and a retry.

• Solution: Generally, retrying can succeed. If it fails continuously, contact OceanBase technical support for assistance.

ORA-00600: arbitration service does not exist

• OceanBase error code: 4747

• SQLSTATE: HY000

• Cause: The arbitration service address has not been configured for the cluster.

• Solution: You cannot perform arbitration-related operations without configuring the arbitration service address. You can use OCP or execute the alter system add arbitration service‘$svr_ip:$svr_port’; statement to add the arbitration service address to the cluster.

ORA-00600: arbitration service already exist

• OceanBase error code: 4748

• SQLSTATE: HY000

• Cause: The cluster already has a valid arbitration service address.

• Solution: You cannot configure multiple arbitration services for a cluster at the same time.

ORA-00600: wait degration finished timeout

• OceanBase error code: 4751

• SQLSTATE: HY000

• Cause: The timeout occurs when waiting for the tenant to be degraded during the Stop Server operation.

• Solution: Retry the Stop Server command until it succeeds.

ORA-00600: unknown SET option '%s'

• OceanBase error code: 4764
• SQLSTATE: HY000
• Cause: An unknown SET option was specified when setting parameters.
• Solution: Check whether the options specified in the SET command are correct and ensure that there are no spelling errors or syntax errors.

ORA-00600: internal error code, arguments: -4780, This service_name is not found in the tenant

• OceanBase error code: 4780

• SQLSTATE: HY000

• Cause: The specified service_name does not exist.

• Solution: Check whether the service_name specified in the connection string is correct, or check the connectivity between Proxy and OCP.

ORA-00600: internal error code, arguments: -4781, The service has not started on all servers

• OceanBase error code: 4781

• SQLSTATE: HY000

• Cause: When a service_name-related operation (such as creating or deleting a service_name) notifies each OBServer node to apply the change, some servers failed.

• Solution: Wait for a while. In normal cases, a background thread refreshes periodically, with a default refresh interval of about 10 seconds.

ORA-00600: internal error code, arguments: -4782, The tenant is not PRIMARY

• OceanBase error code: 4782

• SQLSTATE: HY000

• Cause: When a service_name and failover_mode are specified, the tenant must be a primary tenant. If the current tenant is no longer the primary tenant, this indicates a Proxy routing error.

• Solution: The Proxy or OCP cache may be incorrect. If both caches are normal, the system retries and refreshes automatically. Re-execute the SQL statement to route to the correct primary tenant.

ORA-00600: internal error code, arguments: -4783, The service has stopped

• OceanBase error code: 4783

• SQLSTATE: HY000

• Cause: The specified service_name has been stopped by the user.

• Solution: Start the service_name by using the following operation command: ALTER SYSTEM START SERVICE service_name TENANT = tenant_name;.

ORA-00600: Cannot create a JSON value from a string

• OceanBase error code: 5415

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: Internal error code. Contact technical support engineers for assistance.

ORA-00600: Invalid JSON character data provided to function

• OceanBase error code: 5416

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: Internal error code. Contact technical support engineers for assistance.

ORA-00600: Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required

• OceanBase error code: 5417

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: Internal error code. Contact technical support engineers for assistance.

ORA-00600: Cannot CAST value to JSON

• OceanBase error code: 5418

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: Internal error code. Contact technical support engineers for assistance.

ORA-00600: A path expression must be encoded in the utf8 character set

• OceanBase error code: 5419

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: Internal error code. Contact technical support engineers for assistance.

ORA-00600: In this situation, path expressions may not contain the * and ** tokens

• OceanBase error code: 5420

• SQLSTATE: 22032

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-00600: The JSON value is too big to be stored in a JSON column

• OceanBase error code: 5421

• SQLSTATE: 22032

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-00600: JSON column '%.*s' cannot be used in key specification

• OceanBase error code: 5423

• SQLSTATE: 22032

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-00600: The path expression is not allowed in this context

• OceanBase error code: 5424

• SQLSTATE: 22032

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-00600: The oneOrAll argument may take these values: \'one\' or \'all\'

• OceanBase error code: 5425

• SQLSTATE: 22032

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-00600: Out of range JSON value for CAST

• OceanBase error code: 5426

• SQLSTATE: 22032

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-00600: Invalid JSON value for CAST

• OceanBase error code: 5427

• SQLSTATE: 22032

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-00600: The JSON document exceeds the maximum depth

• OceanBase error code: 5428

• SQLSTATE: 22032

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-00600: Invalid default value for \'%.*s\'

• OceanBase error code: 5430

• SQLSTATE: 22032

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-00600: A path expression is not a path to a cell in an array

• OceanBase error code: 5431

• SQLSTATE: 22032

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-40600: JSON_EQUAL used outside predicate

• OceanBase error code: 5448
• SQLSTATE: 42000
• Cause: JSON_EQUAL is used outside a predicate.
• Action: Use JSON_EQUAL in a predicate, such as in a CASE expression.

ORA-00600: auto increment service busy

• OceanBase error code: 5794

• SQLSTATE: HY000

• Cause: an internal error has occurred.

• Action: Contact OceanBase Technical Support for assistance.

ORA-00600: rowid type mismatch, expect %.*s, got %.*s"

• OceanBase error code: 5870

• SQLSTATE: HY000

• Cause: Internal error code.

• Action: Internal error code. Contact technical support engineers for troubleshooting.

ORA-00600: rowid num mismatch, expect %ld, actual %ld

• OceanBase error code: 5871

• SQLSTATE: HY000

• Cause: Internal error code.

• Action: Internal error code. Contact technical support engineers for troubleshooting.

ORA-00600: internal error code, arguments: -7124, partitions are already balanced, %s

• OceanBase error code: 7124

• SQLSTATE: HY000

• Cause: During a partition balancing operation, the partition is already in a balanced state.

ORA-00600: Binary geometry function given two geometries of different srids.Binary geometry function %s given two geometries of different srids: %u and %u, which should have been identical

• OceanBase error code: 7201
• SQLSTATE: HY000
• Cause: The binary geometry function was given two geometries with different SRIDs: %u and %u, which should have been identical. The geometry values passed as parameters to the spatial function must have the same SRID value.

ORA-00600: Calling geometry function with unsupported types of arguments.Calling geometry function %s with unsupported types of arguments

• OceanBase error code: 7202
• SQLSTATE: HY000
• Cause: The geometry function %s was called with unsupported argument types.

ORA-00600: Unknown GIS error occurred in function.Unknown GIS error occurred in function %s

• OceanBase error code: 7203
• SQLSTATE: HY000
• Cause: An unknown GIS error occurred in the function %s.

ORA-00600: Unknown exception caught in GIS function.Unknown exception caught in GIS function %s

• OceanBase error code: 7204
• SQLSTATE: HY000
• Cause: An unknown exception was caught in the GIS function %s.

ORA-00600: Invalid GIS data provided to function.Invalid GIS data provided to function %s

• OceanBase error code: 7205
• SQLSTATE: 22023
• Cause: Invalid GIS data was provided to function %s. A spatial function was called with a parameter that is not recognized as a valid geometry value.

ORA-00600: The geometry has no data in function.The geometry has no data in function %s

• OceanBase error code: 7206
• SQLSTATE: HY000
• Cause: The geometry has no data in function %s.

ORA-00600: Unable to calculate centroid because geometry is empty in function.Unable to calculate centroid because geometry is empty in function %s

• OceanBase error code: 7207
• SQLSTATE: HY000
• Cause: Unable to calculate centroid because the geometry is empty in function %s.

ORA-00600: Geometry overlay calculation error: geometry data is invalid in function.Geometry overlay calculation error: geometry data is invalid in function %s

• OceanBase error code: 7208
• SQLSTATE: HY000
• Cause: Geometry overlay calculation error: geometry data is invalid in function %s.

ORA-00600: Geometry turn info calculation error: geometry data is invalid in function.Geometry turn info calculation error: geometry data is invalid in function %s

• OceanBase error code: 7209
• SQLSTATE: HY000
• Cause: Geometry turn info calculation error: geometry data is invalid in function %s.

ORA-00600: Analysis procedures of intersection points interrupted unexpectedly in function.Analysis procedures of intersection points interrupted unexpectedly in function %s

• OceanBase error code: 7210
• SQLSTATE: HY000
• Cause: The analysis procedures of intersection points were interrupted unexpectedly in function %s.

ORA-00600: Unknown exception thrown in function.Unknown exception thrown in function %s

• OceanBase error code: 7211
• SQLSTATE: HY000
• Error: An unknown exception is thrown in the function %s.

ORA-00600: Geometry byte string must be little endian

• OceanBase error code: 7212
• SQLSTATE: HY000
• Error: The geometry byte string must be little-endian.

ORA-00600: Online operation is not supported on a table with a GIS index

• OceanBase error code: 7213
• SQLSTATE: HY000
• Error: Online operations are not supported on a table with a GIS index.

ORA-00600: Inconsistent intersection points.Inconsistent intersection points

• OceanBase error code: 7214
• SQLSTATE: HY000
• Error: Inconsistent intersection points.

ORA-00600: Parameter exceeds the maximum number of points in a geometryin function.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s

• OceanBase error code: 7215
• SQLSTATE: HY000
• Error: The parameter %s exceeds the maximum number of points in the geometry (%lu) in the function %s.

ORA-00600: value is a geometry of unexpected type.%.64s value is a geometry of unexpected type %.64s in %.64s

• OceanBase error code: 7216
• SQLSTATE: 22S01
• Error: The %s value is a geometry of an unexpected type %s in %s.

ORA-00600: Can't parse the spatial reference system definition of SRID.Can't parse the spatial reference system definition of SRID %u

• OceanBase error code: 7217
• SQLSTATE: SR002
• Error: The spatial reference system definition of SRID %u cannot be parsed.

ORA-00600: The spatial reference system definition for SRID does not specify the mandatory (EPSG) projection parameter.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter

• OceanBase error code: 7218
• SQLSTATE: SR003
• Cause: The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.

ORA-00600: There's no spatial reference system with SRID.There's no spatial reference system with SRID %u

• OceanBase Database error code: 7219
• SQLSTATE: 01000
• Cause: There is no spatial reference system with SRID %u.

ORA-00600: Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian

• OceanBase Database error code: 7220
• SQLSTATE: 22S00
• Cause: Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.

ORA-00600: Function is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID, which has not been defined.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined

• OceanBase Database error code: 7221
• SQLSTATE: SR001
• Cause: Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.

ORA-00600: There's no spatial reference system with SRID.There's no spatial reference system with SRID %u

• OceanBase Database error code: 7222
• SQLSTATE: SR001
• Cause: There is no spatial reference system with SRID %u.

ORA-00600: There is no spatial reference system with SRID. The axis order is unknown. There is no spatial reference system with SRID %u. The axis order is unknown

• OceanBase Database error code: 7223
• SQLSTATE: 01000
• Cause: There is no spatial reference system with SRID %u. The axis order is unknown.

ORA-00600: It has not been implemented for geographic spatial reference systems.%.192s(%.80s) has not been implemented for geographic spatial reference systems

• OceanBase error code: 7224
• SQLSTATE: 22S00
• Cause: %s(%s) has not been implemented for geographic spatial reference systems.

ORA-00600: The SRID of the geometry does not match the SRID of the column. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column

• OceanBase error code: 7225
• SQLSTATE: HY000
• Cause: The SRID of the geometry does not match the SRID of the column '%s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.

ORA-00600: The SRID specification on the column cannot be changed because there is a spatial index on the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification

• OceanBase error code: 7226
• SQLSTATE: HY000
• Cause: The SRID specification on the column '%s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.

ORA-00600: The spatial index on column will not be used by the query optimizer since the column does not have an SRID attribute.The spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column

• OceanBase error code: 7227
• SQLSTATE: HY000
• Cause: The query optimizer will not use the spatial index on column "%s" because the column does not have an SRID attribute. Consider adding an SRID attribute to the column.

ORA-00600: Function is only defined for SRID 0 and SRID 4326.Function %.192s is only defined for SRID 0 and SRID 4326

• OceanBase error code: 7228
• SQLSTATE: 22S00
• Cause: The function %s is defined only for SRID 0 and SRID 4326.

ORA-00600: It has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for Cartesian spatial reference systems

• OceanBase error code: 7229
• SQLSTATE: 22S00
• Cause: %s(%s) has not been implemented for Cartesian spatial reference systems.

ORA-00600: It has not been implemented for projected spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems

• OceanBase error code: 7230
• SQLSTATE: 22S00
• Cause: %s(%s) has not been implemented for projected spatial reference systems.

ORA-00600: Missing mandatory attribute.Missing mandatory attribute %s

• OceanBase error code: 7231
• SQLSTATE: SR006
• Cause: The mandatory attribute %s is missing.

ORA-00600: Multiple definitions of attribute.Multiple definitions of attribute %s

• OceanBase error code: 7232
• SQLSTATE: SR006
• Cause: The attribute %s has multiple definitions.

ORA-00600: The spatial reference system name can't be an empty string or start or end with whitespace

• OceanBase error code: 7233
• SQLSTATE: SR006
• Cause: The spatial reference system name cannot be an empty string or start or end with whitespace.

ORA-00600: The organization name can't be an empty string or start or end with whitespace

• OceanBase error code: 7234
• SQLSTATE: SR006
• Cause: The organization name cannot be an empty string or start or end with whitespace.

ORA-00600: There is already a spatial reference system with SRID.There is already a spatial reference system with SRID %u

• OceanBase error code: 7235
• SQLSTATE: SR004
• Cause: A spatial reference system with SRID %u already exists.

ORA-00600: There is already a spatial reference system with SRID.There is already a spatial reference system with SRID %u

• OceanBase error code: 7236
• SQLSTATE: 01S00
• Cause: A spatial reference system with SRID %u already exists.

ORA-00600: SRID 0 is not modifiable

• OceanBase error code: 7237
• SQLSTATE: SR000
• Cause: SRID 0 is not modifiable.

ORA-00600: The SRID range has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade

• OceanBase error code: 7238
• SQLSTATE: 01S01
• Cause: The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified, or removed without warning during upgrade.

ORA-00600: Can't modify SRID. There is at least one column depending on it.Can't modify SRID %u. There is at least one column depending on it

• OceanBase error code: 7239
• SQLSTATE: SR005
• Cause: Cannot modify SRID %u. At least one column depends on it.

ORA-00600: Invalid character in attribute.Invalid character in attribute %s

• OceanBase error code: 7240
• SQLSTATE: SR006
• Cause: The character in attribute %s is invalid.

ORA-00600: Attribute is too long.Attribute %s is too long. The maximum length is %u characters

• OceanBase error code: 7241
• SQLSTATE: SR006
• Cause: Attribute %s is too long. The maximum length is %u characters.

ORA-00600: Function is only defined for geographic spatial reference systems, but one of its arguments is in SRID, which is not geographic.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic

• OceanBase error code: 7242
• SQLSTATE: 22S00
• Cause: Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.

ORA-00600: Function encountered a polygon that was too large. Polygons must cover less than half the planet.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet

• OceanBase error code: 7243
• SQLSTATE: 22023
• Cause: Function %s encountered a polygon that was too large.

ORA-00600: Spatial indexes can't be primary or unique indexes

• OceanBase error code: 7244
• SQLSTATE: HY000
• Cause: Spatial indexes cannot be primary or unique indexes.

ORA-00600: The index type is not supported for spatial indexes.The index type %.20s is not supported for spatial indexes

• OceanBase error code: 7245
• SQLSTATE: HY000
• Cause: The spatial index does not support the index type %s.

ORA-00600: A parameter of function contains a geometry with longitude, which is out of range.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f]

• OceanBase error code: 7246
• SQLSTATE: 22S02
• Cause: The parameter of the function %s contains a geometry with a longitude of %f, which is out of range. It must be within (%f, %f].

ORA-00600: A parameter of function contains a geometry with latitude, which is out of range.A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f]

• OceanBase error code: 7247
• SQLSTATE: 22S03
• Cause: The parameter of the function %s contains a geometry with a latitude of %f, which is out of range. It must be within [%f, %f].

ORA-00600: The spatial reference system definition for SRID specifies invalid geographic axes. One axis must be NORTH or SOUTH and the other must be EAST or WEST.he spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST

• OceanBase error code: 7248
• SQLSTATE: SR002
• Cause: The spatial reference system definition for SRID %u specifies invalid geographic axes of %.20s and %.20s. One axis must be NORTH or SOUTH, and the other must be EAST or WEST.

ORA-00600: The spatial reference system definition for SRID specifies invalid geographic axes. One axis must be NORTH or SOUTH and the other must be EAST or WEST.he spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST

• OceanBase error code: 7249
• SQLSTATE: SR002
• Cause: The spatial reference system definition for SRID %u specifies invalid geographic axes "%s" and "%s". One axis must be NORTH or SOUTH, and the other must be EAST or WEST.

ORA-00600: The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere

• OceanBase error code: 7250
• SQLSTATE: SR002
• Cause: The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.

ORA-00600: The angular unit conversion factor must be a positive number

• OceanBase error code: 7251
• SQLSTATE: SR002
• Cause: The angular unit conversion factor must be a positive number.

ORA-00600: The prime meridian must be within (*180, 180] degrees, specified in the SRS angular unit

• OceanBase error code: 7252
• SQLSTATE: SR002
• Cause: The prime meridian must be within (*180, 180] degrees, specified in the SRS angular unit.

ORA-00600: Transformation from SRID is not supported.Transformation from SRID %u is not supported

• OceanBase error code: 7253
• SQLSTATE: 22S00
• Cause: Transformation from SRID %u is not supported.

ORA-00600: Transformation to SRID is not supported.Transformation to SRID %u is not supported

• OceanBase error code: 7254
• SQLSTATE: 22S00
• Cause: Transformation to SRID %u is not supported.

ORA-00600: Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause

• OceanBase error code: 7255
• SQLSTATE: 22S00
• Cause: The transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.

ORA-00600: Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause

• OceanBase error code: 7256
• SQLSTATE: 22S00
• Cause: The transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.

ORA-00600: Cannot create a functional index on a function that returns a JSON or GEOMETRY value

• OceanBase error code: 7257
• SQLSTATE: 42000
• Cause: A functional index cannot be created on a function that returns a JSON or GEOMETRY value.

ORA-00600: Spatial functional index is not supported

• OceanBase error code: 7258
• SQLSTATE: HY000
• Cause: Spatial functional index is not supported.

ORA-00600: The geometry passed to function is in SRID 0, which doesn't specify a length unit. Can't convert.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'

• OceanBase Database error code: 7259
• SQLSTATE: SU001
• Cause: The geometry passed to function %s is in SRID 0, which does not specify a length unit. The geometry cannot be converted to '%s'.

ORA-00600: Invalid cast.Invalid cast from %s to %s

• OceanBase Database error code: 7260
• SQLSTATE: 22S01
• Cause: The conversion from %s to %s is invalid.

ORA-00600: Invalid cast. A polygon ring is in the wrong direction.Invalid cast from %s to %s. A polygon ring is in the wrong direction

• OceanBase Database error code: 7261
• SQLSTATE: 22S04
• Cause: The conversion from %s to %s is invalid. The direction of the polygon ring is incorrect.

ORA-00600: Arguments to function contains geometries with different SRIDs. All geometries must have the same SRID.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID

• OceanBase Database error code: 7262
• SQLSTATE: 22S05
• Cause: The function %s contains geometries %u and %u with different SRIDs. All geometries must have the same SRID.

ORA-00600: Longitude is out of range in function.Longitude %f is out of range in function %.192s. It must be within (%f, %f]

• OceanBase Database error code: 7263
• SQLSTATE: 22S02
• Cause: The longitude %f is out of range in function %s. It must be within (%f, %f].

ORA-00600: Latitude is out of range in function.Latitude %f is out of range in function %.192s. It must be within [%f, %f]

• OceanBase Database error code: 7264
• SQLSTATE: 22S03
• Cause: The latitude %f is out of range in function %s. It must be within [%f, %f].

ORA-00600: Memory allocation error.Memory allocation error: %*.256s in function %s

• OceanBase error code: 7265
• SQLSTATE: HY000
• Cause: A memory allocation error occurred in function %s: %s.

ORA-00600: Domain error.Domain error: %*.256s in function %s

• OceanBase error code: 7266
• SQLSTATE: HY000
• Cause: A domain error occurred in function %s: %s.

ORA-00600: Length error.Length error: %*.256s in function %s

• OceanBase error code: 7267
• SQLSTATE: HY000
• Cause: A length error occurred in function %s: %s.

ORA-00600: Invalid argument error.Invalid argument error: %*.256s in function %s

• OceanBase error code: 7268
• SQLSTATE: HY000
• Cause: An invalid argument error occurred in function %s: %s.

ORA-00600: Out of range error.Out of range error: %*.256s in function %s

• OceanBase error code: 7269
• SQLSTATE: HY000
• Cause: An out-of-range error occurred in %s of the function %s.

ORA-00600: Overflow error.Overflow error: %*.256s in function %s

• OceanBase error code: 7270
• SQLSTATE: HY000
• Cause: An overflow error occurred in %s of the function %s.

ORA-00600: Range error.Range error: %*.256s in function %s

• OceanBase error code: 7271
• SQLSTATE: HY000
• Cause: A range error occurred in %s of the function %s.

ORA-00600: Underflow error.Underflow error: %*.256s in function %s

• OceanBase error code: 7272
• SQLSTATE: HY000
• Cause: An underflow error occurred in %s of the function %s.

ORA-00600: Logic error.Logic error: %*.256s in function %s

• OceanBase error code: 7273
• SQLSTATE: HY000
• Cause: A logic error occurred in %s of the function %s.

ORA-00600: Runtime error.Runtime error: %*.256s in function %s

• OceanBase error code: 7274
• SQLSTATE: HY000
• Cause: A runtime error occurred in %s of the function %s.

ORA-00600: unknown exception: %*.384s in function %s

• OceanBase error code: 7275
• SQLSTATE: HY000
• Cause: An unknown exception occurred in %s of the function %s.

ORA-00600: cannot get geometry object from data you send to the GEOMETRY field

• OceanBase error code: 7276
• SQLSTATE: 22003
• Cause: The geometry object cannot be obtained from the data you sent to the GEOMETRY field.

ORA-00600: incorrect usage of srid, srid column attribute only support in geometry

• OceanBase error code: 7277
• SQLSTATE: HY000
• Error: The srid is used incorrectly. The srid column attribute is supported only for geometry.

ORA-00600: incorrect usage of spatial/fulltext/hash index and explicit index order

• OceanBase error code: 7278
• SQLSTATE: HY000
• Error: The spatial, fulltext, and hash indexes and the explicit index order are used incorrectly.

ORA-00600: a spatial index may only contain a geometrical type column

• OceanBase error code: 7279
• SQLSTATE: 42000
• Error: The SPATIAL index may only contain a geometrical type column.

ORA-00600: all parts of a spatial index must be not null

• OceanBase error code: 7280
• SQLSTATE: 42000
• Error: All parts of the SPATIAL index must be NOT NULL.

ORA-00600: The index type is not supported for spatial indexes.The index type %s is not supported for spatial indexes

• OceanBase error code: 7281
• SQLSTATE: HY000
• Error: The index type %s is not supported for spatial indexes.

ORA-00600: There's no unit of measure.There's no unit of measure named '%s'

• OceanBase error code: 7282
• SQLSTATE: SU001
• Error: There is no unit of measure named "%s".

ORA-00600: The string is not a valid key value pair in function.The string '%.192s' is not a valid key %c value pair in function %.192s

• OceanBase error code: 7283
• SQLSTATE: 22023
• Error: The string '%s' is not a valid key %c value pair in the function %s.

ORA-00600: Invalid radius provided to function: Radius must be greater than zero.Invalid radius provided to function %s: Radius(%lf) must be greater than zero

• OceanBase error code: 7284
• SQLSTATE: 22023
• Error: The radius provided to the function %s is invalid. The radius must be greater than zero.

ORA-00600: Spatial reference system is empty

• OceanBase error code: 7285
• SQLSTATE: SR001
• Error: The spatial reference system with the SRID %u does not exist.

ORA-00600: Invalid option key in function.Invalid option key '%.192s' in function %.192s

• OceanBase error code: 7286
• SQLSTATE: 22023
• Error: The option key %s in the function %s is invalid.

ORA-00600: Invalid value for option in function.Invalid value '%.192s' for option '%.192s' in function '%.192s'

• OceanBase error code: 7287
• SQLSTATE: 22023
• Error: The value %s of the option %s in the function %s is invalid.

ORA-00600: Unknown WKB type.Unknown WKB type(%d)! Full WKB type number was (%d)

• OceanBase error code: 7288
• SQLSTATE: 22S01
• Error: The geometry value %s is of an unexpected type %s in %s.

ORA-00600: internal error code, arguments: -9129, object storage io error

• OceanBase error code: 9129
• SQLSTATE: HY000
• Error: An error occurred in the object storage. The common causes are the connectivity and compatibility issues with the object storage.
• Solution: Check the connectivity with the object storage and contact technical support after confirming that there are no connectivity issues.

ORA-00600: tmp file exceeds disk quota

• OceanBase error code: 9135

• SQLSTATE: HY000

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

• Solution: Check the disk space usage and analyze the reasons for the large number of temporary files by identifying slow SQL queries. If the data volume is as expected, you can increase the temporary_file_max_disk_size parameter to adjust the temporary file limit.

ORA-00600: internal error code, arguments: -9140, the object is locked by worm

• OceanBase error code: 9140

• SQLSTATE: HY000

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

• Solution: Check whether the backup or archive path is configured with a retention policy and whether the enable_worm parameter is correctly set when the backup or archive path is configured. If the enable_worm parameter is correctly set, contact OceanBase Technical Support for further assistance.

ORA-00600: internal error code, arguments: -9142, the object can not be overwritten with different content

• OceanBase error code: 9142

• SQLSTATE: HY000

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

• Solution: Contact OceanBase Technical Support for further assistance.

ORA-00600: Incorrect usage of %s

• OceanBase error code: 9751
• SQLSTATE: HY000
• Cause: The usage is incorrect.
• Solution: Check whether the usage is correct and use it correctly.

ORA-00600:internal error code, arguments: -11049,Exceed query memory limit (mem_limit=%ld, mem_hold=%ld), please check whether the query_memory_limit_percentage configuration item is reasonable.

• OceanBase error code: 11049
• SQLSTATE: HY000
• Cause: The query memory exceeds the limit.
• Solution: Check the value of the query_memory_limit_percentage parameter and confirm whether the setting is reasonable.

ORA-00600: internal error code, arguments: -4406, license is expired.

• OceanBase error code: 4406
• SQLSTATE: HY000
• Cause: The license has expired.
• Solution: Contact OceanBase to renew the license.

ORA-00600: internal error code, arguments: -4407, exceed the license scope: %s.

• OceanBase error code: 4407
• SQLSTATE: HY000
• Cause: The current feature exceeds the scope of the license.
• Solution: If you want to use the current feature, contact OceanBase.

ORA-00603: Prepare statement checksum error

• OceanBase error code: 5777

• SQLSTATE: HY000

• Cause: The server session is in an unrecoverable state.

• Solution: Log in to OceanBase Database again to automatically create a new server session. For more information, check the session trace file.

ORA-00739: FORALL INSERT/UPDATE/DELETE not supported on remote tables

• OceanBase error code: 9752
• SQLSTATE: HY000
• Cause: FORALL INSERT/UPDATE/DELETE cannot be used on remote tables.
• Solution: Do not use FORALL INSERT/UPDATE/DELETE on remote tables.

ORA-00900: invalid SQL statement

• OceanBase error code: 5001

• SQLSTATE: 42000

• Cause: The SQL statement is invalid.

• Solution: Refer to the SQL Reference (Oracle-compatible mode) of your OceanBase Database version for the correct SQL statement.

• OceanBase error code: 5006

• SQLSTATE: 42000

• Cause: The SQL statement is invalid.

• Solution: For the correct syntax, refer to the "SQL Reference (Oracle-compatible mode)" of the corresponding OceanBase Database version.

ORA-00902: invalid datatype

• OceanBase error code: 5874

• SQLSTATE: HY000

• Cause: The specified data type is invalid.

ORA-00903: invalid table name

• OceanBase error code: 5163

• SQLSTATE: 42000

• Cause: The specified table name is invalid.

ORA-00904: invalid identifier '%.*s'

• OceanBase error code: 5164

• SQLSTATE: 42000

• Cause: The string contains an invalid identifier.

ORA-00904: invalid identifier '%.*s'in '%.*s'

• OceanBase error code: 5217

• SQLSTATE: 42S22

• Cause: The string contains an invalid identifier.

ORA-00904: '%.*s': invalid identifier

• OceanBase error code: 5211

• SQLSTATE: 42000

• Cause: The string contains an invalid identifier.

ORA-00905: missing keyword

• OceanBase error code: 5096

• SQLSTATE: HY000

• Cause: The SQL statement is missing a keyword.

ORA-00909: invalid number of arguments in the call to native function '%.*s'

• OceanBase error code: 5054

• SQLSTATE: 42000

• Cause: The number of arguments is invalid.

ORA-00910: specified length too longfor column '%s' (max = %d byte)

• OceanBase error code: 5198

• SQLSTATE: 42000

• Cause: The specified string length exceeds the maximum supported by the data type. For the CHAR and RAW data types, the specified string length exceeds 2000. For other data types, the specified string length exceeds 4000.

• Solution: Reduce the string length, or switch to a data type that supports a longer string length, such as VARCHAR2, LONG CHAR, or LONG RAW.

ORA-00911: invalid character

• OceanBase error code: 9782

• SQLSTATE: HY000

• Cause: The character is invalid.

• Solution: Check and use a valid character set.

ORA-00913: too many values

• OceanBase error code: 5613

• SQLSTATE: HY000

• Cause: Too many values are specified.

ORA-00917: missing comma

• OceanBase error code: 7403
• SQLSTATE: 42000
• Cause: A comma is missing in the INSERT statement or in the column or value list in the form of ((C,D),(E,F), ...).
• Solution: Correct the syntax and check the SQL statement for missing or incorrectly used commas.

ORA-00918: column '%.*s' in %.*%s ambiguously defined

• OceanBase error code: 5207

• SQLSTATE: 23000

• Cause: The column definition is ambiguous.

ORA-00925: missing INTO keyword

• OceanBase error code: 9712

• SQLSTATE: HY000

• Cause: The INTO keyword is missing in the INSERT statement.

• Solution: Add the missing INTO keyword and re-execute the statement.

ORA-00926: missing VALUES keyword

• OceanBase error code: 5574

• SQLSTATE: HY000

• Cause: The VALUES keyword is missing.

ORA-00931: missing identifier

• OceanBase error code: 5963

• SQLSTATE: HY000

• Cause: An identifier is missing.

ORA-00932: inconsistent datatypes: left_type=%s right_type=%s

• OceanBase error code: 5083

• SQLSTATE: 22000

• Cause: Data types are inconsistent.

ORA-00932: inconsistent datatypes,inconsistent datatypes: expected %s got %s

• OceanBase error code: 7402
• SQLSTATE: 22000
• Cause: Incompatible data types are used in the SQL query.
• Solution: Check the SQL query statement for inconsistent data types and use the CAST or CONVERT function to convert the data types to the same type.

ORA-00933: SQL command not properly ended

• OceanBase error code: 5607

• SQLSTATE: HY000

• Cause: The SQL command is not properly ended.

ORA-00934: group function is not allowed here

• OceanBase error code: 5694

• SQLSTATE: HY000

• Cause: The GROUP function is not supported here.

ORA-00937: not a single-group group function

• OceanBase error code: 5853

• SQLSTATE: HY000

• Cause: The GROUP function is not a single-group function.

ORA-00938: not enough arguments for function

• OceanBase error code: 5774

• SQLSTATE: HY000

• Cause: The function does not have enough arguments.

ORA-00939: too many arguments for function

• OceanBase error code: 5683

• SQLSTATE: HY000

• Cause: The function has too many arguments.

ORA-00942: table or view \'%s.%s\'does not exist

• OceanBase error code: 5019

• SQLSTATE: 42S02

• Cause: The table or view does not exist. For OceanBase Database V2.2.70 and later, if the current role does not have the SELECT privilege on certain tables or views, this error is also returned.

• Solution: Check the spelling of your SQL statement. For OceanBase Database V2.2.70 and later, check the privileges of the current role.

ORA-00942: table or view '%.*s' does not exist

• OceanBase error code: 5201

• SQLSTATE: 42S02

• Cause: The table or view does not exist. In OceanBase Database V2.2.70 and later, if the current role does not have the SELECT privilege on certain tables or views, this error is also returned.

• Solution: Check the spelling of your SQL statement. In OceanBase Database V2.2.70 and later, check the privileges of the current role.

ORA-00947: not enough values

• OceanBase error code: 5614

• SQLSTATE: HY000

• Cause: The number of values is insufficient.

ORA-00955: name is already used by an existing object

• OceanBase error code: 5331, 5834

• SQLSTATE: HY000

• Cause: The name is already used by an existing object.

ORA-00957: duplicate column name

• OceanBase error code: 4228

• SQLSTATE: 42000

• Cause: The column name is duplicated.

ORA-00959: tablespace '%.*s' does not exist

• OceanBase error code: 4354

• SQLSTATE: HY000

• Cause: The specified tablespace does not exist.

ORA-00964: table name not in FROM list

• OceanBase error code: 5490
• SQLSTATE: 42000
• Cause: The table name is not in the FROM list.
• Solution: Confirm that the name is a correct table name and that it is in the FROM list.

ORA-00969: missing ON keyword

• OceanBase error code: 5370

• SQLSTATE: HY000

• Cause: The ON keyword is missing.

ORA-00972: identifier \'%.*s\' is too long

long

• OceanBase error code: 5179

• SQLSTATE: 42000

• Cause: The specified identifier exceeds the limit.

• Solution: Set the number of bytes of the specified identifier to within the limit.

ORA-00976: Specified pseudo column or operator not allowed here

• OceanBase error code: 5763

• SQLSTATE: HY000

• Cause: The LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF, or CONNECT_BY_ISCYCLE keyword cannot be used at this location.

• Solution: Remove the LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF, or CONNECT_BY_ISCYCLE keyword.

ORA-00979: '%.*s' not a GROUP BY expression

• OceanBase error code: 5218

• SQLSTATE: 42000

• Cause: The expression is not a GROUP BY expression.

ORA-00980: synonym translation is no longer valid

• OceanBase error code: 5330

• SQLSTATE: HY000

• Cause: The synonym cannot be resolved to a valid target object. This may be due to one of the following reasons:

  • The target schema does not exist.

  • The target object does not exist.

  • The synonym specifies an invalid database link.

  • The synonym does not support version control, but specifies a target object that supports version control.

• Solution: Modify the synonym definition to point to a valid target object.

ORA-00984: column not allowed here

• OceanBase error code: 5942

• SQLSTATE: HY000

• Cause: The column cannot be inserted at this location.

ORA-00988: missing or invalid password(s)

• OceanBase error code: 5887

• SQLSTATE: HY000

• Cause: The password is invalid.

ORA-00998: must name this expression with a column alias

• OceanBase error code: 5872

• SQLSTATE: HY000

• Cause: The expression must be named with a column alias.

OBE-0098: Cursor Variable in record, object, or collection is not supported by this release

• OceanBase error code: 9811
• SQLSTATE: HY000
• Cause: The current version does not support nested cursor variables in records, objects, or collections.
• Solution: Avoid nested cursor structures.