Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Micros 3700 - XX amount of check not purged

Status
Not open for further replies.

CH Morel

Technical User
Sep 20, 2016
9
US
We recently upgraded to 5.7 from 5.4 and are getting "XX amount of checks have not been purged" warning on the WSs almost everyday. I end up having run call micros.sp_purgehistory script almost daily in dbisql. Our End of night autosequence has the step set up to purge historical totals and skip step is false yet we still have this issue. I have run the script below and it returned no result.

Select * from micros.chk_dtl
where chk_open = 't'
order by chk_seq

Local micros office has no idea, any ideas on how to resolve?

Thanks
 
Jesus how bad is support these days if they cant workout a check purging issue.


So the purging issue is not USUALLY caused by open checks but by closed checks which are in the database for longer than 14 days.

You want to run this sql to see whats the oldest transaction record in the database:

select max(business_date) from micros.trans_dtl

You want to run your micros.sp_purgehistory until this date is 14 days before the current date. Keep running the purchase until the date doesnt change for a few times in a row to make sure all records from the last date are gone.

Next you will let your End of Night try and purge the history normally.
You will want to look into your 3700d.log file the next day and search for the purge task and see if there are any errors.






Specialist in creating custom applications for the Micros POS range: 3700, 9700, Simphony FE, Simphony. SIM Scripts, Data Exports, Simphony extension applications, API Creation and integration. If you need anything please contact me via my website
 
A successful purge will look something like this:

Mon Jan 18 17:33:58 2021 | SERVER | Autosequence.dll | 0 | {CALL MICROS.sp_PurgeHistory} |
Mon Jan 18 17:34:00 2021 | SERVER | Autosequence.dll | 0 | Step completed. |
Mon Jan 18 17:34:00 2021 | SERVER | Autosequence.dll | 0 | Autosequence 10020 step 2 of type S has completed in -2 seconds. |
Mon Jan 18 17:34:00 2021 | SERVER | Autosequence.dll | 0 | -------------------------------------------- |

Specialist in creating custom applications for the Micros POS range: 3700, 9700, Simphony FE, Simphony. SIM Scripts, Data Exports, Simphony extension applications, API Creation and integration. If you need anything please contact me via my website
 
Thanks CathalMF,

assume you meant select min(business_date) from micros.trans_dtl rather than max date. Already have done all that and it shows 14 days before the current date. In the past after i have done that the warning will pop back up after a few days.
 
Yes sorry min :)

Have you been monitoring the logs to see if the purge is running without errors?

Specialist in creating custom applications for the Micros POS range: 3700, 9700, Simphony FE, Simphony. SIM Scripts, Data Exports, Simphony extension applications, API Creation and integration. If you need anything please contact me via my website
 
See if you have a check stuck preventing the purge....do you get an error in the log as per CathalMF?
Have you tried a rebuild then purge?
Have you called the purge directly and not thru an autosequence?
 
Sure enough there is an error there.

Fri Apr 23 04:00:03 2021 | MICROS37 | AutoSeqServer | 0 | Purge Historical Totals |
Fri Apr 23 04:00:03 2021 | MICROS37 | Autosequence.dll | 0 | {CALL MICROS.sp_PurgeHistory} |
Fri Apr 23 04:00:05 2021 | MICROS37 | Autosequence.dll | 0 | SQLExecDirect: (40001)[SAP][ODBC Driver][SQL Anywhere]Deadlock detected |
Fri Apr 23 04:00:05 2021 | MICROS37 | AutoSeqServer | 0 | Autosequence 10102 step 8 of type S has encountered a stored procedure error...Error executing stored procedure. |

Any ideas on how to resolve?
 
Deadlocks are a pain to investigate.

It basically means something else is working on the tables that the purge history needs to access. Do you have any other programs installed that access the database transaction tables?

Specialist in creating custom applications for the Micros POS range: 3700, 9700, Simphony FE, Simphony. SIM Scripts, Data Exports, Simphony extension applications, API Creation and integration. If you need anything please contact me via my website
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top