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

Announcements
Qlik Unveils New Agentic Capabilities Across Analytics, Data Engineering, and Trust: Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
CHahn
Contributor II
Contributor II

High Diskspace usage Sorter Swap Files

Hello,

there was an high processing load on source Oracle Database, which producing few hundert gb of archivelogs.
So tasks also created a lot of sorter swap files until the available diskspace was full.

So my question is, if there is a possibility of configuration max usage on diskspace for stroing swap files?
On Service level or at leased on task level?

BR 
Christian

Labels (3)
1 Solution

Accepted Solutions
john_wang
Support
Support

Hello Christian, @CHahn 

Thanks for the detailed information.

However, this configuration is not available in the current major versions. If this functionality is required, please submit a feature request.

Best 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!

View solution in original post

3 Replies
john_wang
Support
Support

Hello Christian, @CHahn 

If I understand correctly, a very large batch job was executed on the source Oracle database. As a result, the transactions became too large to remain in memory and were offloaded to disk, eventually exhausting the available disk space.

In this scenario, Qlik Replicate requires sufficient disk space to temporarily store these transactions, so adequate disk allocation is necessary.

I’m not sure how long it will take to process the accumulated archived redo logs. If sufficient disk space cannot be provided, you may consider the following options:

  1. Configure disk-usage notifications so you can stop the task before the disk becomes full and receive alerts in advance.

  2. Change the location of the Qlik Replicate data directory. See Qlik Replicate Moving the Data Directory on the same server to a larger drive.
  3. Skip the redo logs if the changes can be ignored—for example, by starting the task from a specific timestamp or SCN.

  4. If the changes cannot be skipped, the task will need to be reloaded to maintain data integrity.

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!
CHahn
Contributor II
Contributor II
Author

Hi John,

thank you very much for jour explainations.

But it does not protect me from next higher load on source or target, so that again much swap space is needed.
Montoring including alerting is a good idea, but in that case I wouldn't be able to react fast enough.
And to put there 1TB disk space which is most of time empty, isn't that great.

So my point it would be very useful parameter to configure how much disk space is allowed to use for swap files. Latest at that time it is used, reading next processing data is stopped. Replicate collected data from swap files until enough swap space is available again.

Only some idea for future release or features.
Thanks
Christian 

john_wang
Support
Support

Hello Christian, @CHahn 

Thanks for the detailed information.

However, this configuration is not available in the current major versions. If this functionality is required, please submit a feature request.

Best 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!