ORA-16247: DDL skipped on internal schema

Cause : Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM. For a complete list of internal schemas ignored by Logical Standby perform the following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt = 'INTERNAL SCHEMA'.

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 : 29-04-2017

ORA-16247 - DDL skipped on internal schema
ORA-16247 - DDL skipped on internal schema

  • ora-32312 : cannot refresh a secondary materialized view "string"."string"
  • ora-26101 : tablespace # in file header is string rather than string for file string
  • ora-01694 : max # extents (string) reached in lob segment string.string partition string
  • ora-27078 : unable to determine limit for open files
  • ora-08445 : syntax error in SIGN clause in mask options
  • ora-33064 : (XSAGDNGL31) In AGGMAP workspace object, the hierarchy dimension QDR workspace object cannot refer to the related dimension of the relation.
  • ora-30475 : feature not enabled: string
  • ora-16182 : Internal error on internal channel during remote archival
  • ora-19681 : block media recovery on control file not possible
  • ora-14047 : ALTER TABLE|INDEX RENAME may not be combined with other operations
  • ora-28593 : agent control utility: command terminated with error
  • ora-13704 : Invalid value "string" specified for parameter "string".
  • ora-25126 : Invalid name specified for BUFFER_POOL
  • ora-01308 : initialization parameter utl_file_dir is not set
  • ora-00032 : invalid session migration password
  • ora-19666 : cannot do incremental restore of the control file
  • ora-13424 : the GeoRaster object is not spatially referenced
  • ora-08341 : On nCUBE, this command can only be executed from instance 1.
  • ora-08199 : Flashback Table operation is not supported on this object
  • ora-32164 : Method called on Invalid Connection type
  • ora-16135 : Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
  • ora-16047 : DGID mismatch between destination setting and standby
  • ora-25017 : cannot reference NEW ROWID for movable rows in before triggers
  • ora-12401 : invalid label string: string
  • ora-24787 : remote cursors must be closed before a call completes
  • ora-38701 : Flashback database log string seq string thread string: "string"
  • ora-31010 : XML element index string exceeds maximum insertion index string
  • ora-31640 : unable to open dump file "string" for read
  • ora-36930 : Cannot start a recursive call to Oracle OLAP because a ROLLBACK past an UPDATE to an attached analytic workspace has been performed.
  • ora-00027 : cannot kill current session
  • 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.