Oracle 11g Error Codes and Solution Suggestions from ORA-13400 to ORA-13500
- 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.
- ORA-13466: format not appropriate for specified compression method: string
- 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.
- ORA-13467: unsupported GeoRaster metadata specification: string
- Cause: The GeoRaster metadata specification is not supported.
- Action: Check the documentation for the supported GeoRaster metadata specifications.
- ORA-13468: invalid blockMBR
- Cause: Invalid blockMBR geometries were stored in the raster data table.
- Action: Make sure the blockMBR geometries stored in the raster data table are valid, or call SDO_GEOR.generateBlockMBR() to regenerate the blockMBR geometries.
- ORA-13469: cannot perform updateRaster operation
- Cause: The data of the source GeoRaster object could not be used to update that of the target GeoRaster object.
- Action: Make sure 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.
- ORA-13470: target and source layers or bands mismatched
- 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.
- ORA-13471: unable to determine the owner of string
- Cause: The owner of the specified raster data table could not be determined.
- Action: Make sure the GeoRaster object that refers to the raster data table has been registered by inserting the object into a GeoRaster table.
- ORA-13472: invalid geometry parameter
- 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.
- ORA-13473: invalid rasterSpec parameter
- Cause: The rasterSpec parameter contained an invalid specification.
- Action: Check the documentation and make sure the rasterSpec parameter contains only valid keywords and values.
- ORA-13474: invalid rasterDataTable name: string
- 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.
- ORA-13475: invalid GeoRaster object for output
- 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.
- ORA-13476: invalid or out of scope point specification
- 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.
- ORA-13477: invalid GCP georeferencing specification: string
- 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.
- ORA-13478: the target SRID is the same as the source GeoRaster object’s SRID
- 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.
- ORA-13479: cannot reproject
- Cause: Reprojection from source to destination projection produced a large distortion.
- Action: Check the destination projection and make sure it is suitable for the area covered by the source GeoRaster object. Check the GeoRaster documentation for more information about reprojection.
- ORA-13480: the Source Type is not supported
- Cause: The specified source type was not supported.
- Action: Check the documentation for the source types (such as FILE and HTTP) supported by GeoRaster.
- ORA-13481: the destination type is not supported
- Cause: The specified destination type was not supported.
- Action: Check the documentation for the destination types (such as FILE) supported by GeoRaster.
- ORA-13482: GeoRaster object is not initialized for the image
- 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.
- ORA-13483: insufficient memory for the specified GeoRaster data
- 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.
- ORA-13484: the file format or compression type is not supported: string
- Cause: The file format or compression type was not supported.
- Action: Check the documentation for formats that are currently supported by GeoRaster.
- ORA-13485: error occurred during compression or decompression: string
- 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.
- ORA-13486: invalid or insufficient GeoTIFF metadata to georeference the GeoRaster object: string
- 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.
- ORA-13487: SRID not found for source coordinate system metadata
- 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.
- ORA-13497: string
- Cause: This is an internal GeoRaster error.
- Action: Contact Oracle Support Services. You may want to make sure the GeoRaster object is valid before you do so.
- ORA-13498: string
- 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.
- ORA-13499: string
- Cause: This is an internal Spatial error.
- Action: Contact Oracle Support Services.
- ORA-13500: SYSAUX DATAFILE clause specified more than once
- Cause: The CREATE DATABASE command contains more than one SYSAUX DATAFILE clause.
- Action: Specify at most one SYSAUX DATAFILE clause.