ORA-16152: standby database is in 'no-data-loss' protected mode

Cause : The attempted database operation is not allowed while the standby database is in 'no-data-loss' protected mode.

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

Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement.

update : 23-07-2017

ORA-16152 - standby database is in 'no-data-loss' protected mode
ORA-16152 - standby database is in 'no-data-loss' protected mode

  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-19551 : device is busy, device type: string, device name: string
  • ora-36846 : (XSLMGEN16) AW name is greater than 30 bytes
  • ora-24383 : Overflow segment of an IOT cannot be described
  • ora-28669 : bitmap index can not be created on an IOT with no mapping table
  • ora-15126 : component within ASM file name 'string' exceeds maximum length
  • ora-30047 : Internal event for kti tracing
  • ora-06307 : IPA: Cannot reset connection
  • ora-00000 : normal, successful completion
  • ora-03207 : subpartitioned type must be specified for composite object
  • ora-32614 : illegal MODEL SELECT expression
  • ora-16076 : unknown standby database destination
  • ora-36881 : (XSSRF00) The OLAP DML ROW2CELL function can only be used in a LIMITMAP.
  • ora-08270 : sksachk: Illegal archival control string
  • ora-23358 : invalid remote user
  • ora-24328 : illegal attribute value
  • ora-28111 : insufficient privilege to evaluate policy predicate
  • ora-25956 : join index cannot be created on tables owned by SYS
  • ora-29502 : NAMED keyword required in CREATE JAVA RESOURCE
  • ora-31114 : XDB configuration has been deleted or is corrupted
  • ora-00381 : cannot use both new and old parameters for buffer cache size specification
  • ora-06261 : NETNTT: nrange() failed
  • ora-08468 : mask option string is not supported
  • ora-38472 : VARCHAR representation of the data item is too long.
  • ora-01509 : specified name 'string' does not match actual 'string'
  • ora-01944 : IDENTIFIED EXTERNALLY already specified
  • ora-12620 : TNS:requested characteristic not available
  • ora-29853 : keyword UNIQUE may not be used in creating domain indexes
  • ora-29326 : SET COMPATIBILITY release number higher than string
  • ora-13028 : Invalid Gtype in the SDO_GEOMETRY object
  • 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.