Oracle 11g Error Codes and Solution Suggestions from ORA-13200 to ORA-13400

Posted on by Fatih Acar

Oracle 11g Error Codes and Solution Suggestions from ORA-13200 to ORA-13400

ORA-13200: internal error [string] in spatial indexing.
Cause: This is an internal error.
Action: Contact Oracle Support Services with the exact error text.
ORA-13201: invalid parameters supplied in CREATE INDEX statement
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.
ORA-13202: failed to create or insert into the SDO_INDEX_METADATA table
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.
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
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.
ORA-13204: failed to create spatial index 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.
ORA-13205: internal error while parsing spatial parameters
Cause: An internal error was encountered while parsing the spatial parameters.
Action: Check that the parameters passed in the parameter string are all valid.
ORA-13206: internal error [string] while creating the spatial index
Cause: An internal error was encountered while creating the spatial index.
Action: Contact Oracle Support Services with the exact error text.
ORA-13207: incorrect use of the [string] operator
Cause: An error was encountered while evaluating the specified operator.
Action: Check the parameters and the return type of the specified operator.
ORA-13208: internal error while evaluating [string] operator
Cause: An internal error was encountered.
Action: Contact Oracle Support Services with the exact error text.
ORA-13209: internal error while reading SDO_INDEX_METADATA table
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.
ORA-13210: error inserting data into the index table
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.
ORA-13211: failed to tessellate the window object
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.
ORA-13212: failed to compare tile with the window object
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.
ORA-13213: failed to generate spatial index for window object
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.

