topic Re: No tables were found at task initialization in Qlik Replicate

No tables were found at task initialization

lqthinguyen — Tue, 01 Oct 2024 02:35:18 GMT

Good evening,

I have verified that supplemental logging are on at both

1) the database level on SOURCE

select SUPPLEMENTAL_LOG_DATA_MIN, SUPPLEMENTAL_LOG_DATA_PK, SUPPLEMENTAL_LOG_DATA_UI from v$database;

YES YES NO

2) at the table level also on SOURCE

ALTER TABLE HR.EMPLOYEES DROP SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS; ALTER TABLE HR.EMPLOYEES DROP SUPPLEMENTAL LOG DATA (UNIQUE) COLUMNS; ALTER TABLE HR.EMPLOYEES DROP SUPPLEMENTAL LOG DATA (ALL) COLUMNS;

Captured from the Replication log below

Questions 1) Why the message - Supplemental logging automatic definition is disabled ? and 2) No tables were found at task initialization. Either the selected table(s) no longer exist or no match was found for the table selection pattern(s) - Please enlighten what need to be configured or missing from the confiugration THANK YOU!

2024-09-30T15:59:00 [METADATA_MANAGE ]I: Supplemental logging automatic definition is disabled (oracle_endpoint_imp.c:946)
2024-09-30T15:59:00 [METADATA_MANAGE ]I: Replication Setting/ECA 'openTransactionWindow' is Disabled (oracle_endpoint_imp.c:1397)
2024-09-30T15:59:00 [METADATA_MANAGE ]I: Going to connect to Oracle server (DESCRIPTION=(CONNECT_TIMEOUT=8)(ENABLE=BROKEN)(ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=))(CONNECT_DATA=(SERVICE_NAME=))) with username DIGITAL_NSY_APP_USER (oracle_endpoint_imp.c:1471)
2024-09-30T15:59:00 [METADATA_MANAGE ]I: Connecting to Oracle: Beginning session (oracle_endpoint_conn.c:1049)
2024-09-30T15:59:00 [METADATA_MANAGE ]I: Source endpoint 'Oracle' is using provider syntax 'Oracle' (provider_syntax_manager.c:894)
2024-09-30T15:59:00 [METADATA_MANAGE ]I: Going to connect to ODBC connection string: DRIVER={PostgreSQL};SERVER=d;UID=Digitalpilots; (odbc_endpoint_imp.c:2212)
2024-09-30T15:59:00 [METADATA_MANAGE ]I: Target endpoint 'PostgreSQL' is using provider syntax 'PostgreSQLLinux' (provider_syntax_manager.c:900)
2024-09-30T15:59:00 [METADATA_MANAGE ]I: postgres_set_encoding(...) Main encoding details: Name='UTF8', Language='all', isServerEncoding?='true' storageFactor=4, ConverterName='UTF-8' (odbc_endpoint_imp.c:3220)
2024-09-30T15:59:00 [METADATA_MANAGE ]I: Postgres Endpoint created using default mode (odbc_endpoint_imp.c:3939)
2024-09-30T15:59:00 [TASK_MANAGER ]I: Preparing all components (replicationtask.c:2237)
2024-09-30T15:59:00 [TASK_MANAGER ]I: Task - 67WD6KV24RFJRC7OEWJ2WIGVII is in STARTING state, updating starting status to AR_PREPARING_COMPONENTS (repository.c:5491)
2024-09-30T15:59:00 [TASK_MANAGER ]I: Creating threads for all components (replicationtask.c:2270)
2024-09-30T15:59:00 [TASK_MANAGER ]I: Task - 67WD6KV24RFJRC7OEWJ2WIGVII is in STARTING state, updating starting status to AR_CREATING_TREADS (repository.c:5491)
2024-09-30T15:59:00 [TASK_MANAGER ]I: Task - 67WD6KV24RFJRC7OEWJ2WIGVII is in STARTING state, updating starting status to AR_CREATING_TABLES_LIST (repository.c:5491)
2024-09-30T15:59:00 [TABLES_MANAGER ]I: Calling for get capture table list from the Metadata Manager started. (tasktablesmanager.c:960)
2024-09-30T15:59:00 [METADATA_MANAGE ]I: OCI_ATTR_RECEIVE_TIMEOUT temporary set to 1800000 millisecs (~30 mins) (oracle_endpoint_lists.c:1023)
2024-09-30T15:59:00 [TABLES_MANAGER ]I: Calling for get capture table list from the Metadata Manager ended. (tasktablesmanager.c:967)
2024-09-30T15:59:00 [TABLES_MANAGER ]W: No tables were found at task initialization. Either the selected table(s) no longer exist or no match was found for the table selection pattern(s). (tasktablesmanager.c:1292)
2024-09-30T15:59:00 [TASK_MANAGER ]E: No tables were found at task initialization. Either the selected table(s) no longer exist or no match was found for the table selection pattern(s). [1021707] (replicationtask.c:2409)

Re: No tables were found at task initialization

john_wang — Tue, 01 Oct 2024 03:31:40 GMT

