Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 13000-13199: Spatial Data Option Messages

This section lists some of the messages that can be returned when the Spatial Data option is enabled.

##### ORA-13000: dimension number is out of range

Cause: The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.

Action: Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.

##### ORA-13001: dimensions mismatch error

Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match.

Action: Make sure that the number of dimensions in the HHCODEs match.

##### ORA-13002: specified level is out of range

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.

##### ORA-13003: the specified range for a dimension is invalid

Cause: The specifed range for a dimension is invalid.

Action: Make sure that the lower bound (lb) is less than the upper bound (ub).

##### ORA-13004: the specified buffer size is invalid

Cause: The buffer size for a function is not valid.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-13005: recursive HHCODE function error

Cause: An error occured in a recursively called HHCODE function.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-13006: the specified cell number is invalid

Cause: The cell identifier is either less than 0 or greater that (2^ndim - 1).

Action: Make sure that the cell identifier is between 0 and (2^ndim - 1).

##### ORA-13007: an invalid HEX character was detected

Cause: A character that is not in the range [0-9] or [A-Fa-f] was detected.

Action: Verify that all characters in a string are in [0-9] or [A-Fa-f].

##### ORA-13008: the specified date format has an invalid component

Cause: Part of specified date format is invalid.

Action: Verify that the date format is valid.

##### ORA-13009: the specified date string is invalid

Cause: The specified date string has a bad component or does not match the specified format string.

Action: Make sure that the components of the date string are valid and that the date and format strings match.

##### ORA-13010: an invalid number of arguments has been specified

Cause: An invalid number of arguments was specified for an SDO function.

Action: Verify the syntax of the function call.

##### ORA-13011: value is out of range

Cause: A specifed dimension value is outside the range defined for that dimension.

Action: Make sure that all values to be encoded are within the defined dimension range.

##### ORA-13012: an invalid window type was specifed

Cause: An invalid window type was specifed.

Action: Valid window types are RANGE, PROXIMITY, POLYGON.

##### ORA-13013: the specified topology was not INTERIOR or BOUNDARY

Cause: A topology was specified that was not INTERIOR or BOUNDARY.

Action: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE's topology.

##### ORA-13014: a topology identifier outside the range of 1 to 8 was specified

Cause: A topology identifier outside the range of 1 to 8 was specified

Action: Specify a topology in the range of 1 to 8.

##### ORA-13015: the window definition is not valid

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.

##### ORA-13016: bad partition definition

Cause: The partition common code was not correctly decoded.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-13017: unrecognized line partition shape

Cause: The shape of a 2-D line partition could not be determined.

Action: This is an internal error. Contact Oracle Worldwide Support.

##### ORA-13018: bad distance type

Cause: The specified distance type is invalid.

Action: The only supported distance functions are EUCLID and MANHATTAN.

##### ORA-13019: coordinates out of bounds

Cause: Vertex coordinates lie outside the valid range for specified dimension

Action: Re-define vertex coordinates within specified boundaries

##### ORA-13020: coordinate is NULL

Cause: A vertex coordinate has a NULL value

Action: Re-define vertex coordinate to have non-NULL value

##### ORA-13021: element not continuous

Cause: The coordinates defining a geometric element are not connected

Action: Re-define coordinates for the geometric element

##### ORA-13022: polygon crosses itself

Cause: The coordinates defining a polygonal geometric element represent crossing segments

Action: Re-define coordinates for the polygon

##### ORA-13023: interior element interacts with exterior element

Cause: An interior element of a geometric object interacts with the exterior element of that object

Action: Re-define coordinates for the geometric elements

##### ORA-13024: polygon has less than three segments

Cause: The coordinates defining a polygonal geometric element represent less than three segments

Action: Re-define the coordinates for the polygon

##### ORA-13025: polygon does not close

Cause: The coordinates defining a polygonal geometric element represents an open polygon

Action: Re-define the coordinates of the polygon

##### ORA-13026: unknown element type for element <layer>_SDOGEOM.SpatialObjectID.Element_Number

Cause: The SDO_ETYPE column in the <layer>_SDOGEOM table contains an invalid geometric element type value

Action: Re-define 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 Cartridge user's guide for an explanation of SDO_ETYPE and its possible values.

##### ORA-13027: unable to read dimension definition from <layer>_SDODMIN

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.

##### ORA-13039: failed to update spatial index for element <layer>_SDOGEOM.SpatialObjectID.Element_Number

Cause: Another error will accompany this message that will indicate the problem.

Action: Correct any accompanying errors. If no accompanying error message appears then contact Oracle Worldwide Support.

##### ORA-13040: failed to subdivide tile

Cause: This is an internal error.

Action: Note any accompanying errors and contact Oracle Worldwide Support.

