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

Announcements
Write Table now available in Qlik Cloud Analytics: Read Blog
cancel
Showing results for 
Search instead for 
Did you mean: 
iti-attunity-sup
Partner - Creator III
Partner - Creator III

Best Practices for Teradata Table Management

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.

Labels (3)
1 Solution

Accepted Solutions
john_wang
Support
Support

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.

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 @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.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
iti-attunity-sup
Partner - Creator III
Partner - Creator III
Author

Hello John-san

I got it. Thank you for your response.

Best Regards

john_wang
Support
Support

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

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