3.15 Maintaining GeoRaster Objects and System Data in the Database

Although GeoRaster provides strict internal database mechanism to prevent the creation of invalid GeoRaster objects and system data, sometimes such GeoRaster objects and system data may exist in the database. This happens if the GeoRaster DML trigger on a GeoRaster column is missing or after some user errors in operations on GeoRaster system data. Examples of such invalid objects and system data include the following:

  • An entry in the GeoRaster system data views (xxx_SDO_GEOR_SYSDATA, described in GeoRaster System Data Views (xxx_SDO_GEOR_SYSDATA)) refers to a nonexistent GeoRaster table or column.

  • Two or more GeoRaster objects have the same pair of RDT name and raster ID values.

  • Some GeoRaster objects, tables, columns, or RDTs not registered.

  • An RDT name is not unique.

  • A GeoRaster object is non-empty or nonblank, but an associated RDT does not exist.

For regular maintenance, or maintenance after a database upgrade, call the following functions or procedures to check and correct any possible errors:

See the reference and detailed usage information about these procedures and functions in SDO_GEOR_ADMIN Package Reference.