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 : 28-04-2017
ORA-16235

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

  • ora-07509 : scgfal: $deq parent lock unexpected return
  • ora-00087 : command cannot be executed on remote instance
  • ora-19914 : unable to encrypt backup
  • ora-10656 : Table is in unusable state due to incomplete operation
  • ora-09855 : removeCallback: bad message format.
  • ora-38502 : invalid XML tag: string
  • ora-32733 : Error occurred when executing Parallel Oradebug
  • ora-28043 : invalid bind credentials for DB-OID connection
  • ora-09978 : skxfqhdel: Error Disconnecting from another endpoint.
  • ora-13293 : cannot specify unit for geometry without a georeferenced SRID
  • ora-01555 : snapshot too old: rollback segment number string with name "string" too small
  • ora-00020 : maximum number of processes (string) exceeded
  • ora-16409 : Archive log switchover reference number mismatch
  • ora-26507 : null master connection
  • ora-34487 : (MXMAINT08) You cannot string values of non-unique concat dimension workspace object.
  • ora-14297 : Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-32144 : Cannot perform operation on a null interval
  • ora-12993 : tablespace 'string' is offline, cannot drop column
  • ora-00216 : control file could not be resized for migration from 8.0.2
  • ora-01253 : cannot start online backup - file string in recovery manager backup
  • ora-02303 : cannot drop or replace a type with type or table dependents
  • ora-12354 : secondary object being dropped
  • ora-09316 : szrpc: unable to verify password for role
  • ora-24756 : transaction does not exist
  • ora-26007 : invalid value for SETID or OID column
  • ora-09961 : Unable to restore termination signal handler
  • ora-15113 : alias name 'string' refers to a directory
  • ora-39126 : Worker unexpected fatal error in string [string] string
  • ora-30201 : Unable to load NLS data 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.