Expand my Community achievements bar.

SOLVED

Approach to delete remp tables created by wkf:Uncheck interim result workflows, purge history and manually execute the cleanup workflow. We saw in the backend database that it deletes the data without manual intervention.

Avatar

Level 4

@Denis_Bozonnet ,All

 

please recomemnd:

We have close to 2000 OLD wkfs LAST PROCESSED ON 2019 where  "kEep interim result ..." is checked 

now coz of this lot of temp tables were created and right now also they exist in db

now wwe want those tables to deleted from db====

we are thinking to follow this approach as recommeded by one of our colleegue":

Could you please suggest if this approach is safe in this case:

 

1. Uncheck interim result workflows, purge history and manually execute the cleanup workflow. We saw in the backend database that it deletes the data without manual intervention.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Shruti1 ,

Refer here for Workflow to uncheck keepInterim in all Workflows

As you have more number of workflows to uncheck keepInterim, You can create and modify the above workflow to uncheck all the WKFs automatically where keepInterim is enabled. Once unchecked, the temp table will get deleted in days mentioned in workflow property.

ParthaSarathy_0-1665405632383.png

 

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @Shruti1 ,

Refer here for Workflow to uncheck keepInterim in all Workflows

As you have more number of workflows to uncheck keepInterim, You can create and modify the above workflow to uncheck all the WKFs automatically where keepInterim is enabled. Once unchecked, the temp table will get deleted in days mentioned in workflow property.

ParthaSarathy_0-1665405632383.png

 

Avatar

Community Advisor

Hi @Shruti1 ,

 

After executing the remedy steps suggested by @ParthaSarathy you can ask your DBA (if On-Prem hosted) or Adobe (if Adobe hosted) to perform DB Vacuum.
A DB Vacuum will help you reclaims storage occupied by the dead tuples from your DB.

 

Br,

Shubham