Respected Contributor.. Paul Meaders Respected Contributor..
Respected Contributor..
985 views

database purging flows

Jump to solution

At some point it appears that two new database purging flows were added to the HPE Solutions content pack.  In earlier content packs I didn't see the "Purge Executions" and "Purge Rerun Data"

From the description there seems to be an overlap between "Purge Execution Summary" and "Purge Executions" flows.

Do all five purge database flows address different database tables, or is there some overlap.  Should I schedule all five for execution?

Thanks

 

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Re: database purging flows

Jump to solution

Hi, 

In the latest HPE Solutions content pack you are right to notice that a new purge flow was added.  This CP was released together with OO 10.70 in which you have the ability to set rerun points in your flows and in case of flow failure to re run the flow starting with that point. The data needed to make this possible is stored in a different table than the regular execution data and as such a new purge API and flow was required in order to clean up this data. Do note that rerun data is only stored for failed executions, sucessfull executions have this data automatically purged upon completion.

Regarding the purge flows themselves all flows target different tables and aspects of OO. 

Purge audit records targets the audit data saved when audit is enabled. This should only be used if audit is enabled.

Purge debug events clears up the data generated by studio remote debug events. These events are stored in different tables than the regular flow executions. Just as above this should be used only when remote debug is happening on the central.

Purge execution summary deals with  the regular execution data (flow inputs, outputs and step data).

Purge rerun data deletes the records generated by the rerun points of flows. The rerun data is only stored in the db if a flow has rerun points, the execution is  in a failed state and the rerun points are enabled in central. This flow will not work for versions of OO prior to 10.70 (the api behind it does not exist) and unlesss all 3 previously mentioned conditions are enabled there is no need to run it.

 

Hope this clears up what each purge flow does. 

Regards,

Vlad

0 Likes
3 Replies
Respected Contributor.. Paul Meaders Respected Contributor..
Respected Contributor..

Re: database purging flows

Jump to solution

Oops.. didn't notice that Purge Executions is an operation, not a flow.  So ony Purge Rerun Data is new.

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: database purging flows

Jump to solution

Hi, 

In the latest HPE Solutions content pack you are right to notice that a new purge flow was added.  This CP was released together with OO 10.70 in which you have the ability to set rerun points in your flows and in case of flow failure to re run the flow starting with that point. The data needed to make this possible is stored in a different table than the regular execution data and as such a new purge API and flow was required in order to clean up this data. Do note that rerun data is only stored for failed executions, sucessfull executions have this data automatically purged upon completion.

Regarding the purge flows themselves all flows target different tables and aspects of OO. 

Purge audit records targets the audit data saved when audit is enabled. This should only be used if audit is enabled.

Purge debug events clears up the data generated by studio remote debug events. These events are stored in different tables than the regular flow executions. Just as above this should be used only when remote debug is happening on the central.

Purge execution summary deals with  the regular execution data (flow inputs, outputs and step data).

Purge rerun data deletes the records generated by the rerun points of flows. The rerun data is only stored in the db if a flow has rerun points, the execution is  in a failed state and the rerun points are enabled in central. This flow will not work for versions of OO prior to 10.70 (the api behind it does not exist) and unlesss all 3 previously mentioned conditions are enabled there is no need to run it.

 

Hope this clears up what each purge flow does. 

Regards,

Vlad

0 Likes
Respected Contributor.. Paul Meaders Respected Contributor..
Respected Contributor..

Re: database purging flows

Jump to solution

Makes sense.  Thanks for the details.

Paul

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.