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 : 21-08-2017
ORA-13376

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

  • ora-06804 : TLI Driver: could not bind an IPX address at initialization
  • ora-16055 : FAL request rejected
  • ora-08234 : smsget: cannot get instance listener address
  • ora-14187 : partitioning method for LOCAL index is inconsistent with that of the underlying table
  • ora-02421 : missing or invalid schema authorization identifier
  • ora-22872 : OID INDEX clause not allowed on tables with primary key based object identifiers
  • ora-01890 : NLS error detected
  • ora-09798 : Label comparison failed.
  • ora-19649 : offline-range record recid string stamp string not found in file string
  • ora-33247 : (CRENAME03) %K is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.
  • ora-12737 : Instant Client Light: unsupported server character set string
  • ora-01629 : max # extents (string) reached saving undo for tablespace string
  • ora-31504 : cannot alter or drop predefined change source
  • ora-12427 : invalid input value for string parameter
  • ora-14640 : add/coalesce index partition operation is valid only for hash partitioned global indexes
  • ora-19160 : XP0003 - syntax error: invalid variable name string
  • ora-13023 : interior element interacts with exterior element
  • ora-26515 : no master log available for 'string.string'
  • ora-02452 : invalid HASHKEYS option value
  • ora-12210 : TNS:error in finding Navigator data
  • ora-02163 : invalid value for FREELIST GROUPS
  • ora-24416 : Invalid session Poolname was specified.
  • ora-31527 : could not find source column string for CDC change table string.string
  • ora-15157 : rolling upgrade or downgrade is not allowed
  • ora-01641 : tablespace 'string' is not online - cannot add data file
  • ora-19863 : device block size string is larger than max allowed: string
  • ora-36700 : (XSRELTBL04) Dimension workspace object cannot be qualified more than once.
  • ora-14603 : [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables
  • ora-01569 : data file too small for system dictionary tables
  • ora-14514 : LOCAL option not valid without subpartition name
  • 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.