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 : 20-08-2017
ORA-16162

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

  • ora-38769 : FLASHBACK DATABASE failed after modifying data.
  • ora-15151 : missing or invalid version number for rolling upgrade or downgrade
  • ora-31670 : Username argument must be specified and non-null.
  • ora-12227 : TNS:syntax error
  • ora-02440 : Create as select with referential constraints not allowed
  • ora-32743 : command cannot be executed on remote instance
  • ora-19800 : Unable to initialize Oracle Managed Destination
  • ora-19731 : cannot apply change to unverified plugged-in datafile string
  • ora-00069 : cannot acquire lock -- table locks disabled for string
  • ora-27125 : unable to create shared memory segment
  • ora-07268 : szguns: getpwuid error.
  • ora-02039 : bind by value is not allowed for array type
  • ora-33918 : (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.
  • ora-30033 : Undo tablespace cannot be specified as default user tablespace
  • ora-19265 : XQ0045 - invalid or unknown prefix string in function declaration
  • ora-16700 : the standby database has diverged from the primary database
  • ora-07742 : slemop: $CONNECT failure
  • ora-28551 : pass-through SQL: SQL parse error
  • ora-03130 : the buffer for the next piece to be fetched is required
  • ora-30159 : OCIFileOpen: Cannot create the file or cannot open in the requested mode
  • ora-14055 : keyword REBUILD in ALTER INDEX REBUILD must immediately follow
  • ora-39121 : Table string can't be replaced, data will be skipped. Failing error is: string
  • ora-19513 : failed to identify sequential file
  • ora-16526 : unable to allocate task element
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-06445 : ssvpstevrg: Incorrect parameters passed to function call
  • ora-01456 : may not perform insert/delete/update operation inside a READ ONLY transaction
  • ora-02268 : referenced table does not have a primary key
  • ora-16130 : supplemental log information is missing from log stream
  • ora-21526 : initialization failed
  • 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.