ORA-13431: GeoRaster metadata rasterType error

Cause : The rasterType in the metadata of the GeoRaster object was inconsistent with the GeoRaster rasterType attribute.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Make sure the rasterType in the metadata of the GeoRaster object and the GeoRaster rasterType attribute have the same value.

update : 27-05-2017

ORA-13431 - GeoRaster metadata rasterType error
ORA-13431 - GeoRaster metadata rasterType error

  • ora-16700 : the standby database has diverged from the primary database
  • ora-31609 : error loading file "string" from file system directory "string"
  • ora-03211 : The segment does not exist or is not in a valid state
  • ora-00073 : command string takes between string and string argument(s)
  • ora-15093 : buffer only contains string bytes, I/O requested is string bytes
  • ora-38451 : index is in an inconsistent state
  • ora-37012 : (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.
  • ora-16251 : LSP1 Background Build not permitted
  • ora-19809 : limit exceeded for recovery files
  • ora-13113 : invalid tg_layer_id in sdo_topo_geometry constructor
  • ora-30134 : reserved for future use
  • ora-22286 : insufficient privileges on file or directory to perform string operation
  • ora-39088 : file name cannot contain a path specification
  • ora-06007 : NETASY: bad dialogue format
  • ora-19043 : Multiply nested XMLROOT function disallowed
  • ora-25176 : storage specification not permitted for primary key
  • ora-23359 : error on creating a ddl record for a repcatlog record
  • ora-36268 : (XSCGMDLAGG01) 'string' is not a valid dimension value.
  • ora-23619 : non-Oracle system error: string
  • ora-32813 : propagation schedule string already exists
  • ora-32823 : subscriber exists for queue string and destination string
  • ora-07587 : spdcr: $CREPRC failure
  • ora-02790 : File name is too long
  • ora-16710 : the resource guard is out of memory
  • ora-36951 : (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle.
  • ora-19712 : table name exceeds maximum length of string
  • ora-13066 : wrong feature geometry or element type
  • ora-01228 : SET DATABASE option required to install seed database
  • ora-14031 : partitioning column may not be of type LONG or LONG RAW
  • ora-10932 : trace name context forever
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.