cancel
Showing results for 
Search instead for 
Did you mean: 

Deadlock for table APQI

Former Member
0 Kudos

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!

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

This is your note to look at .

1866532 - Batch input: SM35 status change for an already running job

Kind Regards,

Johan

Former Member
0 Kudos

note  32129 - Deadlock analysis for the SQL server should explain you about the deadlock issue.

Former Member
0 Kudos

Hello!

I go through this sap note and this are the questions I still have:

1) How long do the deadlocks stay in SAP system (in deadlock monitor)?

2) What is the procedure to solve these deadlocks (delete these, wait until they are disappear, etc.)?



Former Member
0 Kudos

If you go the DBACOCKPIT --> diagnostics --> deadlock monitor --> clock on Menu GoTo --> information. should provide you the required information.

Former Member
0 Kudos

Hello,

tihs is the same view like DB01 or ST04.

I need answer for the following questions:

1) How long do the deadlocks stay in SAP system (in deadlock monitor)?

2) What is the procedure to solve these deadlocks (delete these, wait until they are disappear, etc.)?

Former Member
0 Kudos

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.

Former Member
0 Kudos

What will happen when I delete these deadlocks?

What is the procedure for that?

Former Member
0 Kudos

Hi,

If no active session, then you can directly delete the dead lock.

Enque/locking mechanism is automatically managed by respective application. But sometimes it happens that system leaves the lock as it is (in situations like abnormal termination etc.).

Regards,

Nick Loy


Former Member
0 Kudos

Hi,

You can check if you find anything in your Batch Input sessions tabs & logs then if applicable further analyze session and decide whether to lock it or delete it.

Regards,

GK