Database Purge and Summarize has been running for TWO WEEKS

You are welcome!

Epicor 9.05.702A 32-Bit Progress, 64-Bit Windows


I started a Database Purge and Summarize back in the beginning of April on a test box and it looked like it wasn't going to do anything, as the System Monitor would just show 'PartTran: 0'. I decided to leave it for a week and come back to it rather than just canceling the process. 


After a week, lo and behold it shows 'PartTran: 300', but the last activity datetime was from two days before. It's now been two weeks and we're on to the Labor Table, but there's no way that this is any sort of acceptable. We've only got a 15GB database, so I can't imagine those of you with 100+ GB DBs...


Any ideas as to how to speed this up? CPU shows virtually no activity.



There is an issue with the PartTran purge.  We received a fix for it, and the PartTran purge did finally complete.  Labor and Journal Details are broken.  Don't bother with those.  After applying the PartTran fix, we purged about 10 million records(including POs, SOs, etc) in about 9 hours.  Our DB was around 90GB at the time.

--Matt Caldwell
Good to know, thanks!

Did you get an SCR or something I can reference when I call up Epicor to hopefully speed through the process?
Here you go...

**RETRO FIX FOR SCR 132127 - Database Purge and Summarize - Purge of Transactions (PartTran) hangs and does not complete

 

Before Installing:

     Prior to use of this retro it is recommended to make a backup of the database and/or files being replaced then test this issue in a test area to confirm proper operation.

 

     Server

          server\xa     dbpurgelogic.r

HOW TO APPLY THE SCR FIX

Please test before applying to production.

Steps to apply fix:

Server

1)  Make a backup copy of the dbpurgelogic.r file in the server\xa directory.

2)  Copy this new dbpurgelogic.r file into the server\xa directory.

 

 

Note:  Remember that this change has NOT gone through QA and regression testing.  While every effort has been made to ensure that it will operate properly, it is the customer's responsibility to ensure that it is operating correctly in their specific situation prior to placing it in a live environment.

DATABASE VERSION:  9.05.70x Progress64


Fantastic. Thanks!