Oracle 12c R2 Error Codes and Solution Suggestions from ORA-13100 to ORA-13200
- ORA-13100: feature does not exist
Cause: The feature does not exist.
Action: Contact Oracle Support Services.
Cause: An incorrect ptn_type parameter was specified.
Action: Ensure the ptn_type parameter value is correct.
Cause: An incorrect ptn_capacity parameter was specified.
Action: Ensure the ptn_capacity parameter value is correct.
Cause: An incorrect numdim parameter was specified.
Action: Ensure the numdim parameter value is correct.
Cause: Null values cannot be specified in the supplied input data.
Action: Ensure that all null-values have been removed from the data.
Cause: One or more parameters for the Partition_Table() function are invalid.
Action: Ensure that the identified parameters are correctly specified.
Cause: The specified MASK parameter was invalid.
Action: Ensure that the MASK parameter values are correctly specified.
Cause: This operation cannot be executed for Non-Uniform Rational B-Spline curves.
Action: Specify a geometry that does not contain a Non-Uniform Rational B-Spline curve type.
Cause: The specified spatial table did not exist.
Action: Check the spatial data dictionary to ensure that the table is registered.
Cause: The specified spatial table is registered in the Spatial data dictionary.
Action: Remove the existing table from the Spatial data dictionary or use a different name.
Cause: The drop_topology procedure was invoked for a topology that has assocated topo_geometry layers with it.
Action: Delete the topo_geometry layers from the topology before dropping the topology. Use SDO_TOPO.delete_topo_geometry_layer to delete topo_geometry layers from the topology.
Cause: It was not possible to add the specified TOPO_GEOMETRY layer to the topology.
Action: Ensure that the TOPO_GEOMETRY layer table exists in the database.
Cause: It was not possible to delete the specified topo_geometry layer from the topology.
Action: Check USER_SDO_TOPO_METADATA to see if the specified topo_geometry layer is part of the topology. Only those topo_geometry layers which are part of the topology can be deleted from it.
Cause: An invalid layer_id was passed to the SDO_TOPO_GEOMETRY constructor.
Action: Valid layer_ids are obtained by adding a topo_geometry layer to the topology. Check USER_SDO_TOPO_METADATA to find out the layer_id for an existing topo_geometry layer.
Cause: The NODE$ table for the topology did not exist in the database.
Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.
Cause: The EDGE$ table for the topology did not exist in the database.
Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.
Cause: The FACE$ table for the topology did not exist in the database.
Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.
Cause: The RELATION$ table for the topology did not exist in the database.
Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number.
Cause: A topology node operation was invoked with an invalid node_id.
Action: Check the topology node$ table to see if the specified node_id exists in the topology.
Cause: A topology edge operation was invoked with an invalid edge_id.
Action: Check the topology edge$ table to see if the specified edge_id exists in the topology.
Cause: A topology face operation was invoked with an invalid face_id.
Action: Check the topology face$ table to see if the specified face_id exists in the topology.
Cause: The tg_type in SDO_TOPO_GEOMETRY constructor did not match the type specified for the layer.
Action: Check the USER_SDO_TOPO_METADATA view to see the layer type for the layer and use it in the constructor.
Cause: The SDO_TOPO_GEOMETRY object passed into the function/operator was not valid.
Action: Check the SDO_TOPO_GEOMETRY object and verify that it is a valid topo_geometry object.
Cause: The create_topo operation requires a unique TOPOLOGY name, that already does not exist in the database.
Action: Check to see if there is already an entry in the USER_SDO_TOPO_METADATA (or the MDSYS.SDO_TOPO_METADATA_TABLE) with this topology name.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: A partition key is already set for the spatial table.
Action: Only one partition key can be specified per spatial table.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The specified spatial column does not exist.
Action: Verify that the specified column is a spatial column by checking the Spatial data dictionary.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The specified target type is not valid.
Action: Substitute a valid target type. Valid target types are TABLE and VIEW.
Cause: The RANGE window specified is not correctly defined.
Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (e.g.: lower_bound1,upper_bound1,lower_bound2,upper_bound2,…). There should be an even number of values.
Cause: The PROXIMITY window specified is not correctly defined.
Action: A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values.
Cause: The POLYGON window specified is not correctly defined.
Action: A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: The partition name substitution variable %s was not found in the SQL filter.
Action: The substitution variable %s must be in the SQL filter to indicate where that partition name should be placed.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: Operation failed to insert a record into the exception table.
Action: Fix any other errors reported.
Cause: Operation failed to remove a record from the exception table.
Action: Fix any other errors reported.
Cause: Specified HHCODE type is not valid.
Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.
Cause: The high water mark was not greater than or equal to zero.
Action: Ensure that the high water mark is an integer greater than or equal to zero.
Cause: The precision specified is out of range.
Action: The precision must be an integer greater than or equal to zero.
Cause: The number of dimensions specified is out of range.
Action: The number of dimension must be between 1 and 32.
Cause: The specified table contained rows.
Action: Ensure that the table to be registered is empty.
Cause: The specified Oracle error was encountered.
Action: Correct the Oracle error.
Cause: The specified object does not exist.
Action: Verify that the specified object exists.
Cause: The specified table already exists.
Action: Drop the specified table.
Cause: The length of the SDO_CODE column in the layer_SDOINDEX table could not be determined.
Action: Ensure that the layer_SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Then retry the operation.
Cause: The specified element could not be read from the layer_SDOGEOM table.
Action: Verify that the specified element exists in the table. Then retry the operation.
Cause: The geometry type in the layer_SDOGEOM table is unsupported.
Action: Modify the geometry type to be one of the supported types.
Cause: Initialization of the tessellation package failed.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: There was insufficient memory to read the geometry from the database.
Action: Validate the geometry. Record the error messages that are returned and contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
Cause: The system was unable to compute the minimum bounding HHCODE 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 element. This error could be caused if the geometry definition puts the geometry outside the domain defined in the layer_SDODIM table.
Action: Verify that the geometry is valid and within the defined domain.
Cause: Internal error in some Oracle Spatial stored procedure.
Action: Record the sequence of procedure calls or events that preceded this error, and contact Oracle Support Services if the error message text does not clearly specify the cause of the error.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services with the exact error text.