Unable to allocate record in VVLOCKS1

[rdeardorff@spi-ind.com]

This morning we had an odd error come up on 6.3.20251117

image.png?

this was locked for about 30 minutes and then recovered itself. There is nothing in the joblog other than what I have in the screen shot.

thoughts?

[robert.swanson]

Hard to say exactly what happened without seeing the full call stack at the time of the lock-wait, and/or knowing which specific job/process was holding the lock in the first place...

Do you see anything in the Errors log for that time period?

My best guess: One of the last steps of the login process involves a housekeeping task executed via VVSECURE where expired sessions are terminated. This process can only be executed by one job at a time, and normally takes under a second to complete. In the event that the process has taken longer than one minute, as indicated by a VVLOCKS record with a minute+ old timestamp, then it will attempt to clear the record on the presumption that the job which created it is no longer active. I suspect (but can't confirm) this is what happened there -- something was causing a session termination to take an abnormally long time, and it wound up propagating up through someone else's login attempt, where it couldn't get a lock on the VVLOCKS record it was trying to clear. Apparently the problem eventually resolved itself, but hard to say what that problem was in the first place.

I would say this is a super rare occurrence. Perhaps there was a program holding a lock on an old VVSESSDATA record for some reason, but I can't fathom what that could be. Possibly a custom program?

[rdeardorff@spi-ind.com]

I will let you know if I can dig up more information on this.