ORA-26532: replication parallel push simulated site failure

Cause : A parallel push executed with event 26531 enabled raises this error to simulation failure of network or destination site.

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

Do not enable the event for normal operation.

update : 26-05-2017
ORA-26532

ORA-26532 - replication parallel push simulated site failure
ORA-26532 - replication parallel push simulated site failure

  • ora-24047 : invalid agent name string, agent name should be of the form NAME
  • ora-08177 : can't serialize access for this transaction
  • ora-32808 : message system link string does not exist
  • ora-01208 : data file is an old version - not accessing current version
  • ora-24240 : invalid database access descriptor (DAD) name
  • ora-16800 : redo transport service for a standby database incorrectly set to ALTERNATE
  • ora-39022 : Database version string is not supported.
  • ora-12560 : TNS:protocol adapter error
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-16181 : SGA specified for Logical Standby is too large
  • ora-30002 : SYS_CONNECT_BY_PATH function is not allowed here
  • ora-31187 : Cannot Add Node 'string' (type='string') to Simple Type Node 'string'
  • ora-00378 : buffer pools cannot be created as specified
  • ora-31512 : name cannot contain double quotation marks
  • ora-01172 : recovery of thread string stuck at block string of file string
  • ora-16161 : Cannot mix standby and online redo log file members for group string
  • ora-29877 : failed in the execution of the ODCIINDEXUPDATE routine
  • ora-12455 : internal error in Label Security MMON cleanup task
  • ora-00068 : invalid value string for parameter string, must be between string and string
  • ora-24782 : Cannot detach from a non-migratable transaction
  • ora-29952 : cannot issue DDL on a domain index partition marked as LOADING
  • ora-31048 : Unsaved resources cannot be updated
  • ora-04089 : cannot create triggers on objects owned by SYS
  • ora-01222 : MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
  • ora-24121 : both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
  • ora-25954 : missing primary key or unique constraint on dimension
  • ora-31208 : DBMS_LDAP: PL/SQL - Invalid LDAP Message.
  • ora-35023 : (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions.
  • ora-13435 : GeoRaster metadata dimension inconsistent
  • 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.