ORA-16769: the physical standby database is open read-only

Cause : All isntance sin th ephysiacl stadnby daatbase ewre pu tinto aread-noly sttae insetad ofL OG-APLPY-OFF.

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

Issuet he se tstatec omman dto moev the adtabas eto LO-GAPPLYO-FF sttae.

update : 16-08-2017

ORA-16769 - the physical standby database is open read-only
ORA-16769 - the physical standby database is open read-only

  • ora-36406 : (VCACHE00) 'number' is an invalid value for the VARCACHE option. The only permissible values are 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-26063 : Can not flashback to specified SCN value - Wrap: string Base: string.
  • ora-32829 : Messaging Gateway agent cannot be shut down while it is starting
  • ora-12024 : materialized view log on "string"."string" does not have primary key columns
  • ora-39601 : Hash key is required.
  • ora-19028 : Invalid ADT parameter passed to toObject() function
  • ora-10973 : backout evet for 2619509
  • ora-25217 : enqueue failed, visibility must be IMMEDIATE for queue string.string
  • ora-13342 : an arc geometry has fewer than three coordinates
  • ora-14273 : lower-bound partition must be specified first
  • ora-36637 : (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-02021 : DDL operations are not allowed on a remote database
  • ora-19033 : schema specified in the XML document does not match the schema parameter
  • ora-16618 : response document of size "string" bytes is too large
  • ora-01470 : In-list iteration does not support mixed operators
  • ora-07250 : spcre: semget error, unable to get first semaphore set.
  • ora-25503 : cannot open database because the database is being quiesced
  • ora-30676 : socket read or write failed
  • ora-31428 : no publication contains all the specified columns
  • ora-07231 : slemcc: invalid file handle, seals do not match.
  • ora-32407 : cannot exclude new values when materialized view log includes new values
  • ora-27207 : syntax error in device PARMS - parentheses mismatch or missing
  • ora-31535 : cannot support change source string in this configuration
  • ora-02708 : osnrntab: connect to host failed, unknown ORACLE_SID
  • ora-01218 : logfile member is not from the same point-in-time
  • ora-23354 : deferred RPC execution disabled for "string" with "string"
  • ora-16181 : SGA specified for Logical Standby is too large
  • ora-29364 : plan directive string, string already exists
  • ora-24786 : separated transaction has been completed
  • ora-25288 : AQ HTTP propagation encountered error, status-code number, 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.