on 01-29-2014 1:27 PM
Hello!
We have 2 entries for a deadlock from the table APQI in our SAP system.
The first entry occured because the job accessing/updating this table was aborted.
The second entry was created during the tcode SM35 and a batch input.
Question:
Are there some actions/investigation requiered? If yes how to proceed?
Thank you!
Hi,
This is your note to look at .
1866532 - Batch input: SM35 status change for an already running job
Kind Regards,
Johan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
note 32129 - Deadlock analysis for the SQL server should explain you about the deadlock issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dont linke copy / paste, anyway See below:
Database Deadlocks
This monitor displays the history of deadlocks. The deadlock history is
recorded in the database for up to 1 month.
For individual deadlocks you can view the abap source code for the
statement which encountered a deadlock error.
Whenever the SAP kernel gets database error 1205 indicating a deadlock a
entry is written to a database table to record the deadlock.
Additionally you may use trace flags 1204 and 3605 to write more
information to the errorlog for later deadlocks. A weekly job deletes
the information which is older than one month.
More information about a single deadlock can be found in the SQL Server
error log, in the short dump written for the deadlock, and in developer
trace file of the work process.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.