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 - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Make sure the geometry parameter has a null SRID.

update : 23-08-2017

ORA-13420 - the SRID of the geometry parameter was not null
ORA-13420 - the SRID of the geometry parameter was not null

  • ora-38406 : attribute set string already exists
  • ora-19674 : file string is already being backed up with proxy copy
  • ora-04028 : cannot generate diana for object stringstringstringstringstring
  • ora-31616 : unable to write to dump file "string"
  • ora-14015 : too many partition descriptions
  • ora-12585 : TNS:data truncation
  • ora-02228 : duplicate SIZE specification
  • ora-15070 : maximum number of files string exceeded in diskgroup "string"
  • ora-28116 : insufficient privileges to do direct path access
  • ora-16575 : request terminated at broker discretion
  • ora-25273 : AQ QMN process alternate cleanup event
  • ora-16064 : remote archival is disabled by another instance
  • ora-04061 : existing state of string has been invalidated
  • ora-10646 : Too many recursive extensions during SYSTEM tablespace migration
  • ora-06909 : CMX: error during acknowledge of ORACLE_SID
  • ora-00820 : Specified value of sga_max_size is too small, needs to be at least stringM
  • ora-33068 : (XSAGDNGL33) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must specify a positive dimension offset.
  • ora-39055 : The string feature is not supported in version string.
  • ora-30061 : Internal Event for Savepoint Tracing
  • ora-25467 : table alias not specified
  • ora-37078 : (XSMCSESS06) The dimension being maintained (workspace object) cannot also be used as a step dimension.
  • ora-36691 : (NTEXTCNV02) Invalid escape sequence in argument to UNISTR function: string.
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-31422 : owner schema string does not exist
  • ora-32117 : Source LOB is null
  • ora-32128 : setDataBuffer called after fetch has started
  • ora-13447 : GeoRaster metadata BRS error
  • ora-30975 : invalid Order Key Index option for XML Index
  • ora-38702 : Cannot update flashback database log file header.
  • 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.