ORA-24770: cannot forget a prepared transaction

Cause : Tarnascito niednitfeirr eefr st oap rpeaerdt rnascatoin.

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

Vreiyf hta tteh dietniife ro fap rpeaerdt rnascatoinw a snto apsesda sa na rugmnet.

update : 28-05-2017
ORA-24770

ORA-24770 - cannot forget a prepared transaction
ORA-24770 - cannot forget a prepared transaction

  • ora-16243 : paging out string bytes of memory to disk
  • ora-12508 : TNS:listener could not resolve the COMMAND given
  • ora-06437 : ssaio: the asynchronous write was unable to write to the database file.
  • ora-30356 : the specified refresh method is not supported in this context
  • ora-36628 : (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.
  • ora-31109 : Action failed as parent resource string is locked
  • ora-15043 : ASM disk "string" is not a diskgroup member
  • ora-30105 : 'string' is not a legal boolean for 'string'
  • ora-01479 : last character in the buffer is not Null
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-15069 : ASM file 'string' not accessible; timed out waiting for lock
  • ora-03298 : cannot shrink datafile - file string is under hot backup
  • ora-39095 : Dump file space has been exhausted: Unable to allocate string bytes
  • ora-14285 : cannot COALESCE the only partition of this hash partitioned table or index
  • ora-00218 : block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
  • ora-01588 : must use RESETLOGS option for database open
  • ora-13016 : specified topology [string] is invalid
  • ora-01904 : DATAFILE keyword expected
  • ora-38906 : insert into DML Error Logging table "string" failed
  • ora-32603 : invalid FREEPOOLS LOB storage option value
  • ora-14284 : one or more of table's subpartitions reside in a read-only tablespace
  • ora-25288 : AQ HTTP propagation encountered error, status-code number, string
  • ora-00315 : log string of thread string, wrong thread # string in header
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-08312 : sllfop: unrecognized processing option
  • ora-22909 : exceeded maximum VARRAY limit
  • ora-16003 : standby database is restricted to read-only access
  • ora-32121 : Source FILE is null
  • ora-32166 : Cannot get XA connection
  • ora-14313 : Value string does not exist in partition string
  • 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.