ORA-13005: recursive HHCODE function error
Cause:
An error occurred in a recursively called HHCODE function.
Action:
This is an internal error. Contact Oracle Support Services.
ORA-13006: the specified cell number is invalid
Cause:
The cell identifier is either less than 0 or greater than (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-F a-f] was detected.
Action:
Verify that all characters in a string are in [0-9] or [A-F a-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 specified 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 specified
Cause:
An invalid window type was specified.
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: specified topology [string] is
invalid
Cause:
The specified topology did not exist in the database, or some components of the
topology were missing from the database.
Action:
Check the specified topology by executing the SDO_TOPO.validate_topology
function.
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 Support Services.
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:
Redefine vertex coordinates within specified boundaries.
ORA-13020: coordinate is NULL
Cause:
A vertex coordinate has a NULL value.
Action:
Redefine vertex coordinate to have non-NULL value.
ORA-13021: element not continuous
Cause:
The coordinates defining a geometric element are not connected.
Action:
Redefine coordinates for the geometric element.
ORA-13022: polygon crosses itself
Cause:
The coordinates defining a polygonal geometric element represent crossing
segments.
Action:
Redefine 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:
Redefine 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:
Redefine the coordinates for the polygon.
ORA-13025: polygon does not close
Cause:
The coordinates defining a polygonal geometric element represent an open
polygon.
Action:
Redefine the coordinates of the polygon.
ORA-13026: unknown element type for element string.string.string
Cause:
The SDO_ETYPE column in the <layer>_SDOGEOM table contains an invalid
geometric element type value.
Action:
Redefine 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 documentation for an explanation of SDO_ETYPE and its
possible values.
ORA-13027: unable to read dimension definition from
string
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-13028: Invalid Gtype in the SDO_GEOMETRY object
Cause:
There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
Action:
Verify that the geometries have valid gtypes.
ORA-13029: Invalid SRID in the SDO_GEOMETRY object
Cause:
There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may
be outside the valid SRID range.
Action:
Verify that the geometries have valid SRIDs.
ORA-13030: Invalid dimension for the SDO_GEOMETRY
object
Cause:
There is a mismatch between the dimension in the SDO_GTYPE and dimension in the
SDO_GEOM_METADATA for the SDO_GEOMETRY object.
Action:
Verify that the geometries have valid dimensionality.
ORA-13031: Invalid Gtype in the SDO_GEOMETRY object
for point object
Cause:
There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the VARRAYs are
NULL but the SDO_GTYPE is not of type POINT.
Action:
Verify that the geometries have valid gtypes.
ORA-13032: Invalid NULL SDO_GEOMETRY object
Cause:
There are invalid SDO_POINT_TYPE or SDO_ELEM_INFO_ARRAY or SDO_ORDINATE_ARRAY
fields in the SDO_GEOMETRY object.
Action:
Verify that the geometries have valid fields. To specify a NULL geometry,
specify the whole SDO_GEOMETRY as NULL instead of setting each field to NULL.
ORA-13033: Invalid data in the SDO_ELEM_INFO_ARRAY
in SDO_GEOMETRY object
Cause:
There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY
object. The triplets in this field do not make up a valid geometry.
Action:
Verify that the geometries have valid data.
ORA-13034: Invalid data in the SDO_ORDINATE_ARRAY
in SDO_GEOMETRY object
Cause:
There is invalid data in the SDO_ORDINATE_ARRAY field of the SDO_GEOMETRY
object. The coordinates in this field do not make up a valid geometry. There
may be NULL values for X or Y or both.
Action:
Verify that the geometries have valid data.
ORA-13035: Invalid data (arcs in geodetic data) in
the SDO_GEOMETRY object
Cause:
There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY
object. There are arcs in a geometry that has geodetic coordinates.
Action:
Verify that the geometries have valid data.
ORA-13036: Operation [string] not supported
for Point Data
Cause:
The specified geometry function is not supported for point data.
Action:
Make sure that the specified geometry function is not called on point data.
ORA-13037: SRIDs do not match for the two
geometries
Cause:
A Spatial operation is invoked with two geometries where one geometry has an
SRID and the other geometry does not have an SRID.
Action:
Make sure that the spatial operations are invoked between two geometries with
compatible SRIDs.
ORA-13039: failed to update spatial index for
element string.string.string
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-13040: failed to subdivide tile
Cause:
This is an internal error.
Action:
Note any accompanying errors and contact Oracle Support Services.
ORA-13041: failed to compare tile with element string.string.string
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_WITH_CONTEXT procedure. If the procedure does not return any
errors, note any errors that accompany
ORA-13041
and contact Oracle Support Services.
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 documentation. Then retry the operation.
ORA-13043: failed to read metadata from the
<layer>_SDOLAYER table
Cause:
An error was encountered reading the layer metadata 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 Support Services.
ORA-13044: the specified tile size is smaller than
the tolerance
Cause:
The tile size specified for fixed size tessellation is smaller than the
tolerance as specified in the layer metadata.
Action:
See the Oracle Spatial documentation 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 smaller tile size value than the current one.
ORA-13045: invalid compatibility flag
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13046: invalid number of arguments
Cause:
An invalid number of arguments were specified for an SDO_GEOM function.
Action:
See the Oracle Spatial 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 Support Services.
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 Support Services.
ORA-13051: failed to initialize spatial object
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13052: unsupported geometric type for geometry string.string
Cause:
The geometry type for a specific instance in a <layer>_SDOGEOM table is
not among the set of geometry types supported by Oracle Spatial.
Action:
Check the Oracle Spatial documentation 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 documentation 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 Support Services.
ORA-13055: Oracle object string 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-13060: topology with the name string
already exists
Cause:
The specified topology name was not unique in the database.
Action:
Verify that the CREATE_TOPOLOGY call specifies the correct topology name and
that the procedure is invoked from the correct schema.
ORA-13061: topology with the name string
does not exist
Cause:
The specified topology did not exist in the database.
Action:
Verify that the current procedure/function call specifies the correct schema
and topology name.
ORA-13062: topology IDs do not match in the feature
table and the topology
Cause:
The specified topology ID in the feature table did not match the topology ID
stored in the topology metadata.
Action:
Verify that the specified topology ID matches the topology ID stored in the
topology metadata.
ORA-13063: relationship information table is
missing data for feature table [string]
Cause:
The topology relationship information table (xxx_RELATION$) did not have the
matching partition corresponding to the feature table.
Action:
Make sure the correct topology IDs and names are specified in the call to
register the feature table with the topology.
ORA-13064: relationship information table has
inconsistent data for feature table [string]
Cause:
The topology_id, tg_layer_id values stored in the feature table did not match
the values stored in the topology relationship information table
(xxx_RELATION$).
Action:
Make sure that the correct feature tables are specified in the call to register
the feature table with the topology.
ORA-13065: cannot delete a child layer with a
parent layer
Cause:
A call was made to delete a feature layer which has a dependent layer defined
on it.
Action:
Make sure that all dependent feature layers are deleted before deleting the
current feature layer.
ORA-13066: wrong feature geometry or element type
Cause:
The SDO_TOPO_GEOMETRY object had the wrong geometry and/or element type.
Action:
Correct the geometry and/or element type in the SDO_TOPO_GEOMETRY object.
ORA-13067: operator requires both parameters from
the same topology
Cause:
Both SDO_TOPO_GEOMETRY parameters did not come from the same topology.
Action:
Make sure both the parameters to the operator are from the same topology. If
this is not possible, consider using a signature of the operator that does not
use two SDO_TOPO_GEOMETRY parameters.
ORA-13068: wrong table or column name in
SDO_TOPO_GEOMETRY constructor
Cause:
An SDO_TOPO_GEOMETRY constructor was invoked with incorrect parameters for
table name and/or column name.
Action:
Fix the parameters in the call and try again.
ORA-13108: spatial table string not found
Cause:
The specified spatial table does not exist.
Action:
Check the Spatial data dictionary to make sure that the table is registered.
ORA-13109: spatial table string exists
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.
ORA-13110: cannot drop topology with associated
topo_geometry tables
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.
ORA-13111: cannot add topo_geometry layer [string]
to topology
Cause:
It was not possible to add the specified topo_geometry layer to the topology.
Action:
Make sure the topo_geometry layer table exists in the database.
ORA-13112: cannot delete topo_geometry layer [string]
from topology
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.
ORA-13113: invalid tg_layer_id in sdo_topo_geometry
constructor
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.
ORA-13114: [string]_NODE$ table does not
exist
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.
ORA-13115: [string]_EDGE$ table does not
exist
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.
ORA-13116: [string]_FACE$ table does not
exist
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.
ORA-13117: [string]_RELATION$ table does not
exist
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.
ORA-13118: invalid node_id [string]
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.
ORA-13119: invalid edge_id [string]
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.
ORA-13120: invalid face_id [string]
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.
ORA-13121: layer type type mismatch with
topo_geometry layer type
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.
ORA-13122: invalid topo_geometry specified
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.
ORA-13123: invalid <TOPOLOGY> name specified
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.
ORA-13124: unable to determine column id for column
string
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
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 string
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13127: failed to generate target partition
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13128: current tiling level exceeds user
specified tiling level
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13129: HHCODE column string 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 dictionary.
ORA-13135: failed to alter spatial table
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13136: null common code generated
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13137: failed to generate tablespace sequence
number
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13138: could not determine name of object string
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13139: could not obtain column definition for string
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13140: invalid target type
Cause:
The specified target type is not valid.
Action:
Substitute a valid target type. Valid target types are TABLE and 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 string not found
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13145: failed to generate range list
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13146: could not find table substitution
variable string
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.
ORA-13147: failed to generate MBR
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13148: failed to generate SQL filter
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
ORA-13149: failed to generate next sequence number
for spatial table string
Cause:
This is an internal error.
Action:
Contact Oracle Support Services.
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 remove a record from 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 high water mark must be greater than or equal to zero.
Action:
Make sure that the high water 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 string.string
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 ORAstring
encountered while string
Cause:
The specified Oracle error was encountered.
Action:
Correct the Oracle error.
ORA-13158: Oracle object string does not
exist
Cause:
The specified object does not exist.
Action:
Verify that the specified object exists.
ORA-13159: Oracle table string already
exists
Cause:
The specified table already exists.
Action:
Drop the specified table.
ORA-13181: unable to determine length of column string_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 string.string.string
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 string.string
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 Support
Services.
ORA-13185: failed to generate initial HHCODE
Cause:
This is an internal error.
Action:
Record the error messages that are returned and contact Oracle Support
Services.
ORA-13186: fixed tile size tessellation failed
Cause:
This is an internal error.
Action:
Record the error messages that are returned and contact Oracle Support
Services.
ORA-13187: subdivision failed
Cause:
This is an internal error.
Action:
Record the error messages that are returned and contact Oracle Support
Services.
ORA-13188: cell decode failed
Cause:
This is an internal error.
Action:
Record the error messages that are returned and contact Oracle Support
Services.
ORA-13189: recursive SQL parse failed
Cause:
This is an internal error.
Action:
Record the error messages that are returned and contact Oracle Support
Services.
No hay comentarios:
Publicar un comentario