ORA-16789: missing standby redo logs

Cause : Standby redo logs are missing and are needed for SYNC and ASYNC log transport modes.

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

Check the Data Guard documentation to see how to create standby redo logs.

update : 17-08-2017
ORA-16789

ORA-16789 - missing standby redo logs
ORA-16789 - missing standby redo logs

  • ora-14194 : only one subpartition may be rebuilt
  • ora-24149 : invalid rule name
  • ora-16136 : Managed Standby Recovery not active
  • ora-07750 : slemcr: fopen failure
  • ora-19750 : change tracking file: 'string'
  • ora-16753 : resource guard could not open standby database
  • ora-02492 : missing required file block increment size in NEXT clause
  • ora-19378 : invalid mode
  • ora-21615 : an OTS (named or simple) instance failed
  • ora-16162 : Cannot add new standby databases to protected configuration
  • ora-01289 : cannot add duplicate logfile string
  • ora-19932 : control file is not clone or standby
  • ora-14019 : partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
  • ora-29556 : object type has changed
  • ora-12446 : Insufficient authorization for administration of policy string
  • ora-36710 : (XSMXALLOC01) TARGETLOG variable workspace object must be dimensioned identically to TARGET variable workspace object.
  • ora-13152 : invalid HHCODE type
  • ora-16165 : LGWR failed to hear from network server
  • ora-01088 : cannot shut down ORACLE while active processes exist
  • ora-13002 : specified level is out of range
  • ora-36994 : (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.
  • ora-27103 : internal error
  • ora-31604 : invalid string parameter "string" for object type string in function string
  • ora-07256 : sptrap: cannot set up signal handler to catch exceptions.
  • ora-38486 : FUNCTION/PACKAGE/TYPE already exists for the attribute set
  • ora-28673 : Merge operation not allowed on an index-organized table
  • ora-03252 : initial extent size not enough for LOB segment
  • ora-32057 : invalid lock mode
  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-13249 : %s
  • 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.