ORA-13136: null common code generated
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Monday, 5 March 2012
ORA-13135: failed to alter spatial table
ORA-13135: failed to alter spatial table
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13129: HHCODE column string not found
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.
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-13128: current tiling level exceeds user specified tiling level
ORA-13128: current tiling level exceeds user specified tiling level
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13127: failed to generate target partition
ORA-13127: failed to generate target partition
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13126: unable to determine class for spatial table string
ORA-13126: unable to determine class for spatial table string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13125: partition key is already set
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.
Cause: A partition key is already set for the spatial table.
Action: Only one partition key can be specified per spatial table.
ORA-13124: unable to determine column id for column string
ORA-13124: unable to determine column id for column string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13123: invalid lamp;lt;lamp;nbsp;TOPOLOGYlamp;gt; name specified
ORA-13123: invalid lamp;lt;lamp;nbsp;TOPOLOGYlamp;gt; 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.
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-13122: invalid topo_geometry specified
ORA-13122: invalid topo_geometry specified
Cause: The SDO_TOPO_GEOMETRY object passed into the function or operator was not valid.
Action: Check the SDO_TOPO_GEOMETRY object and verify that it is a valid topo_geometry object.
Cause: The SDO_TOPO_GEOMETRY object passed into the function or operator was not valid.
Action: Check the SDO_TOPO_GEOMETRY object and verify that it is a valid topo_geometry object.
ORA-13121: layer type type mismatch with topo_geometry layer type
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.
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-13120: invalid face_id (string(
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.
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-13119: invalid edge_id (string(
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.
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-13118: invalid node_id (string(
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.
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-13117: (string(_RELATION$ table does not exist
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.
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-13116: (string(_FACE$ table does not exist
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.
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-13115: (string(_EDGE$ table does not exist
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.
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-13114: (string(_NODE$ table does not exist
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.
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-13113: invalid tg_layer_id in sdo_topo_geometry constructor
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.
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-13112: cannot delete topo_geometry layer (string( from topology
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.
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-13111: cannot add topo_geometry layer (string( to 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.
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-13110: cannot drop topology with associated topo_geometry tables
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.
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-13109: spatial table string exists
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.
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-13108: spatial table string not found
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.
Cause: The specified spatial table does not exist.
Action: Check the Spatial data dictionary to make sure that the table is registered.
ORA-13068: wrong table or column name in SDO_TOPO_GEOMETRY constructor
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 or column name.
Action: Fix the parameters in the call and try again.
Cause: An SDO_TOPO_GEOMETRY constructor was invoked with incorrect parameters for table name and or or column name.
Action: Fix the parameters in the call and try again.
ORA-13067: operator requires both parameters from the same topology
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.
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-13066: wrong feature geometry or element type
ORA-13066: wrong feature geometry or element type
Cause: The SDO_TOPO_GEOMETRY object had the wrong geometry and or or element type.
Action: Correct the geometry and or or element type in the SDO_TOPO_ GEOMETRY object.
Cause: The SDO_TOPO_GEOMETRY object had the wrong geometry and or or element type.
Action: Correct the geometry and or or element type in the SDO_TOPO_ GEOMETRY object.
ORA-13065: cannot delete a child layer with a parent layer
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.
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-13064: relationship information table has inconsistent data for feature table (string(
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.
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-13063: relationship information table is missing data for feature table (string(
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.
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-13062: topology IDs do not match in the feature table and the topology
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.
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-13061: topology with the name string does not exist
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 or function call specifies the correct schema and topology name.
Cause: The specified topology did not exist in the database.
Action: Verify that the current procedure or function call specifies the correct schema and topology name.
ORA-13060: topology with the name string already exists
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.
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-13055: Oracle object string does not exist in specified table
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.
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-13054: recursive SQL parse error
ORA-13054: recursive SQL parse error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13053: maximum number of geometric elements in argument list exceeded
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.
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-13052: unsupported geometric type for geometry string.string
ORA-13052: unsupported geometric type for geometry string.string
Cause: The geometry type for a specific instance in a lamp;lt;lamp;nbsp;layerlamp;gt;_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.
Cause: The geometry type for a specific instance in a lamp;lt;lamp;nbsp;layerlamp;gt;_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-13051: failed to initialize spatial object
ORA-13051: failed to initialize spatial object
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13050: unable to construct spatial object
ORA-13050: unable to construct spatial object
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13049: unable to determine tolerance value from table lamp;lt;lamp;nbsp;layerlamp;gt;_SDODIM
ORA-13049: unable to determine tolerance value from table lamp;lt;lamp;nbsp;layerlamp;gt;_SDODIM
Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer lamp;lt;lamp;nbsp;layerlamp;gt;.
Action: Verify that the lamp;lt;lamp;nbsp;layerlamp;gt;_SDODIM table has a valid value for the column SDO_TOLERANCE.
Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer lamp;lt;lamp;nbsp;layerlamp;gt;.
Action: Verify that the lamp;lt;lamp;nbsp;layerlamp;gt;_SDODIM table has a valid value for the column SDO_TOLERANCE.
ORA-13048: recursive SQL fetch error
ORA-13048: recursive SQL fetch error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13047: unable to determine ordinate count from table lamp;lt;lamp;nbsp;layerlamp;gt;_SDOLAYER
ORA-13047: unable to determine ordinate count from table lamp;lt;lamp;nbsp;layerlamp;gt;_SDOLAYER
Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer lamp;lt;lamp;nbsp;layerlamp;gt;.
Action: Verify that the lamp;lt;lamp;nbsp;layerlamp;gt;_SDOLAYER table has a valid value for the column SDO_ORDCNT. Then retry the operation.
Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer lamp;lt;lamp;nbsp;layerlamp;gt;.
Action: Verify that the lamp;lt;lamp;nbsp;layerlamp;gt;_SDOLAYER table has a valid value for the column SDO_ORDCNT. Then retry the operation.
ORA-13046: invalid number of arguments
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.
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-13045: invalid compatibility flag
ORA-13045: invalid compatibility flag
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13044: the specified tile size is smaller than the tolerance
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.
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-13043: failed to read metadata from the lamp;lt;lamp;nbsp;layerlamp;gt;_SDOLAYER table
ORA-13043: failed to read metadata from the lamp;lt;lamp;nbsp;layerlamp;gt;_SDOLAYER table
Cause: An error was encountered reading the layer metadata from the lamp;lt;lamp;nbsp;layerlamp;gt;_ 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.
Cause: An error was encountered reading the layer metadata from the lamp;lt;lamp;nbsp;layerlamp;gt;_ 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-13042: invalid SDO_LEVEL and SDO_NUMTILES combination
ORA-13042: invalid SDO_LEVEL and SDO_NUMTILES combination
Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the lamp;lt;lamp;nbsp;layerlamp;gt;_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.
Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the lamp;lt;lamp;nbsp;layerlamp;gt;_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-13041: failed to compare tile with element string.string.string
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 Services.
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 Services.
ORA-13040: failed to subdivide tile
ORA-13040: failed to subdivide tile
Cause: This is an internal error.
Action: Note any accompanying errors and contact Oracle Support Services.
Cause: This is an internal error.
Action: Note any accompanying errors and contact Oracle Support Services.
ORA-13039: failed to update spatial index for element string.string.string
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.
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-13037: SRIDs do not match for the two geometries
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.
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-13036: Operation (string( not supported for Point 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.
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-13035: Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
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.
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-13034: Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
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.
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-13033: Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
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.
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-13032: Invalid NULL SDO_GEOMETRY object
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.
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-13031: Invalid Gtype in the SDO_GEOMETRY object for point object
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.
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-13030: Invalid dimension for the SDO_GEOMETRY object
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.
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-13029: Invalid SRID in the SDO_GEOMETRY object
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.
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-13028: Invalid Gtype in the SDO_GEOMETRY object
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.
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid gtypes.
Subscribe to:
Posts (Atom)