I have configured a Log Stream task that is reading from an Oracle source database. Over the last few months I’ve added more than 50’000 tables to the Log Stream and the task was always able to run without issues.
Today, I tried adding other 5’000 tables to the Log Stream. Unfortunately, after adding them, the task failed to resume successfully. Qlik Replicate logged the following errors: [METADATA_MANAGE ]E: Failed to get the capture list from the endpoint [TABLES_MANAGER ]E: Cannot get captured tables list [TASK_MANAGER ]E: Build tables list failed
It seemed to me that the tables list was too long. So, I removed all the 5’000 tables I just added. However, even after removing them, the Log Stream task is still unable to resume and continues to return the same error.
Is it possible that a task with the same configuration (both at task and endpoint level) is able to read and replicate a full list of tables, but then at some point can no longer handle it?
Is there any Qlik Replicate configuration (at the task or endpoint level) that could help prevent this type of issue or at least allow more time for retrieving the tables list?
It appears there may be a practical limitation on the number of tables that can be included in a single task. Based on lab observations, when the table count exceeds 20,000, the GUI response becomes noticeably slow. When it goes beyond 50,000, the repository may become unstable or corrupted, and the GUI can stop responding entirely—often requiring the task to be removed from the repository to recover.
Although the exact upper limit is not clearly defined, it is strongly recommended to keep the number of tables within a reasonable range—for example, by splitting them across multiple tasks.
If cleanup is required, you can remove the task either through the GUI (if it is still responsive) or via the command line (if the GUI is no longer usable):
Command-line steps:
Run “Qlik Replicate Command Line” as Administrator
Navigate to the Replicate bin directory
Execute:
repctl [-d YOURDATADIR] deletetask <taskName>
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!
It appears there may be a practical limitation on the number of tables that can be included in a single task. Based on lab observations, when the table count exceeds 20,000, the GUI response becomes noticeably slow. When it goes beyond 50,000, the repository may become unstable or corrupted, and the GUI can stop responding entirely—often requiring the task to be removed from the repository to recover.
Although the exact upper limit is not clearly defined, it is strongly recommended to keep the number of tables within a reasonable range—for example, by splitting them across multiple tasks.
If cleanup is required, you can remove the task either through the GUI (if it is still responsive) or via the command line (if the GUI is no longer usable):
Command-line steps:
Run “Qlik Replicate Command Line” as Administrator
Navigate to the Replicate bin directory
Execute:
repctl [-d YOURDATADIR] deletetask <taskName>
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!
