PMSE tables cleaning in database

Hi Enes Saridogan

For cleaning up the SugarBPM processes, Sugar has the following ER: 79949 (https://portal.sugarondemand.com/#supp_Bugs/79949) that is fixed in release 10.3.0 Cloud only). I would suggest opening a ticket with the Sugar support portal and get a hotfix containing the ability to delete BPM tables via the scheduler job.

Kind Regards,

Junaid

Hello Junaid,

Thanks for the trick, I'll check that if the toothpast command won't work for Oracle

Best regards,

Enes

Hi Enes,

You are welcome

I have another question related to SugarBPM as you are already using the Oracle database. Did you guys face the issue that records stop showing up in the process management view once the 'Process Number' reached 9999? Also in the logs start getting the following error message.

"ORA-01438: value larger than specified precision allowed for (CAS_ID) this column"

Kind Regards,

Junaid

Hi Junaid,

Currently we have more than 560.000 records in pmse_inbox table, and no problem related to the one you mentionned

We are running in Oracle 12c.

Best regards and have a nice friday !

Enes

Hi Enes,

Yes, the cas_id field in the pmse_inbox table is all good. The problem comes in the related tables like pmse_bpm_thread, pmse_bpm_flow as they can only store up to 4 digit values in the mentioned field.

We are also using Oracle 12c, so it's strange you didn't notice that problem yet. Anyway, I am in contact with Sugar support on this, and let's see what they have to say.

Kind Regards and have a nice weekend ahead.

Junid

Hello Junaid,

I just checked in my database, and the cas_id column in pmse_bpm_flow table is not limited to 4 digits, no problem at all. Very strange :/

By the way, how are the general performance for your instance ? We are running in Sugar 7.9.3 (migration planned next year) and it is very slow when saving or displaying cases for example (700.000+ cases).

Best regards and have a nice week.

Enes

Hello Junaid,

I just checked in my database, and the cas_id column in pmse_bpm_flow table is not limited to 4 digits, no problem at all. Very strange :/

By the way, how are the general performance for your instance ? We are running in Sugar 7.9.3 (migration planned next year) and it is very slow when saving or displaying cases for example (700.000+ cases).

Best regards and have a nice week.

Enes

Enes Saridogan,

Sugar had a huge amount of performance improvements since version 7.9 (2017 release).

Please note that 7.9 has not been supported for a number of years as well, as the current on-premise version is 10.0.x.

The recommendation from me is to start planning the upgrade, as there are many steps involved (both on the infrastructure/architecture and at the application level) on getting through 3+ years worth of releases.

For your specific scenario you will find especially useful for listviews speed up some features we released back in version 8 to optimise record listing retrieval.

In saying that, it is good to think about either an archival strategy or a performance testing combined with system scaling strategy to make sure your system is in optimal shape for your business needs.

Hi Enes,

Then looks like they introduced that in Sugar9 or 8 because sugar support considers it as a bug.

Regarding performance issues, I would highly recommend upgrading your instance to Sugar9. As Enrico already mentioned, since Sugar8 there are a lot of performance improvements and things are loading pretty fast as compare to Sugar7.

Kind Regards,

Junaid