ORA-00000 to ORA-00999

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

• OceanBase error code: 5780

• SQLSTATE: HY000

• Cause: The error code indicates a normal exit.

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

• OceanBase error code: 5781

• SQLSTATE: HY000

• Cause: The error code indicates a normal exit.

  Note

  The 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: An UPDATE or INSERT statement is attempting to insert a duplicate key.

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

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

• OceanBase error code: 5595

• SQLSTATE: 23000

• Cause: An UPDATE or INSERT statement is attempting to insert a duplicate key.

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

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

• OceanBase error code: 5334

• SQLSTATE: HY000

• Cause: An UPDATE or INSERT statement is attempting to insert a duplicate key.

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

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

• OceanBase error code: 5562

• SQLSTATE: HY000

• Cause: An UPDATE or INSERT statement is attempting to insert a duplicate key.

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

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

• OceanBase error code: 9697

• SQLSTATE: HY000

• Cause: You are attempting to go more than the specified number of recursive SQL levels.

• Solution: Remove the recursive SQL or the recursive trigger.

ORA-00051: timeout occurred while waiting for a resource

• OceanBase error code: 5848

• SQLSTATE: HY000

• Cause: The error is usually caused by dead instances.

• Solution: Check whether dead or unrecovered instances exist. If yes, recover the instances.

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

• OceanBase error code: 6006

• SQLSTATE: HY000

• Cause: The resource is busy.

• Solution: Try again or increase the timeout period.

ORA-00185: invalid argument for %s call

• OceanBase error code: 5488
• SQLSTATE: HY000
• Cause: The %s call contains an invalid argument.

ORA-00060: deadlock detected while waiting for resource

• OceanBase error code: 4101

• SQLSTATE: HY000

• Cause: A deadlock is detected while waiting for resources.

• Solution: View the Trace file and the involved transactions and resources. Try again if necessary.

ORA-00600: arbitration service does not exist

• OceanBase error code: 4747

• SQLSTATE: HY000

• Cause: The arbitration service endpoint is not configured for the cluster.

• Solution: OceanBase clusters do not support arbitration if the arbitration service endpoint is not configured. Set the arbitration service endpoint for the cluster by using OCP or the SQL command alter system add arbitration service'$svr_ip:$svr_port';.

ORA-00600: arbitration service already exist

• OceanBase error code: 4748

• SQLSTATE: HY000

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

• Solution: Configure only one arbitration service endpoint for the cluster.

ORA-00600: wait degration finished timeout

• OceanBase error code: 4751

• SQLSTATE: HY000

• Cause: Waiting for tenant degradation timed out during a Stop Server operation.

• Solution: Execute the Stop Server command again until it succeeds.

ORA-00600: unknown SET option '%s'

• OceanBase error code: 4764
• SQLSTATE: HY000
• Cause: An unknown option is specified in the SET command.
• Solution: Make sure that the options specified in the SET command are free of spelling or syntax errors.

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

• OceanBase error code: 5415

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

ORA-00600: Invalid JSON character data provided to function

• OceanBase error code: 5416

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

ORA-00600: Cannot CAST value to JSON

• OceanBase error code: 5418

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase error code: 5419

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase error code: 5420

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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 occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase error code: 5423

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase error code: 5424

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase error code: 5425

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

ORA-00600: Out of range JSON value for CAST

• OceanBase error code: 5426

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

ORA-00600: Invalid JSON value for CAST

• OceanBase error code: 5427

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

ORA-00600: The JSON document exceeds the maximum depth

• OceanBase error code: 5428

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase error code: 5430

• SQLSTATE: 22032

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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 occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

ORA-40600: JSON_EQUAL used outside predicate

• OceanBase error code: 5448
• SQLSTATE: 42000
• Cause: JSON_EQUAL is used outside the predicate.
• Solution: Use JSON_EQUAL in the predicate. For example, embed it in a CASE expression.

ORA-00600: auto increment service busy

• OceanBase error code: 5794

• SQLSTATE: HY000

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase error code: 5870

• SQLSTATE: HY000

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase error code: 5871

• SQLSTATE: HY000

• Cause: An internal error occurred.

• Solution: This is an internal error code. Contact OceanBase Technical Support for troubleshooting.

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 has given two different SRIDs: %u and %u, which should be the same. The geometry values passed as arguments 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: An unsupported argument type is used for calling geometry functions.

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 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 occurred 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: The GIS data provided to function %s is invalid. The spatial function is called with an input 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: The centroid cannot be calculated because the geometry in function %s is empty.

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: An error occurs in the geometry overlay calculation. The geometry data in the function %s is invalid.

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: An error occurs in the geometry turn calculation. The geometry data in the function %s is invalid.

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 intersection point analysis procedure was interrupted unexpectedly in function %s.

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

• OceanBase error code: 7211
• SQLSTATE: HY000
• Cause: An unknown exception was thrown in function %s.

