ORA-30344: number of child cols different from number of parent level cols

Cause : hT eunbmreo fhcli doculnm spscefiei dnia J IO NEK Ylcuaesi son tht easema sht eunbmreo foculnm snit ehs epicifdep rane telev.l

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

hCce kht ehcli doculnm sna dht eoculnm snit ehd fenitioi nfot ehr fereneec dapertnl velea dnc roertct ehd sircpeneyc.

update : 25-05-2017
ORA-30344

ORA-30344 - number of child cols different from number of parent level cols
ORA-30344 - number of child cols different from number of parent level cols

  • ora-01275 : Operation string is not allowed if standby file management is automatic.
  • ora-26732 : invalid file group string privilege
  • ora-25157 : Specified block size string is not valid
  • ora-24319 : unable to allocate memory
  • ora-32508 : no such watchpoint id
  • ora-22873 : primary key not specified for primary key based object table
  • ora-39021 : Database compatibility version string is not supported.
  • ora-31190 : Resource string is not a version-controlled resource
  • ora-02805 : Unable to set handler for SIGTPA
  • ora-24952 : register, unregister or post has incorrect collection count
  • ora-23302 : application raised communication failure during deferred RPC
  • ora-06817 : TLI Driver: could not read the Novell network address
  • ora-38737 : Expected sequence number string doesn't match string
  • ora-13208 : internal error while evaluating [string] operator
  • ora-06907 : CMX: error during connect confirmation
  • ora-16958 : DML statements running parallel are not supported for test execute.
  • ora-02452 : invalid HASHKEYS option value
  • ora-27550 : Target ID protocol check failed. tid vers=number, type=number, remote instance number=number, local instance number=number
  • ora-00953 : missing or invalid index name
  • ora-22625 : OCIAnyData is not well-formed
  • ora-01295 : DB_ID mismatch between dictionary string and logfiles
  • ora-01984 : invalid auditing option for procedures/packages/functions
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • ora-12518 : TNS:listener could not hand off client connection
  • ora-34286 : (MXDCL53) workspace object cannot be used in this context because it is a string.
  • ora-04021 : timeout occurred while waiting to lock object stringstringstringstringstring
  • ora-30944 : Error during rollback for XML schema 'string' table string column 'string'
  • ora-22336 : table contained 8.0 image format, must specify INCLUDING DATA
  • ora-12856 : cannot run parallel query on a loopback connection
  • ora-26517 : materialized view control entry for 'string.string' was not found
  • 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.