JMast
Reputable Poster
All,
We recently upgraded from SQL 2000 to SQL 2005 SP3. We also moved from SP23_K to SP23_ZA1. We have Win 2003 Enterprise with 12 GB RAM on the DB server.
Everything went well on the upgrade and we are seeing the expected performance gains....except in two slippery instances.
1. R42118 which allocates inventory to backordered Sales lines occasionally (1 out of 10 times a day every 3 or so days) errors on the server.
2. P4210 blows up a Sales Order when the Place Order button is clicked randomly (every other day or so).
We place 200+ orders a day, so this is a rare occurrence and you could chalk it up to the occasional JDE cache failure except it did not happen this often before the upgrade.
I have had no luck in debugging or SQL tracing an order that blows up.
I did see the attached log for one of the failed R42118.
Has anyone seen something similar after upgrading a JDE Service Pack/Tools or a database upgrade? Any tips you have on tracking this down would be great. I tried turning debug on for R42118, but the log was over 1GB which becomes useless.
I know this is not much info, but that is the slippery nature of this problem.
Thanks for your insight,
Jer
We recently upgraded from SQL 2000 to SQL 2005 SP3. We also moved from SP23_K to SP23_ZA1. We have Win 2003 Enterprise with 12 GB RAM on the DB server.
Everything went well on the upgrade and we are seeing the expected performance gains....except in two slippery instances.
1. R42118 which allocates inventory to backordered Sales lines occasionally (1 out of 10 times a day every 3 or so days) errors on the server.
2. P4210 blows up a Sales Order when the Place Order button is clicked randomly (every other day or so).
We place 200+ orders a day, so this is a rare occurrence and you could chalk it up to the occasional JDE cache failure except it did not happen this often before the upgrade.
I have had no luck in debugging or SQL tracing an order that blows up.
I did see the attached log for one of the failed R42118.
Has anyone seen something similar after upgrading a JDE Service Pack/Tools or a database upgrade? Any tips you have on tracking this down would be great. I tried turning debug on for R42118, but the log was over 1GB which becomes useless.
I know this is not much info, but that is the slippery nature of this problem.
Thanks for your insight,
Jer