ORA-29389: too many errors during validation

Cause : The number of errors detected during validation is too high.

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

Perform the necessary actions to remove some errors, and retry validation.

update : 16-08-2017

ORA-29389 - too many errors during validation
ORA-29389 - too many errors during validation

  • ora-12469 : no user levels found for user string and policy string
  • ora-30456 : 'string.string' cannot be refreshed because of insufficient privilege
  • ora-38746 : error occurred while restoring data block (file# string, block# string)
  • ora-01316 : Already attached to a Logminer session
  • ora-12429 : label list range exceeded
  • ora-01925 : maximum of string enabled roles exceeded
  • ora-27197 : skgfprs: sbtpcrestore returned error
  • ora-31673 : worker process interrupt for normal exit by master process
  • ora-01650 : unable to extend rollback segment string by string in tablespace string
  • ora-23340 : incorrect resolution method string
  • ora-40286 : remote operations not permitted on mining models
  • ora-08183 : Flashback cannot be enabled in the middle of a transaction
  • ora-29663 : Unable to find a method that matches one or more of the functions
  • ora-30757 : cannot access type information
  • ora-33460 : (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string.
  • ora-38851 : cannot mark the current instance (redo thread) as disabled
  • ora-12951 : Attempt to change default permanent tablespace to temporary
  • ora-14030 : non-existent partitioning column in CREATE TABLE statement
  • ora-13203 : failed to read USER_SDO_GEOM_METADATA view
  • ora-01605 : missing numbers in clause "string" of string
  • ora-00109 : invalid value for attribute string: string
  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-15205 : requested mirror side unavailable
  • ora-13209 : internal error while reading SDO_INDEX_METADATA table
  • ora-36740 : A CHILDLOCK was detected in your valueset
  • ora-22316 : input type is not a collection type
  • ora-01657 : invalid SHRINK option value
  • ora-35017 : (QFCHECK06) The Analytic Workspace and EIF file definitions of workspace object have different partitioning methods.
  • ora-02338 : missing or invalid column constraint specification
  • ora-33092 : (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.
  • 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.