Error: F_JD22D3 DBMS Error: SQL0443 - Object Not Journaled in Specified Receiver Range

Issue

A Capture job logs the following error when HVR is unable to locate the required journal receiver, making it impossible to identify the previous transaction:

F_JD22D3: DBMS error [SQL0443 - Object not journaled in specified receiver range].

Environment

• HVR Version: HVR 6
• Source Database: DB2 for i (IBM DB2 for iSeries)

Resolution

To resolve this issue, see the steps below:

Verify DB2 for i source requirements

Ensure your environment meets the necessary Capture requirements and permissions for using DB2 for i as a source. For more information, see our HVR 6 DB2 for i Privileges/Permissions documentation.

Determine journal receiver availability

Identify which journal receiver HVR is currently processing:

1. Go to the following directory:

   HVR_CONFIG/hubs/<HubName>/channels/<ChannelName>/locs/<SourceLoc>/router/
   

2. Use the hvrrouterview command to examine the .cap_state file:

   hvrrouterview <HubName> <ChannelName> <filename.cap_state>
   

3. Locate the journal receiver name in the output's scan_start_addr field.

   The first two segments represent the journal receiver library and name. The final segment, a sequence number, is typically not relevant. For example, in OSCEN.QSQJRN0001.12345, the journal receiver library and name are OSCEN.QSQJRN0001.

Scenario A: The required journal receiver is available in backup

If the necessary journal receiver is available in a backup:

1. Restore the journal receiver from the backup.
2. Run Activate Replication with the following options selected:
   • Jobs
   • Replace all old Enrollment

Scenario B: The required journal receiver is not available

If you can't recover the required journal receiver:

1. Run Activate Replication with the following options selected to capture changes going forward:
   • No Rewind
   • Replace all old Enrollment
2. Perform Refresh to ensure data consistency.
3. Increase the retention period of journal receivers on the DB2 for i system. This ensures receivers remain available for capture even in case of processing delays.

Cause

This issue may occur for any of the following reasons:

• Missing or incomplete prerequisites for DB2 for i capture.
• Journal receivers have been cleaned up or purged.
• Journal receivers have been renamed.