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 : 24-07-2017

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

  • ora-26096 : transfer size too small for row data (number bytes required)
  • ora-31450 : invalid value for change_table_name
  • ora-12422 : max policies exceeded
  • ora-08261 : ora_addr: cannot find name in nameserver
  • ora-13621 : The task_or object string is marked as a template and cannot perform the requested operation.
  • ora-02732 : osnrnf: cannot find a matching database alias
  • ora-31027 : Path name or handle string does not point to a resource
  • ora-01345 : must be a LogMiner coordinator process
  • ora-36886 : (XSSRF05) Error rewritting OLAP DML expression. Rewritten expression is greater than number bytes
  • ora-19736 : can not plug a tablespace into a database using a different national character set
  • ora-32037 : unsupported use of LEVEL in membership condition
  • ora-01093 : ALTER DATABASE CLOSE only permitted with no sessions connected
  • ora-12061 : invalid ALTER MATERIALIZED VIEW option
  • ora-27001 : unsupported device type
  • ora-06767 : TLI Driver: alloc failed during release
  • ora-28112 : failed to execute policy function
  • ora-25288 : AQ HTTP propagation encountered error, status-code number, string
  • ora-19753 : error writing to change tracking file
  • ora-13861 : Statistics aggregation for client identifier string is already enabled
  • ora-16165 : LGWR failed to hear from network server
  • ora-29926 : association already defined for the object
  • ora-02731 : osnrnf: malloc of buffer failed
  • ora-02777 : Stat failed on log directory
  • ora-07703 : error in archive text: need '/' after device type
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-00357 : too many members specified for log file, the maximum is string
  • ora-12851 : PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, string
  • ora-07486 : scg_get_inst: cannot convert(get) instance number lock.
  • ora-25186 : INCLUDING clause specified for index-organized table without OVERFLOW
  • ora-24806 : LOB form mismatch
  • 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.