OSSYS_BPM_ACTIVITY

OSSYS_BPM_ACTIVITY

  

Hi all,

Want to know about this table OSIDX_OSSYS_BPM_ACTIVITY. What is the impact when we truncate this table? 

Thanks in advance.

Regards,

Sripriya Sekar

That's the index for BPT Activities.

What kind of problem are you facing? Slowness with BPT processes?

Hi Joao,

Thanks for your quick response.

This table is utilizing more space around 1050 MB. Because of this, we are facing tablespace issue and also need to know the exact impact when we truncate this table. 

Thanks,

Sripriya Sekar



If the index grew maybe it's because the table being indexed (ossys_bpm_activity) grew also. Have you checked your processes? Are there more instances than usual?

I suggest we first try to understand why the index is taking more space...

Hi this is regarding the same problem reported by Sripriya.

Yes there were loads of processes running than usual. Those processes were terminated safely by BPT Utils tool.

Processes were fixed. But it looks loads of data in OSSYS_BPM_ACTIVITY table.

Now the question is, the data inside the OSSYS_BPM_ACTIVITY can be truncated?

Please use the BPT API.

Make a tool to cleanup your BPT processes.

In this tool you'll have, for instance, a query that gets all the terminated processes. Then call Process_Delete for each identified process. This way you guarantee the meta-model remains consistent.


https://success.outsystems.com/Documentation/10/Reference/OutSystems_APIs/BPT_API

Ya we know about BPT API and it is used in BPT Utils forge as well. 

But for now we want to know whether I can truncate the records in table ossys_bpm_activity.? 

If truncating this table records will not impact any process/ function of the application?

As this table is causing performance issue in application.

Did you even read the documentation?

Why truncate that specific table leaving behind "input parameters values, output parameters values, processes instances, etc".

Why not doing it the right way (IMHO)?

Solution

If you want to quickly fix your database issue (before doing anything else), you can safely delete the closed/terminated processes (OSSYS_BPM_PROCESS WHERE STATUS_ID IN (2, 5) ) instead of the activities directly (activities will cascade delete) and the data will keep its consistency. Just be sure you know what you are deleting.

Best regards,
Tiago

Solution

Tiago Martins wrote:

If you want to quickly fix your database issue (before doing anything else), you can safely delete the closed/terminated processes (OSSYS_BPM_PROCESS WHERE STATUS_ID IN (2, 5) ) instead of the activities directly (activities will cascade delete) and the data will keep its consistency. Just be sure you know what you are deleting.

Best regards,
Tiago

Great! We are trying this one


Arunkumar Balu wrote:

Great! We are trying this one

Good luck!