JR62333: IIDR ORACLE IN DATAGUARD SHIPPING MODE USING THE STANDBY QUERY MAY STILL TRANSFORM THE ARCHIVE LOG FILE NAME AND PATH.

APAR status

• Closed as program error.

Error description

• IIDR Oracle  in DataGuard Log Shipping mode has option to Query
  the Standby instance for log metadata.  No Transformation or
  change to the Standby metadata of the archived log files should
  be performed.
  
  IIDR is always using the transformation for standby file names
  based on if results were from the Primary db.  This results in
  the fully qualified path being changed if the  Archive Directory
  value is specified, AND the FileName being changed to match the
  log_archive_format  string pattern,  rather than use what is in
  the Standby database v$archived_log view and the results from
  the standby query.
  
  The results should be used as returned from the Standby db, with
  no change in path or file name.
  

Local fix

• Local Fix may be suitable  IF and only IF the log_archive_format
  can be specified to match the Standby db parameter value and the
  archive directory is consistent.
  
  If  Oracle Managed Files are used, then there is no usable
  workaround other than to no longer use  OMF.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This issue may affect you if you are using CDC for Oracle as *
  * a source, and you use DataGuard log shipping with the option *
  * to query the standby database.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IIDR Oracle  in DataGuard Log Shipping mode has the option   *
  * to query the standby instance for log metadata.  The engine  *
  * was using the fully qualified path name and file pattern     *
  * rather than   rather than using the results from the Standby *
  * database query.                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IDR 11.4.0.3-5576 or newer for Oracle.            *
  ****************************************************************
  

Problem conclusion

• The engine now uses the log information from the standby
  database. Upgrading to IDR 11.4.0.3-5576 or newer for Oracle
  resolves the issue.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IS CDC ORACLE

• Fixed component ID

  5725E30OR

Applicable component levels