Oracle 12c R2 Error Codes and Solution Suggestions from ORA-13000 to ORA-13100
- ORA-13000: dimension number is out of range
Cause: The specified dimension was either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.
Action: Ensure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.
Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation did not match.
Action: Ensure that the number of dimensions in the HHCODEs match.
Cause: The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE.
Action: Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE.
Cause: The specified range for a dimension was invalid.
Action: Ensure that the lower bound (lb) is less than the upper bound (ub).
Cause: The buffer size for a function is not valid.
Action: This is an internal error. Contact Oracle Support Services.
Cause: An error occurred in a recursively called HHCODE function.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The cell identifier was either less than 0 or greater than (2^ndim – 1).
Action: Ensure that the cell identifier is between 0 and (2^ndim – 1).
Cause: A character that is not in the range [0-9] or [A-F a-f] was detected.
Action: Verify that all characters in a string are in [0-9] or [A-F a-f].
Cause: Part of specified date format is invalid.
Action: Verify that the date format is valid.
Cause: The specified date string had a bad component or did not match the specified format string.
Action: Ensure that the components of the date string are valid and that the date and format strings match.
Cause: An invalid number of arguments was specified for an SDO function.
Action: Verify the syntax of the function call.
Cause: A specified dimension value was outside the range defined for that dimension.
Action: Ensure that all values to be encoded are within the defined dimension range.
Cause: An invalid window type was specified.
Action: Valid window types are RANGE, PROXIMITY, POLYGON.
Cause: A topology was specified that was not INTERIOR or BOUNDARY.
Action: Ensure that INTERIOR or BOUNDARY is used to describe the topology of the HHCODE.
Cause: A topology identifier outside the range of 1 to 8 was specified.
Action: Specify a topology in the range of 1 to 8.
Cause: The number of values used to define the window does not correspond to the window type.
Action: Verify that the number of values used to defined the window is correct for the window type and number of dimensions.
Cause: The specified topology did not exist in the database, or some components of the topology were missing from the database.
Action: Check the specified topology by executing the SDO_TOPO.validate_topology function.
Cause: The shape of a 2-D line partition could not be determined.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The specified distance type is invalid.
Action: The only supported distance functions are EUCLID and MANHATTAN.
Cause: Vertex coordinates lie outside the valid range for specified dimension.
Action: Redefine vertex coordinates within specified boundaries.
Cause: A vertex coordinate has a NULL value.
Action: Redefine vertex coordinate to have non-NULL value.
Cause: The coordinates defining a geometric element are not connected.
Action: Redefine coordinates for the geometric element.
Cause: The coordinates defining a polygonal geometric element represent crossing segments.
Action: Redefine coordinates for the polygon.
Cause: An interior element of a geometric object interacts with the exterior element of that object.
Action: Redefine coordinates for the geometric elements.
Cause: The coordinates defining a polygonal geometric element represent less than three segments.
Action: Redefine the coordinates for the polygon.
Cause: The coordinates defining a polygonal geometric element represent an open polygon.
Action: Redefine the coordinates of the polygon.
Cause: The SDO_ETYPE column in the layer_SDOGEOM table contains an invalid geometric element type value.
Action: Redefine the geometric element type in the layer_SDOGEOM table for the specified geometric element using one of the supported SDO_ETYPE values. See the Oracle Spatial documentation for an explanation of SDO_ETYPE and its possible values.
Cause: There was a problem reading the dimension definition from the layer_SDODIM table.
Action: Verify that the layer_SDODIM table exists and that the appropriate privileges exist on the table. Address any other errors that might appear with the message.
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid gtypes.
Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may be outside the valid SRID range.
Action: Verify that the geometries have valid SRIDs.
Cause: There is a mismatch between the dimension in the SDO_GTYPE and dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.
Action: Verify that the geometries have valid dimensionality.
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the VARRAYs are NULL but the SDO_GTYPE is not of type POINT.
Action: Verify that the geometries have valid gtypes.
Cause: There are invalid SDO_POINT_TYPE or SDO_ELEM_INFO_ARRAY or SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid fields. To specify a NULL geometry, specify the whole SDO_GEOMETRY as NULL instead of setting each field to NULL.
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. The triplets in this field do not make up a valid geometry.
Action: Verify that the geometries have valid data.
Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the SDO_GEOMETRY object. The coordinates in this field do not make up a valid geometry. There may be NULL values for X or Y or both.
Action: Verify that the geometries have valid data.
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. There are arcs in a geometry that has geodetic coordinates.
Action: Verify that the geometries have valid data.
Cause: The specified geometry function was not supported for point data.
Action: Ensure that the specified geometry function is not called on point data.
Cause: A spatial operation was invoked with two geometries where one geometry had an SRID and the other geometry did not have an SRID.
Action: Ensure that the spatial operations are invoked between two geometries with compatible SRIDs.
Cause: Another error will accompany this message that will indicate the problem.
Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services.
Cause: This is an internal error.
Action: Note any accompanying errors and contact Oracle Support Services.
Cause: The spatial relationship between a generated tile and the specified element could not be determined.
Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any errors that accompany ORA-13041 and contact Oracle Support Services.
Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the layer_SDOLAYER table. The most likely cause is that the columns are NULL.
Action: Verify the that SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial documentation. Then retry the operation.
Cause: An error was encountered reading the layer metadata from the layer_SDOLAYER table.
Action: This error is usually the result of an earlier error which should also have been reported. Address this accompanying error and retry the current operation. If no accompanying error was reported, contact Oracle Support Services.
Cause: The tile size specified for fixed size tessellation is smaller than the tolerance as specified in the layer metadata.
Action: See the Oracle Spatial documentation for an explanation of tiling levels, tile size, and tiling resolution. Ensure that the tiling parameters are set such that any generated tile is always larger than or equal to a tile at the maximum level of resolution. This can be achieved by using a fewer number of tiles per geometric object or specifying a smaller tile size value than the current one.
Cause: An invalid number of arguments were specified for an SDO_GEOM function.
Action: See the Oracle Spatial documentation for a description of the syntax and semantics of the relevant SDO_GEOM function.
Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer layer.
Action: Verify that the layer_SDOLAYER table has a valid value for the column SDO_ORDCNT. Then retry the operation.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer layer.
Action: Verify that the layer_SDODIM table has a valid value for the column SDO_TOLERANCE.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The geometry type for a specific instance in a layer_SDOGEOM table is not among the set of geometry types supported by Oracle Spatial.
Action: Check the Oracle Spatial documentation for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema.
Cause: The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded.
Action: Check the Oracle Spatial documentation for the syntax of the SDO_GEOM function and use fewer arguments to describe the geometry, or check the description of the SDO_WINDOW package for a workaround that permits storing the object in a table and then using it in as an argument in a call to the SDO_GEOM function.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The requested object is not present in the specified table.
Action: Verify the syntax of the function or procedure that reported this error and verify that the object does indeed exist in the specified table. Then retry the operation.
Cause: The operation required a valid SRID but none was specified.
Action: Contact Oracle Support Services.
Cause: The specified SRID is not known.
Action: Ensure that the specified SRID was valid.
Cause: The SRID for the operation could not be determined.
Action: Ensure that the SRID for the operation is valid.
Cause: An invalid “WRK_TBLSPC” parameter value was specified.
Action: Ensure that the specified “WRK_TBLSPC” exists and is accessible to the current user.
Cause: The specified topology name was not unique in the database.
Action: Verify that the CREATE_TOPOLOGY call specifies the correct topology name and that the procedure is invoked from the correct schema.
Cause: The specified topology did not exist in the database.
Action: Verify that the current procedure/function call specifies the correct schema and topology name.
Cause: The specified topology ID in the feature table did not match the topology ID stored in the topology metadata.
Action: Verify that the specified topology ID matches the topology ID stored in the topology metadata.
Cause: The topology relationship information table (xxx_RELATION$) did not have the matching partition corresponding to the feature table.
Action: Ensure the correct topology IDs and names are specified in the call to register the feature table with the topology.
Cause: The topology_id and tg_layer_id values stored in the feature table did not match the values stored in the topology relationship information table (xxx_RELATION$).
Action: Ensure that the correct feature tables are specified in the call to register the feature table with the topology.
Cause: A call was made to delete a feature layer which has a dependent layer defined on it.
Action: Ensure that all dependent feature layers are deleted before deleting the current feature layer.
Cause: The SDO_TOPO_GEOMETRY object had the wrong geometry and/or element type.
Action: Correct the geometry and/or element type in the SDO_TOPO_GEOMETRY object.
Cause: Both SDO_TOPO_GEOMETRY parameters did not come from the same topology.
Action: Ensure that both of the parameters to the operator are from the same topology. If this is not possible, consider using a signature of the operator that does not use two SDO_TOPO_GEOMETRY parameters.
Cause: An SDO_TOPO_GEOMETRY constructor was invoked with incorrect parameters for table name and/or column name.
Action: Fix the parameters in the call and try again.
Cause: An incorrect degree value <=1 was passed for a Non-Uniform Rational B-Spline curve.
Action: Correct the degree value for the Non-Uniform Rational B-Spline curve.
Cause: An incorrect number of control points was passed for a Non-Uniform Rational B-Spline curve.
Action: Correct the number of control points for the Non-Uniform Rational B-Spline curve.
Cause: An incorrect number of control points and degree was passed for a Non-Uniform Rational B-Spline curve.
Action: Ensure that the number of control points is greater than the degree for a Non-Uniform Rational B-Spline curve.
Cause: An incorrect number of knot values was passed for a Non-Uniform Rational B-Spline curve.
Action: Correct the number of knot values passed for the Non-Uniform Rational B-Spline curve.
Cause: An incorrect value was passed for the weight of a control point of a Non-Uniform Rational B-Spline curve.
Action: Ensure all weight values for control points are positive.
Cause: An incorrect knot value was passed for a Non-Uniform Rational B-Spline curve.
Action: Ensure the knot values passed for the Non-Uniform Rational B-Spline curve are in non-decreasing order.
Cause: An incorrect knot value sequence was passed for a Non-Uniform Rational B-Spline curve.
Action: Ensure the knot values passed for the Non-Uniform Rational B-Spline curve have no more than a sequence of ‘k’ consecutive identical values or no more than ‘k + 1’ consecutive same values at the beginning or end of Non-Uniform Rational B-Spline curve.
Cause: An incorrect knot value sequence was passed for a Non-Uniform Rational B-Spline curve.
Action: Ensure the knot value sequence passed for the Non-Uniform Rational B-Spline curve is a normalized vector beginning at zero and ending at one.
Cause: The end point of a subelement for a compound curve was not equal to the start point of the next subelement, or the start point of a subelement was not equal to the end point of the previous subelement and one of the subelements was a NURBS curve.
Action: Ensure that the end point of each subelement is equal to the start point of the next subelement and that the start point of each subelement is equal to the end point of the previous subelement when one of the subelements is a NURBS curve.
Cause: An attempt was made to commit changes to a spatial table in a distributed transaction, but spatial indexes are not supported in distributed transactions.
Action: Perform all transactional changes to spatial tables (tables containing spatial geometry columns) in a local non-distributed transaction. For more information about this restriction, refer to the Oracle Spatial Data and Graph documentation.
Cause: The specified schema name was invalid.
Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the schema name is valid.
Cause: The specified spatial index name was invalid.
Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the spatial index name is valid.
Cause: The specified index table name was invalid.
Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the index table name is valid. The index table name typically starts with “MDRT_” prefix.
Cause: The specified index partition name was invalid.
Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the index partition name was valid.
Cause: The specified index parameter or parameter combination was invalid.
Action: Check the list of index parameters to ensure that they are correctly specified and valid for the corresponding index operation.
Cause: An attempt was made to create the spatial index on an index- organized table (IOT).
Action: Spatial indexes cannot be created on index-organized tables.
Cause: The specified column name was invalid.
Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the index column name is valid. If the column name is a function, ensure the function name is properly spelled and case-sensitive.
Cause: An attempt was made to use optimized geodetic minimum bounding rectangles (MBR).
Action: The object tracker cannot be used on objects that are composed of optimized MBRs.
Cause: The number of table columns specified for the PointInPolygon() function was incorrect.
Action: Ensure that there are at least two columns specified, and that the first two columns are of the NUMBER type, representing the X and Y coordinates.
Cause: It has been detected that 1 or more rows have been pre-fetched from the specified query cursor.
Action: One or more rows were pre-fetched from the specified query cursor.
Cause: The specified tolerance value was invalid.
Action: The tolerance value must be greater than 0.0.
Cause: The specified geometry is not two-dimensional.
Action: Ensure the geometry is two-dimensional.
Cause: The operation is not valid using geodetic MBRs.
Action: Ensure the geometry is not using geodetic MBRs.
Cause: The operation failed.
Action: Contact Oracle Support Services.
Cause: The polygon ring size exceeded half the area of the earth.
Action: Contact Oracle Support Services.
Cause: The specified query cursor was invalid.
Action: Contact Oracle Support Services.
Cause: The specified element number is incorrect.
Action: Ensure the specified element number is valid for the geometry.
Cause: The specified geometry type is incorrect.
Action: Ensure the specified geometry type (GTYPE) is valid for the geometry.
Cause: The specified element type is incorrect.
Action: Ensure the specified element type (GTYPE) is valid for the geometry.
Cause: There are more elements than were specified.
Action: Ensure the specified number of elements is valid for the geometry.
Cause: The geometry ring topology (inner or outer) is wrong.
Action: Contact Oracle Support Services.
Cause: The feature does not exist.
Action: Contact Oracle Support Services.