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 : 25-04-2017
ORA-16152

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

  • ora-32343 : let MVIEW engine know that it is IMPORT from 9i or earlier
  • ora-24308 : illegal define position
  • ora-37035 : (XSMLTDCL01) You can only DEFINE SESSION objects in analytic workspace string because it is attached in MULTI mode.
  • ora-12046 : cannot use trusted constraints for refreshing remote MV
  • ora-19377 : no "SQL Tuning Set" with name like "string" exists for owner like "string"
  • ora-33098 : (APABBR01) A value of 'string' is not valid for the workspace object option.
  • ora-12001 : cannot create log: table 'string' already has a trigger
  • ora-02354 : error in exporting/importing data string
  • ora-25446 : duplicate column value for table alias: string, column: string
  • ora-13604 : The specified parameter string cannot be fetched as a SQL table.
  • ora-10706 : Print out information about global enqueue manipulation
  • ora-36641 : (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.
  • ora-24436 : Invalid statement Handle.
  • ora-12058 : materialized view cannot use prebuilt table
  • ora-32616 : missing DIMENSION BY keyword in MODEL clause
  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-38423 : Attribute set created from an ADT may not be extended.
  • ora-36648 : (XSDUNION09) Concat dimension workspace object is already defined as UNIQUE.
  • ora-27026 : skgfrls: sbtend returned error
  • ora-16041 : Remote File Server fatal error
  • ora-10660 : Segment is a shared lob segment
  • ora-13295 : geometry objects are in different coordinate systems
  • ora-10282 : Inhibit signalling of other backgrounds when one dies
  • ora-00385 : cannot enable Very Large Memory with new buffer cache parameters
  • ora-38721 : Invalid file number.
  • ora-12985 : tablespace 'string' is read only, cannot drop column
  • ora-10704 : Print out information about what enqueues are being obtained
  • ora-32586 : multiple specification of a supplemental logging attribute
  • ora-12823 : default degree of parallelism may not be specified here
  • ora-23445 : missing template site
  • 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.