Oracle 12c R2 Error Codes and Solution Suggestions from ORA-13300 to ORA-13500
- ORA-13300: single point transform error
Cause: Low-level coordinate transformation error trap.
Action: Check the accompanying error messages.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
Cause: The MASK passed to the RELATE function is not valid.
Action: Verify that the mask is not NULL. See the Oracle Spatial documentation for a list of supported masks.
Cause: The given LRS segment was not a valid line string.
Action: A valid LRS geometric segment is a line string geometry in Oracle Spatial. It could be a simple or compound line string (made of lines or arcs, or both). The dimension information must include the measure dimension as the last element in the Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or longitude/latitude, plus measure)
Cause: The specified LRS point was not a point geometry with measure information.
Action: Check the given point geometry. A valid LRS point is a point geometry in Oracle Spatial with an additional dimension for measure.
Cause: The given measure for linear referencing was out of range.
Action: Redefine the measure.
Cause: The specified geometric segments are not connected.
Action: Check the start/end points of the given geometric segments.
Cause: The measure information of a geometric segment was not assigned (IS NULL).
Action: Assign/define the measure information. An LRS geometric segment is defined if its start and end measure are assigned (non-null).
Cause: There is no room for the measure dimension in the given diminfo, or the specified standard geometry is not a point a line string.
Action: Check if the diminfo dimensions are less than 3 or if the geometry type is point or line string.
Cause: Referencing system (LRS) concatenation involving LRS polygons is not supported.
Action: Check the geometry and element types to ensure that the concatenate operation is not called with a polygon type.
Cause: Reversing a referencing system (LRS) polygon or collection geometry produced an invalid geometry.
Action: Check the geometry type to ensure that this operation is called on non-polygon geometries.
Cause: Clipping (dynseg) a polygon across multiple rings is not allowed.
Action: Polygon clipping is allowed only for a single ring.
Cause: A geometry, specified as being a point, has more than one coordinate in its definition.
Action: A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon, set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, remove the extraneous coordinates from its definition.
Cause: A geometry, specified as being a line, has fewer than two coordinates in its definition.
Action: A line must consist of at least two distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
Cause: A geometry, specified as being an arc, has fewer than three coordinates in its definition.
Action: An arc must consist of at least three distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
Cause: A geometry, specified as being a polygon, has fewer than four coordinates in its definition.
Action: A polygon must consist of at least four distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
Cause: A geometry, specified as being an arcpolygon, has fewer than five coordinates in its definition.
Action: An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
Cause: A geometry, specified as being a compound polygon, has fewer than five coordinates in its definition.
Action: A compound polygon must contain at least five coordinates. A compound polygon consists of at least one arc and one line, each of which must be described using three and at least two distinct coordinates respectively. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
Cause: Invalid definition of an arc. An arc is defined using three non-collinear coordinates.
Action: Alter the definition of the arc, or set the SDO_ETYPE or SDO_GTYPE to the line type.
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.
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.
Cause: The boundary of a polygon intersects itself.
Action: Correct the geometric definition of the object.
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.
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.
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.
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.
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.
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.
Cause: There are repeated points in the sequence of coordinates.
Action: Remove the redundant point.
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.
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.
Cause: The two points representing the extent are identical.
Action: Confirm that the two points describing the extent type are distinct.
Cause: This subtype is not allowed within the ETYPE specified.
Action: Check the Oracle Spatial documentation for type definitions.
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.
Cause: Compound polygon must describe an enclosed area.
Action: Confirm that all sub-elements are connected.
Cause: None of the ETYPEs within the geometry is supported.
Action: Confirm that there is at least one valid ETYPE.
Cause: The spatial layer had a geometry with a different dimensions than the dimensions specified for the layer.
Action: Ensure 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.
Cause: The spatial layer had a geometry with a different SRID than the SRID specified for the layer.
Action: Ensure 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.
Cause: In an Oracle Spatial geometry, interior and exterior rings were not used consistently.
Action: Ensure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array.
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.
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.
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.
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.
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.
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.
Cause: A geodetic line segment was not less than half of a great circle.
Action: Densify the line by adding points.
Cause: The SDO_MBR functionality is not supported for geodetic data.
Action: Find an alternative function that can be used in this context.
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.
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.
Cause: An element of the geometry had orientation specified while some other element had no orientation specified (4-digit etype).
Action: Ensure that all of the polygon elements have orientation specified using the 4-digit etype notation.
Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry.
Action: Ensure that the parameters to the extract function are in the valid range for the geometry.
Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry.
Action: Ensure that the parameters to the extract function are in the valid range for the geometry.
Cause: The specified network was not found in the network metadata.
Action: Insert the network information in the USER_SDO_NETWORK_METADATA view.
Cause: The specified table was not found in the network metadata.
Action: Insert the table information in the USER_SDO_NETWORK_METADATA view.
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.
Cause: There was an inconsistency between the network metadata and the node/link information.
Action: Check the network metadata and the node/link information.
Cause: The network table(s) did not have required column(s)
Action: Check the network schema.
Cause: There was an internal error in network manager.
Action: Contact Oracle Customer Support for more help.
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’);
Cause: The specified value for sdo_batch_size was too high or too low.
Action: Change the value to be in the specified range.
Cause: The dst_spec parameter was specified in the wrong format.
Action: Check the documentation for this parameter.
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.
Cause: There was an internal error in the specified analysis function.
Action: Contact Oracle Customer Support for more help.
Cause: An attempt was made to violate GeoRaster management restrictions.
Action: Check the documentation for more detailed information.
Cause: There was an error on status report related operation.
Action: Check the error message for details.
Cause: The operation failed because the input parameter was null or invalid.
Action: Correct the parameter and try again.
Cause: The two input GeoRaster objects had different dimension sizes.
Action: Check the documentation and ensure that the dimension size is the same for both input GeoRaster objects.
Cause: The expression parameter was not a valid math expression.
Action: Check the documentation and ensure that the expression parameter is correct.
Cause: The condition parameter was not a valid boolean expression.
Action: Check the documentation and ensure that the condition parameter is correct.
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.
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.
Cause: The specified rasterType was null or not supported.
Action: Check the documentation for the rasterType number and/or formats supported by GeoRaster.
Cause: The raster data table name specified for a GeoRaster object was not unique among raster data table names in the database; or for a GeoRaster object, which was not empty and was not blank, or was used as an output GeoRaster object, one or more of the following requirements were not met. The raster data table must: – Exist. – Be visible in the current schema. – Be defined in the same schema as the GeoRaster data table. – Be an object table of SDO_RASTER type or a relational table with the same columns as the attributes of the SDO_RASTER type.
Action: Check the rasterDataTable specification and ensure that all relevant raster data table requirements are met.
Cause: The ultCoordinate array parameter had the wrong length or contained an invalid value.
Action: Check the documentation and ensure that the ultCoordinate parameter is correct.
Cause: The dimensionSize array parameter was NULL, had the wrong length, or contained an invalid value.
Action: Check the documentation and ensure that the dimensionSize parameter is correct.
Cause: The GeoRaster object for output was NULL or invalid.
Action: Ensure that the GeoRaster object for output has been initialized properly.
Cause: The storage parameter contained an invalid specification.
Action: Check the documentation and ensure that the storage parameter is correct.
Cause: The blockSize storage parameter had the wrong length or contained an invalid value.
Action: Check the documentation and ensure that the blockSize storage parameter is correct.
Cause: The specified pyramidLevel parameter was NULL or invalid.
Action: Ensure that the pyramidLevel parameter specifies a valid pyramid level value for the GeoRaster object.
Cause: The layerNumbers or bandNumbers parameter was invalid.
Action: Check the documentation and ensure that the layerNumbers or bandNumbers parameter is valid.
Cause: The intersection of cropArea and source GeoRaster object was NULL.
Action: Check the documentation and ensure that the cropArea parameter is correct.
Cause: The scale parameter contained an invalid specification.
Action: Check the documentation and ensure that the scale parameter is correct.
Cause: The resampling parameter was NULL or invalid.
Action: Check the documentation and ensure that the resampling parameter is correct.
Cause: The pyramid parameter was invalid.
Action: Check the documentation and ensure that the pyramid parameter is correct.
Cause: The point position specified by the <ptGeom, layerNumber> or <rowNumber, colNumber, bandNumber> parameter combination was invalid or out of scope.
Action: Ensure that the parameters specify a valid point that is or can be translated into a cell position inside the cell space of the GeoRaster object.
Cause: The geometry parameter did not specify a valid single-point geometry.
Action: Specify a valid single-point geometry.
Cause: The layerNumber parameter was null or out of scope.
Action: Specify a valid layerNumber parameter.
Cause: A parameter for set metadata operations was null or invalid.
Action: Check the documentation for information about the parameters.
Cause: An attempt to perform a mosaic or append operation failed.
Action: Check the error message for details.
Cause: The input geometry was not in the GeoRaster cell space, which had a NULL SRID value.
Action: Ensure that the geometry parameter has a NULL SRID.
Cause: The cell value was NULL or out-of-scope.
Action: Ensure that the cell value is not NULL and is in the range as designated by the cellDepth definition of the specified GeoRaster object.
Cause: The model coordinate array parameter had the wrong length or had NULL ordinate element(s).
Action: Ensure that the model coordinate parameter is valid.
Cause: The cell coordinate array parameter had the wrong length or had NULL ordinate element(s).
Action: Ensure that the cell coordinate parameter is valid.
Cause: The GeoRaster object was not spatially referenced.
Action: Ensure that the GeoRaster object is spatially referenced.
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: Ensure that the parameter that specifies the background filling value is valid. The size of the array must equal 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.
Cause: The specified window parameter was invalid.
Action: Specify a valid window parameter. Check the documentation for details.
Cause: The bitmap mask was not a valid 1-bit GeoRaster object, or it had the wrong dimension sizes.
Action: Ensure that the bitmap mask is a valid 1-bit 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.
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).
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.
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.
Cause: The rasterType in the metadata of the GeoRaster object was inconsistent with the GeoRaster rasterType attribute.
Action: Ensure that the rasterType in the metadata of the GeoRaster object and the GeoRaster rasterType attribute have the same value.
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 the SDO_GEOR.setBlankCellValue package to add blankCellValue to the metadata whenever the isBlank element value is TRUE, and ensure that the specified blankCellValue element value is not NULL and is in the range as designated by the cellDepth definition of the GeoRaster object.
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.
Cause: The cellRepresentation type was not supported.
Action: Check the documentation for supported cellRepresentation types.
Cause: The specification of dimensions or totalDimensions was inconsistent with rasterType, or vice versa.
Action: Ensure that the dimension specifications are consistent.
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.
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.
Cause: The specified pyramid type was not supported.
Action: Check the documentation for supported pyramid types.
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.
Cause: The specified compression type was not supported.
Action: Check the documentation for supported compression types.
Cause: The specified error related to the polynomialModel element in the spatial reference system (SRS) metadata.
Action: Check the documentation and ensure that a valid polynomial model is specified.
Cause: There was no SYSDATA entry for the specified GeoRaster object.
Action: Ensure that a sysdata entry has been inserted for the specified GeoRaster object.
Cause: There were NULL or invalid component values in the specified metadata.
Action: Check the documentation and ensure that all of the component values are valid.
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: Ensure that 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.
Cause: There was an invalid NODATA value or value range in the metadata, or the specified NODATA value or value range was invalid.
Action: Ensure that 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.
Cause: The GeoRaster Temporal Reference System was not supported.
Action: Set isReferenced to FALSE.
Cause: The GeoRaster Band Reference System was not supported.
Action: Set isReferenced to FALSE.
Cause: The GeoRaster spectral extent specification was incorrect.
Action: The MIN value must be less than the MAX value in the spectralExtent element.
Cause: The GeoRaster rasterInfo ULTCoordinate was not correct.
Action: Check the documentation for restrictions.
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.
Cause: The scaling function had a zero denominator.
Action: Ensure that the scaling function denominator is not zero.
Cause: The bin function data did not match its type.
Action: For EXPLICIT type, provide a binTableName element; otherwise, provide a binFunctionData element.
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.
Cause: The GeoRaster metadata was invalid against its XML Schema.
Action: Run the schemaValidate routine to find the errors.
Cause: The beginDateTime value was later than the endDateTime value.
Action: Ensure that the beginDateTime value is not later than the endDateTime value.
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.
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.
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.
Cause: The polynomial model was not an six-parameter transformation, or the six-parameter transformation was not valid.
Action: Check the documentation and ensure that the polynomial model is a valid six-parameter affine transformation.
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.
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.
Cause: The specified blocking configuration was invalid.
Action: Check the documentation for the blocking specification supported by GeoRaster.
Cause: An internal error occurred while retrieving GeoRaster data from the database.
Action: Check the error message for details.
Cause: An internal error occurred while loading GeoRaster data into the database.
Action: Check the error message for details.
Cause: The specified table or column did not exist, or the column was not a GeoRaster column.
Action: Ensure that the specified table exists and the specified column is a GeoRaster column.
Cause: The operation failed because the GeoRaster object had an inappropriate type or format for the specified compression method. The GeoRaster type or format is not supported for the specified compression.
Action: Check the error message for details. Check the documentation for the appropriate GeoRaster types and formats for each compression method. Use SDO_GEOR.changeFormatCopy to transform the GeoRaster object to an appropriate format, or apply another compression method.
Cause: The GeoRaster metadata specification is not supported.
Action: Check the documentation for the supported GeoRaster metadata specifications.
Cause: Invalid blockMBR geometries were stored in the raster data table.
Action: Ensure that the blockMBR geometries stored in the raster data table are valid, or call the SDO_GEOR.generateBlockMBR() package to regenerate the blockMBR geometries.
Cause: The data of the source GeoRaster object could not be used to update that of the target GeoRaster object.
Action: Ensure that the source and the target GeoRaster objects have the same cell depth, and that both objects are either georeferenced or not georeferenced at all. If both are georeferenced, they should be in the same coordinate system and have the same spatial resolutions.
Cause: The number of specified target layers or bands and source layers or bands did not match.
Action: When updating layers or bands of a target GeoRaster object to reflect the associated layers or bands of the source GeoRaster object, specify the same number of layers or bands for both the source and the target objects. Check the documentation for details.
Cause: The owner of the specified raster data table could not be determined.
Action: Ensure that the GeoRaster object that refers to the raster data table has been registered by inserting the object into a GeoRaster table.
Cause: The geometry parameter did not specify a valid geometry.
Action: Specify a valid 2D or 3D geometry. If the model SRID is null or indicates a 2D coordinate system, the geometry must be 2D. If the model SRID indicates a 3D coordinate system, the geometry must either be a 3D geometry or a 2D geometry that can be converted to 3D with the specified vertical axis (or vertical SRID) and ellipsoidal parameters.
Cause: The rasterSpec parameter contained an invalid specification.
Action: Check the documentation and ensure that the rasterSpec parameter contains only valid keywords and values.
Cause: The rasterDataTable name was not a valid nonquoted identifier, it contained a period separator, or not all of the alphanumeric characters were uppercase.
Action: Ensure that the table name is a valid nonquoted identifier without any period separators, and that all the alphanumeric characters are uppercase.
Cause: The output GeoRaster object had the same RASTER_DATA_TABLE and RASTER_ID combination as that of an input GeoRaster object.
Action: Ensure that the output GeoRaster object is different from any of the input GeoRaster objects.
Cause: The point position specified by the point geometry parameter or the rowNumber/colNumber parameter combination was null or out of scope.
Action: Ensure that the parameters specify a valid point that translates or can be translated into a cell position inside the cell space of the GeoRaster object.
Cause: The specified functional fitting method was not supported, the number of GCPs was insufficient, some GCPs were invalid, or the distribution of the GCPs led to no solution or an unstable solution.
Action: Check the GeoRaster documentation for the supported functional fitting methods and the requirements of GCPs.
Cause: The target SRID was not different from the source GeoRaster object’s SRID.
Action: Specify a different valid SRID for the target GeoRaster object.
Cause: Reprojection from source to destination projection produced a large distortion.
Action: Check the destination projection and ensure that it is suitable for the area covered by the source GeoRaster object. Check the GeoRaster documentation for more information about reprojection.
Cause: The specified source type was not supported.
Action: Check the documentation for the source types (such as FILE and HTTP) supported by GeoRaster.
Cause: The specified destination type was not supported.
Action: Check the documentation for the destination types (such as FILE) supported by GeoRaster.
Cause: No GeoRaster object has been initialized for the specified image.
Action: Initialize a GeoRaster object to hold this image before loading it into the database. Check the documentation for details.
Cause: There was insufficient memory to hold the specified GeoRaster data for this operation.
Action: Use SDO_GEOR.subset to isolate a subset of the GeoRaster data, or reblock the GeoRaster data into smaller sized blocks. Check the documentation for details.
Cause: The file format or compression type was not supported.
Action: Check the documentation for formats that are currently supported by GeoRaster.
Cause: The operation could not be completed because an error occurred during compression or decompression. Check the error message for details.
Action: Check that the GeoRaster object is valid, that its metadata is valid for the specified compression format, and that valid parameters are passed into the compression or decompression operation.
Cause: The GeoTIFF metadata of the specified input image contained invalid or insufficient information to georeference the GeoRaster object.
Action: Check the error message for details.
Cause: No SRID was found in the Oracle Spatial CS_SRS table to match the source coordinate system metadata.
Action: Add a user-defined coordinate reference system for this coordinate system, as explained in the Oracle Spatial documentation.
Cause: An attempt to perform a transformation operation failed.
Action: Check the error message for details.
Cause: There was an error in the GeoRaster operation, parameters, or compression types.
Action: Check the error message and take the appropriate action or contact Oracle Support Services for further assistance.
Cause: The specified option is not installed or enabled.
Action: Consider purchasing and installing the missing option or enabling the option if it was already installed.
Cause: This is an internal GeoRaster error.
Action: Contact Oracle Support Services. You may want to ensure that the GeoRaster object is valid before you do so.
Cause: An error related to an external plugin was encountered in the GeoRaster component.
Action: Check the documentation for the external plugin, or contact the plugin provider and supply the exact error text.
Cause: This is an internal Oracle Spatial error.
Action: Contact Oracle Support Services.
Cause: The CREATE DATABASE command contains more than one SYSAUX DATAFILE clause.
Action: Specify at most one SYSAUX DATAFILE clause.