Error: F_JT1456: Log Parsing Error F_JZ1150

Issue

The Capture process on an Oracle source logs the following error:

F_JT1456: Log parsing error F_JZ1150. There is not enough information to make a decision whether the row (hrid=0x1594d087.f) of the compressed table <TableID> has been ready for composing or not.

Environment

• HVR 5
• Source database: Oracle

Resolution

To resolve this issue, do the following:

Verify that supplemental logging is enabled on the database

1. Run the following query to ensure supplemental logging is enabled at the database level:

   SELECT SUPPLEMENTAL_LOG_DATA_MIN, SUPPLEMENTAL_LOG_DATA_PK, SUPPLEMENTAL_LOG_DATA_UI, SUPPLEMENTAL_LOG_DATA_ALL FROM v$database;
   

   If supplemental logging is enabled, the SUPPLEMENTAL_LOG_DATA_MIN value should return YES at a minimum.
2. Run the following query to ensure supplemental logging is enabled at the table level:

   SELECT LOG_GROUP_NAME, TABLE_NAME, LOG_GROUP_TYPE, DECODE(ALWAYS, 'ALWAYS', 'Unconditional', NULL, 'Conditional') AS ALWAYS FROM DBA_LOG_GROUPS WHERE TABLE_NAME='<TableName>';
   

   If supplemental logging is enabled, the LOG_GROUP_TYPE value should return ALL COLUMN LOGGING and the ALWAYS value should return Unconditional.

If the outputs do not match the expected results, enable supplemental logging on the database.

Verify table enrollment in the repository

1. Locate the table enrollment file in the following HVR Hub directory: $HVR_CONFIG/hubs/<hub>/channels/<chn>/locs/<loc>/enroll
2. Review the file to ensure the table enrollment matches the source table definition, correcting any discrepancies.

Activate table enrollment in the channel

Run HVR Initialize with the following options selected:

• Table Enrollment
• Replace old Enrollment
• Supplemental Logging
• Scripts and Jobs

Skip the transaction and refresh

If the issue persists, skip the problematic transaction using the hvrcontrol command, then perform a Refresh to reprocess the data.

Cause

This issue may occur for either of the following reasons:

• Supplemental logging is not enabled on the source database or table.
• There is a mismatch between the source table definition and the table enrollment in the repository.