STMS import problem

[Former Member]

Dear experts,

I've got a problem importing my packages from Netweaver Trial 7.01 into Netweaver Trial 7.01 SR 1. I've already asked this in the trial forum, but it appears that this issue is too specifically connected to STMS configuration for the trial people to know...

STMS configuration generally seems to be working. I've created a new transport which I was able to export, got the header and data file, which I was able to append to the import queue again.

However, in the same directories with the "new" transport files, I've copied the files from the old release. But the search help, when adding transports to the queue, simply doesn't provide the old transport request... I've manually entered the transport numer, but it claims that the transport doesn't exist.

I've also debugged into the serach help to find out that the transport list comes from an RFC module which doesn't allow remote debugging.

I've also tried calling tp.exe manually (tp IMPORT K900001 NSP), which also gives an error.

Now, I must admit, I've run out of ideas what else I could check. If anyone here has an idea, that'd be just great!

Best wishes,

Jan

[Former Member]

Hi,

I've also tried calling tp.exe manually (tp IMPORT K900001 NSP), which also gives an error.

Please add transport to buffer by following command

tp addtobuffer <transport> <SID> pf=<transport profile>

then use tp import. Please try with NSPK900001in tp command.

Hope this helps.

Manoj

[Former Member]

Thanks for your answer.

I'm getting the following result:

C:\usr\sap\NSP\SYS\exe\uc\NTI386>tp addtobuffer NSPK900001 NSP pf=C:\usr\sap\trans\bin\TP_DOMAIN_NSP.PFL

This is tp version 372.04.40 (release 701, unicode enabled)

Addtobuffer successful for NSPK900001

tp finished with return code: 0

meaning:

Everything OK

C:\usr\sap\NSP\SYS\exe\uc\NTI386>tp import NSPK900001 NSP pf=C:\usr\sap\trans\bin\TP_DOMAIN_NSP.PFL

This is tp version 372.04.40 (release 701, unicode enabled)

ERROR: No connect due to DbSl Load Lib Failure

ERROR: environment variable dbms_type is not set.

ERROR: Connect to NSP failed (20090405201136).

INFO: no trace information stored

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0249

tp finished with return code: 249

meaning:

connect failed due to DbSL load lib failure

In STMS, the import queue is empty...

Best regards,

Jan

P.S.: I also found this:

C:\usr\sap\NSP\SYS\exe\uc\NTI386>tp showbuffer NSP pf=C:\usr\sap\trans\bin\TP_DO

MAIN_NSP.PFL

This is tp version 372.04.40 (release 701, unicode enabled)

NSP buffer:

TASK |PROJECT |P|CMD Im|DD Im |DD Act|MainIm|Enq.Ac|A

DO Im|VersFl|Deploy|XPRA |Gener |UMODE|TAGS

-

---

----

---

-----------+--+--+----+-

-

---

----------+--+--+-+--

NSPK900001 | | |1 |1 |1 |1 | |

6

3

2

that makes 1 transport to be imported.

tp finished with return code: 0

meaning:

Everything OK

Edited by: Jan Krohn on Apr 5, 2009 8:20 PM

[Former Member]

You can also check this

C:\usr\sap\NSP\SYS\exe\uc\NTI386>tp import NSPK900001 NSP Client=XXX pf=C:\usr\sap\trans\bin\TP_DOMAIN_NSP.PFL

Regards,

Subhash