ORA-13304: failure to insert a transformed geometry object in a table

ORA-13304: failure to insert a transformed geometry object in a table

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13303: failure to retrieve a geometry object from a table

ORA-13303: failure to retrieve a geometry object from a table

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13300: single point transform error

ORA-13300: single point transform error

Cause: Low-level coordinate transformation error trap.

Action: Check the accompanying error messages.

ORA-13296: incorrect coordinate system specification

ORA-13296: incorrect coordinate system specification

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.

ORA-13295: geometry objects are in different coordinate systems

ORA-13295: geometry objects are in different coordinate systems

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.

ORA-13294: cannot transform geometry containing circular arcs

ORA-13294: cannot transform geometry containing circular arcs

Cause: It is impossible to transform a 3-point representation of a circular arc without distortion.

Action: Make sure a geometry does not contain circular arcs.

ORA-13293: cannot specify unit for geometry without a georeferenced SRID

ORA-13293: cannot specify unit for geometry without a georeferenced SRID

Cause: An Oracle Spatial function with a UNIT parameter was called on a geometry without a georeferenced SRID.

Action: Make sure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs.

ORA-13292: incorrect ARC_TOLERANCE specification

ORA-13292: incorrect ARC_TOLERANCE specification

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 ARC_TOLERANCE specification and make sure it is correct.

ORA-13291: conversion error between the specified unit and standard unit

ORA-13291: conversion error between the specified unit and standard unit

Cause: Cannot convert the specified unit from or to standard unit for linear distance, angle, or area.

Action: Check the unit specification and respecify it.

ORA-13290: the specified unit is not supported

ORA-13290: the specified unit is not supported

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.

ORA-13288: point coordinate transformation error

ORA-13288: point coordinate transformation error

Cause: An internal error occurred while transforming points.

Action: Check the accompanying error messages.

ORA-13287: can t transform unknown gtype

ORA-13287: can t transform unknown gtype

Cause: A geometry with a gtype of lamp;lt;lamp;nbsp;= 0 was specified for transformation. Only a gtype lamp;gt;= 1 is allowed.

Action: Check the Oracle Spatial documentation for SDO_GTYPE values, and specify a value whose last digit is 1 or higher.

ORA-13285: Geometry coordinate transformation error

ORA-13285: Geometry coordinate transformation error

Cause: A coordinate pair was out of valid range for a conversion or projection.

Action: Check that data to be transformed is consistent with the desired conversion or projection.

ORA-13284: failure to copy geometry object for conversion in place

ORA-13284: failure to copy geometry object for conversion in place

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13283: failure to get new geometry object for conversion in place

ORA-13283: failure to get new geometry object for conversion in place

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13282: failure on initialization of coordinate transformation

ORA-13282: failure on initialization of coordinate transformation

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.

ORA-13281: failure in execution of SQL statement to retrieve WKT

ORA-13281: failure in execution of SQL statement to retrieve WKT

Cause: OCI internal error, or SRID does not match a table entry.

Action: Check that a valid SRID is being used.

ORA-13278: failure to convert SRID to native format

