STMS tp.exe export command problem

[Former Member]

Hi,

I´m applying SP SAPKB70210 (phase MAIN IMPORT) in my system and SPAM is returning error 8:

Object R3TRPROGSDB1FHDB is in repair status. Therefore, it cannot be imported.

Now, because KB70210 is a SAP_BASIS patch and import wasn´t successful, when I try to access transaction SE01,SE09,SE10,SE03 to release the order which is locking the object, I get SYNTAX_ERROR dumps in these transactions. I need to do it manually.

Y check table TLOCK directly in DB and I get program SDB1FHDB is locked in task SIDK900062.

When I execute command:

tp.exe export SIDK900061 pf=G:\usr\sap\trans\bin\TP_DOMAIN_SID.PFL

...in log I see:

2 EPU230XExecution of the export pre-processing methods for request "SIDK900061"

4 EPU111    on the application server: "SERVERNAME"

4 EPU138    in client                            : "000"

2 EPU246XStart: Check for unreleased tasks

2EETR732 Referencing task "QASK900062" not yet released

2 EPU247 End: Check for unreleased tasks

4 EPU239 Database rollback executed

It seems obvious I have to release task SIDK900062 first, but when I execute command:

tp.exe export SIDK900062 pf=G:\usr\sap\trans\bin\TP_DOMAIN_SID.PFL

I get this message in window:

This is tp.exe version 380.03.82 (release 720)

createinfo failed: no info about transport request found

                   or SIDK900062 is not a transport request.

How can I release task SIDK900062? Any idea?

Thanks,

Pablo.

[Former Member]

Hello

I resolved problem by se38 -> the name of the impacted program = SDB1FHDB -> Display -> Goto -> Object directory entry -> Lock overview -> Release transport.

These TCODE are not impacted by dumps.

Good luck

Karel

[former_member610738]

Hi

Kindly recreate the transport with the objects created in first transport.

Now release it from SE01.

If you have xmanager in your system , goto source system first and manually copy and paste the transport req from cofiles and datafile to your local machine.

Then again thru xmanager , copy and transport the request from your local machine to target system.

Before copy and paste procedure , check the permissions for transports or you can change permission by -

Goto the file system where cofile and datafile located in target system and run command

chown sidadm:sapsys <req> (for datafile)

chown sidadm:sapsys <req> ( for cofile)

Now login as sidadm in target system

sidadm> tp addtobuffer <tr no> SID client=555 pf=/usr/sap/trans/bin/TP_DOMAIN_SID.pfl

Now try to import with stms.

If you are not to release the request , check permissions of request in source system at OS level.

Hope this will help you.

WR Swati

[Former Member]

Hi, thanks for response.

Swati, I have no access to transaction SE01, I cannot recreate the transport. I just need a command to release a transport task.

Sunny, could you please explain which command do I have to execute? Do you mean task and transport request in same command?

Regards,

pablo.

[sunny_pahuja2]

Hello,

In same command, give task number first.

Thanks

Sunny

[Former Member]

Hi Sunny,

Excuse me for insist, but what is the command syntax? I´m not an expert in this area.

I´m trying,

tp.exe export SIDK900062 SIDK900061 pf=G:\usr\sap\trans\bin\TP_DOMAIN_SID.PFL

..but it is failing obviously. I´m getting syntax errors.

Thanks.

[sunny_pahuja2]

tp.exe export <task name> pf=G:\usr\sap\trans\bin\TP_DOMAIN_SID.PFL

Thanks

Sunny

[Former Member]

When I execute that command I get message:

This is tp.exe version 380.03.82 (release 720)

createinfo failed: no info about transport request found

                   or SIDK900062 is not a transport request.

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0200

tp finished with return code: 200

meaning:

  ERROR: see tp's stdout (Standard Out may not be available)

That is the reason of this message.

[sunny_pahuja2]

What is SID of your system ? You have to replace SID in transport number with your system SID.

I would recommend you to please ask Basis expert to do this if you are not aware of these functions.

Thanks

Sunny

[former_member610738]

Hi

As you said in above post " returning error 8".

When error code is 8 or 12 then its object related problem attached to that transport.

Please check the objects ,you can sit with your abap team to check which object is causing the error.

If you do transport at OS level, i dont think you need to release it and then transport it.

For os level transport , steps are already mentioned above.

Still if you need guidance in transporting at OS level , please reply.

for me better option wud be to delete the request and regenarate it and then still it shows error, i will try to do it at OS level.

WR

swati

[former_member610738]

Also please check if rddimpdp and rddnewpp jobs are scheduled in the system or not.

Also check if you have latest tp r3trans version in the system.

WR

Swati

[former_member188883]

Hi Pablo,

As suggested by Sunnym you need to first release the task number 61 and then release the main request number 62.

Command to be used is

tp.exe export QASK900061 pf=G:\usr\sap\trans\bin\TP_DOMAIN_QAS.PFL

tp.exe export QASK900062 pf=G:\usr\sap\trans\bin\TP_DOMAIN_QAS.PFL

Above will unlock the object and patching can be continued.

Regards,

Deepak Kori

[Former Member]

Hi,

Finally I couldn´t export task. I changed flag SRCDEP in table TADIR to unmark repair status of the locked object.

Not an elegant method but it allowed me to continue the import.

Thanks,

Pablo.

[sunny_pahuja2]

Hello,

To release/export task then first give the task number and then transport request no in above command.

Thanks

Sunny