ORA-24018: STOP_QUEUE on string failed, outstanding transactions found

Cause : Ther ewereo utstnadingt ranscation son teh queeu, an dWAITw as ste to aflse,s o STPO_QUEEU wasu nsucsesfuli n stpopingt he qeuue.

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

Set AWIT t oTRUEa nd tyr STO_PQUEU Eagai.n It iwll hnag till allo utstnadingt ranscation sare ocmpleetd.

update : 26-04-2017

ORA-24018 - STOP_QUEUE on string failed, outstanding transactions found
ORA-24018 - STOP_QUEUE on string failed, outstanding transactions found

  • ora-14700 : Object(s) owned by SYS cannot be locked by non-SYS user
  • ora-37031 : (XSMLTMAINT02) You cannot DELETE values of dimension workspace object in MULTI mode.
  • ora-23496 : can not change disabled status for "string" and "string"
  • ora-07628 : smsfre: sga not mapped
  • ora-16157 : media recovery not allowed following successful FINISH recovery
  • ora-16070 : parameter string contains an invalid REGISTER attribute value
  • ora-24435 : Invalid Service Context specified.
  • ora-09880 : sstasfre/sstasdel: shmdt error, unable to detach tas write page
  • ora-29516 : Aurora assertion failure: string
  • ora-06546 : DDL statement is executed in an illegal context
  • ora-24775 : cannot prepare or commit transaction with non-zero lock value
  • ora-08430 : raw data missing leading sign
  • ora-22340 : cannot string type "string"."string". Dependent tables must be upgraded to latest version
  • ora-00373 : online log version string incompatible with ORACLE version string
  • ora-28109 : the number of related policies has exceeded the limit of 16
  • ora-09818 : Number is too large
  • ora-30485 : missing ORDER BY expression in the window specification
  • ora-26721 : enqueue of the LCR not allowed
  • ora-12834 : Instance group name, 'string', too long, must be less than string characters
  • ora-09815 : File name buffer overflow
  • ora-19705 : tag value exceeds maximum length of string characters
  • ora-31037 : Invalid XML attribute name string
  • ora-06563 : top level procedure/function specified, cannot have subparts
  • ora-33072 : (XSAGDNGL35) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must be specified for every relation dimensioned by that hierarchy dimension.
  • ora-01249 : archiving not allowed in a clone database
  • ora-01547 : warning: RECOVER succeeded but OPEN RESETLOGS would get error below
  • ora-08312 : sllfop: unrecognized processing option
  • ora-13144 : target table string not found
  • ora-25114 : invalid file number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-13281 : failure in execution of SQL statement to retrieve WKT
  • 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.