topic Re: Best Practices for Teradata Table Management in Qlik Replicate

Best Practices for Teradata Table Management

iti-attunity-sup — Thu, 28 Aug 2025 09:15:22 GMT

Hello.

When Teradata is specified as the target endpoint, My understanding is that Qlik Replicate creates log and error tables (with table names ending in *L0, *E1, or *E2 and so on).

Could you please confirm when these tables are generated, and whether they need to be manually deleted?

If manual deletion is required, we assume that the relevant task should be stopped beforehand.
Aside from that, if there are any other precautions or considerations we should be aware of, your guidance would be greatly appreciated.

[Background of the question]
A large number of log and error tables have been created and the customer would like to clean them up as part of system maintenance.

Best Regards.

Re: Best Practices for Teradata Table Management

john_wang — Mon, 01 Sep 2025 16:19:58 GMT

Hello @iti-attunity-sup ,

Thanks for reaching out to Qlik Community!

These log and error tables are required for Teradata client–server communication, particularly during the upload of interim CSV files to the Teradata server. They are created by Teradata itself—not by Qlik Replicate.

As for cleanup, some of these tables are removed automatically, while others remain. In particular, if errors occur, the corresponding tables are retained so you can review and address the issues. For more details, please refer to the official Teradata documentation.

These tables can be cleaned by script or as part of system maintenance if they are useless anymore.

Hope this helps.

John.

Re: Best Practices for Teradata Table Management

iti-attunity-sup — Tue, 02 Sep 2025 06:41:48 GMT

Hello John-san

I got it. Thank you for your response.

Best Regards

Re: Best Practices for Teradata Table Management

john_wang — Tue, 02 Sep 2025 06:44:36 GMT

Thank you so much for your outstanding support! @iti-attunity-sup