ORA-13214: failed to compute supercell for window object
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.
ORA-13215: window object is out of range
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.
ORA-13216: failed to update spatial index
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.
ORA-13217: invalid parameters supplied in ALTER INDEX statement
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.
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.
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-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 errors, note any errors that accompany ORA-13220 and contact Oracle Support Services.
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-13249: string
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-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-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-13260: layer table string does not exist
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.
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-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-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-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-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-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-13267: error reading data from layer table string
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.
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-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-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-13271: error allocating memory for geometry object
Cause: Insufficient memory.
Action: Make more memory available to the current session/process.
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-13273: dimension metadata table string does not exist
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.
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-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-13276: internal error [string] in coordinate transformation
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
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-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-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-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-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-13285: Geometry coordinate transformation error
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.
ORA-13287: can’t transform unknown gtype
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.
ORA-13288: point coordinate transformation error
Cause: An internal error occurred while transforming points.
Action: Check the accompanying error messages.
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-13291: conversion error between the specified unit and standard unit
Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area.
Action: Check the unit specification and respecify it.
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-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-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-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-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-13300: single point transform error
Cause: Low-level coordinate transformation error trap.
Action: Check the accompanying error messages.
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-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-13330: invalid MASK
Cause: The MASK passed to the RELATE function is not valid.
Action: Verify that the mask is not NULL. See the Oracle Spatial documentation for a list of supported masks.
ORA-13331: invalid LRS segment
Cause: The given LRS segment was not a valid line string.
Action: A valid LRS geometric segment is a line string geometry in Oracle Spatial. It could be a simple or compound line string (made of lines or arcs, or both). The dimension information must include the measure dimension as the last element in the Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or longitude/latitude, plus measure)
ORA-13332: invalid LRS point
Cause: The specified LRS point was not a point geometry with measure information.
Action: Check the given point geometry. A valid LRS point is a point geometry in Oracle Spatial with an additional dimension for measure.
ORA-13333: invalid LRS measure
Cause: The given measure for linear referencing was out of range.
Action: Redefine the measure.
ORA-13334: LRS segments not connected
Cause: The specified geometric segments are not connected.
Action: Check the start/end points of the given geometric segments.
ORA-13335: LRS measure information not defined
Cause: The measure information of a geometric segment was not assigned (IS NULL).
Action: Assign/define the measure information. An LRS geometric segment is defined if its start and end measure are assigned (non-null).
ORA-13336: failure in converting standard diminfo/geometry to LRS dim/geom
Cause: There is no room for the measure dimension in the given diminfo, or the specified standard geometry is not a point a line string.
Action: Check if the diminfo dimensions are less than 3 or if the geometry type is point or line string.
ORA-13337: failure in concatenating LRS polygons
Cause: LRS concatenation involving LRS polygons is not supported.
Action: Check the geometry and element types to make sure the concatenate operation is not called with a polygon type.
ORA-13338: failure in reversing LRS polygon/collection geometry
Cause: Reversing an LRS polygon/collection geometry produces an invalid geometry.
Action: Check the geometry type to make sure this operation is called on non-polygon geometries.
ORA-13339: LRS polygon clipping across multiple rings
Cause: Clipping (dynseg) a polygon across multiple rings is not allowed.
Action: Polygon clipping is allowed only for a single ring.
ORA-13340: a point geometry has more than one coordinate
Cause: A geometry, specified as being a point, has more than one coordinate in its definition.
Action: A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon, set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, remove the extraneous coordinates from its definition.
ORA-13341: a line geometry has fewer than two coordinates
Cause: A geometry, specified as being a line, has fewer than two coordinates in its definition.
Action: A line must consist of at least two distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13342: an arc geometry has fewer than three coordinates
Cause: A geometry, specified as being an arc, has fewer than three coordinates in its definition.
Action: An arc must consist of at least three distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13343: a polygon geometry has fewer than four coordinates
Cause: A geometry, specified as being a polygon, has fewer than four coordinates in its definition.
Action: A polygon must consist of at least four distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13344: an arcpolygon geometry has fewer than five coordinates
Cause: A geometry, specified as being an arcpolygon, has fewer than five coordinates in its definition.
Action: An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13345: a compound polygon geometry has fewer than five coordinates
Cause: A geometry, specified as being a compound polygon, has fewer than five coordinates in its definition.
Action: A compound polygon must contain at least five coordinates. A compound polygon consists of at least one arc and one line, each of which must be described using three and at least two distinct coordinates respectively. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13346: the coordinates defining an arc are collinear
Cause: Invalid definition of an arc. An arc is defined using three non-collinear coordinates.
Action: Alter the definition of the arc, or set the SDO_ETYPE or SDO_GTYPE to the line type.
ORA-13347: the coordinates defining an arc are not distinct
Cause: Two or more of the three points defining an arc are the same.
Action: Alter the definition of the arc to ensure that three distinct coordinate values are used.
ORA-13348: polygon boundary is not closed
Cause: The boundary of a polygon does not close.
Action: Alter the coordinate values or the definition of the SDO_GTYPE or SDO_ETYPE attribute of the geometry.
ORA-13349: polygon boundary crosses itself
Cause: The boundary of a polygon intersects itself.
Action: Correct the geometric definition of the object.
ORA-13350: two or more rings of a complex polygon touch
Cause: The inner or outer rings of a complex polygon touch.
Action: All rings of a complex polygon must be disjoint. Correct the geometric definition of the object.
ORA-13351: two or more rings of a complex polygon overlap
Cause: The inner or outer rings of a complex polygon overlap.
Action: All rings of a complex polygon must be disjoint. Correct the geometric definition of the object.
ORA-13352: the coordinates do not describe a circle
Cause: The set of coordinates used to describe a circle are incorrect.
Action: Confirm that the set of coordinates actually represent points on the circumference of a circle.
ORA-13353: ELEM_INFO_ARRAY not grouped in threes
Cause: The ELEM_INFO_ARRAY in an SDO_GEOMETRY definition has more or fewer elements than expected.
Action: Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by 3.
ORA-13354: incorrect offset in ELEM_INFO_ARRAY
Cause: The offset field in ELEM_INFO_ARRAY of an SDO_GEOMETRY definition references an invalid array subscript in SDO_ORDINATE_ARRAY.
Action: Confirm that the offset is a valid array subscript in SDO_ORDINATE_ARRAY.
ORA-13355: SDO_ORDINATE_ARRAY not grouped by number of dimensions specified
Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user.
Action: Confirm that the number of dimensions is consistent with data representation in SDO_ORDINATE_ARRAY.
ORA-13356: adjacent points in a geometry are redundant
Cause: There are repeated points in the sequence of coordinates.
Action: Remove the redundant point.
ORA-13357: extent type does not contain 2 points
Cause: Extent type should be represented by two points: lower left and upper right.
Action: Confirm that there are only two points for an extent type.
ORA-13358: circle type does not contain 3 points
Cause: Circle type should be represented by three distinct points on the circumference.
Action: Confirm that there are only three points for a circle type.
ORA-13359: extent does not have an area
Cause: The two points representing the extent are identical.
Action: Confirm that the two points describing the extent type are distinct.
ORA-13360: invalid subtype in a compound type
Cause: This subtype is not allowed within the ETYPE specified.
Action: Check the Oracle Spatial documentation for type definitions.
ORA-13361: not enough sub-elements within a compound ETYPE
Cause: The compound type declare more sub-elements than actually defined.
Action: Confirm that the number of sub-elements is consistent with the compound type declaration.
ORA-13362: disjoint sub-element in a compound polygon
Cause: Compound polygon must describe an enclosed area.
Action: Confirm that all sub-elements are connected.
ORA-13363: no valid ETYPE in the geometry
Cause: None of the ETYPEs within the geometry is supported.
Action: Confirm that there is at least one valid ETYPE.
ORA-13364: layer dimensionality does not match geometry dimensions
Cause: The spatial layer has a geometry with a different dimensions than the dimensions specified for the layer.
Action: Make sure that all geometries in a layer have the same dimensions and that they match the dimensions in the SDO_DIM_ARRAY object for the layer in the USER_SDO_GEOM_METADATA view.
ORA-13365: layer SRID does not match geometry SRID
Cause: The spatial layer has a geometry with a different SRID than the SRID specified for the layer.
Action: Make sure that all geometries in a layer have the same SRID and that the SRIDs match the SRID for the layer in the USER_SDO_GEOM_METADATA view.
ORA-13366: invalid combination of interior exterior rings
Cause: In an Oracle Spatial geometry, interior and exterior rings are not used consistently.
Action: Make sure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array.
ORA-13367: wrong orientation for interior/exterior rings
Cause: In an Oracle Spatial geometry, the exterior and/or interior rings are not oriented correctly.
Action: Be sure that the exterior rings are oriented counterclockwise and the interior rings are oriented clockwise.
ORA-13368: simple polygon type has more than one exterior ring
Cause: In a polygon geometry there is more than one exterior ring.
Action: Set the type to be multipolygon if more than one exterior ring is present in the geometry.
ORA-13369: invalid value for etype in the 4-digit format
Cause: A 4-digit etype for a non-polygon type element is used, or the orientation is not a valid orientation for interior/exterior rings of the polygon.
Action: Correct the geometry definition.
ORA-13370: failure in applying 3D LRS functions
Cause: Only non-geodetic 3D line string geometries (made of line segments) are supported for 3D LRS functions.
Action: Check the geometry and element types and the SRID values.
ORA-13371: invalid position of measure dimension
Cause: LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in the dim_info_array.
Action: Check the geometry’s gtype and its position in the dim_info_array.
ORA-13372: failure in modifying metadata for a table with spatial index
Cause: Modifying the metadata after the index is created will cause an inconsistency between the geometry’s gtype and diminfo.
Action: Modify (or Prepare) metadata before creating an index on the SDO_GEOMETRY column.
ORA-13373: invalid line segment in geodetic data
Cause: A geodetic line segment was not less than half of a great circle.
Action: Densify the line by adding points.
ORA-13374: SDO_MBR not supported for geodetic data
Cause: The SDO_MBR functionality is not supported for geodetic data.
Action: Find an alternative function that can be used in this context.
ORA-13375: the layer is of type [string] while geometry inserted has type [string]
Cause: The layer has a type that is different or inconsistent with the type of the current geometry.
Action: Change the geometry type to agree with the layer type, or change the layer type to agree with the geometry type.
ORA-13376: invalid type name specified for layer_gtype parameter
Cause: An invalid type name is specified for the layer_gtype constraint.
Action: See the Spatial documentation for of valid keywords that can be used in defining a layer_gtype constraint.
ORA-13377: invalid combination of elements with orientation
Cause: An element of the geometry has orientation specified while some other element has no orientation specified (4-digit etype).
Action: Make sure all the polygon elements have orientation specified using the 4-digit etype notation.
ORA-13378: invalid index for element to be extracted
Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the geometry.
ORA-13379: invalid index for sub-element to be extracted
Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the geometry.
ORA-13380: network not found
Cause: The specified network was not found in the network metadata.
Action: Insert the network information in the USER_SDO_NETWORK_METADATA view.
ORA-13381: table:string not found in network:string
Cause: The specified table was not found in the network metadata.
Action: Insert the table information in the USER_SDO_NETWORK_METADATA view.
ORA-13382: geometry metadata (table:string column:string) not found in spatial network:string
Cause: The specified geometry metadata was not found in the spatial network metadata.
Action: Insert the spatial metadata information in the USER_SDO_NETWORK_METADATA view.
ORA-13383: inconsistent network metadata: string
Cause: There was an inconsistency between the network metadata and the node/link information.
Action: Check the network metadata and the node/link information.
ORA-13384: error in network schema: string
Cause: The network table(s) did not have required column(s)
Action: Check the network schema.
ORA-13385: error in network manager: [string]
Cause: There was an internal error in network manager.
Action: Contact Oracle Customer Support for more help.
ORA-13386: commit/rollback operation error: [string]
Cause: The index-level changes were not fully incorporated as part of the commit or rollback operation.
Action: Correct the specified error and use the following statement: ALTER INDEX <index-name> PARAMETERS (‘index_status=synchronize’);
ORA-13387: sdo_batch_size for array inserts should be in the range [number,number]
Cause: The specified value for sdo_batch_size was too high or too low.
Action: Change the value to be in the specified range.
ORA-13388: invalid value for dst_spec parameter
Cause: The dst_spec parameter was specified in the wrong format.
Action: Check the documentation for this parameter.
ORA-13389: unable to compute buffers or intersections in analysis function
Cause: There was an internal error in computing the buffers or intersections in the specified spatial analysis function.
Action: Modify the tolerance value in the USER_SDO_GEOM_METADATA view before invoking the spatial analysis function.
ORA-13390: error in spatial analysis and mining function: [string]
Cause: There was an internal error in the specified analysis function.
Action: Contact Oracle Customer Support for more help.
ORA-13391: string
Cause: An attempt was made to violate GeoRaster management restrictions.
Action: Check the documentation for more detailed information.
ORA-13393: null or invalid string parameter
Cause: The operation failed because the input parameter was null or invalid.
Action: Correct the parameter and try again.
ORA-13400: duplicate entry for string in USER_SDO_GEOR_SYSDATA view
Cause: The current operation caused a duplicate RASTER_DATA_TABLE and RASTER_ID combination to be inserted into the USER_SDO_GEOR_SYSDATA view.
Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID combination to be inserted into the USER_SDO_GEOR_SYSDATA view is unique.

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.