Oracle 12c R2 Error Codes and Solution Suggestions from ORA-13200 to ORA-13300
- ORA-13200: internal error [string] in spatial indexing.
Cause: This is an internal error.
Action: Contact Oracle Support Services with the exact error text.
Cause: An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement.
Action: Check the Oracle Spatial documentation for the number, syntax, and semantics of expected parameters for spatial index creation.
Cause: An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it.
Action: Verify that the current user has CREATE TABLE privilege and that the user has sufficient quota in the default or specified tablespace.
Cause: An error encountered while trying to read the USER_SDO_GEOM_METADATA view.
Action: Check that USER_SDO_GEOM_METADATA has an entry for the current geometry table.
Cause: An error was encountered while trying to create the index table.
Action: Check that user has CREATE TABLE privilege in the current schema and that the user has sufficient quota in the default or specified tablespace.
Cause: An internal error was encountered while parsing the spatial parameters.
Action: Check that the parameters passed in the parameter string are all valid.
Cause: An internal error was encountered while creating the spatial index.
Action: Contact Oracle Support Services with the exact error text.
Cause: An error was encountered while evaluating the specified operator.
Action: Check the parameters and the return type of the specified operator.
Cause: An internal error was encountered.
Action: Contact Oracle Support Services with the exact error text.
Cause: An internal error was encountered while trying to read the SDO_INDEX_METADATA table.
Action: Contact Oracle Support Services. Note this and accompanying error numbers.
Cause: An error was encountered while trying to insert data into the index table. Likely causes are: – Insufficient quota in the current tablespace – User does not appropriate privileges
Action: Check the accompanying error messages.
Cause: An internal error was encountered while trying to tessellate the window object.
Action: Verify the geometric integrity of the window object using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure.
Cause: The spatial relationship between a generated tile and the specified window object 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 accompanying errors and contact Oracle Support Services.
Cause: Another error, indicating the real cause of the problem, should accompany this error.
Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services.
Cause: The system was unable to compute the minimum bounding tile or supercell for the geometry.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
Cause: Tessellation did not generate any tiles for this geometry. This error could be caused if the geometry definition puts the geometry outside the domain defined in the USER_SDO_GEOM_METADATA view.
Action: Verify that the geometry is valid and within the defined domain.
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: An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement.
Action: Check the Oracle Spatial documentation for the number, syntax, and semantics of expected parameters for the spatial ALTER INDEX statement.
Cause: An add_index parameter was passed to ALTER INDEX when the number of existing index tables is already at maximum.
Action: Delete one of the index tables before adding another index table.
Cause: An error was encountered while trying to create the index table.
Action: There is a table in the index’s schema with the specified name. The CREATE INDEX statement will try to create an index table with this name. Either rename this table or change the name of the index.
Cause: The spatial relationship between a generated tile and the specified geometry could not be determined.
Action: This is an internal error. Validate the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any errors that accompany ORA-13220 and contact Oracle Support Services.
Cause: The SDO_GTYPE attribute in the geometry object contains an invalid value
Action: Redefine the geometric type in the geometry table using one of the supported SDO_GTYPE values. See the Oracle Spatial documentation for an explanation of SDO_GTYPE and its possible values.
Cause: The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
Cause: There are duplicate entries for the given table and column value pair in the USER_SDO_GEOM_METADATA view.
Action: Check that the specified table and geometry column names are correct. There should be only one entry per table, geometry column pair in the USER_SDO_GEOM_METADATA view.
Cause: A tolerance of zero or NULL was supplied for a layer in the USER_SDO_GEOM_METADATA view.
Action: Check the tolerance specified to ensure that it is a positive value.
Cause: An index table name is specified which is longer than the supported length of the spatial index table name.
Action: Check the supported size of the index table name and reduce the size of the index name.
Cause: The geometry table does not have a spatial index.
Action: Verify that the geometry table referenced in the spatial operator has a spatial index on it.
Cause: The SDO_LEVEL values for the two index tables used in the spatial join operator do not match.
Action: Verify that two compatible indexes are used for the spatial join operator. Quadtree indexes are compatible if they have the same SDO_LEVEL and SDO_NUMTILES values
Cause: An attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY.
Action: Ensure that the index is created on a column of type SDO_GEOMETRY.
Cause: The specified temporary table either already exists or there is not enough tablespace.
Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privileges and has sufficient space in the default or specified tablespace.
Cause: The specified index table either already exists or there is not enough tablespace.
Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privileges and has sufficient space in the default or specified tablespace. If that fails to correct the problem, contact Oracle Support Services.
Cause: This feature assumes a minimum of 64K memory for bulk creation.
Action: Create the index for a small subset of the data. Then, use transactional insert operations for the rest of the data.
Cause: The specified sequence number exists.
Action: Delete the sequence object, or contact Oracle Support Services.
Cause: The index table is either deleted or corrupted.
Action: Rebuild the index or contact Oracle Support Services with accompanying error messages.
Cause: An internal error occurred in R-tree processing.
Action: Contact Oracle Support Services with the message text.
Cause: An inconsistency is encountered during concurrent updates, possibly due to the use of serializable isolation level.
Action: Change the isolation level to “read committed” using the ALTER SESSION statement, or contact Oracle Support Services with the message text.
Cause: An error occurred in reading the dimensionality parameter
Action: Check the documentation for a valid range, and specify the dimensionality as a parameter.
Cause: An error occurred because of too few values in the query minimum bounding rectangle (MBR).
Action: Omit the dimensionality, or use the dimensionality of the query.
Cause: An error occurred because the dimensionality specified in the CREATE INDEX statement does not match that of the data.
Action: Change the statement to reflect the data dimensionality.
Cause: Currently, an R-tree index with three or more index dimensions can be used only with the SDO_FILTER operator.
Action: Use the SDO_FILTER operator, and check the documentation for the querytype parameter for SDO_FILTER; or contact Oracle Support Services.
Cause: An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component.
Action: Contact Oracle Support Services with the exact error text.
Cause: The user requesting the operation does not have the appropriate privileges on the referenced tables.
Action: Check that the specified feature and geometry table names are correct, and then verify that the current user has at least SELECT privilege on those tables.
Cause: The specified entry already exists in the metadata table.
Action: Check that the specified feature and geometry table names are correct. A feature-geometry table association should be registered only once.
Cause: Data migration source table layer_SDOGEOM does not exist.
Action: Ensure that the specified layer name is correct and that the corresponding spatial layer tables exist in the current schema.
Cause: The specified geometry table does not exist in the current schema.
Action: Create a table containing a column of type SDO_GEOMETRY and a column of type NUMBER for the GID values.
Cause: The specified table does not have a column of type SDO_GEOMETRY.
Action: Alter or re-create the table such that it includes a column of type SDO_GEOMETRY and a column of type NUMBER.
Cause: The column intended for storing the geometry is not of type SDO_GEOMETRY.
Action: Alter the column definition to be of type SDO_GEOMETRY.
Cause: The specified table does not contain a GID column.
Action: Confirm that the GID column name was correctly specified and that it exists in the specified table.
Cause: GID column is not of type NUMBER.
Action: Alter the table definition such that the column containing the geometry identifier (GID) is of type NUMBER.
Cause: An OCI error occurred, or the user has insufficient quota in the active tablespace, or the rollback segments are too small.
Action: There should be an accompanying error message that indicates the cause of the problem. Take appropriate action to correct the indicated problem.
Cause: There was an error reading the geometry data from the layer_SDOGEOM table.
Action: Verify that layer_SDOGEOM and layer_SDODIM exist. If they do exist, run VALIDATE_LAYER_WITH_CONTEXT on the specified layer.
Cause: There is no entry in the USER_SDO_GEOM_METADATA view for the specified geometry table.
Action: Insert an entry for the destination geometry table with the correct dimension information.
Cause: An internal error occurred.
Action: Contact Oracle Support Services with the exact error message text.
Cause: An OCI error occurred while processing the layer or geometry tables.
Action: Take the appropriate steps to correct the OCI-specific error.
Cause: Insufficient memory.
Action: Make more memory available to the current session/process.
Cause: The specified object failed the geometric integrity checks performed by the validation function.
Action: Check the Oracle Spatial documentation for information about the geometric integrity checks performed by VALIDATE_GEOMETRY_WITH_CONTEXT and correct the geometry definition if required.
Cause: The layer_SDODIM table does not exist.
Action: Verify that the specified layer name is correct and that the layer_SDODIM table exists in the current schema.
Cause: A spatial operator was invoked with a window geometry with an SRID but the layer has no SRID; or the window has no SRID but the layer has an SRID.
Action: Ensure that the layer and window both have an SRID or that they both do not have an SRID.
Cause: An attempt was made to create a spatial index on a column that was not of type SDO_GEOMETRY.
Action: A spatial index can only be created on a column of type SDO_GEOMETRY. Ensure that the indexed column is of type SDO_GEOMETRY.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: OCI internal error, or SRID does not match a table entry.
Action: Check that a valid SRID is being used.
Cause: Parsing error on source or destination coordinate system WKT, or incompatible coordinate systems.
Action: Check the validity of the WKT for table entries, and check if the requested transformation is valid.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: A coordinate pair was out of valid range for a conversion/projection.
Action: Check that data to be transformed is consistent with the desired conversion/projection.
Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a gtype >= 1 is allowed.
Action: Check the Oracle Spatial documentation for SDO_GTYPE values, and specify a value whose last digit is 1 or higher.
Cause: An internal error occurred while transforming points.
Action: Check the accompanying error messages.
Cause: An Oracle Spatial function was called with an unknown UNIT value.
Action: Check Spatial documentation for the supported units, and call the function with the correct UNIT parameter.
Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area.
Action: Check the unit specification and respecify it.
Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE must be specified, and it should not be less than the tolerance specified for the geometry.
Action: Check the ARC_TOLERANCE specification and ensure that it is correct.
Cause: An Oracle Spatial function with a UNIT parameter was called on a geometry without a georeferenced SRID.
Action: Ensure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs.
Cause: An attempt was made to transform a 3-point representation of a circular arc without distortion.
Action: Ensure that a geometry does not contain circular arcs.
Cause: An Oracle Spatial function was called with two geometries that have different SRIDs.
Action: Transform geometry objects to be in the same coordinate system and call the spatial function.
Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID.
Action: Check WKT in the MDSYS.CS_SRS table for Earth radius and inverse flattening.
Cause: Low-level coordinate transformation error trap.
Action: Check the accompanying error messages.