ORA-00600: Geometry byte string must be little endian

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

ORA-00600: Do not support online operation on table with GIS index

• OceanBase error code: 7213
• SQLSTATE: HY000
• Cause: Online operations on tables with GIS indexes are not supported.

ORA-00600: Inconsistent intersection points. Inconsistent intersection points

• OceanBase error code: 7214
• SQLSTATE: HY000
• Cause: The intersection points are inconsistent.

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

• OceanBase error code: 7215
• SQLSTATE: HY000
• Cause: The parameter %s has exceeded the maximum number of points for geometry %lu in 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
• Cause: The value %s is a geometry of 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
• Cause: The spatial reference system definition for 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 did 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 error code: 7219
• SQLSTATE: 01000
• Cause: The spatial reference system for SRID %u is not defined.

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 error code: 7220
• SQLSTATE: 22S00
• Cause: Function %s is only defined for Cartesian spatial reference systems, but one of its parameters is in SRID %u, which is not a Cartesian spatial reference system.

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 error code: 7221
• SQLSTATE: SR001
• Cause: Function %s is only defined for Cartesian spatial reference systems, but one of its parameters 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 error code: 7222
• SQLSTATE: SR001
• Cause: The spatial reference system for SRID %u is not defined.

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

• OceanBase error code: 7223
• SQLSTATE: 01000
• Cause: The spatial reference system for SRID %u is not defined. 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 geospatial 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 column '%s'. The SRID of the geometry is %lu, while the SRID of the column is %lu. Change the SRID of the geometry or the SRID attribute 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 of column '%s' cannot be modified because the column has a spatial index. You need to drop the spatial index before modifying 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. You can add 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: Function %s is only defined 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: 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 a space.

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 a space.

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: The spatial reference system of 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: The spatial reference system of SRID %u already exists.

ORA-00600: SRID 0 is not modifiable

• OceanBase error code: 7237
• SQLSTATE: SR000
• Cause: SRID 0 cannot be modified.

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] is reserved for system use. During the upgrade process, SRSs in this range may be added, modified, or deleted without warning.

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: SRID %u cannot be modified because 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: Attribute %s has invalid characters.

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 cannot exceed the maximum length of %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 parameters is in SRID %u, which is not a geographic spatial reference system.

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 has encountered a polygon that is too large.

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

• OceanBase error code: 7244
• SQLSTATE: HY000
• Cause: A spatial index cannot be a primary or unique index.

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 index type %s is not supported for spatial indexes.

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: A parameter of function %s contains a geometry with longitude %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: A parameter of function %s contains a geometry with latitude %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. The 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 has specified invalid axes %s and %s. 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. The 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 has specified invalid 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 greater 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: Transformation from SRID %u is not supported. The spatial reference system does not have a 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: Transformation to SRID %u is not supported. The spatial reference system does not have a 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: You cannot create a function index 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 function indexes are 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 error code: 7259
• SQLSTATE: SU001
• Cause: The geometry passed to function %s is in SRID 0. It cannot be converted to %s because its length unit is not specified.

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

• OceanBase error code: 7260
• SQLSTATE: 22S01
• Cause: 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 error code: 7261
• SQLSTATE: 22S04
• Cause: Conversion from %s to %s is invalid. A polygon ring is in the wrong direction.

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 error code: 7262
• SQLSTATE: 22S05
• Cause: A parameter of function %s contains geometries with different SRIDs: %u and %u. 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 error code: 7263
• SQLSTATE: 22S02
• Cause: Longitude %f is out of the range of 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 error code: 7264
• SQLSTATE: 22S03
• Cause: Latitude %f is out of the range of 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 occurs for %s in function %s.

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

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

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

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

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

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

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 occurs for %s in function %s.

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

• OceanBase error code: 7270
• SQLSTATE: HY000
• Cause: An overflow error occurs for %s in function %s.

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

• OceanBase error code: 7271
• SQLSTATE: HY000
• Cause: A range error occurs for %s in function %s.

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

• OceanBase error code: 7272
• SQLSTATE: HY000
• Cause: An underflow error occurs for %s in function %s.

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

• OceanBase error code: 7273
• SQLSTATE: HY000
• Cause: A logic error occurs for %s in function %s.

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

• OceanBase error code: 7274
• SQLSTATE: HY000
• Cause: A runtime error occurs for %s in function %s.

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

• OceanBase error code: 7275
• SQLSTATE: HY000
• Cause: An unknown exception occurs for %s in 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 that you send to the GEOMETRY field.

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

• OceanBase error code: 7277
• SQLSTATE: HY000
• Cause: The SRID is not used correctly. SRID column attributes are supported only in geometries.

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

• OceanBase error code: 7278
• SQLSTATE: HY000
• Cause: The spatial, full-text, or hash index or the explicit index order is used incorrectly.

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