ORA-13278: failure to convert SRID to native format

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13276: internal error (string( in coordinate transformation

ORA-13276: internal error (string( in coordinate transformation

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13275: spatial index creation failure on unsupported type

ORA-13275: spatial index creation failure on unsupported type

Cause: An attempt was made to create a spatial index create on a column that is not of type SDO_GEOMETRY.

Action: A spatial index can only be created on a column of type SDO_ GEOMETRY. Make sure the indexed column is of type SDO_GEOMETRY.

ORA-13274: operator invoked with non-compatible SRIDs

ORA-13274: operator invoked with non-compatible SRIDs

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: Make sure that the layer and window both have an SRID or that they both do not have an SRID.

ORA-13273: dimension metadata table string does not exist

ORA-13273: dimension metadata table string does not exist

Cause: The lamp;lt;lamp;nbsp;layerlamp;gt;_SDODIM table does not exist.

Action: Verify that the specified layer name is correct and that the lamp;lt;lamp;nbsp;layerlamp;gt;_ SDODIM table exists in the current schema.

ORA-13272: geometric object string in table string is invalid

ORA-13272: geometric object string in table string is invalid

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.

ORA-13271: error allocating memory for geometry object

ORA-13271: error allocating memory for geometry object

Cause: Insufficient memory.

Action: Make more memory available to the current session or process.

ORA-13270: OCI error string

ORA-13270: OCI error string

Cause: An OCI error occurred while processing the layer or geometry tables.

Action: Take the appropriate steps to correct the OCI-specific error.

ORA-13269: internal error (string( encountered when processing geometry table

ORA-13269: internal error (string( encountered when processing geometry table

Cause: An internal error occurred.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13268: error obtaining dimension from USER_SDO_GEOM_METADATA

ORA-13268: error obtaining dimension from USER_SDO_GEOM_METADATA

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.

ORA-13267: error reading data from layer table string

ORA-13267: error reading data from layer table string

Cause: There was an error reading the geometry data from the lamp;lt;lamp;nbsp;layerlamp;gt;_ SDOGEOM table.

Action: Verify that lamp;lt;lamp;nbsp;layerlamp;gt;_SDOGEOM and lamp;lt;lamp;nbsp;layerlamp;gt;_SDODIM exist. If they do exist, run VALIDATE_LAYER_WITH_CONTEXT on the specified layer.

ORA-13266: error inserting data into table string

ORA-13266: error inserting data into table string

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.

ORA-13265: geometry identifier column string in table string is not of type NUMBER

ORA-13265: geometry identifier column string in table string is not of type NUMBER

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.

ORA-13264: geometry identifier column string does not exist in table string

ORA-13264: geometry identifier column string does not exist in table string

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.

ORA-13263: column string in table string is not of type SDO_GEOMETRY

ORA-13263: column string in table string is not of type SDO_GEOMETRY

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.

ORA-13262: geometry column string does not exist in table string

ORA-13262: geometry column string does not exist in table string

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.

ORA-13261: geometry table string does not exist

ORA-13261: geometry table string does not exist

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.

ORA-13260: layer table string does not exist

ORA-13260: layer table string does not exist

Cause: Data migration source table lamp;lt;lamp;nbsp;layerlamp;gt;_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.

ORA-13251: duplicate entry string in metadata table

ORA-13251: duplicate entry string in metadata table

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.

ORA-13250: insufficient privileges to modify metadata table entries

ORA-13250: insufficient privileges to modify metadata table entries

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.

ORA-13249: %s

ORA-13249: %s

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.

ORA-13243: specified operator is not supported for 3- or higher-dimensional R-tree

ORA-13243: specified operator is not supported for 3- or higher-dimensional R-tree

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.

ORA-13241: specified dimensionality does not match that of the data

ORA-13241: specified dimensionality does not match that of the data

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.

ORA-13240: specified dimensionality greater than that of the query mbr

ORA-13240: specified dimensionality greater than that of the query mbr

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.

ORA-13239: sdo_dimensionality not specified during n-d R-tree creation

ORA-13239: sdo_dimensionality not specified during n-d R-tree creation

Cause: An error occurred in reading the dimensionality parameter

Action: Check the documentation for a valid range, and specify the dimensionality as a parameter.

ORA-13237: internal error during R-tree concurrent updates: (string(

ORA-13237: internal error during R-tree concurrent updates: (string(

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.

ORA-13236: internal error in R-tree processing: (string(

ORA-13236: internal error in R-tree processing: (string(

Cause: An internal error occurred in R-tree processing.

Action: Contact Oracle Support Services with the message text.

ORA-13234: failed to access R-tree-index table (string(

ORA-13234: failed to access R-tree-index table (string(

Cause: The index table is either deleted or corrupted.

Action: Rebuild the index or contact Oracle Support Services with accompanying error messages.

ORA-13233: failed to create sequence number (string( for R-tree

ORA-13233: failed to create sequence number (string( for R-tree

Cause: The specified sequence number exists.

Action: Delete the sequence object, or contact Oracle Support Services.

ORA-13232: failed to allocate memory during R-tree creation

ORA-13232: failed to allocate memory during R-tree creation

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.

ORA-13231: failed to create index table (string( during R-tree creation

ORA-13231: failed to create index table (string( during R-tree creation

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.

ORA-13230: failed to create temporary table (string( during R-tree creation

ORA-13230: failed to create temporary table (string( during R-tree creation

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.

ORA-13228: spatial index create failed due to invalid type

ORA-13228: spatial index create failed due to invalid type

Cause: An Attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY.

Action: Make sure that the index is created on a column of type SDO_ GEOMETRY.

ORA-13227: SDO_LEVEL values for the two index tables do not match

ORA-13227: SDO_LEVEL values for the two index tables do not match

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

ORA-13226: interface not supported without a spatial index

ORA-13226: interface not supported without a spatial index

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.

ORA-13225: specified index table name is too long for a spatial index

ORA-13225: specified index table name is too long for a spatial index

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.

ORA-13224: zero tolerance specified for layer in USER_SDO_GEOM_METADATA

ORA-13224: zero tolerance specified for layer in USER_SDO_GEOM_METADATA

Cause: A tolerance of zero or NULL is supplied for a layer in USER_SDO_ GEOM_METADATA view.

Action: Check the tolerance specified to make sure it is a positive value.

ORA-13223: duplicate entry for string in SDO_GEOM_METADATA

ORA-13223: duplicate entry for string in SDO_GEOM_METADATA

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.

ORA-13222: failed to compute supercell for geometry in string

ORA-13222: failed to compute supercell for geometry in string

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.

ORA-13221: unknown geometry type in the geometry object

ORA-13221: unknown geometry type in the geometry object

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.

ORA-13220: failed to compare tile with the geometry

ORA-13220: failed to compare tile with the geometry

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

ORA-13219: failed to create spatial index table (string(

ORA-13219: failed to create spatial index table (string(

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.

ORA-13218: max number of supported index tables reached for (string( index

ORA-13218: max number of supported index tables reached for (string( index

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.