ORA-16772: error switching over between primary and standby databases

Cause : There was an error during switchover of primary and standby databases.

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

Check the Data Guard broker log and Oracle alert log for more details.

update : 26-09-2017
ORA-16772

ORA-16772 - error switching over between primary and standby databases
ORA-16772 - error switching over between primary and standby databases

  • ora-13707 : Either the start snapshot string or the end snapshot string is incomplete or missing key statistics.
  • ora-37113 : OLAP API initialization error: (string)
  • ora-13422 : invalid model coordinate parameter
  • ora-28671 : UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
  • ora-36838 : (XSLMGEN08) Dimension string.string!string attribute string is missing a COLUMNNAME property value
  • ora-36720 : (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
  • ora-29309 : export dump file was generated by different version of DBMS_PITR package
  • ora-30475 : feature not enabled: string
  • ora-33288 : (DBERR15) Another user has incompatible access to analytic workspace string, and the wait timeout has expired.
  • ora-22609 : error string during initialization of FDO
  • ora-23413 : table "string"."string" does not have a materialized view log
  • ora-40207 : duplicate or multiple function settings
  • ora-38715 : Invalid log number specified in the DUMP FLASHBACK command.
  • ora-16227 : DDL skipped due to missing object
  • ora-08205 : ora_addr: $ORACLE_SID not set in environment
  • ora-37104 : (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.
  • ora-02735 : osnfpm: cannot create shared memory segment
  • ora-06433 : ssaio: LSEEK error, unable to seek to requested block.
  • ora-12711 : this CREATE CONTROLFILE character set is not allowed
  • ora-30508 : client logon triggers cannot have BEFORE type
  • ora-29854 : keyword BITMAP may not be used in creating domain indexes
  • ora-06043 : NETDNT: message send failure
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-01526 : error in opening file 'string'
  • ora-38444 : statistics do not exist for the expression set
  • ora-06536 : IN bind variable bound to an OUT position
  • ora-10933 : trace name context forever
  • ora-07845 : sllfcl: LIB$FREE_VM failue
  • ora-31214 : DBMS_LDAP: PL/SQL - Invalid LDAP mod type.
  • ora-24396 : invalid attribute set in server handle
  • 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.