Hello @lqthinguyen ,

Thanks for reaching out to Qlik Community!

>> 1) Why the message - Supplemental logging automatic definition is disabled ?

Select this option to automatically set up supplemental logging for the Oracle monitored tables. Enabling this option requires the necessary privileges, as Qlik Replicate will alter the tables on your behalf if supplemental logging has not yet been configured.

In your scenario, this option was disabled, which led to the messages. So far you need manually setup the supplemental loggings.

>> 2) No tables were found at task initialization. Either the selected table(s) no longer exist or no match was found for the table selection pattern(s)

During task initialization, no table was found. For example, the table "EMP" was included in the task during the design phase and is visible in the GUI, allowing you to select it and add it to the monitoring list. However, before the task could run, the table was dropped, resulting in the message.

Hope this helps.

John.

Re: No tables were found at task initialization

john_wang — Tue, 01 Oct 2024 04:09:27 GMT

additional comments:

1. In your sample

ALTER TABLE HR.EMPLOYEES DROP SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS; 
ALTER TABLE HR.EMPLOYEES DROP SUPPLEMENTAL LOG DATA (UNIQUE) COLUMNS; 
ALTER TABLE HR.EMPLOYEES DROP SUPPLEMENTAL LOG DATA (ALL) COLUMNS;

It seems you meant to use ADD instead of DROP.

2. Supplemental logging determines how many column values are recorded in the redo log. Adding more columns to the redo log increases storage requirements and can impact database performance. For Qlik Replicate, minimal supplemental logging is usually sufficient. The specific level of supplemental logging is determined based on the source table’s structure (in order):

If a PK exists
If no PK exists and has a single UI
If no PK exists and has multiple UI
If no PK no UI
If a filter or transformation is used
If UPSERT mode is used

For more detailed information, refer to the User Guide: Make sure that the required supplemental logging is added.

So far for table HR.EMPLOYEES, you need NOT the 3 SQLs, one ALTER TABLE is enough.

Good luck with your project,

John.

Re: No tables were found at task initialization

lqthinguyen — Tue, 01 Oct 2024 05:03:56 GMT

Good evening Mr. John

SOURCE is Oracle AWS RDS and Supplemental Logging is turned on manually at both the database as well as the table levels; therefore we could ignore the "1) Supplemental logging automatic definition is disabled" ????

In your scenario, this option was disabled, which led to the messages. So far you need manually setup the supplemental loggings.

TARGET is using AWS DMS as a Replicate Tool. and PostGreSQL. I believe AWS DMS is Qlik Replicate product (?)

Thank you

Theresa

Re: No tables were found at task initialization

lqthinguyen — Tue, 01 Oct 2024 05:06:28 GMT

Good evening Mr. John

I believe you are correct on both notes. I meant 'ADD' not 'DROP' also overpowering with the supplemental logging could impact performance, sir

2) No tables were found at task initialization. Either the selected table(s) no longer exist or no match was found for the table selection pattern(s)

Re: No tables were found at task initialization

john_wang — Tue, 01 Oct 2024 05:08:48 GMT

@lqthinguyen Hi,

>> we could ignore the "1) Supplemental logging automatic definition is disabled" ????

Yes. Either Qlik Replicate set it up on behalf of you. Or your DBA config it manually.

>> I believe AWS DMS is Qlik Replicate product (?)

Yes, it's OEM product.

Hope this helps.

John.

Re: No tables were found at task initialization

MoeE — Wed, 04 Mar 2026 04:59:37 GMT

Hi John,

Do you have any further insight into problem 2? A client is facing the same issue and it occurs randomly. When you say the table was dropped, do you mean it was dropped from the source database, or was it dropped from the QR task? Thank you.

Regards,

Mohammed

Re: No tables were found at task initialization

john_wang — Wed, 04 Mar 2026 05:17:16 GMT

Hello Mohammed, @MoeE

2) No tables were found at task initialization. Either the selected table(s) no longer exist or no match was found for the table selection pattern(s)

If all tables were dropped or renamed in the source database, Qlik Replicate fails to locate any one table during task startup, which results in this message being displayed.

To verify table availability before starting the task, click “Full Table List.” Qlik Replicate will retrieve the complete list of currently available tables, including both explicitly included tables and those matched by selection patterns, as shown below:

Hope this helps.

John.

Re: No tables were found at task initialization

MoeE — Wed, 04 Mar 2026 05:43:25 GMT

Hi John,

Thank you. I've been unable to recreate the exact behaviour my client is seeing. The client only experiences a warning but the task continues running without any errors or failiures.

I tried renamed my source table to something else and then reloading my task however I am not able to recreate their exact behaviour. In my case, the table is suspended and the task fails. Furthermore, I don't get the exact message: "No tables were found at task initialization. Either the selected table(s) no longer exist or no match was found for the table selection pattern(s)."

I think I will create a Qlik case to address this issue.

Regards,

Mohammed

Re: No tables were found at task initialization

john_wang — Wed, 04 Mar 2026 06:22:49 GMT

Thank you for your support ! @MoeE