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 : 19-08-2017

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-10571 : Test recovery canceled
  • ora-00057 : maximum number of temporary table locks exceeded
  • ora-31435 : an error occurred during the purge operation
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-30020 : UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
  • ora-28141 : error in creating audit index file
  • ora-01152 : file string was not restored from a sufficiently old backup
  • ora-09765 : osnmop: fork failed
  • ora-01967 : invalid option for CREATE CONTROLFILE
  • ora-14059 : partition "string": INITRANS value must be less than MAXTRANS value
  • ora-22603 : cannot add an attribute to the already generated TDS handle
  • ora-00365 : the specified log is not the correct next log
  • ora-23349 : cannot generate replication support for functions
  • ora-09988 : error while detaching SGA
  • ora-13291 : conversion error between the specified unit and standard unit
  • ora-39704 : permission to modify component registry entry denied
  • ora-29316 : datafile string been imported twice
  • ora-30202 : NULL pointer to OCIMsgh was passed to OCIMsg function
  • ora-33100 : (APABBR02) Value 'number' is not valid for the workspace object option.
  • ora-15075 : disk(s) are not visible cluster-wide
  • ora-12008 : error in materialized view refresh path
  • ora-22958 : This operation is not allowed in check constraints or triggers
  • ora-32611 : incorrect use of MODEL CV operator
  • ora-24151 : no evaluation context is associated with rule string.string or rule set string.string
  • ora-12523 : TNS:listener could not find instance appropriate for the client connection
  • ora-24304 : datatype not allowed for this call
  • ora-12809 : cannot set string_INSTANCES when mounted in exclusive mode
  • ora-02151 : invalid tablespace name: string
  • ora-22956 : The set contains no elements
  • ora-37140 : (XSCCOMP15) Cannot AGGREGATE partitioned variable workspace object using AGGMAP workspace object because you cannot use the base of a COMPRESSED COMPOSITE as a partition dimension.
  • 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.