JR50540: MIRRORING FAILS SWITCHING FROM AN ASM-STORED REDO LOG TO A NON-ASM-STORED LOG

Fix list for IBM InfoSphere Change Data Capture

APAR status

• Closed as program error.

Error description

• After processing an ASM-stored log, if the next log processed
  is not stored in ASM, mirroring can end with errors like
  
  Error 2919 jr_rac Jun 17, 2014 12:39:54 PM IBM InfoSphere
  Change Data Capture daemon has encountered an error message.
  Redo log file information not found for subscription
  SHAREDSCRAPE. The Oracle database does not contain valid redo
  log file information corresponding to the log position
  '593925840.0.0.0.0.0.0' for the current database incarnation.
  Error detected in file OracleRedoNativeApi.java at line 1178.
  This may be caused by any of the following: a) The SCN portion
  of the log position 593925840.0.0.0.0.0.0 is invalid. b) The
  SCN associated with log position 593925840.0.0.0.0.0.0 does not
  correspond to a current on-line redo log file and ARCHIVELOG
  mode is not enabled. c) The redo log file(s) corresponding to
  log position 593925840.0.0.0.0.0.0 does not currently exist,
  exists but is inaccessible or exists and is corrupt. d) The
  control file contains invalid information. e) The database was
  shut down abort. Re-start replication will resolve this issue.
  f) There was error archiving redo logs because of insufficient
  disk space. Try to resolve this issue by doing the following
  and re-start replication: a) Change the log position to specify
  a correct SCN value. b) Examine the views V$LOG and
  V$ARCHIVED_LOG to determine a valid SCN for which a
  corresponding online or archived redo log file exists. Change
  the log position to specify a valid SCN for the current
  database incarnation. c) Restore a valid copy of the required
  redo log file(s) from backup. d) Ensure the disk space for
  archived redo logs is not full.
  Information 2917 jr_rac Jun 17, 2014 12:39:54 PM IBM InfoSphere
  Change Data Capture daemon has reported an informational
  message.
  Oracle Redo log /archivelog/l11grac/1_10805_697040652.dbf is
  corrupted, CDC will restart from last good position
  593925840.1.1.35007.284.0.0 and avoid this corrupted log.
  Error 2919 jr_rac Jun 17, 2014 12:39:54 PM IBM InfoSphere
  Change Data Capture daemon has encountered an error message.
  Invalid internal file structure contents detected in file
  '/archivelog/l11grac/1_10805_697040652.dbf'. The oracle file
  '/archivelog/l11grac/1_10805_697040652.dbf' does not contain
  valid internal format or information. Reason code = 4. Error
  detected in file
  /dmbuild/luntbuild/ts-java2/work-dmlnxbld/build-output/temp/iRef
  lectEngine/src/oraraw/orarfile.c at line 560. The most likely
  cause is a corrupt file or an incompatible version of Oracle.
  Reason codes are as follows: 1) Failure trying to determine
  file block size. 2) Invalid Control file block check
  information. 3) Redo Log file block number mismatch. 4) Invalid
  internal logical structure. 5) Record spanning 2 redo log
  files. 6) Invalid record entry size. 7) Invalid number of
  record entries. The preceding message may contain more
  information.
  

Local fix

• Restart mirroring
  

Problem summary

• IIDR 10.2 and 10.2.1 for Oracle Redo fail with the errors
  similar to:
  
  Error 2919 jr_rac Jun 17, 2014 12:39:54 PM IBM InfoSphere Change
   Data Capture daemon has encountered an error message.
  Redo log file information not found for subscription
  SHAREDSCRAPE. The Oracle database does not contain valid redo
  log file information corresponding to the log position
  '593925840.0.0.0.0.0.0' for the current database incarnation.
  Error detected in file OracleRedoNativeApi.java at line 1178.
  This may be caused by any of the following: a) The SCN portion
  of the log position 593925840.0.0.0.0.0.0 is invalid. b) The SCN
  associated with log position 593925840.0.0.0.0.0.0 does not
  correspond to a current on-line redo log file and ARCHIVELOG
  mode is not enabled. c) The redo log file(s) corresponding to
  log position 593925840.0.0.0.0.0.0 does not currently exist,
  exists but is inaccessible or exists and is corrupt. d) The
  control file contains invalid information. e) The database was
  shut down abort. Re-start replication will resolve this issue.
  f) There was error archiving redo logs because of insufficient
  disk space. Try to resolve this issue by doing the following and
  re-start replication: a) Change the log position to specify a
  correct SCN value. b) Examine the views V$LOG and V$ARCHIVED_LOG
  to determine a valid SCN for which a corresponding online or
  archived redo log file exists. Change the log position to
  specify a valid SCN for the current database incarnation. c)
  Restore a valid copy of the required redo log file(s) from
  backup. d) Ensure the disk space for archived redo logs is not
  full.
  Information 2917 jr_rac Jun 17, 2014 12:39:54 PM IBM InfoSphere
  Change Data Capture daemon has reported an informational
  message.
  Oracle Redo log /archivelog/l11grac/1_10805_697040652.dbf is
  corrupted, CDC will restart from last good position
  593925840.1.1.35007.284.0.0 and avoid this corrupted log.
  Error 2919 jr_rac Jun 17, 2014 12:39:54 PM IBM InfoSphere Change
  Data Capture daemon has encountered an error message.
  Invalid internal file structure contents detected in file
  '/archivelog/l11grac/1_10805_697040652.dbf'. The oracle file
  '/archivelog/l11grac/1_10805_697040652.dbf' does not contain
  valid internal format or information. Reason code = 4. Error
  detected in file
  /dmbuild/luntbuild/ts-java2/work-dmlnxbld/build-output/temp/iRef
  lectEngine/src/oraraw/orarfile.c at line 560. The most likely
  cause is a corrupt file or an incompatible version of Oracle.
  Reason codes are as follows: 1) Failure trying to determine file
  block size. 2) Invalid Control file block check information. 3)
  Redo Log file block number mismatch. 4) Invalid internal logical
  structure. 5) Record spanning 2 redo log files. 6) Invalid
  record entry size. 7) Invalid number of record entries. The
  preceding message may contain more information.
  
  when finishing up processing an ASM managed log and having the
  next log to process not managed by ASM.
  
  This issue affect users running IIDR 10.2 Interim Fix 17 for
  Oracle Redo (and below) and IIDR 10.2.1 Interim Fix 5 for Oracle
  Redo (and below) under the described circumstances.
  

Problem conclusion

• This issue is fixed by applying the following interim fixes
  depending on the product version:
  - IIDR 10.2 Interim Fix 18 for Oracle Redo; or
  - IIDR 10.2.1 Interim Fix 6 for Oracle Redo.
  

Temporary fix

• Restart replication
  

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

• RA20 PSY

     UP

• RA21 PSY

     UP