AnsweredAssumed Answered

PRLOCK table filling with junk during job execution

Question asked by chris_shaffer on Dec 28, 2012
Latest reply on Jan 10, 2013 by chris_shaffer
In a 12.0.4 test environment, the time slicing job is causing the PRLOCK table to fill with records.

PRUSERID = 7 (job scheduler internal id)

At first I thought this was happening with just the Time Slicing job but it has been proven to happen with any job. I do not see anything showing on the app or bg logs so I am stumped. I recycled everything and even removed and re-added the BG just to see if that would work with no luck. It is a dual server setup so I even tried to see if it was happening with one server versus another as well. This was also refreshed from a production copy so I thought it may be data related but the same copy was applied to dev with no issue.

I seem to remember seeing this before somewhere either in a post or on the old board and was curious if anyone has seen this before?

While it does not cause immediate harm, when the table fills up to 30k records the system starts to get sluggish so I am looking for any glimmer of hope.

Happy holidays!