topic Re: Facing anywhere existence error in Qlik Replicate

Facing anywhere existence error

chandraprakash_j_volvo — Tue, 23 Apr 2024 05:15:47 GMT

Source: On-Prem SQL server

Target: Azure SQL server

We are copying 196 tables from source to target. For whole night it was running fine. Full load and Change processing was perfect over a night.

Suddenly we encountered this error.

Re: Facing anywhere existence error

DesmondWOO — Tue, 23 Apr 2024 05:56:49 GMT

Hi @chandraprakash_j_volvo ,

According to the error message, Replicate cannot find the LSN from the transaction log. Please check this article: "Failure validating initial LSN 'xx:xx:xx' 'anywhere existance'. Found nowhere" for details.

Regards,
Desmond

Re: Facing anywhere existence error

SushilKumar — Tue, 23 Apr 2024 08:06:29 GMT

Hello @chandraprakash_j_volvo

Such error occurred when QR is not able to find the Transaction logs to apply the changes being cached since the Full load initiated. To resolve such issue, you need to pick the best option as per your business requirement from where Qlik Replicate read the changes. Such as Transaction logs/Online logs / backup logs. And you must have sufficient space to hold till they are read or process by Qlik replicate.

You may need to observe the volume of data to anticipate the Space requirement.

Regards,

Sushil Kumar

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!

Re: Facing anywhere existence error

narendersarva — Tue, 23 Apr 2024 23:36:41 GMT

@chandraprakash_j_volvo

Additionally, please check the sql server logs around the same time to find out the SQL native errors.

Thanks
Naren