ORA-16235: DDL skipped because import has occurred

Cause : An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export.

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 : 18-08-2017
ORA-16235

ORA-16235 - DDL skipped because import has occurred
ORA-16235 - DDL skipped because import has occurred

  • ora-28120 : driving context already exists
  • ora-00128 : this command requires a dispatcher name
  • ora-31073 : Resource not retrieved using path name
  • ora-32315 : REFRESH FAST of "string"."string" unsupported after mixed DML and Direct Load
  • ora-27007 : failed to open file
  • ora-39202 : Data cannot be filtered or selected in string jobs.
  • ora-32156 : Cannot perform operation on stream
  • ora-13230 : failed to create temporary table [string] during R-tree creation
  • ora-30488 : argument should be a function of expressions in PARTITION BY
  • ora-30020 : UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
  • ora-31196 : XML nodes over string in size cannot be printed
  • ora-19235 : XQ0015 - unsupported must-understand extension
  • ora-09822 : Translation of audit file name failed.
  • ora-22277 : cannot use two different locators to modify the same LOB
  • ora-16136 : Managed Standby Recovery not active
  • ora-19506 : failed to create sequential file, name="string", parms="string"
  • ora-19634 : filename required for this function
  • ora-16954 : SQL parse error.
  • ora-01081 : cannot start already-running ORACLE - shut it down first
  • ora-25264 : cant get signature for this queue
  • ora-07446 : sdnfy: bad value 'string' for parameter string.
  • ora-19695 : fixed table x$krbmsft has not been populated
  • ora-31432 : invalid source table
  • ora-30205 : invalid Character set
  • ora-16531 : unable to post message
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-07484 : snlkput: cannot convert(put) lock.
  • ora-27210 : syntax error in device PARMS
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-14100 : partition extended table name cannot refer to a remote object
  • 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.