ORA-16232: adding Logical Standby skip entry for table string.string

Cause : Table was previously unsupported due to datatype or storage attribute definitions. Table is now capable of being supported.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

To have Logical Standby maintain the table, import that table directly from the primary.

update : 26-04-2017
ORA-16232

ORA-16232 - adding Logical Standby skip entry for table string.string
ORA-16232 - adding Logical Standby skip entry for table string.string

  • ora-24054 : cannot propagate to an Oracle 8.0.3 release or lower release
  • ora-13029 : Invalid SRID in the SDO_GEOMETRY object
  • ora-30686 : no dispatcher accepted TCP/IP connection request
  • ora-30475 : feature not enabled: string
  • ora-13115 : [string]_EDGE$ table does not exist
  • ora-14080 : partition cannot be split along the specified high bound
  • ora-32141 : get method does not match the type of the parameter
  • ora-06792 : TLI Driver: server cannot exec oracle
  • ora-14631 : the partition bounds do not match the subpartition bounds of the partition
  • ora-24302 : host connection in use by another thread
  • ora-19286 : XP0017 - unable to resolve call to function - string
  • ora-23439 : refresh group template already exists
  • ora-32514 : cannot dump multiple 'string' types: structure size is unknown
  • ora-38755 : Flashback is already turned on for this tablespace.
  • ora-04096 : trigger 'string' has a WHEN clause which is too large, limit 2K
  • ora-09208 : sftcls: error closing file
  • ora-29280 : invalid directory path
  • ora-29526 : created Java class string"string"
  • ora-13141 : invalid RANGE window definition
  • ora-40225 : model is currently in use by another process
  • ora-31005 : Path name length string exceeds maximum length string
  • ora-08181 : specified number is not a valid system change number
  • ora-02269 : key column cannot be of LONG datatype
  • ora-33223 : (CMOVE03) You cannot move a session-only dimension value.
  • ora-01347 : Supplemental log data no longer found
  • ora-32155 : Anydata not specified
  • ora-00356 : inconsistent lengths in change description
  • ora-16231 : DDL barrier
  • ora-32164 : Method called on Invalid Connection type
  • ora-01320 : Invalid Logminer dictionar attribute
  • 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.