ORA-25405: transaction status unknown

Cause : A failure occured while a transaction was attempting to commit. Failover could not automatically determine instance status.

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

The user must determine the transaction's status manually.

update : 20-08-2017
ORA-25405

ORA-25405 - transaction status unknown
ORA-25405 - transaction status unknown

  • ora-12418 : user string not found
  • ora-09812 : Unable to get user clearance from connection
  • ora-10632 : Invalid rowid
  • ora-17626 : ksfdcre: string file exists
  • ora-00438 : %s Option not installed
  • ora-27213 : failed to unload Media Management Library
  • ora-24003 : Queue table index string inconsistent with queue table string
  • ora-01119 : error in creating database file 'string'
  • ora-32103 : error from OCI call
  • ora-07710 : sksaprs: file name buffer too small
  • ora-31435 : an error occurred during the purge operation
  • ora-27032 : failed to obtain file size limit
  • ora-25457 : evaluation function string returns failure
  • ora-23327 : imported deferred rpc data does not match string of importing db
  • ora-02793 : Close of asynchronous I/O failed.
  • ora-07247 : skgfrfms, skgfrnms: read error, unable to read block from database file
  • ora-12680 : Native services disabled but required
  • ora-02043 : must end current transaction before executing string
  • ora-19672 : media management software returned invalid file status
  • ora-24020 : Internal error in DBMS_AQ_IMPORT_INTERNAL, string
  • ora-24148 : cannot drop rule string.string with dependents
  • ora-16640 : CRS warns that multiple instances may still be running
  • ora-32763 : Turn off N-Pass Temp LOB cleanup
  • ora-22805 : cannot insert NULL object into object tables or nested tables
  • ora-10645 : Recursive Extension in SYSTEM tablespace during migration
  • ora-01500 : failure in getting date/time
  • ora-14500 : LOCAL option not valid without partition name
  • ora-00085 : current call does not exist
  • ora-16140 : standby online logs have not been recovered
  • ora-24805 : LOB type 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.