ORA-16230: committing transaction string string string

Cause : Logical Standby apply was committing changes for the given transaction.

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 : 28-05-2017

ORA-16230 - committing transaction string string string
ORA-16230 - committing transaction string string string

  • ora-28336 : cannot encrypt SYS owned objects
  • ora-08430 : raw data missing leading sign
  • ora-00341 : log string of thread string, wrong log # string in header
  • ora-37185 : length of string (string) exceeds maximum (string)
  • ora-24272 : initialization value must be either F or T
  • ora-38490 : invalid name: quotes do not match
  • ora-14501 : object is not partitioned
  • ora-31405 : cannot make changes while change set string is advancing
  • ora-22055 : unknown sign flag value [string]
  • ora-12731 : invalid collation class in regular expression
  • ora-19107 : invalid XQueryX - unsupported construct - string
  • ora-02303 : cannot drop or replace a type with type or table dependents
  • ora-02368 : file string is not valid for this load operation
  • ora-24062 : Subscriber table string inconsistent with queue table string
  • ora-33458 : (ESDREAD09) Discarding compiled code for workspace object because number is now type string, whereas it was type string when the code was compiled.
  • ora-13195 : failed to generate maximum tile value
  • ora-24068 : cannot start queue string, queue table string is being migrated
  • ora-13223 : duplicate entry for string in SDO_GEOM_METADATA
  • ora-12345 : user string lacks CREATE SESSION privilege in database link (linkname string)
  • ora-03264 : cannot drop offline datafile of locally managed tablespace
  • ora-36972 : (XSRELTBL13) Relation workspace object must be dimensioned by workspace object.
  • ora-14254 : cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table
  • ora-02059 : ORA-2PC-CRASH-TEST-string in commit comment
  • ora-13113 : invalid tg_layer_id in sdo_topo_geometry constructor
  • ora-02842 : Client unable to fork a server
  • ora-26061 : Concurrent direct unloads is not allowed.
  • ora-16808 : unable to resolve the full path name
  • ora-10373 : parallel query server kill event
  • ora-02290 : check constraint (string.string) violated
  • ora-06318 : IPA: Local maximum number of connections exceeded
  • 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.