• OceanBase error code: 7279
• SQLSTATE: 42000
• Cause: The spatial index may contain only columns of the geometrical type.

ORA-00600: All parts of a SPATIAL index must be NOT NULL

• OceanBase error code: 7280
• SQLSTATE: 42000
• Cause: All parts of a 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
• Cause: 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
• Cause: The measuring unit named %s does not exist.

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
• Cause: String %s is not a valid key-value pair in 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
• Cause: The radius provided to function %s is invalid. The radius must be greater than zero.

ORA-00600: Spatial reference system is empty

• OceanBase error code: 7285
• SQLSTATE: SR001
• Cause: The spatial reference system for SRID %u is not defined.

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

• OceanBase error code: 7286
• SQLSTATE: 22023
• Cause: Option key %s in 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
• Cause: Value %s for option %s in 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
• Cause: The value %s is a geometry of unexpected type %s in %s.

ORA-00603: Prepare statement checksum error

• OceanBase error code: 5777

• SQLSTATE: HY000

• Cause: The server session is unrecoverable.

• Solution: Log on to OceanBase Database again so that the system automatically creates a server session. For more information, see the session trace file.

ORA-00900: invalid SQL statement

• OceanBase error code: 5001

• SQLSTATE: 42000

• Cause: An error exists in the SQL statement.

• Solution: For the correct SQL statements, see SQL Reference (Oracle Mode) of the corresponding OceanBase Database version.

• OceanBase error code: 5006

• SQLSTATE: 42000

• Cause: An error exists in the SQL statement.

• Solution: For the correct SQL statements, see SQL Reference (Oracle Mode) of the corresponding OceanBase Database version.

ORA-00902: invalid datatype

• OceanBase error code: 5874

• SQLSTATE: HY000

• Cause: The data type is invalid.

ORA-00903: invalid table name

• OceanBase error code: 5163

• SQLSTATE: 42000

• Cause: The 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: A keyword is missing from the SQL statement.

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 long for column '%s' (max = %d byte)

• OceanBase error code: 5198

• SQLSTATE: 42000

• Cause: The specified string length is greater than the length supported by the data type. Specifically, the specified string length exceeds 2000 for the CHAR and RAW data types and 4000 for other data types.

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

ORA-00913: too many values

• OceanBase error code: 5613

• SQLSTATE: HY000

• Cause: Too many values exist.

ORA-00917: missing comma

• OceanBase error code: 7403
• SQLSTATE: 42000
• Cause: Necessary commas (,) are missing from an INSERT statement or from a list of columns or values in the ((C,D),(E,F), ...) format.
• Solution: Check the SQL statement to make sure that required commas (,) are present and correctly used.

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: An INSERT statement has been executed without the keyword INTO.

• Solution: Insert the keyword INTO where required and then retry 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: The identifier is missing.

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

• OceanBase error code: 5083

• SQLSTATE: 22000

• Cause: The data types are inconsistent.

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

• OceanBase error code: 7402
• SQLSTATE: 22000
• Cause: An incompatible data type is used in the SQL query.
• Solution: Check the SQL query to find the incompatible data type and use the CAST or CONVERT function to convert the incompatible data type to a compatible one.

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.

ORA-00937: not a single-group group function

• OceanBase error code: 5853

• SQLSTATE: HY000

• Cause: A non-single-group group function is used.

ORA-00938: not enough arguments for function

• OceanBase error code: 5774

• SQLSTATE: HY000

• Cause: Arguments of the function are insufficient.

ORA-00939: too many arguments for function

• OceanBase error code: 5683

• SQLSTATE: HY000

• Cause: The function contains excessive 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. In OceanBase Database V2.2.70 and later versions, role privileges are added. If the current role does not have the SELECT privilege on some tables or views, this error is returned.

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

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 versions, role privileges are added. If the current role does not have the SELECT privilege on some tables or views, this error is returned.

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

ORA-00947: not enough values

• OceanBase error code: 5614

• SQLSTATE: HY000

• Cause: Values are not enough.

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

• OceanBase error code: 5331 and 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 duplicate with an existing one.

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

• OceanBase error code: 4354

• SQLSTATE: HY000

• Cause: The 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: Make sure that the name entered is a correct table name and 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

• OceanBase error code: 5179

• SQLSTATE: 42000

• Cause: The specified identifier exceeds the maximum length.

• Solution: Reduce the number of bytes of the specified identifier to less than the maximum length.

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 is not allowed at the current location.

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

ORA-00979: 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 is not converted into a valid target object. The possible causes are as follows:

  • The target mode does not exist.

  • The target object does not exist.

  • The synonym specifies an incorrect database link.

  • The synonym specifies a target object for versioning but does not perform versioning.

• Solution: Modify the definition of the synonym so that the synonym points to a valid object.

ORA-00984: column not allowed here

• OceanBase error code: 5942

• SQLSTATE: HY000

• Cause: This column cannot be inserted here.

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.