Question Re: STMS import problem in Technology Q&A

STMS import problem

Former Member — Sun, 05 Apr 2009 14:49:29 GMT

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

Re: STMS import problem

Former Member — Sun, 05 Apr 2009 17:42:35 GMT

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

Re: STMS import problem

Former Member — Sun, 05 Apr 2009 18:17:10 GMT

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:

----

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

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

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

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

Re: STMS import problem

Former Member — Mon, 06 Apr 2009 02:59:08 GMT

"ERROR: environment variable dbms_type is not set"

Was this parameter set in your environement variable if not set it

dbms_type=ora (If your database is oracle)

Regards

Uday

Re: STMS import problem

Former Member — Mon, 06 Apr 2009 06:21:42 GMT

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

Re: STMS import problem

Former Member — Mon, 06 Apr 2009 18:16:07 GMT

MaxDB Database should be:

C:\usr\sap\NSP\SYS\exe\uc\NTI386>set dbms_type=sdb

So I'm trying...


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: Connect to NSP failed (20090406200822, probably wrong environment).
TRACE-INFO: 1:  [dev trc     ,00000]  Mon Apr 06 20:08:22 2009                  25184  0.025184
TRACE-INFO: 2:  [dev trc     ,00000]  load shared library (dbsdbslib.dll), hdl 0, addr 11530000
TRACE-INFO: 3:                     99  0.025283
TRACE-INFO: 4:  [dev trc     ,00000]      using "C:\usr\sap\NSP\SYS\exe\uc\NTI386\dbsdbslib.dll"
TRACE-INFO: 5:                     62  0.025345
TRACE-INFO: 6:  [dev trc     ,00000]  } DbSlSdbControl(rc=0)                   1352  0.026697
TRACE-INFO: 7:  [dev trc     ,00000]  { DbSlSdbControl(con_hdl=-1,command=39,arg_p=00000000)         61  0.026758
TRACE-INFO: 8:  [dev trc     ,00000]  } DbSlSdbControl(rc=0)                    117  0.026875
TRACE-INFO: 9:  [dev trc     ,00000]  { DbSlSdbControl(con_hdl=-1,command=10,arg_p=018DEEC8)         61  0.026936
TRACE-INFO: 10:  [dev trc     ,00000]  } DbSlSdbControl(rc=0)                      51  0.026987
TRACE-INFO: 11:  [dev trc     ,00000]  { DbSlSdbControl(con_hdl=-1,command=10,arg_p=010666E0)        187  0.027174
TRACE-INFO: 12:  [dev trc     ,00000]  } DbSlSdbControl(rc=0)                      53  0.027227
TRACE-INFO: 13:  [dev trc     ,00000]  { DbSlSdbConnect(con_info_p=00000000)                     165  0.027392
TRACE-INFO: 14:  [dev trc     ,00000]  DBSDBSLIB : version 700.08, patch 0.024 (Make PL 0.29)        172  0.027564
TRACE-INFO: 15:  [dev trc     ,00000]  MAXDB shared library (dbsdbslib) patchlevels (last 10)         58  0.027622
TRACE-INFO: 16:  [dev trc     ,00000]    (0.024) Default value for max. input variables is 2000 (note 655018)
TRACE-INFO: 17:                      79  0.027701
TRACE-INFO: 18:  [dev trc     ,00000]    (0.024) Profile parameter to define max. input variables (note 655018)
TRACE-INFO: 19:                     121  0.027822
TRACE-INFO: 20:  [dev trc     ,00000]    (0.024) Switch SQLMODE after CREATE INDEX SERIAL (note 1267841)
TRACE-INFO: 21:                      75  0.027897
TRACE-INFO: 22:  [dev trc     ,00000]    (0.024) Input parameters for SQL statements increased (note 655018)
TRACE-INFO: 23:                      75  0.027972
TRACE-INFO: 24:  [dev trc     ,00000]    (0.018) Create index serial for MaxDB 7.6 (note 1267841)
TRACE-INFO: 25:                      73  0.028045
TRACE-INFO: 26:  [dev trc     ,00000]    (0.018) More trace in case of packed to string conversion error (note 1262799)
TRACE-INFO: 27:                      79  0.028124
TRACE-INFO: 28:  [dev trc     ,00000]    (0.016) R3trans export aborts with signal 6 (note 1262245)
TRACE-INFO: 29:                      73  0.028197
TRACE-INFO: 30:  [dev trc     ,00000]    (0.009) IA64 alignment errors (note 1245982)                 58  0.028255
TRACE-INFO: 31:  [dev trc     ,00000]    (0.007) Support DB-Type 'SAP DB' by UPDSTAT (note 1225668)
TRACE-INFO: 32:                      99  0.028354
TRACE-INFO: 33:  [dev trc     ,00000]                      43  0.028397
TRACE-INFO: 34:  [dev trc     ,00000]   -> init()                      89  0.028486
TRACE-INFO: 35:  [dev trc     ,00000]    STATEMENT_CACHE_SIZE = 1000                     419  0.028905
TRACE-INFO: 36:  [dev trc     ,00000]   -> sdb_malloc(size=108000) : 0374C5B0 (108008 bytes allocated)
TRACE-INFO: 37:                     226  0.029131
TRACE-INFO: 38:  [dev trc     ,00000]   -> sdb_malloc(size=604000) : 02F40038 (712016 bytes allocated)
TRACE-INFO: 39:                     152  0.029283
TRACE-INFO: 40:  [dev trc     ,00000]   -> sdb_malloc(size=264000) : 03767010 (976024 bytes allocated)

Edited by: Jan Krohn on Apr 6, 2009 8:38 PM

Re: STMS import problem

Former Member — Mon, 06 Apr 2009 18:44:53 GMT

And the second part of the trace file as it's too large for a single posting...


TRACE-INFO: 41:                     159  0.029442
TRACE-INFO: 42:  [dev trc     ,00000]   -> sdb_malloc(size=8072) : 037A79A8 (984104 bytes allocated)
TRACE-INFO: 43:                      97  0.029539
TRACE-INFO: 44:  [dev trc     ,00000]   -> sdb_malloc(size=16024) : 037A9B88 (1000136 bytes allocated)
TRACE-INFO: 45:                     115  0.029654
TRACE-INFO: 46:  [dev trc     ,00000]   -> loadClientRuntime()                    7185  0.036839
TRACE-INFO: 47:  [dev trc     ,00000]  Loading SQLDBC client runtime ...                      98  0.036937
TRACE-INFO: 48:  [dev trc     ,00000]  SQLDBC SDK Version : SQLDBC.H  7.6.0    BUILD 002-121-083-965
TRACE-INFO: 49:                    3991  0.040928
TRACE-INFO: 50:  [dev trc     ,00000]  SQLDBC Library Version : libSQLDBC 7.6.5   BUILD 011-123-196-300
TRACE-INFO: 51:                      73  0.041001
TRACE-INFO: 52:  [dev trc     ,00000]  SQLDBC client runtime is MaxDB 7.6.5.011CL 196300            249  0.041250
TRACE-INFO: 53:  [dev trc     ,00000]  SQLDBC supports new DECIMAL interface : 0                     127  0.041377
TRACE-INFO: 54:  [dev trc     ,00000]  SQLDBC supports VARIABLE INPUT data   : 1                      56  0.041433
TRACE-INFO: 55:  [dev trc     ,00000]  SQLDBC supports keepAlive indicator   : 0                      82  0.041515
TRACE-INFO: 56:  [dev trc     ,00000]   -> getNewConnection()                      73  0.041588
TRACE-INFO: 57:  [dev trc     ,00000]   -> sdb_malloc(size=1640) : 037AF340 (1001784 bytes allocated)
TRACE-INFO: 58:                      99  0.041687
TRACE-INFO: 59:  [dev trc     ,00000]   -> sdb_malloc(size=344) : 037AFC00 (1002136 bytes allocated)
TRACE-INFO: 60:                     250  0.041937
TRACE-INFO: 61:  [dev trc     ,00000]   <- getNewConnection(con_hdl=0)                     372  0.042309
TRACE-INFO: 62:  [dev trc     ,00000]   -> checkEnvironment(con_hdl=0)                     105  0.042414
TRACE-INFO: 63:  [dev trc     ,00000]   -> connect()                     114  0.042528
TRACE-INFO: 64:  [dev trc     ,00000]  INFO : SQLOPT= -I 0 -t 0 -S SAPR3                     183  0.042711
TRACE-INFO: 65:  [dev trc     ,00000]  Try to connect (DEFAULT) on connection 0...                 1220  0.043931
TRACE-INFO: 66:  [dbsdbsql    ,00000]  *** ERROR => Connect to database failed,rc = -10757 (XUSER error (the USERKEY is unknown))
TRACE-INFO: 67:                    1746  0.045677
TRACE-INFO: 68:  [dev trc     ,00000]  Try to connect (SQLOPT) on connection 0 ...                   118  0.045795
TRACE-INFO: 69:  [dbsdbsql    ,00000]  *** ERROR => Connect to database failed,rc = -10709 (Connection failed (RTE:Database name is missing))
TRACE-INFO: 70:                    1885  0.047680
TRACE-INFO: 71:  [dev trc     ,00000]   -> SetSapdbCA(errcode=-10709)                      88  0.047768
TRACE-INFO: 72:  [dev trc     ,00000]   -> freeConnection(con_hdl=0)                     100  0.047868
TRACE-INFO: 73:  [dev trc     ,00000]   -> sdb_free(p=037AFC00, size=344 (1001784 bytes allocated))
TRACE-INFO: 74:                     290  0.048158
TRACE-INFO: 75:  [dev trc     ,00000]   -> sdb_free(p=037AF340, size=1640 (1000136 bytes allocated))
TRACE-INFO: 76:                     182  0.048340
TRACE-INFO: 77:  [dev trc     ,00000]  } DbSlSdbConnect(rc=99)                      65  0.048405
TRACE-INFO: 78:  [dblink      ,00431]  ***LOG BY2=>sql error -10709 performing CON [dblink#2 @ 431]
TRACE-INFO: 79:                     362  0.048767
TRACE-INFO: 80:  [dblink      ,00431]  ***LOG BY0=>Connection failed (RTE:Database name is missing) [dblink#2 @ 431]
TRACE-INFO: 81:                      80  0.048847

tp returncode summary:

TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0232
tp finished with return code: 232
meaning:
  connect failed

Suhash's solution delivers the same trace messages. Any ideas now?

Many thanks in advance!

Jan

Re: STMS import problem

Former Member — Mon, 06 Apr 2009 18:50:31 GMT

Hello Jan,

*** ERROR => Connect to database failed,rc = -10757 (XUSER error (the USERKEY is unknown))
TRACE-INFO: 67:                    1746  0.045677

This is the error, it is not able to connecto to database, but as the database is maxdb, so some maxdb experts can help you further to resolve the problem

Regards,

Subhash

Re: STMS import problem

Former Member — Mon, 06 Apr 2009 19:45:00 GMT

Since generally importing and exporting works, I don't think that this is a MaxDB problem.

I'm coming a bit closer to the solution...

I've clicked the lock/unlock icon in the import queue, and the transport NSPK900001 popped up - probably because I added it to the buffer.

Then I go to import -> synchronous import.

Error message:

System NSP Command TMS_MGR_IMPORT_TR_REQUEST

Client 000 Service Transport Service

User DDIC Start Online

Date 06.04.2009 Function TMS_TP_IMPORT

Time 21:41:09 Message TP_REPORTED_ERROR

Transport control program tp ended with error code 0211

Errors: no info about transport request found

From the log directory:

START imp single NSP 20090406214109 DDIC jan 20090406214109161

START DD IMPORT NSP H 20090406214109 DDIC jan 20090406214109161

HALT 20090406214109

ERROR: tpsettainfo: Cofile
jan\sapmnt\trans\cofiles\K900001.NSP does not exist!

ERROR: EXIT(16) -> process ID is: 824

STOP imp single NSP 0016 20090406214109 DDIC jan 20090406214109161

However!!! Cofile "
JAN\sapmnt\trans\cofiles\K900001.NSP" does exist! This is very strange indeed....

Best wishes,

Jan

Re: STMS import problem

Former Member — Tue, 07 Apr 2009 07:54:57 GMT

Hello John,

Please Check XSEVER service running on this server , Which is service used to connect database for MaxDB.

If it is stopped ,please restart the XSERVER services .

Regrads

Rajasekhar

Re: STMS import problem

Former Member — Tue, 07 Apr 2009 21:29:47 GMT

XServer is running fine:

C:\sapdb\programs\pgm\serv.exe

(I still doubt that this is a database issue since I can import other transports that originate from the very same system.)

Best Regards,

Jan

Re: STMS import problem

Former Member — Wed, 08 Apr 2009 06:22:36 GMT

Hello ,

Please database connectivity using R3trans -d

Regards,

Raja

Re: STMS import problem

Former Member — Wed, 08 Apr 2009 06:25:34 GMT

Hello ,

Check this link :

http://www.ncsu.edu/it/mirror/mysql/doc/maxdb/en/cd/883e4045796913e10000000a1550b0/frameset.htm

Re: STMS import problem

Former Member — Wed, 08 Apr 2009 11:51:18 GMT

Not sure about it, but as nobody else so far asked about it:

It might be a permission problem.

As which user did you do the various steps so far?

What about read and write permission for datafile and cofile?

Re: STMS import problem

Former Member — Wed, 08 Apr 2009 13:51:55 GMT

Jan,

Make sure you have datafile and cofile. Also permission for these files. Then try following commands.

tp addtobuffer NSPK900001 NSP

tp import NSPK900001 NSP Client=XXX pf=C:\usr\sap\trans\bin\TP_DOMAIN_NSP.PFL

Hope this helps.

Manoj

Re: STMS import problem

Former Member — Thu, 09 Apr 2009 14:08:52 GMT

Hi,

Check if you have the cofile and data file at the right place with the right permissions (the owner should be nspadm)

Try to import your transport in command prompt (at os level) with the Windows session opened with user nspadm

Adrian

Re: STMS import problem

Former Member — Thu, 09 Apr 2009 23:12:04 GMT

I've copied the files from the old release.

You cant import the transport with different SAP releases. Suppose if your source OS,DB & your target OS,DB are different then also you can move the transport but your SAP release must be same. If your SAP release is not same then I think you cant import the transport.

Please raise an OSS message to clarify the same.

Hope this helps.

Thanks

Sushil

Re: STMS import problem

Former Member — Mon, 13 Apr 2009 12:08:39 GMT

Adrian,

You've solved it!!! Thanks!

However, for further reference:

Owner must be SAPServiceNSP. Also, SAP_LocalAdmin needs to have full permissions.

Afterwards, the import worked properly.

Best wishes,

Jan

Re: STMS import problem

Former Member — Wed, 05 Jan 2011 17:18:57 GMT

I had this issue also, and here is the solution.

When a transport was moved from Dev to QA, in QA it had no 'CLNT' data (it was blank)

Root Problem, due to system copy I had the wrong domain profile ...

1. Determine which system is your domain Controller.

2. On the Domain Controller, In /usr/sap/trans/bin make sure your TP_DOMAIN_SID file is present and your System is in this file

3.Execute tp addtobuffer (transport) H10 pf=/usr/sap/trans/bin/TP_DOMAIN_D10.PFL client=100

So in this case, D10 is my domain controller, H10 is the system I want the transports to go to. So from H10 I issue this command and H10 gets it Target Client from this string (ie 100) and is populated correctly in STMS.

I hope this helps.

Kelly.

Re: STMS import problem

Former Member — Fri, 21 Jun 2013 00:27:31 GMT

Hi,

Apart from this you can add the parameter CTC=1 and redistrubute the STMS configuration.

STMS -> system overview -> double click on the required SID> goto Transport Tool tab.

Ensure that you are in DC + edit mode to perform this.

Then come back to systems overview and goto Extras -> Distrubute and activate configuration.

This should also fix the issue of client.

Regards

Omkar