Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!

Qlik Replicate captures no Data after the Oracle Source has been upgraded to 4 Node RAC

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Bill_Steinagle
Support
Support

Qlik Replicate captures no Data after the Oracle Source has been upgraded to 4 Node RAC

Last Update:

Feb 14, 2023 2:51:43 AM

Updated By:

Sonja_Bauernfeind

Created date:

Feb 14, 2023 2:51:43 AM

The SCN value of the Qlik Replicate task is no longer valid after the Oracle environment upgrade as the SCN has changed.

Example:

Oracle was upgraded from a two-node RAC to a four-node RAC.

If the old SCN value is used during the restart of a Task, it will not capture changes. If SOURCE_CAPTURE is set to VERBOSE in the Qlik Replicate logs, you will see it log  No Data

 

Resolution

Before the upgrade: check the task log from the task being stopped for the Final saved task state.

The last source timestamp has the timestamp you can run on the Oracle Source using the Oracle function scn_to_timestamp using the value as shown from the last source timestamp (1667933318000000).

Final saved task state. Stream position 00000000.0117643d.00000001.0000.00.0000:181.137796.16, Source id 5406, next Target id 37, confirmed Target id 33, last source timestamp 1667933318000000

Select scn_to_timestamp(1667933318000000) as timestamp from dual:

TIMESTAMP

--------------------

04-DEC-22 01:48:38

The timestamp returned can be used as the start option for the task doing an Advance Run Option start from timestamp. This will start processing from the Oracle environment from the time the Task stopped and restarts reading from the saved timestamp prior to the upgrade.

Bill_Steinagle_0-1675890589599.png

 

Bill_Steinagle_1-1675890589616.png

 

 

Labels (1)
Version history
Last update:
‎2023-02-14 02:51 AM
Updated by: