HVR Shows TABLE ID in its error log which make no use to user
Answered
We receive error like this
F_JT0400: Log scanning error F_JZ320A. Transaction 0x200b48825eb encountered commit at sequence 000000030C7CE92A0000004F95272C95 but a change for table id 1245394 is still open with pending lob fragments. To skip all log records for this timestamp, u.......
F_JT1410: The previous error occurred after scanning record 3064, which has LFS,LSN 30c7ce92a,4f95272c95 and timestamp 2026-07-15T22:31:29-04:00.
table id 1245394 is not a Database table id and even not stored in HVR Repo
It will be more simple if we just print name which is more easy for user to understand and ID and Name both is available to HVR
-
Hi Tushar, let me investigate if it is possible to give some meaning full names in this error message. Is it for a specific source, or for all sources? Is it for all tables or only specific. It can be that this table gives an error while it is not known in the HVR repo.
Best regards,
Edwin
-
Hi Tushar,
It seems to us that this is DB2 LUW related. The table id is a combination of tablespace ID and tableid. We can also mention those separate, so you can find the related info yourself. We will also be looking into showing the schema and table name (if known to us).
Would that work?
Edwin
-
Hi Edwin
This is seen in multiple product like Sybase / db2 postgres / sql server We we get table id instead of table name.
Again its not a straightforward to know this info. You need to involve respective DBAs to get this thing.
This info is available with HVR as they now what transaction they are executing on which table.
-
Hi Tushar, we are planning to improve this as far as this information is within HVR. We don't have an ETA yet on the delivery.
Best regards,
Edwin
Please sign in to leave a comment.
Comments
4 comments