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 : 23-09-2017

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

  • ora-19525 : temporary file for the clone database must be renamed
  • ora-08448 : syntax error in DECIMAL-POINT environment clause
  • ora-06322 : IPA: Fatal shared memory error
  • ora-19641 : backup datafile checkpoint is SCN string time string
  • ora-37076 : (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute.
  • 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-09360 : Windows 3.1 Two-Task driver unable to allocate context area
  • ora-31117 : Table "string"."string" is not resource metadata enabled
  • ora-24006 : cannot create QUEUE, string already exists
  • ora-03289 : partition name and segment type do not match
  • ora-37120 : MDX string is null
  • ora-24342 : unable to destroy a mutex
  • ora-28261 : CURRENT_USER can not be used in PLSQL Definer's Right procedure.
  • ora-02027 : multi-row UPDATE of LONG column is not supported
  • ora-19667 : cannot do incremental restore of datafile string
  • ora-01108 : file string is in backup or media recovery
  • ora-13192 : failed to read number of element rows
  • ora-16408 : Incompatible archival Redo Branch lineage
  • ora-22060 : argument [string] is an invalid or uninitialized number
  • ora-40286 : remote operations not permitted on mining models
  • ora-38750 : FLASHBACK DATABASE may not be performed using a dispatcher.
  • ora-36863 : (XSTFRC03) The OLAPRC_TABLE function encountered an error while parsing the COLUMNMAP.
  • ora-29936 : NULL association is allowed only with a column or an index
  • ora-00104 : deadlock detected; all public servers blocked waiting for resources
  • ora-02167 : LOGFILE clause specified more than once
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-21600 : path expression too long
  • ora-32622 : illegal multi-cell reference
  • ora-16015 : log string sequence# string not archived, media recovery disabled
  • ora-01510 : error in deleting log files
  • 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.