transport giving the "TIME OUT"

[former_member1293411]

Hi,

We are facing the issue with the transport release, we are getting the "time out" while release the releasing the transport. We have tried the in both dialog and background.

regards,

shanti prajapati

[sujeet2918]

Hello Shanti,

You just need to check whether your request number has some locked objects or not?

if locked objects are there then please delete first.and use SE09 to transport.

if still getting problem then send me time out details.

Regards,

Sujeet

[former_member1293411]

thanks Sujit for your quick reply...

i think you are talking about TLOCKP and TLOCKPC tables entries. there are almost 2 lacks entries are there. But one confusion, After deleting the lock entries, Is there any side effect will be there.....?

regards,

shanti prajapati

[sujeet2918]

Hello Shanti,

I am talking about Lock Object in Transport Request.

Please tell me on which SAP Version you are currently working.

If this is ECC, then goto Tcode SE03 -> lock/unlock entries -> put your request number(which you want to transport) and unlock first.

there is no problem in Unlocking any Object before further transportation.

Regards,

Sujeet

[former_member1293411]

hi Sujit,

thanks for your reply.

But actual process is, If we unlock the object related to the transport. than the transport wont contain the unlock object. am i right...?

regards,

shanti prajapati

[sujeet2918]

Hi Shanti,

No you are wrong.

It Just Unlock locked objects of Transport Request. Never lock any objects.

it is for Unlocking.

regards,

Sujeet

[Former Member]

hi,

Note 358688 - Performance for request release: TLOCKPC

Report:SAPLTR_PROJECT_LOCKS

Table: TLOCKPC

thanks

[former_member1293411]

Hi Rimpa,

thanks for your reply.

we already have check the note no 358688, and the secondery index "T02" is already available in the system.

regards,

shanti prajapati

[Former Member]

hi,

Can you import the request? give the SLOG ....

[Private_Member_27907]

Thanks so much for that note.

It solved our problem.

Regards

[Former Member]

After implementing the above note we added additional indexes on HIKEY, LOKEY, and TABNAM. This resolved our issue.

[Former Member]

Even we have same problem when releasing the change Request.

Please increase the parameter rdisp/max_wp_run_time=1000.

It is dynamic parameter hence u able to release the request

Regards,

Rajesh N