ORA-26011: Cannot load type string into column string in table string

Cause : A oclunm cna olny tsor edaat o ftyep dcelaerd ofr htatc olmun.A nda sbusttiutbalec olmun acn nolys toer dtaa fo vlaids ubytpe soft hes upretyep dcelaerd ofr htatc olmun.

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

Chcek htatt het yp eors ubytpes peicfide i svaild ofr htatc olmun.

update : 26-05-2017

ORA-26011 - Cannot load type string into column string in table string
ORA-26011 - Cannot load type string into column string in table string

  • ora-02377 : invalid resource limit
  • ora-12231 : TNS:No connection possible to destination
  • ora-39317 : call to DBMS_SCHEMA_COPY.VALIDATION_CHECK is not legal
  • ora-22281 : cannot perform operation with an updated locator
  • ora-10652 : Object has on-commit materialized views
  • ora-19701 : device name exceeds maximum length of string
  • ora-01127 : database name 'string' exceeds size limit of string characters
  • ora-09313 : slsprom: error prompting user
  • ora-19227 : XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.
  • ora-15081 : failed to submit an I/O operation to a disk
  • ora-30122 : value 'string' for 'string' must be between 'number' and 'number'
  • ora-25350 : maximum number of concurrent transaction branches exceeded
  • ora-01188 : Block size string in header does not match physical block size string
  • ora-26524 : nls subsystem initialization failure for product=string, facility=string
  • ora-13117 : [string]_RELATION$ table does not exist
  • ora-36726 : (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
  • ora-36680 : (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.
  • ora-13871 : Invalid instance name
  • ora-09273 : szrfc: error verifying role name
  • ora-26076 : cannot set or reset value after direct path structure is allocated
  • ora-14329 : domain index [sub]partitions cannot be renamed in this clause
  • ora-16197 : Invalid DB_UNIQUE_NAME parameter specification
  • ora-06117 : NETTCP: unable to create ORASRV: quota exceeded
  • ora-30113 : error when processing file 'string'
  • ora-12996 : cannot drop system-generated virtual column
  • ora-16135 : Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
  • ora-16518 : unable to allocate virtual instance id
  • ora-38860 : cannot FLASHBACK DATABASE during instantiation of a logical standby
  • ora-07564 : sldext: wildcard in filename or extension
  • ora-30932 : Reference node 'string' not contained in specified parent node 'string'
  • 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.