ORA-16162: Cannot add new standby databases to protected configuration

Cause : An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.

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

The standby database must be added to the configuration before the primary database is opened.

update : 23-06-2017
ORA-16162

ORA-16162 - Cannot add new standby databases to protected configuration
ORA-16162 - Cannot add new standby databases to protected configuration

  • ora-01347 : Supplemental log data no longer found
  • ora-09945 : Unable to initialize the audit trail file
  • ora-31523 : could not find change source string for CDC change set string
  • ora-09311 : slsleep: error temporarily suspending process
  • ora-14004 : missing PARTITION keyword
  • ora-04090 : 'string' specifies same table, event and trigger time as 'string'
  • ora-14156 : invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
  • ora-07327 : smpdal: attempt to destroy pga when it was not mapped.
  • ora-01344 : LogMiner coordinator already attached
  • ora-06250 : NETNTT: cannot allocate send and receive buffers
  • ora-06908 : CMX: error during transfer of ORACLE_SID
  • ora-02449 : unique/primary keys in table referenced by foreign keys
  • ora-29363 : plan directive string, string is mandatory and cannot be modified or deleted
  • ora-32611 : incorrect use of MODEL CV operator
  • ora-16232 : adding Logical Standby skip entry for table string.string
  • ora-31607 : function string is inconsistent with transform.
  • ora-27093 : could not delete directory
  • ora-25230 : invalid value string, WAIT should be non-negative
  • ora-12713 : Character data loss in NCHAR/CHAR conversion
  • ora-06781 : TLI Driver: error reading negotation string
  • ora-04089 : cannot create triggers on objects owned by SYS
  • ora-16152 : standby database is in 'no-data-loss' protected mode
  • ora-07267 : spwat: invalid process number.
  • ora-30023 : Duplicate undo tablespace specification
  • ora-25124 : Database link name not allowed.
  • ora-30676 : socket read or write failed
  • ora-10926 : trace name context forever
  • ora-22877 : invalid option specified for a HASH partition or subpartition of a LOB column
  • ora-38905 : DML error logging is not supported for LONG column "string"
  • ora-04088 : error during execution of trigger 'string.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.