ORA-16125: large transaction string string string is waiting for more data

Cause : The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.

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

No action necessary, this informational statement is provided to record the event for diagnostic purposes.

update : 22-08-2017
ORA-16125

ORA-16125 - large transaction string string string is waiting for more data
ORA-16125 - large transaction string string string is waiting for more data

  • ora-16518 : unable to allocate virtual instance id
  • ora-01184 : logfile group string already exists
  • ora-22851 : invalid CHUNK LOB storage option value
  • ora-00216 : control file could not be resized for migration from 8.0.2
  • ora-02054 : transaction string in-doubt
  • ora-01294 : error occurred while processing information in dictionary file string, possible corruption
  • ora-06523 : Maximum number of arguments exceeded
  • ora-12923 : tablespace string is in force logging mode
  • ora-01999 : password file cannot be updated in SHARED mode
  • ora-02447 : cannot defer a constraint that is not deferrable
  • ora-25275 : Test support for buffered queues
  • ora-32407 : cannot exclude new values when materialized view log includes new values
  • ora-15073 : diskgroup string is mounted by another ASM instance
  • ora-08449 : invalid numeric symbol found in picture mask
  • ora-02477 : can not perform parallel direct load on object string
  • ora-07284 : sksaprd: volume size specification not terminated properly.
  • ora-37140 : (XSCCOMP15) Cannot AGGREGATE partitioned variable workspace object using AGGMAP workspace object because you cannot use the base of a COMPRESSED COMPOSITE as a partition dimension.
  • ora-00452 : foreground process unexpectedly terminated with error string
  • ora-19658 : cannot inspect string - file is from different resetlogs
  • ora-32020 : SID=* clause needed to modify this parameter
  • ora-24505 : cannot change character set id on the handle
  • ora-00236 : snapshot operation disallowed: mounted control file is a backup
  • ora-22610 : error while adding a scalar to the image handle
  • ora-16096 : ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY
  • ora-12202 : TNS:internal navigation error
  • ora-13296 : incorrect coordinate system specification
  • ora-03237 : Initial Extent of specified size cannot be allocated in tablespace (string)
  • ora-14005 : missing RANGE keyword
  • ora-36841 : (XSLMGEN11) Dimension string.string!string was not found
  • ora-08448 : syntax error in DECIMAL-POINT environment clause
  • 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.