ORA-16807: unable to change database protection mode

Cause : An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE {PROTECTION | AVAILABILITY | PERFORMANCE} failed.

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

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

update : 29-04-2017
ORA-16807

ORA-16807 - unable to change database protection mode
ORA-16807 - unable to change database protection mode

  • ora-39019 : invalid operation type string
  • ora-08309 : sllfop: Cannot fstat file
  • ora-23375 : feature is incompatible with database version at string
  • ora-22317 : typecode number is not legal as a number type
  • ora-15014 : location 'string' is not in the discovery set
  • ora-25534 : _MEAN_TIME_TO_CLUSTER_AVAILABILITY is specified
  • ora-09842 : soacon: Archmon unable to create named pipe.
  • ora-06753 : TLI Driver: name-to-address mapping failed
  • ora-16540 : invalid argument
  • ora-37178 : column string has no values
  • ora-24374 : define not done before fetch or execute and fetch
  • ora-02809 : Jump buffer not valid
  • ora-02091 : transaction rolled back
  • ora-07597 : spguns: $GETJPIW failure
  • ora-00721 : changes by release string cannot be used by release string
  • ora-16958 : DML statements running parallel are not supported for test execute.
  • ora-28008 : invalid old password
  • ora-32015 : unable to restore SPFILE
  • ora-29935 : missing FROM keyword
  • ora-27513 : parameter string contains invalid value string
  • ora-07208 : sfwfb: failed to flush dirty buffers to disk.
  • ora-19272 : XQ0052 - invalid atomic value in attribute or element constructor
  • ora-28110 : policy function or package string.string has error
  • ora-24159 : invalid variable definiton
  • ora-01429 : Index-Organized Table: no data segment to store overflow row-pieces
  • ora-21522 : attempted to use an invalid connection in OCI (object mode only)
  • ora-22276 : invalid locator for LOB buffering
  • ora-36820 : (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.
  • ora-01333 : failed to establish Logminer Dictionary
  • ora-25194 : invalid COMPRESS prefix length value
  • 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.