ORA-16629: database reports a different protection level from the protection mode

Cause : The actual protection level supported by the standby database was different from the protection mode set on the primary database. This was likely caused by redo transport problems.

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

Check the database alert logs and Data Guard broker logs for more details. Check the redo transport status. Make sure at least one standby redo transport is supporting the protection mode and that the network to the standby database is working.

update : 24-09-2017

ORA-16629 - database reports a different protection level from the protection mode
ORA-16629 - database reports a different protection level from the protection mode

  • ora-12645 : Parameter does not exist.
  • ora-02198 : ONLINE/OFFLINE option already specified
  • ora-00313 : open failed for members of log group string of thread string
  • ora-29528 : invalid Java call in trigger string
  • ora-01286 : start interval required
  • ora-16559 : out of memory at string
  • ora-15018 : diskgroup cannot be created
  • ora-26050 : Direct path load of domain index is not supported for this column type.
  • ora-19624 : operation failed, retry possible
  • ora-06557 : null values are not allowed for any parameters to pipe icd's
  • ora-22895 : referenced table "string" in schema "string" is not an object table
  • ora-01984 : invalid auditing option for procedures/packages/functions
  • ora-03276 : duplicate ALLOCATE EXTENT option specification
  • ora-12987 : cannot combine drop column with other operations
  • ora-01783 : only one RECOVERABLE or UNRECOVERABLE clause may be specified
  • ora-39099 : cannot create index for "string" on master table string
  • ora-24192 : the property name cannot be null
  • ora-31107 : Action failed as resource "string" is locked by name lock
  • ora-24437 : OCIStmtExecute called before OCIStmtPrepare2.
  • ora-36740 : A CHILDLOCK was detected in your valueset
  • ora-21708 : inappropriate operation on a transient object
  • ora-01552 : cannot use system rollback segment for non-system tablespace 'string'
  • ora-06131 : NETTCP: user access denied
  • ora-29323 : ALTER DATABASE SET COMPATIBILITY command not supported by string
  • ora-24339 : cannot set server group name after connecting to server
  • ora-26057 : Conversion is not necessary for this direct path stream.
  • ora-02766 : Invalid maximum of request descriptors
  • ora-29300 : ORACLE error, tablespace point-in-time recovery
  • ora-09272 : remote os logon is not allowed
  • ora-01603 : illegal grouping size in clause "string" of string
  • 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.