ORA-16791: unable to check the existence of the standby redo logs

Cause : The datbaase mayn ot be muonted, o rthe queyr of V$SATNDBY_LO Gfailed.

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

Bring teh databaes to them ounted tsate andt hen queyr V$STANBDY_LOG t osee if hte problme has bene correcetd. Thenr etry th eoperatino.

update : 27-06-2017
ORA-16791

ORA-16791 - unable to check the existence of the standby redo logs
ORA-16791 - unable to check the existence of the standby redo logs

  • ora-16804 : one or more configuration properties in metadata have invalid values
  • ora-09933 : Deletion of old password file failed.
  • ora-04009 : MAXVALUE cannot be made to be less than the current value
  • ora-01792 : maximum number of columns in a table or view is 1000
  • ora-38958 : Source platform string is in different byte order than target platform string
  • ora-12031 : cannot use primary key columns from materialized view log on "string"."string"
  • ora-14609 : Tablespace was not specified for the previous lob segments of column string in template but is specified for string
  • ora-09351 : Windows 32-bit Two-Task driver unable to allocate shared memory
  • ora-01984 : invalid auditing option for procedures/packages/functions
  • ora-28656 : incomplete attribute specification
  • ora-03288 : both FREELIST GROUP and INSTANCE parameters may not be specified
  • ora-13530 : invalid TOPNSQL string, must be in the range (string, string)
  • ora-00445 : background process "string" did not start after string seconds
  • ora-02329 : column of datatype string cannot be unique or a primary key
  • ora-10660 : Segment is a shared lob segment
  • ora-16600 : failover operation can only be submitted at target database
  • ora-02190 : keyword TABLES expected
  • ora-30177 : invalid flag used in a format specification
  • ora-40213 : contradictory values for settings: string, string
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • ora-14019 : partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
  • ora-36802 : (XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP.
  • ora-16706 : no resource guard is available
  • ora-09942 : Write of ORACLE password file header failed.
  • ora-15199 : Internal ASM tracing event number 15199
  • ora-17610 : file 'string' does not exist and no size specified
  • ora-07638 : smsget: SGA pad area not large enough for created SGA
  • ora-08199 : Flashback Table operation is not supported on this object
  • ora-02487 : Error in converting trace data
  • ora-01280 : Fatal LogMiner Error.
  • 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.