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-06-2017
ORA-16235

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

  • ora-15092 : I/O request size string is not a multiple of logical block size string
  • ora-24795 : Illegal string attempt made
  • ora-38422 : invalid datatype for the attribute: string
  • ora-01485 : compile bind length different from execute bind length
  • ora-31526 : could not find source table string.string for CDC change table string.string
  • ora-36816 : (XSTBLFUNC09) The workspace object dimension is of datatype string which does not support custom member upserts.
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-30568 : cannot drop log group - nonexistent log group
  • ora-16797 : database is not using a server parameter file
  • ora-16505 : site ID is invalid
  • ora-03251 : Cannot issue this command on SYSTEM tablespace
  • ora-27214 : skgfrsfe: file search failed
  • ora-08413 : invalid compiler type in FORMAT parameter at string
  • ora-00088 : command cannot be executed by shared server
  • ora-29973 : Unsupported query or operation during change notification registration
  • ora-29524 : wrong types of arguments in call to 'string'
  • ora-30447 : internal data for run number string is inconsistent
  • ora-16706 : no resource guard is available
  • ora-02771 : Illegal request time out value
  • ora-01939 : only the ADMIN OPTION can be specified
  • ora-01117 : adding file 'string' with illegal block size: string; limit is string
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-01026 : multiple buffers of size > 4000 in the bind list
  • ora-13194 : failed to decode supercell
  • ora-39169 : Local version of string cannot work with remote version of string.
  • ora-38788 : More standby database recovery is needed
  • ora-33443 : (ESDREAD14) Discarding compiled code for workspace object because analytic workspace string is not attached.
  • ora-13433 : GeoRaster metadata default RGB error
  • ora-04003 : sequence parameter string exceeds maximum size allowed (string digits)
  • ora-13451 : GeoRaster metadata scaling function error
  • 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.