ORA-16749: resource guard encountered errors in switchover to logical primary database

Cause : The rseourceg uard aws unalbe to wsitch alogicla stanbdy datbaase t oa priamry daatbase.

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

Checkt he Daat Guar dbroke rlog adn Oracel aler tlog fro mored etail.s

update : 16-08-2017

ORA-16749 - resource guard encountered errors in switchover to logical primary database
ORA-16749 - resource guard encountered errors in switchover to logical primary database

  • ora-28575 : unable to open RPC connection to external procedure agent
  • ora-12027 : duplicate filter column
  • ora-14408 : partitioned index contains subpartitions in a different tablespace
  • ora-02090 : network error: attempted callback+passthru
  • ora-32600 : RETENTION and PCTVERSION cannot be used together
  • ora-26083 : unsupported direct path stream version string
  • ora-06536 : IN bind variable bound to an OUT position
  • ora-01147 : SYSTEM tablespace file string is offline
  • ora-02068 : following severe error from stringstring
  • ora-38102 : Invalid column in the INSERT WHERE Clause: string
  • ora-38716 : Must supply an integer for the TYPE option.
  • ora-30339 : illegal dimension attribute name
  • ora-14021 : MAXVALUE must be specified for all columns
  • ora-24305 : bad bind or define context
  • ora-31101 : Token "string" not given while locking resource "string"
  • ora-17502 : ksfdcre:string Failed to create file string
  • ora-16550 : truncated result
  • ora-01871 : the number of seconds must be less than 60
  • ora-32743 : command cannot be executed on remote instance
  • ora-08499 : Warning: picture mask options 'string' ignored by UTL_PG
  • ora-07706 : error in archive text: need disk file name
  • ora-29303 : user does not login as SYS
  • ora-12845 : failed to receive interinstance parallel execution message
  • ora-30197 : reserved for future use
  • ora-16575 : request terminated at broker discretion
  • ora-19726 : cannot plug data [string] at level string into database running at compatibility level string
  • ora-03236 : max # extents (string) reached in index string.string subpartition string
  • ora-19678 : RMAN configuration value exceeds maximum length of string
  • ora-30001 : trim set should have only one character
  • ora-14503 : only one partition name can be specified
  • 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.