ORA-13402: the rasterType is null or not supported

Cause : The specified rasterType was null or not supported.

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

Check the documentation for the rasterType number and/or formats supported by GeoRaster.

update : 23-05-2017
ORA-13402

ORA-13402 - the rasterType is null or not supported
ORA-13402 - the rasterType is null or not supported

  • ora-25335 : AQ array operations not allowed for buffered messages
  • ora-01277 : file 'string' already exists
  • ora-27151 : buffer not large enough to hold process ID string
  • ora-13449 : GeoRaster metadata ULTCoordinate error
  • ora-01372 : Insufficient processes for specified LogMiner operation
  • ora-36188 : (XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable workspace object. Either the values of the COUNTVAR variable are stored improperly, or there is problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support.
  • ora-14294 : Number of partitions does not match number of subpartitions
  • ora-32141 : get method does not match the type of the parameter
  • ora-27068 : I/O buffer is not aligned properly
  • ora-19763 : compatibility version string is higher than maximum allowed: string
  • ora-02071 : error initializing capabilities for remote database string
  • ora-22886 : scoped table "string" in schema "string" is not an object table
  • ora-01716 : NOSORT may not be used with a cluster index
  • ora-32311 : materialized view definition query selects an unsupported user-defined type
  • ora-01028 : internal two task error
  • ora-19908 : datafile string has invalid checkpoint
  • ora-13036 : Operation [string] not supported for Point Data
  • ora-02366 : The following index(es) on table string were processed:
  • ora-12003 : materialized view "string"."string" does not exist
  • ora-13144 : target table string not found
  • ora-38908 : internal error occurred during DML Error Logging
  • ora-39316 : call to DBMS_SCHEMA_COPY.CLEAN_UP is not legal
  • ora-08308 : sllfop: Cannot open file
  • ora-09913 : Malloc of dummy name failed.
  • ora-29519 : name string resolved via a synonym in schema string to a class with a different name
  • ora-29325 : SET COMPATIBILITY release number lower than string
  • ora-24073 : cannot specify RETENTION_TIME on exception queue string.string
  • ora-32826 : Messaging Gateway agent has already been started
  • ora-29317 : datafile string does not exist
  • ora-06546 : DDL statement is executed in an illegal context
  • 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.