ORA-23532: tables with different synchronization mechanisms are in the same group

Cause : Tables belonging to the same replication group were specified to be cached with different synchronization mechanisms.

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

Do not specify different synchronization mechanisms while caching tables belonging to the same replication group.

update : 27-04-2017
ORA-23532

ORA-23532 - tables with different synchronization mechanisms are in the same group
ORA-23532 - tables with different synchronization mechanisms are in the same group

  • ora-22630 : attribute [string] is null or it is not well-formed
  • ora-38488 : attribute set already assigned to the column storing expressions
  • ora-07483 : snlkget: cannot convert(get) lock.
  • ora-24815 : Invalid character set form
  • ora-16725 : the phase supplied to resource guard is invalid
  • ora-00265 : instance recovery required, cannot set ARCHIVELOG mode
  • ora-08191 : Flashback Table operation is not supported on remote tables
  • ora-19559 : error sending device command: string
  • ora-26692 : invalid value string, string should be in string format
  • ora-32125 : Attribute type is not appropriate
  • ora-16166 : LGWR network server failed to send remote message
  • ora-23614 : Script string does not exist
  • ora-14278 : column type or size mismatch in EXCHANGE SUBPARTITION
  • ora-15009 : ASM disk "string" does not exist
  • ora-28534 : Heterogeneous Services preprocessing error
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-08234 : smsget: cannot get instance listener address
  • ora-29829 : implementation type does not exist
  • ora-30110 : syntax error at 'string'
  • ora-32011 : cannot restore SPFILE to location already being used by the instance
  • ora-02845 : Invalid value for the timing wanted flag
  • ora-02256 : number of referencing columns must match referenced columns
  • ora-06812 : TLI Driver: could not read the ethernet driver's node address
  • ora-22851 : invalid CHUNK LOB storage option value
  • ora-16823 : redo transport mode is incompatible for current operation
  • ora-28503 : bind value cannot be translated into SQL text for non-Oracle system
  • ora-13644 : The user "string" is invalid.
  • ora-39767 : finish is not allowed when unloaded stream data exists
  • ora-07579 : spini: $DCLEXH failure
  • ora-00828 : specified value of shared_pool_reserved_size inconsistent with internal settings
  • 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.