Finance | Project Operations, Human Resources, ...

Deadlock in SYSLASTVALUE and BATCHGLOBAL table

(0) Share

Report

Posted on by Binita

Hi All,

Some of my client is still using AX 2009(Kernal version - 5.0.1600.3677). The issue is my AX was on hung state for some time and it not allowing to do any operation. When I checked in SQL database I get below two query was creating blocking. Issue was for 30 to 40 min and post that this blocking get cleated automatically.

Do you have any idea what this query mean and how we can prevent it in future.

UPDATE SYSLASTVALUE SET VALUE=@P1,RECVERSION=@P2 WHERE (((((((USERID=@P3) AND (RECORDTYPE=@P4)) AND (ELEMENTNAME=@P5)) AND (DESIGNNAME=@P6)) AND (ISKERNEL=@P7)) AND (COMPANY=@P8)) AND (RECVERSION=@P9))

UPDATE BATCHGLOBAL SET LASTPROCFINISHEDJOBS=@P1,RECVERSION=@P2 WHERE ((NAME=@P3) AND (RECVERSION=@P4))

Thanks in Advance.

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

André Arnaud de Cal... 303,988 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Binita,

Were these two the head blockers? Update SysLastValue means that a user configuration will be saved. This could be a size of a form or e.g. report parameters. This should not cause such a delay. The second is related to the batch framework.

You can check if you have fragmented indexes. If so, reorganize or rebuild the indexes on the SQL database tables.

When you have this issue again, monitor if it is the head blocker or not. You need to find the SQL queries of the head blocker.

Was this reply helpful? Yes No
Binita on at

Like (0)

Report
Copy link

Link copied!

Hi Andre

Yes this was head blocker , and I get some more query from DB team related to above mention query respectively.

EXEC sp_execute 75,0x07FD30F41E0000010006CE0100762E750064006B000000010078080A0301008B0075006E006F000000010078080A0305009402750064006B00000043007805191612007404750064006B000000D0AE7808060312003C0075006E006F000000030078080C0313004F31750064006B000000C08578080A031300010075006E006F00000010B978080B0316000

(@P1 datetime,@P2 int,@P3 nvarchar(31),@P4 int)UPDATE BATCHGLOBAL SET LASTPROCFINISHEDJOBS=@P1,RECVERSION=@P2 WHERE ((NAME=@P3) AND (RECVERSION=@P4))

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 303,988 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Binita,

Can you check if there is an appropriate index on these tables or if there is a missing index? If there is an index, check if these are fragmented. In that case, you can reorganize or rebuild the index.

Was this reply helpful? Yes No