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 : 30-04-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-35017 : (QFCHECK06) The Analytic Workspace and EIF file definitions of workspace object have different partitioning methods.
  • ora-36669 : (XSDPART07) string is not a legal LIST partition.
  • ora-30044 : 'Retention' can only specified for undo tablespace
  • ora-25197 : an overflow segment already exists for the indexed-organized table
  • ora-07503 : scgcmn: $setimr unexpected return
  • ora-12711 : this CREATE CONTROLFILE character set is not allowed
  • ora-30065 : test support for row dependencies
  • ora-19765 : mount id string does not match mount id string in control file
  • ora-32141 : get method does not match the type of the parameter
  • ora-09369 : Windows 3.1 Two-Task driver bad instance handle
  • ora-25290 : Cannot complete operation on queue string with existing messages
  • ora-38781 : cannot disable media recovery - have guaranteed restore points
  • ora-06953 : Not enough virtual memory
  • ora-29376 : number of consumer groups string in top-plan string exceeds string
  • ora-16555 : the Data Guard database is not active
  • ora-02215 : duplicate tablespace name clause
  • ora-32836 : database user string must be granted role string
  • ora-31497 : invalid value specified for first_scn
  • ora-04033 : Insufficient memory to grow pool
  • ora-36802 : (XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP.
  • ora-31533 : only one change set (string) is allowed in change source
  • ora-09870 : spini: failure initializing maximum number of open files.
  • ora-14061 : data type or length of an index partitioning column may not be changed
  • ora-07391 : sftopn: fopen error, unable to open text file.
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-31664 : unable to construct unique job name when defaulted
  • ora-12210 : TNS:error in finding Navigator data
  • ora-25220 : enqueue failed, signature not specified for a non-repudiable queue
  • ora-14266 : data type or length of an index subpartitioning column may not be changed
  • ora-13753 : "SQL Tuning Set" "string" already exists for user "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.