Database tables holding details for a non - released transport request

[former_member270360]

Dear All,

We are implementing SAP ECC 6.0 u2013 ABAP stack, on IBM iSeries / System i, i5/OS V5R4 -

SAP kernel release 7.00, kernel patch number 173

Could someone please guide me to the database tables holding the details for a non u2013 released transport request.

The problem is the following :

We encountered some data corruption in the database of our development system, so we did a restore from the previous day's backup (RSTLIB command) for the database library : R3DEVDATA, without restoring the /usr/sap/trans directory, then we did an APYJRNCHG command for the journal receiver spanning from the previous day's backup until the corruption time (remote journal on a remote system.)

We are now facing the following conflict :

One of our programmers is now un-capable of updating an ABAP program, which he previously added in a transport request, which he did not release.

( This was done during the day of the data corruption)

When the programmer is trying to update the ABAP program through the ABAP workbench, he receives the error :

'Request lock on non u2013 existent task / request DEVK921426'

No details for the transport request DEVK921426 exist in either of the two directories :

/usr/sap/trans/data , /usr/sap/trans/cofiles

The way I see to solve this conflict (eliminate this lock) is to delete the different entries related to the un-released transport request from the database tables.

Any clues would be highly appreciated.

Thank you in advance for your cooperation.

Best regards.

Reda Khalifa

[Former Member · Accepted solution]

Hi Reda,

I would check in SE03 and try to unlock the transport number, it is referring to ... Then you could check on table TLOCK - if this doesn't help, we have to investigate even more ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

[former_member270360]

Dear Volker,

Thank you very much for your interest.

The transport request of interest did not appear in transaction code SE03

Eliminating the record from table TLOCK indeed did solve the problem.

Thank you again.

Best regards.

Reda Khalifa