How to recover lost messages

[AnujGupta]

Hello Team, 

I have a task in Qlik whose source in Oracle Onprem, task is running fine till may end. After that we lost connection for 45 days. Today connection is again back. How to recover messages which were happen during 45 days. I have full load & apply changes on in task setting.

Source - Oracle. 

Destination - Azure Blob storage.

Qlik Version - Nov release.

Thanks

Anuj Gupta

[SachinB · Accepted solution]

Hello @AnujGupta ,

Thanks for reaching the Qlik Community,

There is a way you can recover the transactions from last 45 days by using the timestamp method from the advanced resume option. In order to do that, you should be having the redo log files which are created 45 days back, However you might not be having these many old redo log files carrying in online/archive location, These might have moved to tape/deleted by your oracle endpoint.

In Oracle Database, the maximum retention policy for redo logs is determined by the size and number of redo log files rather than a specific limit set by the database itself, Kindly check with DBA for retention policy and act accordingly.

The best option is to go for full load.

Let us know in case if you need additional information on same.

Regards,

Sachin B

[Arun_Arasu]

Hello @AnujGupta ,

Thank you for getting in touch with the Qlik community!

Based on my understanding, if you have redo logs available for the 45-day period in your Source system, you may consider starting the task using a timestamp from when it was last stopped.

However, if those logs were deleted, I believe reloading the data is the only viable option.

If you need further assistance or have any more questions, please feel free to ask.

Regards,
Arun

[SushilKumar · Accepted solution]

Hello Team,

Based on Scenarios you may have, If your database connection for 45 Days then it recommends reloading the Target Again.

Would suggest below Steps to test the scenario you have.

1. You Must have space to accommodate that many logs till now.
2. There is no change to archive/redo log format and database Compatible Parameter.
3. Archive/redo log must be cataloged in the DB control file again.

select thread#,sequence#,Status,CREATOR from v$archived_log;

Status of the archived log: ( You might have Status as D,U,X)
A - Available
D - Deleted
U - Unavailable
X - Expired

4. Hence you need to Re-catalogue those again with below commands.

alter database register physical logfile '<Folder where Archive log restored>/Archive_log_name';

5. Rerun the SQL Query again

select thread#,sequence#,Status, CREATOR from v$archived_log;

Status of the archived log: ( You might have Status as A)

A - Available
D - Deleted
U - Unavailable
X - Expired

6. Now you may start the using the timestamp method from the advanced resume option.

if you find the Explanation Useful request you to mark it as Accept as Solution.

Regards,
Sushil Kumar

[AnujGupta]

If we got Database logs from oracle does it help. Any docs ?

[AnujGupta]

DBA reply 

We do not have redo available for 45 days. For Qlik we just keep 72 hours of archives retention on disk after which they are moved to TSM. Additionally we have 14 days retention for backups.

I.e we don't have any option to recover 45days data, is my understanding is correct with DBA reply??

[SushilKumar]

Hello Team,

Changes are stored in the REDO Loges/Archive logs. As we mentioned Earlier you Must have space to accommodate that many logs till now.  You need to follow the steps as mentioned above are need to perform by the DBA on the DB end.

Reagrds,

Sushil Kumar

[SachinB]

Hello @AnujGupta ,

Yes, It's not possible to recover the 45 days back redo log files as per the DBA confirmation, We would strongly recommend going for reload option.

Regards,

Sachin B