Skip to main content

Search

Welcome to Tibero GTS!

How to Adjust ProSync History When an Error Occurs Due to Missing lr File

Document Type | Troubleshooting

Category | Administration

Applicable Product Versions | 6FS06, 6FS07

Document Number | PADTS002

 

Issue

This explains the phenomenon where an error "tli_load_txinfo failed (rc:-3)" occurs in the extraction log (ext), causing synchronization to stop. 
 
 
 

Cause

The redo_data_87670_0.tlr file is lost due to an unspecified reason, resulting in the error "tli_load_txinfo failed (rc:-3)" and synchronization stopping.
[01-11T14:46:44.068990] [REA-04] [I] txinfo found (/app/tibero/prosync4/var/us_to_xx/lr1/redo_data_87670_0.tlr)
[01-11T14:46:44.069004] [REA-04] [E] tli opened (flag:0x02, logblk_size:512, logblk_cnt:8)
[01-11T14:46:44.069019] [REA-04] [I] tli_load_txinfo failed (rc:-3) [prs_ext_tread.c:748]
 
 
 

Solutions

This is the procedure to adjust the history based on a point in the past history where no lr files were missing. 

1. Update the SEQNO value to a previous point in time for the row with the maximum value (max) in the HIST# column of the PRS_CONST_HIST table on the TARGET server.

SQL> select * from PROSYNC_US_TO_XX.PRS_CONST_HIST order by HIST#;

HIST#   NODE#     SEQNO      WRAPNO      GROUP#         TIME
---------- ---------- ---------- ---------- ---------- ---------------------------------------------------------

62245     1       87669         0          1          2024/01/11 13:30:24
62246     1       87670         0          1          2024/01/11 15:45:37


62203 rows selected.


SQL> update PROSYNC_US_TO_XX.PRS_CONST_HIST set SEQNO=87669 where HIST#=62246;

HIST# NODE# SEQNO WRAPNO GROUP#  TIME
---------- ---------- ---------- ---------- ---------- ----------------------------------------------------------------
62245     1       87669         0          1          2024/01/11 13:30:24
62246     1       87669         0          1          2024/01/11 15:45:37
 

2. Delete the problematic SEQ# from the PRS_TXINFO table on the SOURCE server.

SQL> select * from PROSYNC_US_TO_XX.PRS_CONST_HIST order by HIST#;

HIST#   NODE#     SEQNO      WRAPNO      GROUP#         TIME
---------- ---------- ---------- ---------- ---------- ---------------------------------------------------------

62245     1       87669         0          1          2024/01/11 13:30:24
62246     1       87670         0          1          2024/01/11 15:45:37


62203 rows selected.


SQL> update PROSYNC_US_TO_XX.PRS_CONST_HIST set SEQNO=87669 where HIST#=62246;

HIST# NODE# SEQNO WRAPNO GROUP#  TIME
---------- ---------- ---------- ---------- ---------- ----------------------------------------------------------------
62245     1       87669         0          1          2024/01/11 13:30:24
62246     1       87669         0          1          2024/01/11 15:45:37
 

3. Restart ProSync.

Note
Since adjusting the history may cause data inconsistency, it is recommended to perform data consistency verification.
 
 
 
 
 
 
 
 

Related to