ORA-13376: invalid type name specified for layer_gtype parameter

Cause : An invalid type name is specified for the layer_gtype constraint.

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

See the Spatial documentation for of valid keywords that can be used in defining a layer_gtype constraint.

update : 27-06-2017

ORA-13376 - invalid type name specified for layer_gtype parameter
ORA-13376 - invalid type name specified for layer_gtype parameter

  • ora-00217 : control file could not be resized for new record types
  • ora-12162 : TNS:net service name is incorrectly specified
  • ora-12442 : policy column "string" already used by an existing policy
  • ora-08198 : Flashback Table is not supported on object tables, nested tables
  • ora-13028 : Invalid Gtype in the SDO_GEOMETRY object
  • ora-06771 : TLI Driver: error reading version
  • ora-14018 : partition bound list contains too few elements
  • ora-13114 : [string]_NODE$ table does not exist
  • ora-04022 : nowait requested, but had to wait to lock dictionary object
  • ora-21615 : an OTS (named or simple) instance failed
  • ora-16588 : no more internal buffers
  • ora-23538 : cannot explicitly refresh a NEVER REFRESH materialized view ("string")
  • ora-24120 : invalid string parameter passed to DBMS_REPAIR.string procedure
  • ora-28157 : Proxy user 'string' forbidden to set role 'string' for client 'string'
  • ora-02798 : Invalid number of requests
  • ora-12737 : Instant Client Light: unsupported server character set string
  • ora-27489 : unable to process job "string.string" from job class "string"
  • ora-01216 : thread string is expected to be disabled after CREATE CONTROLFILE
  • ora-02148 : EXCLUSIVE specified multiple times
  • ora-14100 : partition extended table name cannot refer to a remote object
  • ora-06571 : Function string does not guarantee not to update database
  • ora-03281 : invalid ALLOCATE EXTENT option
  • ora-13428 : invalid modelCoordinateLocation
  • ora-14105 : RECOVERABLE/UNRECOVERABLE may not be specified in this context
  • ora-30108 : invalid positional parameter value 'string'
  • ora-12562 : TNS:bad global handle
  • ora-01606 : gc_files_to_locks not identical to that of another mounted instance
  • ora-39116 : invalid trigger operation on mutating table string.string
  • ora-31612 : Allocation of process descriptor failed.
  • ora-13458 : GeoRaster metadata SRS error
  • 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.