ORA-16204: DDL successfully applied

Cause : A DDL statement has successfully commited on the logical standby database.

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

ORA-16204 - DDL successfully applied
ORA-16204 - DDL successfully applied

  • ora-01951 : ROLE 'string' not granted to 'string'
  • ora-01256 : error in locking database file string
  • ora-16136 : Managed Standby Recovery not active
  • ora-28268 : Exceeded the maximum allowed size for Context information in a session
  • ora-12832 : Could not allocate slaves on all specified instances
  • ora-32412 : encrypted column "string" not allowed in the materialized view log
  • ora-22293 : LOB already opened in the same transaction
  • ora-12205 : TNS:could not get failed addresses
  • ora-14260 : incorrect physical attribute specified for this partition
  • ora-16233 : The table string.string is unsupported now
  • ora-22287 : invalid or modified directory occurred during string operation
  • ora-33048 : (XSAGDNGL23) In AGGMAP workspace object, the relation workspace object and the relation workspace object are both over the same base dimension.
  • ora-32735 : DIAG process is not running in the instance
  • ora-07479 : scgcmn: cannot open or convert lock.
  • ora-09709 : soacon: failed to accept a connection.
  • ora-14082 : new partition name must differ from that of any other partition of the object
  • ora-25466 : data not specified for variable name: string
  • ora-31020 : The operation is not allowed, Reason: string
  • ora-14621 : cannot add subpartition when DEFAULT subpartition exists
  • ora-30105 : 'string' is not a legal boolean for 'string'
  • ora-13754 : "SQL Tuning Set" "string" does not exist for user "string".
  • ora-01599 : failed to acquire rollback segment (string), cache space is full
  • ora-23302 : application raised communication failure during deferred RPC
  • ora-22055 : unknown sign flag value [string]
  • ora-24005 : must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables
  • ora-19225 : XP0005 - XQuery static type error: expected non empty type got empty sequence
  • ora-14014 : maximum number of partitioning columns is 16
  • ora-40004 : penalty must be negative for BLAST-N
  • ora-16514 : the request was not found
  • ora-39104 : cannot call this function from a SQL parallel query slave process
  • 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.