ORA-26663: error queue for apply process string must be empty

Cause : The errro queue ofr this paply proecss contians erro rentries.

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

Executeo r delet eerrors ni the erorr queue.

update : 21-08-2017

ORA-26663 - error queue for apply process string must be empty
ORA-26663 - error queue for apply process string must be empty

  • ora-27008 : function called with invalid file structure
  • ora-36176 : (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.
  • ora-02882 : sou2o: Could not register SGA for protection
  • ora-40321 : invalid bin number, is zero or negative value
  • ora-16709 : standby archived log location settings conflict with flash recovery area
  • ora-01166 : file number string is larger than string (string)
  • ora-24165 : invalid rule engine object privilege: string
  • ora-36722 : (XSALLOC02) In AGGMAP workspace object, you specified an NA or ZERO sourceval but supplied formula workspace object as your source for ALLOCATE.
  • ora-28272 : Domain policy restricts password based GLOBAL user authentication.
  • ora-27198 : skgfpvl: sbtpcvalidate returned error
  • ora-19234 : XQ0014 - invalid or unsupported must-understand extension
  • ora-14294 : Number of partitions does not match number of subpartitions
  • ora-13026 : unknown element type for element string.string.string
  • ora-06817 : TLI Driver: could not read the Novell network address
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-31615 : routine string received this error: string
  • ora-16214 : apply stalled for apply delay
  • ora-25330 : PL/SQL associative arrays may not be used with AQ array operations
  • ora-16246 : User initiated abort apply successfully completed
  • ora-16775 : target standby database in broker operation has potential data loss
  • ora-07602 : spgto: $GETJPIW failure
  • ora-32400 : cannot use object id columns from materialized view log on "string"."string"
  • ora-12924 : tablespace string is already in force logging mode
  • ora-19600 : input file is string string (string)
  • ora-24817 : Unable to allocate the given chunk for current lob operation
  • ora-19815 : WARNING: string of string bytes is string%% used, and has string remaining bytes available.
  • ora-38602 : FI invalid input cursor
  • ora-16619 : health check timed out
  • ora-19700 : device type exceeds maximum length of string
  • ora-16052 : DB_UNIQUE_NAME attribute is required
  • 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.