JR65028: IIDR ORACLE REDO ENGINE ON WINDOWS OS FAILS TO READ LOG FILES 4GB+ IN SIZE

APAR status

• Closed as program error.

Error description

• This issue affects all previous build of IIDR Oracle Redo Engine
  running on Windows OS platform.
  
  When attempting to read an Oracle online or archived redo log
  file of size greater than 4GB, an internal error is raised
  related to a system call fstat, followed by Event messages
  reporting possible file corruption or invalid  internal file
  structure  on the Log file.
  
  
  This applies even when the IIDR Oracle Redo Engine is running
  on Windows and the Oracle database is Remote on a different OS,
  but log files are provided via shared storage or log shipping.
  
  
  eg:
  
  SHAREDSCRAPE LOG READER{3279}	com.datamirror.ts.eventlog.Event
  Logger	logActualEvent()	Eventlogged: ID=2919 MSG=IBM InfoSphere
  encountered an error message. Error 132 returned by system call
  fstat.Internal Error! Error Unknown error detected in file C:\\
  ci\\build\\pipeline_master\\build-output\\windows\\x86\\default
  \\64\\temp\\ireflect-engine\\src\\main\\c\\oraraw\\oraint.cat li
  
  
  logEventCallback()	Invalid internal file structure contents
  detected in file <Oracle Log file name> Reason code = 1.  (or
  Reason Code =4 ).
  

Local fix

• Using Archived Only mode for reading may be possible if Log
  switch is performed consistently below the 4gb size of new data
  in the online log files.
  
  
  Otherwise  modifying the Oracle Database online Log Files to
  only be 4GB as max would be required.  (Typical process is to
  add NEW online log files for each group and muti-plexed location
   for the new smaller size,  ensure Database is using the new log
  files and then drop the  old log files when they are no longer
  Active. - meaning have been archived successfully. ).
  
  If online logs are changed,  then waiting for log switch and
  ensuring all needed archived logs are below 4GB in size before
  resuming is needed so that any files accessed would be under the
  4GB limit.
  
  Full refresh of all data from a point after a 4GB+ archived log
  would still be required as this file could not be opened
  properly without applying the Fix update.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This issue might affect you if you use IDR 11.4.0.4-5640 or  *
  * older for Oracle as a source on Windows.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Mirroring ends on error.                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IDR 11.4.0.4-5643 or newer for Oracle.            *
  ****************************************************************
  

Problem conclusion

• Upgrading to IDR 11.4.0.4-5643 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