Skip to main content
Announcements
UPGRADE ADVISORY for Qlik Replicate 2024.5: Read More
cancel
Showing results for 
Search instead for 
Did you mean: 
gseckin
Contributor II
Contributor II

Full Load Failed

Hi,

I created a task with cdc + full load with 11 tables. 10 tables loaded but one is failed during full load. I also enabled parallel load, but it didn't help. I'm using oracle as a source and kafka as a target. When I try to find logs related to this failure, I can not see anything. This table contains more than 4b rows. Do you have a configuration for big tables. How can I load big tables without error?

And where can I find the logs?

My last question is that can I start this full load from the point it stopped?

Thanks

Labels (4)
11 Replies
john_wang
Support
Support

Hello @gseckin ,

Thanks for reaching out to Qlik Community!

The detailed error messages recorded in Task log files, depends on Qlik Replicate platform, the log files can be found in below location

Windows - C:\Program Files\Attunity\Replicate\data\logs

Linux - /opt/attunity/replicate/data/logs

BTW, if an error occurs during the Full Load stage then we need to redo the Full Load from scratch.

Hope this helps.

John.

 

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

Hi @john_wang ,

Yes I know the log path, and in the path you said. I also found log files. But I can not find something related the full load failure. It says Task is running, and actually cdc part is still running. I need to find full load log. Do you have different log file for full load?

And my sec question is do you have a configurations to load big tables?

Thanks

john_wang
Support
Support

Hello @gseckin ,
Thanks for the update.

You may change the logging level of different logging components. In order to trace the Full Load stage issue, you may set SOUCE_UNLOAD/TARGET_LOAD to Trace, or Verbose to get detailed information, see below screen sample:

john_wang_0-1720080512726.png

Save the changes, re-run the task and then check the task log files.

Regards,

John.

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

Hello @gseckin 

IF the Full load task is running then its highly likely QR is fetching the Data to process the data further.

There are Some values you can change to extract the data faster, Parallel work when table have partition or try to get the data divide by the parallel config in full load settings.

Regards,

Sushil Kumar 

gseckin
Contributor II
Contributor II
Author

I found this configuration to set log level but it's different than yours

gseckin_0-1720080960765.png

Where I can find the one you showed me?

john_wang
Support
Support

And my sec question is do you have a configurations to load big tables?

I'm not very sure what's the Qlik Replicate version you are running now, I'd like suggest you to use Parallel Load to speed up the Full Load.

Regards,

John.

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

Hi @SushilKumar ,

Yes already did that configuration. Increased max table count to 30 and enable pararlel load for table. Let me share my configurations.

This is task settings

gseckin_1-1720081089889.png

 

and this is table settings

gseckin_2-1720081116849.png

 

What am I missing here? Can you check my configurations? Thanks

 

 

vinayak_m
Contributor III
Contributor III

Hi @gseckin ,

Partition option will work when the partitions are already created in the source system.
Since you've already tried this and it does not seem to work, I suggest you try to use data ranges on a datetime column preferably. 
And segment the data of your table on the specific datetime column.(Year/Date) 
You can also use any ID column or PK column if present in table.

Please see image for reference, 
Let us know if this configuration works for you.

vinayak_m_0-1720081772412.png

 

gseckin
Contributor II
Contributor II
Author

I just saw this error,

ORA-01555 snapshot too old: rollback segment number 565 with name :..... too small. How we can fix this issue? Thanks