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-04-2017
ORA-13376

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

  • ora-30743 : "string" is not an object view
  • ora-28365 : wallet is not open
  • ora-16165 : LGWR failed to hear from network server
  • ora-12219 : TNS:missing community name from address in ADDRESS_LIST
  • ora-19268 : XQ0048 - namespace string does not match target namespace string
  • ora-00823 : Specified value of sga_target greater than sga_max_size
  • ora-13759 : User "string" cannot remove reference "string".
  • ora-32810 : foreign queue string is not registered
  • ora-02290 : check constraint (string.string) violated
  • ora-06440 : ssaio: the asynchronous read returned incorrect number of bytes
  • ora-19686 : SPFILE not restored due to string
  • ora-01715 : UNIQUE may not be used with a cluster index
  • ora-01501 : CREATE DATABASE failed
  • ora-38471 : ROWIDs for table aliases cannot be null
  • ora-02807 : Allocation of memory for I/O vectors failed.
  • ora-24100 : error in ktz testing layer
  • ora-06303 : IPA: Message send error
  • ora-31532 : cannot enable change source string
  • ora-32156 : Cannot perform operation on stream
  • ora-15054 : disk "string" does not exist in diskgroup "string"
  • ora-23541 : tables do not match tables used while defining the redefinition
  • ora-24411 : Session pool already exists.
  • ora-02031 : no ROWID for fixed tables or for external-organized tables
  • ora-10576 : Give up restoring recovered datafiles to consistent state: some error occurred
  • ora-10841 : Default un-inintialized charact set form to SQLCS_IMPLICIT
  • ora-01549 : tablespace not empty, use INCLUDING CONTENTS option
  • ora-09280 : sllfcf: error closing file
  • ora-13521 : Unregister operation on local Database id (string) not allowed
  • ora-09850 : soacon: Archmon unable to lock named pipe.
  • ora-06779 : TLI Driver: error reading ccode
  • 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.