ORA-16097: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY

Cause : None

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

Specify this command to prepare the standby database for switchover

update : 27-04-2017
ORA-16097

ORA-16097 - ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
ORA-16097 - ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY

  • ora-25207 : enqueue failed, queue string.string is disabled from enqueueing
  • ora-29963 : missing BINDING keyword
  • ora-02803 : Retrieval of current time failed
  • ora-23375 : feature is incompatible with database version at string
  • ora-09240 : smpalo: error allocating PGA memory
  • ora-38733 : Physical size string less than needed string.
  • ora-00437 : ORACLE feature is not licensed. Contact Oracle Corp. for assistance
  • ora-00911 : invalid character
  • ora-06028 : NETASY: unable to intialise for logging
  • ora-27209 : syntax error in device PARMS - unknown keyword or missing =
  • ora-02024 : database link not found
  • ora-21522 : attempted to use an invalid connection in OCI (object mode only)
  • ora-09940 : ORACLE password file header is corrupt
  • ora-13774 : insufficient privileges to select data from the workload repository
  • ora-12412 : policy package string is not installed
  • ora-06263 : NETNTT: out of memory in pi_connect
  • ora-25270 : sender info does not match with the actual sender of the message
  • ora-30024 : Invalid specification for CREATE UNDO TABLESPACE
  • ora-10656 : Table is in unusable state due to incomplete operation
  • ora-25221 : enqueue failed, signature specified queue not supporting non-repudiation
  • ora-30381 : REWRITE_TABLE is not compatible with Oracle version
  • ora-19259 : XQ0039 - duplicate parameter name string in function declaration
  • ora-07473 : snclrd: read error when trying to read sgadef.dbf file.
  • ora-37184 : illegal value string for ADVMODE
  • ora-01490 : invalid ANALYZE command
  • ora-36670 : (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.
  • ora-02041 : client database did not begin a transaction
  • ora-02755 : osnfsmcre: cannot create chared memory file ?/dbs/ftt_.dbf
  • ora-38855 : cannot mark instance string (redo thread string) as enabled
  • ora-16798 : unable to complete terminal recovery on the standby database
  • 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.