GoldenGate For DB2 Z/OS Looping When A DB2 Archive Log Does Not Exist (Doc ID 2953064.1)

Last updated on JANUARY 28, 2024

Applies to:

Symptoms

GoldenGate version 21.8 for Db2 z/OS.
The GoldenGate hub runs on Linux x86-64, OS Version Red Hat Enterprise 8.
Db2 z/OS version 12.1 runs on RELEASE z/OS 02.04.00.

When an extract is altered to reference an LSN value for a Db2 archive log that no longer exists, and the extract is started, GoldenGate continues its request for the Db2 archive log once per second until the extract is stopped. This is causing a lot of messages to be written to the Db2 log and the z/OS system log, which is a problem.
Is there a GoldenGate parameter that we can set to limit the number of requests for a Db2 archive log, which when exceeded, causes the extract to abend?

Here are the Db2 log messages that are generated.
09.49.12 STC73304 DSNJ113E @<SSID>DSNJR03A LRSN '00CCD42781423083A400' 005
  005 NOT IN ANY ACTIVE OR ARCHIVE LOG DATA SET. CONNECTION-ID=RRSAF,
  005 CORRELATION-ID=extract, MEMBER-ID=1
09.49.12 STC73304 DSNJ113E @<SSID> DSNJR03A LRSN '00CCD42781423083A400' 007
  007 NOT IN ANY ACTIVE OR ARCHIVE LOG DATA SET. CONNECTION-ID=RRSAF,
  007 CORRELATION-ID=extract, MEMBER-ID=1
09.49.13 STC73304 DSNJ113E @<SSID> DSNJR03A LRSN '00CCD42781423083A400' 017
  017 NOT IN ANY ACTIVE OR ARCHIVE LOG DATA SET. CONNECTION-ID=RRSAF,
  017 CORRELATION-ID=extract, MEMBER-ID=1
09.49.14 STC73304 DSNJ113E @<SSID> DSNJR03A LRSN '00CCD42781423083A400' 041
  041 NOT IN ANY ACTIVE OR ARCHIVE LOG DATA SET. CONNECTION-ID=RRSAF,
  041 CORRELATION-ID=extract, MEMBER-ID=1
09.49.15 STC73304 DSNJ113E @<SSID> DSNJR03A LRSN '00CCD42781423083A400' 043
  043 NOT IN ANY ACTIVE OR ARCHIVE LOG DATA SET. CONNECTION-ID=RRSAF,
  043 CORRELATION-ID=extract, MEMBER-ID=1

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.