ORA-25260: AQ latch cleanup testing event

Cause : N/A.

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

event used for AQ statistics latch cleanup testing.

update : 19-08-2017
ORA-25260

ORA-25260 - AQ latch cleanup testing event
ORA-25260 - AQ latch cleanup testing event

  • ora-24062 : Subscriber table string inconsistent with queue table string
  • ora-31151 : Cyclic definition encountered for string: "string"
  • ora-23315 : repcatlog version or request string is not supported by version string
  • ora-29543 : Java command string not yet implemented
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-32587 : Cannot drop nonexistent string supplemental logging
  • ora-01667 : cannot add any more tablespaces: limit of string exceeded
  • ora-13639 : The current operation was interrupted because it timed out.
  • ora-26715 : time limit reached
  • ora-31477 : could not detach LogMiner session during cleanup
  • ora-25117 : MIN/MAX/Block Number expected
  • ora-02470 : TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
  • ora-25258 : cannot register for notifications on an 8.0 style exception queue
  • ora-36762 : (XSLANGDM02) You cannot modify the string property of %J because analytic workspace string is attached in MULTI mode.
  • ora-06257 : NETNTT: cannot send command line to shadow process
  • ora-13433 : GeoRaster metadata default RGB error
  • ora-31067 : XML nodes must be updated with valid nodes and of the same type
  • ora-25018 : conflicting trigger string already exists
  • ora-06300 : IPA: Disconnect failure
  • ora-19907 : recovery time or SCN does not belong to recovered incarnation
  • ora-36401 : (XSSPROPOTYPE) Property string may only be applied to objects of type string.
  • ora-12606 : TNS: Application timeout occurred
  • ora-07431 : fork failed
  • ora-30101 : unknown parameter name 'string'
  • ora-12814 : only one CACHE or NOCACHE clause may be specified
  • ora-32106 : array fetch not allowed without setBuffer on all columns
  • ora-02255 : obsolete 7.1.5
  • ora-07843 : sllfcl: LIB$FREE_VM failure
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-00291 : numeric value required for PARALLEL option
  • 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.