##### ORA-13041: failed to compare tile with element <layer>_SDOGEOM.SpatialObjectID.Element_Number

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 procedure. If the procedure does not return any errors then note any errors which accompany ORA-13041 and contact Oracle Worldwide Support.

##### ORA-13042: invalid SDO_LEVEL and SDO_NUMTILES combination

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 Cartridge user's guide. Then retry the operation.

##### ORA-13043: failed to read meta data from the <layer>_SDOLAYER table

Cause: An error was encountered reading the layer meta data 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 Worldwide Support.

##### ORA-13044: the specified tile size exceeds the maximum resolution

Cause: The tile size specified for fixed size tessellation exceeds the maximum resolution as computed from the layer meta data.

Action: See the Oracle Spatial Cartridge user's guide 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 lesser tile size value than the current one.

##### ORA-13045: invalid compatibility flag

Cause: This is an internal error.

Action: Contact Oracle Worldwide support.

##### ORA-13046: invalid number of arguments

Cause: An invalid number of arguments were specified for an SDO_GEOM function.

Action: Please refer to the Oracle Spatial Cartridge user documentation for a description of the syntax and semantics of the relevant SDO_GEOM function.

##### ORA-13047: unable to determine ordinate count from table <layer>_SDOLAYER

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.

##### ORA-13048: recursive SQL fetch error

Cause: This is an internal error.

Action: Contact Oracle Worldwide Support.

##### ORA-13049: unable to determine tolerance value from table <layer>_SDODIM

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.

##### ORA-13050: unable to construct spatial object

Cause: This is an internal error.

Action: Contact Oracle Worldwide Support.

##### ORA-13051: failed to initialize spatial object

Cause: This is an internal error.

Action: Contact Oracle Worldwide Support.

##### ORA-13052: unsupported geometric type for geometry <layer>_SDOGEOM.SpatialObjectID

Cause: The geometry type for a specific instance in a <layer>_SDOGEOM table is not among the set of geometry types supported by the Oracle Spatial Cartridge.

Action: Check the Oracle Spatial Cartridge user guide for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema.

##### ORA-13053: maximum number of geometric elements in argument list exceeded

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 Cartridge user guide 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.

##### ORA-13054: recursive SQL parse error

Cause: This is an internal error.

Action: Contact Oracle Worldwide Support.

##### ORA-13055: Oracle object text does not exist in specified table

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.

##### ORA-13108: spatial table name not found

Cause: The specified spatial table does not exist.

Action: Check the Spatial Data option data dictionary to make sure that the table is registered.

##### ORA-13109: spatial table name exists

Cause: The specified spatial table is registered in the Spatial Data data dictionary.

Action: Remove the existing table from the Spatial Data option data dictionary or use a different name.

##### ORA-13110: spatial table name is not partitioned

Cause: The specified spatial table is not partitioned.

Action: Check the Spatial Data option data dictionary and make sure that a high water mark is set.

##### ORA-13111: spatial table name has no partition key defined

Cause: The specified spatial table does not have a partition key defined.

Action: Check the Spatial Data option data dictionary and make sure that the table is partitioned.

##### ORA-13112: invalid count mode name

Cause: The specified count mode is not valid.

Action: Alter the count mode. Valid count modes are ESTIMATE or EXACT.

##### ORA-13113: Oracle table name does not exist

Cause: The specified Oracle table does not exist.

Action: Check the Oracle7 data dictionary and make sure that the table exists.

##### ORA-13114: tablespace name not found

Cause: The specified tablespace does not exist.

Action: Check the Oracle7 data dictionary and make sure that the specified tablespace exists and that there is a space quota defined on it.

##### ORA-13115: tablespace name is already allocated

Cause: The specified tablespace is already allocated to the spatial table.

Action: Allocate another tablespace name to the table.

##### ORA-13116: tablespace name is not allocated to table name

Cause: The specified tablespace is not allocated to the specified spatial table.

Action: Allocate the tablespace to the spatial table.

##### ORA-13117: partition name not found

Cause: The specified partition does not exist.

Action: Verify the name of the partition by checking the Spatial Data option data dictionary.

##### ORA-13119: source and target tablespaces are identical

Cause: Identical source and target tablespaces were specified when trying to move partition.

Action: Specify different source and target tablespaces if you wish to move a partition.

##### ORA-13121: failed to create child partition

Cause: The creation of a child partition failed.

Action: Check for other errors that accompany this error and correct them first.

##### ORA-13122: child partition name not found

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13123: column name is already defined

Cause: The specified column is already defined for the spatial table.

Action: Use a different column name.

##### ORA-13124: unable to determine column id for column name

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13125: partition key is already set

Cause: A partition key is already set for the spatial table.

Action: Only one partition key can be specified per spatial table.

