Hi gurus,
after ASE upgrade from 15.7.0.63 to 15.7.0.135, i'm facing lots of deadlocks in ASE file <SID>.log.
Following an example:
0:0003:00000:00257:2016/02/17 15:00:02.69 server Deadlock Id 445 detected
Deadlock Id 445 detected. 1 deadlock chain(s) involved.
Deadlock Id 445: Process (Familyid 0, Spid 166, Suid 3) was executing a SELECT command in the procedure 'sp_writejoboutput' at line 54 at nested level 1.
Deadlock Id 445: Process 166 was involved in application 'JS Agent'.
Deadlock Id 445: Process 166 was involved on host name ''.
Deadlock Id 445: Process 166 was involved in transaction 'sp_writejoboutput'.
SQL Text: sp_writejoboutput '673411', 'Changed database context to ''saptools''.
(return status = 0)
'
Executing procedure: sp_writejoboutput
Subordinate SQL Text:
select @user_name=jsh_user_req, @tot_size=jsh_size from sybmgmtdb..js_history where jsh_exid=@run_id
Deadlock Id 445: Process (Familyid 0, Spid 257, Suid 3) was executing a UPDATE command in the procedure 'sp_js_agent' at line 272 at nested level 1.
Deadlock Id 445: Process 257 was involved in application 'JS Agent'.
Deadlock Id 445: Process 257 was involved on host name ''.
Deadlock Id 445: Process 257 was involved in transaction '$upd'.
SQL Text: sp_js_agent 'setstate=C1,id=673410'
Executing procedure: sp_js_agent
Subordinate SQL Text:
update sybmgmtdb..js_history set jsh_state=@state where jsh_exid = @id
Deadlock Id 445: Process (Familyid 0, Spid 257) was waiting for a 'update row' lock on row 31 page 6551 of the 'js_history' table in database 'sybmgmtdb' but process (Familyid 0, Spid 166) already held a 'exclusive row' lock on it.
Deadlock Id 445: Process (Familyid 0, Spid 166) was waiting for a 'shared row' lock on row 30 page 6551 of the 'js_history' table in database 'sybmgmtdb' but process (Familyid 0, Spid 257) already held a 'exclusive row' lock on it.
Deadlock Id 445: Process (Familyid 0, Spid 166) was chosen as the victim.
Victim process host = `', user = `jstask' program name = `JS Agent' host processes = `77528' .
End of deadlock information.
Following the corresponding log for <SID>_JSAGENT.log:
00:75024:76920:2016/02/17 15:00:02.73 worker Server message: Your server command (family id #0, process id #166) encountered a deadlock situation. Please re-run your command.
00:75024:76920:2016/02/17 15:00:02.73 worker jso_FlushBuffer: jsd_GetResults() failed for xid 673411
There deadlock happens periorically during scheduled internal ASE activities started by JS Agent (find attached image that shows those activities)
I am not able to find any sapnote or sap document which allows me to eliminate these deadlock.
Does anyone help me to find a solution?
Thanks to anyone would contribute!
Massimo Solleretto