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-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.
ORA-13401: duplicate entry for string in
USER_SDO_GEOR_SYSDATA view
Cause:
The RASTER_DATA_TABLE and RASTER_ID columns contained the same information in
two or more rows in the USER_SDO_GEOR_SYSDATA view.
Action:
Ensure that the RASTER_DATA_TABLE and RASTER_ID columns in the
USER_SDO_GEOR_SYSDATA view contain the correct information, and that the value
pair is unique for each row.
ORA-13402: the rasterType is null or not supported
Cause:
The specified rasterType was null or not supported.
Action:
Check the documentation for the rasterType number and/or formats supported by
GeoRaster.
ORA-13403: invalid rasterDataTable specification: string
Cause:
Each GeoRaster object must have an associated raster data table whose name is
unique among raster data table names in the database. If the GeoRaster object
is not empty and not blank, the raster data table must exist, be visible in the
current schema, be defined in the same schema as the GeoRaster data table, and
be an object table of SDO_RASTER type. However, one or more of these
requirements were not met.
Action:
Check the rasterDataTable specification and ensure that all relevant raster
data table requirements are met.
ORA-13404: invalid ultCoordinate parameter
Cause:
The ultCoordinate array parameter had the wrong length or contained an invalid
value.
Action:
Check the documentation, and make sure the ultCoordinate parameter is correct.
ORA-13405: null or invalid dimensionSize parameter
Cause:
The dimensionSize array parameter was null, had the wrong length, or contained
an invalid value.
Action:
Check the documentation, and make sure the dimensionSize parameter is correct.
ORA-13406: null or invalid GeoRaster object for
output
Cause:
The GeoRaster object for output was null or invalid.
Action:
Make sure the GeoRaster object for output has been initialized properly.
ORA-13407: invalid storage parameterstring
Cause:
The storage parameter contained an invalid specification.
Action:
Check the documentation, and make sure the storage parameter is correct.
ORA-13408: invalid blockSize storage parameter
Cause:
The blockSize storage parameter had the wrong length or contained invalid
value.
Action:
Check the documentation, and make sure the blockSize storage parameter is
correct.
ORA-13409: null or invalid pyramidLevel parameter
Cause:
The specified pyramidLevel parameter was null or invalid.
Action:
Make sure the pyramidLevel parameter specifies a valid pyramid level value for
the GeoRaster object.
ORA-13410: invalid layerNumbers or bandNumbers
parameter
Cause:
The layerNumbers or bandNumbers parameter was invalid.
Action:
Check the documentation and make sure the layerNumbers or bandNumbers parameter
is valid.
ORA-13411: subset results in null data set
Cause:
The intersection of cropArea and source GeoRaster object was null.
Action:
Check the documentation, and make sure the cropArea parameter is correct.
ORA-13412: invalid scale parameterstring
Cause:
The scale parameter contained an invalid specification.
Action:
Check the documentation, and make sure the scale parameter is correct.
ORA-13413: null or invalid resampling parameter
Cause:
The resampling parameter was null or invalid.
Action:
Check the documentation, and make sure the resampling parameter is correct.
ORA-13414: invalid pyramid parameter
Cause:
The pyramid parameter was invalid.
Action:
Check the documentation, and make sure the pyramid parameter is correct.
ORA-13415: invalid or out of scope point
specification
Cause:
The point position specified by the <ptGeom, layerNumber> or
<rowNumber, colNumber, bandNumber> parameter combination was invalid or
out of scope.
Action:
Make sure the parameter(s) specify a valid point that is or can be translated
into a cell position inside the cell space of the GeoRaster object.
ORA-13416: invalid geometry parameter
Cause:
The geometry parameter did not specify a valid single-point geometry.
Action:
Specify a valid single-point geometry.
ORA-13417: null or invalid layerNumber parameter
Cause:
The layerNumber parameter was null or out of scope.
Action:
Specify a valid layerNumber parameter.
ORA-13418: null or invalid parameter(s) for set
functions
Cause:
A parameter for set metadata operations was null or invalid.
Action:
Check the documentation for information about the parameters.
ORA-13419: cannot perform mosaick operation on the
specified table column
Cause:
An attempt to perform a mosaick operation failed because the GeoRaster objects
in the specified table column did not meet necessary conditions.
Action:
Check the documentation for SDO_GEOR.Mosaick for details.
ORA-13420: the SRID of the geometry parameter was
not null
Cause:
The input geometry must be in the GeoRaster cell space, which has a null SRID
value.
Action:
Make sure the geometry parameter has a null SRID.
ORA-13421: NULL or invalid cell value
Cause:
The cell value was NULL or out-of-scope.
Action:
Make sure the cell value is not NULL and is in the range as designated by the
cellDepth definition of the specified GeoRaster object.
ORA-13422: invalid model coordinate parameter
Cause:
The model coordinate array parameter had the wrong length or had null ordinate
element(s).
Action:
Make sure the model coordinate parameter is valid.
ORA-13423: invalid cell coordinate parameter
Cause:
The cell coordinate array parameter had the wrong length or had null ordinate
element(s).
Action:
Make sure the cell coordinate parameter is valid.
ORA-13424: the GeoRaster object is not spatially
referenced
Cause:
The GeoRaster object was not spatially referenced.
Action:
Make sure the GeoRaster object is spatially referenced.
ORA-13425: invalid background filling value
parameter
Cause:
The background filling value parameter was invalid either because the array had
the wrong size or because some of the element values were invalid.
Action:
Make sure the parameter that specifies the background filling value is valid.
The size of the array must equal to either 1 (the value is for all bands) or
the exact band dimension size. The element values must be valid cell values as
determined by the cell depth.
ORA-13426: invalid window parameter
Cause:
The specified window parameter was invalid.
Action:
Specify a valid window parameter. Check the documentation for details.
ORA-13427: invalid bitmap mask
Cause:
The bitmap mask was not a valid 1BIT GeoRaster object, or it had the wrong
dimension sizes.
Action:
Make sure the bitmap mask is a valid 1BIT GeoRaster object with only one band,
and the row and column dimension sizes of the bitmap mask are the same as those
of the target GeoRaster object.
ORA-13428: invalid modelCoordinateLocation
Cause:
The program [or user] specified a modelCoordinateLocation that is not
supported, or the modelCoordinateLocation of the GeoRaster object was wrong.
Action:
Set or specify the modelCoordinateLocation to be CENTER (0) or UPPERLEFT (1).
ORA-13429: invalid xCoefficients or yCoefficients
parameter(s)
Cause:
An attempt to perform a georeference operation failed. Possible reasons include
xCoefficients or yCoefficients having the wrong number of coefficients or
invalid coefficients.
Action:
Check the documentation for supported coefficient specifications.
ORA-13430: the GeoRaster object has null
attribute(s)
Cause:
The metadata or rasterType of the GeoRaster object was null.
Action:
This object may only be used as an output parameter of procedures or functions.
It is not valid for other purposes.
ORA-13431: GeoRaster metadata rasterType error
Cause:
The rasterType in the metadata of the GeoRaster object was inconsistent with
the GeoRaster rasterType attribute.
Action:
Make sure the rasterType in the metadata of the GeoRaster object and the
GeoRaster rasterType attribute have the same value.
ORA-13432: NULL or invalid blankCellValue
Cause:
The blankCellValue element could not be found in the metadata of a blank
GeoRaster object, or the specified blankCellValue element value was NULL or
invalid.
Action:
Call SDO_GEOR.setBlankCellValue to add blankCellValue to the metadata whenever
the isBlank element value is TRUE, and make sure that the specified
blankCellValue element value is not NULL and is in the range as designated by
the cellDepth definition of the GeoRaster object.
ORA-13433: GeoRaster metadata default RGB error
Cause:
At least one of the defaultRed, defaultGreen, and defaultBlue values (logical
layer numbers) was zero, negative, or out of range.
Action:
Check the documentation for details.
ORA-13434: GeoRaster metadata cellRepresentation
error
Cause:
The cellRepresentation type was not supported.
Action:
Check the documentation for supported cellRepresentation types.
ORA-13435: GeoRaster metadata dimension
inconsistent
Cause:
The specification of dimensions or totalDimensions was inconsistent with rasterType,
or vice versa.
Action:
Make sure dimension specifications are consistent.
ORA-13436: GeoRaster metadata dimensionSize error
Cause:
Either the dimensionSize for each dimension was not specified, or an extraneous
dimensionSize was specified.
Action:
Add a dimsenionSize for each dimension of the GeoRaster object and delete extra
dimensionSize elements.
ORA-13437: GeoRaster metadata blocking error
Cause:
Either the wrong block number(s) or block size(s) along dimensions were
specified, or the block numbers and sizes when taken together were not
consistent.
Action:
Check the documentation for details.
ORA-13438: GeoRaster metadata pyramid type error
Cause:
The specified pyramid type was not supported.
Action:
Check the documentation for supported pyramid types.
ORA-13439: GeoRaster metadata pyramid maxLevel error
Cause:
The specified maxLevel exceeded the maximum level allowed by the specified
pyramid type.
Action:
Check the documentation for supported pyramid types and their total level
limitations.
ORA-13440: GeoRaster metadata compression type
error
Cause:
The specified compression type was not supported.
Action:
Check the documentation for supported compression types.
ORA-13441: GeoRaster metadata SRS error: string
Cause:
The specified error relates to the polynomialModel element in the Spatial
Reference System (SRS) metadata.
Action:
Check the documentation and make sure that a valid polynomial model is
specified.
ORA-13442: GeoRaster object not registered: string
Cause:
There was no sysdata entry for the specified GeoRaster object.
Action:
Make sure that a sysdata entry has been inserted for the specified GeoRaster
object.
ORA-13443: null or invalid values in string
Cause:
There were null or invalid component values in the specified metadata.
Action:
Check the documentation and make sure that all the component values are valid.
ORA-13444: cannot perform mergeLayers operation
Cause:
The two GeoRaster objects whose layers are to be combined together either had
different row or column dimension sizes, or their georeferencing information
did not match.
Action:
Make sure the objects have the same row and column dimension sizes. If neither
is georeferenced, their ULTCoordinate values must be the same. Otherwise, they
must be both georeferenced and cover the same area in the model space.
ORA-13445: NULL or invalid NODATA value or value
range
Cause:
There was invalid NODATA value or value range in the metadata, or the specified
NODATA value or value range was invalid.
Action:
Make sure the NODATA value or value range is not NULL and is completely
contained in the range as designated by the cellDepth definition of the
specified GeoRaster object.
ORA-13446: GeoRaster metadata TRS error
Cause:
The GeoRaster Temporal Reference System was not supported.
Action:
Set isReferenced to FALSE.
ORA-13447: GeoRaster metadata BRS error
Cause:
The GeoRaster Band Reference System was not supported.
Action:
Set isReferenced to FALSE.
ORA-13448: GeoRaster metadata BRS error
Cause:
The GeoRaster spectral extent specification was incorrect.
Action:
The MIN value must be less than the MAX value in the spectralExtent element.
ORA-13449: GeoRaster metadata ULTCoordinate error
Cause:
The GeoRaster rasterInfo ULTCoordinate was not correct.
Action:
Check the documentation for restrictions.
ORA-13450: GeoRaster metadata layerInfo error
Cause:
The GeoRaster had more than one layerInfo element, or the layerDimension value
was not supported.
Action:
The current release only supports one layerInfo element; layer can only be
defined along one dimension, and this dimension must be BAND.
ORA-13451: GeoRaster metadata scaling function
error
Cause:
The scaling function had a zero denominator.
Action:
Make sure the scaling function denominator is not zero.
ORA-13452: GeoRaster metadata BIN function error
Cause:
The bin function data did not match its type.
Action:
For EXPLICIT type, provide a binTableName element; otherwise, provide a
binFunctionData element.
ORA-13453: GeoRaster metadata layer error
Cause:
Too many subLayers were defined for the GeoRaster object, or layerNumber or
layerDimensionOrdinate was not assigned correctly.
Action:
The total number of logical layers cannot exceed the total number of physical
layers, and each logical layer must be assigned a valid physical layer number
following the same order. Check the documentation for more details.
ORA-13454: GeoRaster metadata is invalid
Cause:
The GeoRaster metadata was invalid against its XML Schema.
Action:
Run the schemaValidate routine to find the errors.
ORA-13455: GeoRaster metadata TRS error
Cause:
The beginDateTime value was later than the endDateTime value.
Action:
Make sure that the beginDateTime value is not later than the endDateTime value.
ORA-13456: GeoRaster cell data error: string
Cause:
There was an error in the original GeoRaster cell data or in the cell data of
the pyramids.
Action:
If the error is related to the original GeoRaster cell data, the GeoRaster
object is invalid and has to be deleted or manually repaired. If the error is
related to pyramids, delete the pyramids and regenerate them.
ORA-13457: bitmap mask cell data error: string
Cause:
There was an error in the cell data of an original bitmap mask or in the cell
data of the pyramids of a bitmap mask.
Action:
If the error is related to an original bitmap mask, remove the bitmap mask. If
the error is related to the pyramids of a bitmap mask, delete the pyramids and
regenerate them.
ORA-13458: GeoRaster metadata SRS error
Cause:
The polynomial model did not match the requirements of a rectified GeoRaster
object.
Action:
Check the documentation for the requirements of the polynomial model for a
rectified GeoRaster object, or set isRectified to be false.
ORA-13459: GeoRaster metadata SRS error
Cause:
The polynomial model was not an six-parameter transformation, or the
six-parameter transformation was not valid.
Action:
Check the documentation and make sure the polynomial model is a valid
six-parameter affine transformation.
ORA-13460: GeoRaster metadata SRS error
Cause:
The referenced GeoRaster object had a zero model space SRID or the specified
model space SRID was zero.
Action:
Set or specify the model space SRID to be a nonzero number.
ORA-13461: the interleaving type is not supported
Cause:
The interleaving type of the GeoRaster object was not supported.
Action:
Check the documentation for the interleaving types supported by GeoRaster. Use
SDO_GEOR.changeFormatCopy to transform the image to a supported interleaving
type.
ORA-13462: invalid blocking specification
Cause:
The specified blocking configuration was invalid.
Action:
Check the documentation for the blocking specification supported by GeoRaster.
ORA-13463: error retrieving GeoRaster data: string
Cause:
An internal error occurred while retrieving GeoRaster data from the database.
Action:
Check the error message for details.
ORA-13464: error loading GeoRaster data: string
Cause:
An internal error occurred while loading GeoRaster data into the database.
Action:
Check the error message for details.
ORA-13465: null or invalid table or column
specification
Cause:
The specified table or column did not exist, or the column was not a GeoRaster
column.
Action:
Make sure the specified table exists and the specified column is a GeoRaster
column.
No hay comentarios:
Publicar un comentario