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 : 24-06-2017
ORA-16807

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

  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-38757 : Database must be mounted and not open to FLASHBACK.
  • ora-36178 : (XSAGGR01) To be used with AGGREGATE, AGGMAP workspace object must be declared with the AGGMAP command.
  • ora-40220 : maximum number of attributes exceeded
  • ora-01986 : OPTIMIZER_GOAL is obsolete
  • ora-07431 : fork failed
  • ora-02479 : error while translating file name for parallel load
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-06566 : invalid number of rows specified
  • ora-36982 : (XSRELGID03) The grouping variable/relation workspace object must be dimensioned by all dimensions of the source relation workspace object that have more than one value in status.
  • ora-01117 : adding file 'string' with illegal block size: string; limit is string
  • ora-31446 : this session does not own the lock handle for string
  • ora-07628 : smsfre: sga not mapped
  • ora-23482 : column string of "string"."string": object types not allowed.
  • ora-12496 : cannot change existing level, category, or release numbers
  • ora-40305 : invalid impurity metric specified
  • ora-15007 : name is already used by an existing template
  • ora-25240 : message ID and dequeue condition/correlation ID specified in dequeue options
  • ora-31535 : cannot support change source string in this configuration
  • ora-14014 : maximum number of partitioning columns is 16
  • ora-32143 : Environment not specified
  • ora-13825 : missing SQL statement text for create SQL profile
  • ora-12608 : TNS: Send timeout occurred
  • ora-31224 : DBMS_LDAP: invalid LDAP session
  • ora-19114 : error during parsing the XQuery expression: string
  • ora-16578 : failed to read Data Guard configuration file
  • ora-29361 : value string is outside valid range of 0 to 100
  • ora-19725 : can not acquire plug-in enqueue
  • ora-16776 : health check of the redo transport service failed
  • ora-19235 : XQ0015 - unsupported must-understand extension
  • 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.