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 : 28-04-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-16514 : the request was not found
  • ora-29312 : changes by release string cannot be used by release string, type: string
  • ora-01096 : program version (string) incompatible with instance (string)
  • ora-38433 : index "string" could not be maintained due to "string"
  • ora-29829 : implementation type does not exist
  • ora-28037 : Cannot Get Session Key for RACF Authentication
  • ora-30464 : no summaries exist
  • ora-23534 : missing column in materialized view container table "string"."string"
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-04045 : errors during recompilation/revalidation of string.string
  • ora-10618 : Operation not allowed on this segment
  • ora-00471 : DBWR process terminated with error
  • ora-01690 : sort area size too small
  • ora-27092 : size of file exceeds file size limit of the process
  • ora-27148 : spawn wait error
  • ora-16624 : broker protocol version mismatch detected
  • ora-30493 : The percentile value should be a number between 0 and 1.
  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-13192 : failed to read number of element rows
  • ora-14606 : Tablespace was specified for previous subpartitions in template but is not specified for string
  • ora-39753 : unsupported use of subquery in PARTITIONED OUTER JOIN condition
  • ora-14063 : Unusable index exists on unique/primary constraint key
  • ora-02028 : fetching an exact number of rows is not supported by the server
  • ora-14279 : index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-31086 : insufficient privileges to register schema "string"
  • ora-29302 : database is not open clone
  • ora-29393 : user string does not exist or is not logged on
  • ora-15005 : name "string" is already used by an existing alias
  • ora-27015 : skgfcls: failed to close the file
  • ora-01114 : IO error writing block to file string (block # 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.