##### ORA-13126: unable to determine class for spatial table name

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13127: failed to generate target partition

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13128: current tiling level exceeds user specified tiling level

Cause: This is an internal error.

Action: Contact World Wide Support.

##### ORA-13129: HHCODE column name not found

Cause: The specified spatial column does not exist.

Action: Verify that the specified column is a spatial column by checking the Spatial Data option data dictionary.

##### ORA-13135: failed to alter spatial table

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13136: null common code generated

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13137: failed to generate tablespace sequence number

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13138: could not determine name of object name

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13139: could not obtain column definition for name

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13140: invalid target type

Cause: The specified target type is not valid.

Action: Substitute a valid target type. Valid target types are TABLE or VIEW.

##### ORA-13141: invalid RANGE window definition

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.

##### ORA-13142: invalid PROXIMITY window definition

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.

##### ORA-13143: invalid POLYGON window definition

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.

##### ORA-13144: target table name not found

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13145: failed to generate range list

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13146: could not find table substitution variable name

Cause: The partition name substitution variable name was not found in the SQL filter.

Action: The substitution variable name must be in the SQL filter to indicate where that partition name should be placed.

##### ORA-13147: failed to generate MBR

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13148: failed to generate SQL filter

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13149: failed to generate next sequence number for spatial table name

Cause: This is an internal error.

Action: Document messages and contact Oracle Worldwide Support.

##### ORA-13150: failed to insert exception record

Cause: Operation failed to insert a record into the exception table

Action: Fix any other errors reported.

##### ORA-13151: failed to remove exception record

Cause: Operation failed to insert a record into the exception table.

Action: Fix any other errors reported.

##### ORA-13152: invalid HHCODE type

Cause: Specified HHCODE type is not valid.

Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.

##### ORA-13153: invalid high water mark specified

Cause: The highwater mark must be greater than or equal to zero.

Action: Make sure that the highwater mark is an integer greater than or equal to zero.

##### ORA-13154: invalid precision specified

Cause: The precision specified is out of range.

Action: The precision must be an integer greater than or equal to zero.

##### ORA-13155: invalid number of dimensions specified

Cause: The number of dimensions specified is out of range.

Action: The number of dimension must be between 1 and 32.

##### ORA-13156: table to be registered name.name is not empty

Cause: The specified table has rows in it.

Action: Make sure that the table to be registered is empty.

##### ORA-13157: Oracle error ORA-nnnnn encountered while name

Cause: Specified Oracle error was encountered.

Action: Correct the Oracle error.

##### ORA-13158: Oracle object name does not exist

Cause: The specified object does not exist.

Action: Verify that the specified object exists.

##### ORA-13159: Oracle table name already exists

Cause: The specified table already exists.

Action: Drop the specified table.

##### ORA-13181: unable to determine length of column num_SDOINDEX.SDO_CODE

Cause: The length of the SDO_CODE column in the <layer>_SDOINDEX table could not be determined.

Action: Make sure that the <layer>_SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Then retry the operation.

##### ORA-13182: failed to read element <layer>_SDOGEOM.SpatialObjectID.Element_Number

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.

##### ORA-13183: unsupported geometric type for geometry <layer>_SDOGEOM.SpatialObjectID

Cause: The geometry type in the <layer>_SDOGEOM table is unsupported.

Action: Modify the geometry type to be one of the supported types.

##### ORA-13184: failed to initialize tessellation package

Cause: Initialization of the tessellation package failed.

Action: Record the error messages that are returned and contact Oracle Worldwide Support.

##### ORA-13185: failed to generate initial HHCODE

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Worldwide Support.

##### ORA-13186: fixed tile size tessellation failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Worldwide Support.

##### ORA-13187: subdivision failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Worldwide Support.

##### ORA-13188: cell decode failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Worldwide Support.

##### ORA-13189: recursive SQL parse failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Worldwide Support.

##### ORA-13190: recursive SQL fetch failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Worldwide Support.

##### ORA-13191: failed to read SDO_ORDCNT value

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Worldwide Support.

##### ORA-13192: failed to read number or element rows

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Worldwide Support.

##### ORA-13193: failed to allocate space for geometry

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 Worldwide Support.

##### ORA-13194: failed to decode supercell

Cause: This is an internal error.

Action: Contact Oracle Worldwide Support.

##### ORA-13195: failed to generate maximum tile value

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Worldwide Support.

##### ORA-13196: failed to compute supercell for element <layer>_SDOGEOM.SpatialObjectID.Element_Number

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.

##### ORA-13197: element <layer>_SDOGEOM.SpatialObjectID.Element_Number is out of range

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.

##### ORA-13199: text

Cause: This is an internal error.

Action: Contact Oracle Worldwide Support.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index