ORA-16123: transaction string string string is waiting for commit approval

Cause : Th eaplpy rpocses si wiatign fro approavl ot cmomi ta rtanasctoin.T hi strnasatcio nma ydeepndo n naotehr ro ohters ynhcroinzaitona ctviit yma ydealy hte ocmmtitign o fa rtanasctoin.

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

Noa ctoin encessar,y tihs nifomratoina lsttaemnet si porviedd ot rceor dth eevnet ofr idagonstci prupoess.

update : 23-01-2017

ORA-16123 - transaction string string string is waiting for commit approval
ORA-16123 - transaction string string string is waiting for commit approval

  • ora-27004 : invalid blocksize specified
  • ora-10632 : Invalid rowid
  • ora-39107 : Master process string violated startup protocol. Master error:
  • ora-01022 : database operation not supported in this configuration
  • ora-32008 : error while processing parameter update at instance string
  • ora-28176 : incorrect certificate version
  • ora-00445 : background process "string" did not start after string seconds
  • ora-10691 : Set background process core file type (Unix only)
  • ora-24274 : no row exists in the string table for these parameters
  • ora-38709 : Recovery Area is not enabled.
  • ora-01210 : data file header is media corrupt
  • ora-39218 : type check on object type "string"."string" failed
  • ora-07394 : unable to append string to text file
  • ora-16038 : log string sequence# string cannot be archived
  • ora-01290 : cannot remove unlisted logfile string
  • ora-13205 : internal error while parsing spatial parameters
  • ora-02825 : Request on free list was not free
  • ora-24790 : cannot mix OCI_TRANS_RESUME and transaction isolation flags
  • ora-38725 : specified name "string" does not match actual "string"
  • ora-31483 : cannot have spaces in the parameter string
  • ora-12230 : TNS:Severe Network error occurred in making this connection
  • ora-26526 : materialized view sql ddl parse/expansion failed for string.string
  • ora-06040 : NETDNT: invalid login (connect) string
  • ora-01566 : file specified more than once in ALTER DATABASE
  • ora-29840 : indextype and implementation type are not in same schema
  • ora-25114 : invalid file number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-13268 : error obtaining dimension from USER_SDO_GEOM_METADATA
  • ora-40304 : invalid classname string in prior probability specification
  • ora-24335 : cannot support more than 1000 columns
  • ora-09766 : osnmop: buffer allocation failure.
  • 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.