STMS - transport problem

Hi,
We have a DEV and QAS sap systems and the transport system . They have the usr/sap/trans/data and usr/sap/trans/cofiles shared also we have a asolution manager sap system.
We have configured the stms in the solution manager as domain backup and as domain controller is the DEV system. Then if you try to transport a TO from DEV to QAS from the solution manager it seems that is ok , no error appear but the problem is that when you go to QAS although the TO seems to be there the changes are not there so it seems as if the TO is empty.
Could someone help us?
Thnaks a lot
Edited by: sapera sapera on Apr 20, 2010 3:41 PM

Hi,
This is the log:
R3trans version 6.14 (release 701 - 17.11.08 - 18:00:00).
unicode enabled version
===============================================
date&time   : 20.04.2010 - 12:38:10
control file: /usr/sap/trans/QAS/tmp/DEVKK904676.QAS
> #pid 5356 on du2v3sm (somanadm)
> import
> buffersync=yes
> file='/usr/sap/trans/QAS/data/R904676.DEV'
> continuation='/usr/sap/trans/QAS/data/R904676_#.DEV'
> client=200
> csi=yes
> repeatimport=yes
> repeatclimport=yes
>
> createe071sentries='QAS'
> including R3TRFILE
R3trans was called as follows: R3trans -u 26 -w /usr/sap/trans/QAS/tmp/DEVI904676.QAS /usr/sap/trans/QAS/tmp/DEVKK904676.QAS
active unconditional modes: 26
Connected to DBMS = ORACLE     dbs_ora_tnsname = 'SOLMAN'     SYSTEM = 'SOLMAN'.
0 0
trace at level 1 opened for a given file pointer
================== STEP 1 =====================
date&time        : 20.04.2010 - 12:38:11
function         : IMPORT
data file        : /usr/sap/trans/QAS/data/R904676.DEV
Continuation     : /usr/sap/trans/QAS/data/R904676_#.DEV
buffersync       : YES
client           : 200
repeatimport     : YES (corresponds to unconditional mode 1)
repeatclimport   : YES
c.s.i.           : YES
l.s.m.           : VECTOR
charsetadapt     : YES
def. charset     : WEUROPEAN
createe071sentries: QAS
commit           : 100000
table cache      : dynamic
INCLUDING        : 'R3TRFILE'
Data file is compressed with algorithm 'L'.
Export was executed on 20.04.2010 at 12:37:09 by devadm
701
   with R3trans version: 12.06.09 - 15:20:00
Source System = HP (IA-64) with HP-UX on DBMS = ORACLE     dbs_ora_tnsname = 'DEV'     SYSTEM = 'DEV'.
================== STEP 1 =====================
date&time        : 20.04.2010 - 12:38:11
function         : IMPORT
data file        : /usr/sap/trans/QAS/data/R904676.DEV
Continuation     : /usr/sap/trans/QAS/data/R904676_#.DEV
buffersync       : YES
client           : 200
repeatimport     : YES (corresponds to unconditional mode 1)
repeatclimport   : YES
c.s.i.           : YES
l.s.m.           : VECTOR
charsetadapt     : YES
def. charset     : WEUROPEAN
createe071sentries: QAS
commit           : 100000
table cache      : dynamic
INCLUDING        : 'R3TRFILE'
Data file is compressed with algorithm 'L'.
Export was executed on 20.04.2010 at 12:37:09 by devadm
701
   with R3trans version: 12.06.09 - 15:20:00
Source System = HP (IA-64) with HP-UX on DBMS = ORACLE     dbs_ora_tnsname = 'DEV'     SYSTEM = 'DEV'.

Similar Messages

STMS Transport Route Administration - Import Targets not modifiable.

Hello. I'm trying to configure cCTS for use with CHARM. I have created my system clusters and defined a consolidation and delivery route for the clusters. Now when I double click on my clusters in edit mode and navigate to the Import Targets tab, I am not able to modify this tab. I have been following the cCTS for CHARM and QGM Configuration guide.

Thanks Jessica
I'm also working with OSS SAP Support now to try and resolve my issue.
In short I can some up the problem and testing completed so far.
To Start:
The Server group removed old QA server from our SAP Landscape, therefore STMS Transport Route required rebuilding.
Systems:
We have a very complex system setup with SAP R3, CRM and BW systems. Each system has it's own server (Dev = R3D, CRD & BWD, QA Testing is now = R3T, CRT & BWT, Production = R3P, CRP & BWP) The Original QA servers are now being removed (R3Q, CRQ & BWQ)
CRD is the Transport Domain Controller, with transport bins located on CRD for R3D & BWD, CRT for R3T & BWT and CRP for R3P & BWP. (Firewalls and Server locations are the root cause for the different Trans Directories)
Transport route:
Transport route for SAP R3 was: R3D -> R3Q -> R3T & R3P (in a delivery group). The new Transport Route needs to be R3D -> R3T -> R3P.
Main Problem now: With the Transport Route configured like R3D -> R3T -> R3P, any new transport requests created in R3D moves to the R3T Import Queue automatically when the transport is released. Once the transport is successfully imported into R3T, it should automatically be added to the R3P Import Queue, but does not.
Present work around: I've reconfigured the Transport route to R3D -> R3T & R3P. Any tranport request once released, is successfully added to both the R3T & R3P Import Queues.
I have checked all SAPService<sid> OS users and passwords, ensured that the TMSADM user was recreated and working on each of the systems, used telnet to log onto each of the servers from each of the other servers at the OS level (to ensure it's not a landscape firewall security issue), I've also checked all RFC connections in the same manner (to ensure each system can reach the others), recreated the route from R3T to R3P as both a Consolidation and a Delivery type of route,
I will post any resolution found later.
Thanks for the help anyway

Transformation transport problems when containing routine

Hi Gurus,
I'm facing a transport problem.
When i want to transport a transformation that contains routines, the transport says syntax error in routine. The routine in DEV is tested and correct. I realised, that the transport does not bring the routines. After transport, i open the transformation, and the routines contain the default routine: RESULT = .
I found some answers in some posts, but no exact answer how can i get rid of this transport problem. I don't like copy - paste into prod system with manually editing....
If you have any idea, please let me know.
Thanks
Laszlo

Thanks for your help, it worked now, but i think it should work without owerwrite originals. Sometimes it seems that the routines is not included in the transport request, when i modify a routine in a transformation.
But thanks anyway, problem solved now

Open Hub transporting problems

Hi everybody, we have Open Hub transporting problems, it just gives us return code 12 or 8, basically, it doen't want to transport neither Open Hub Destination, nor Transformations, nor DTPs, and bear in mind that we're on the 15th Patch Level. We've looked at all the SAP Notes, but they reffer to the earlier patch levels...
And other problem, is that it's OK in DEV system but in QUALITY system, when you launch a DTP it gives us a dumb with ASSIGN_TYPE_ERROR
Any ideas??

My destination path on the DEV box is simply the following (identified by BID in the following path):
D:\usr\sap\BID\DVEBMGS00\work
And when I locate the un-activated open hub on the QA box, the BID is already changed to BIQ, but the server name box/field is empty....
I am going to try with the object changebility option, btw, is there any documentation on how to change these objects that are marked with object changebility on the QA box (provided that we can not manually change anything on the QA box)...
Anyways, I think my problem is with the server name conversion from "abc-bi-dev" to "abc-bi-qa"....!!!
Also, please note the RSBFILE entry for this object in the QA box has the "btcsrvname" as blank...
Do you think there is any additional setting that needs to be done on the QA box to do this translation (from "abc-bi-dev" to "abc-bi-qa")?
The only two setup we have done as far as the BI is concerned is at the "Tools-> Conversion of logical system name"....where you only put the conversion for client name mapping from dev to qa and local file system mapping from dev to qa.
So, is there anything else to map the host name (from "abc-bi-dev" to "abc-bi-qa") either at BI perspective or Basis/NetWeaver perspective?
Thanks a lot...
~Sabuj.
Edited by: Sabuj Haque on Feb 1, 2009 1:11 PM
Edited by: Sabuj Haque on Feb 1, 2009 5:34 PM

The Object cannot not be processed due to a transport problem

We are trying to delete a standard web template 0ADHOC_TABLE (modified by our coworker before and transported) and reinstall a new one or totally standard one, but when clicking the "X" icon to delete this web template, get the following error:
"The Object cannot not be processed due to a transport problem"
What could be the reason?
Thanks

Hi Kevin,
This message coms up because as you mention, the template has been transported. Since it is in the target system, if you delete form the dev system, the system needs to ensure that it is also removed from the system it has been transported too.
You can check the dev package assigned to the template, assign a new request against this dev class (RSA1 > Transport Connection > Bex Truck icon). Log out and log back into WAD and try to delete it, and then send this transport. Or you can simply reinstall it as Roberto suggests.
Hope this helps...

STMS: Transport control program tp ended with error code 0232

Dear ERP Gurus,
I just encountered problem with STMS in my PRD system. The import is just stuck up on "tp connecting to database". It won't continue unitl the system gives me this error message:
Transport control program tp ended with error code 0232
Errors: connect failed
The tp System log says:
ERROR: Connect to PRD failed (20090227135454, probably wrong environment)
I have verified that the suggestion in SAP Note 165708 has already been implemented in our DEV, QAS, and PRD instances.
Any idea why I am having this problem? Imports were running fine yesterday. Please help.
Your prompt response is highly appreciated.
Thanks a lot.
Best Regards,
Albert

Hi Albert,
First check import monitor and delete all requests from queue, which are still getting imported.
And go to /usr/sap/trans/tmp and mv all those tmp files to other location.
Then kill all OS jobs which are getting execute with tp.
Check all jobs are runnig fine, related to transportation. If not reschedule the same.
Then start importing.
Before doing this just check whether your stms related RFCs are working fine.
I think One of your RFC is getting struck. just try to change ip or hostname accordingly and try.
Regards
Nick Loy

STMS import problem

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

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

STMS - transports get hung on tp import

Hi
There are a number of threads regarding this and I've also looked at OSS note 71353 but so far none have fixed my problem.
When I attempt to import to my new development environment, the transports just hang. There are no entries in TRJOB and TRBAT. I delete the files from stms, kill the tp.exe process from the OS (Windows) but when I add the files back to the import queue and attempt to reimport them, the little truck still appears saying that the import is already running.
I should mention that this new development system was previously the QA system. It is a SAP_ALL client copy of Production. Even when I choose the overwrite originals options for the import of the transport, it still fails.
Any assistance is greatly appreaciated.
Thanks
Conor

hello Connor,
You had delete old tp log files. Further you also need to delete any old entires from import monitor inside stms. Make sure all tp processes are killed as well.
Once this done try importing again. If it works out fine. If not then trying importing the request using TP commands at OS level.
If TP import goes successfully then try importing another request to check if it is fine. Also check if any old import job is running.
There are lots of checks and a number of solutions to this issue.
I have faced this issue a dozen times and solved it in atleast 4 or 5 different ways.
Regards.
Ruchit.

Change STMS transport directory

Hi gurus,
I have a High Availability SAP ERP system (SAP ECC 6.0) as PRD server. We used an old server for DEV system (Host name = sapdev). These two servers belonged to a STMS domain.
Recently we made homogeneous system copy and created a new Development (PRD copy) system to a new server. the new servers host name is AthinaDEV. We created a new STMS domain, joining the new DEV and PRD systems. The problem is that transport directory in PRD seams to be
sapdev\sapmnt\trans\ and in DEV seams to be
athinadev\sapmnt\trans\. In both servers in Transport Tool I have configured TRANSDIR as
athinadev\sapmnt\trans.
How can I change the transport directory to PRD to look
athinadev?
Thanks in advanced

OK,
I added the profile parameter DIR_TRANS with the correct path to both systems and now both systems use
athinadev\sapmnt\trans as transport domain. All seems to be correct now (all checks return success) but I can't transfer any request.
For example: I have created a test ABAP program. I have created a request for that program. I released the request from SE11 transaction succesffully. But when I use STMS transaction I have the following situation: in import overview I can see both systmes and 1 request waiting. When I double click on PRD to enter to import queue the list is empty.
I have cheked the permissions on trans folder and seems to be ok (prdadm has corrrect permissions).
The two systems has connected with transport routes.
Can anyone help me find the solution?

STMS TRANSPORT ROUTES VIEW

Hi,
Can somebody know how we can save transport routes view in stms to file (visio for exemple) ? thanks in advance.
Regards
Sidi

Hi,
I have access to sevral landscapes and same problem and regarding your propositions:
1/ System>List........>local file not available on yhis view
2/custo of local setting no results
3/print screen will not print all the view and even will no allow to modify the out put
For visio was juste example if i can have it on world also will solve the problem.
Regards
Sidi

STMS - transport .SAR file downloaded from SAP notes

Hi,
I have download .SAR files from SAP Support Portal and have used SAPCAR.EXE to unpack it.
As the result, I have 2 files: K123110.L6B and R123110.L6B.
I copied these K123110.L6B to my DEV server \usr\sap\trans\cofiles
and R123110.L6B \usr\sap\trans\data
I would like to transport it from DEV server to QAS server.
So, I logon on to DEV --> STMS, I clicked on the "Transport" logo,
then double click the DEV server.
Then, at the menu bar, I goto Extras --> Other Requests --> Add and
enter Transport Request: L6BK123110
But, there is an error message:
Transport control program tp ended with error code 0247
Errors: addtobuffer has problems with data- and/or cofile
I guess I must miss out some steps, can anybody guide me?
I need to update the SAR file to my QAS server.
thanks in advance.
best regards,
ying ying

Hi,
Please send the files to ur Basis guy. they will upload it to the server.
And also read the documentation of the OSS notes there they mention it.
Thanks
Shiva

STMS: Transport Requests Forever Stuck to Running

Dear SAP Friends,
I am faced right now with a big problem with importing transport requests on our PRD instance.
The TRs are forever stuck on running (truck icon status). I've already edited the tables TRJOB and TRBAT in SM30 but to no avail.
I also checked the tp logs and did some isolation.
Would there be other workarounds? I've already restarted all our instances but I still got the problem.
Hope somebody can help me. Thank you very much in advance!
Best Regards,
Albert

This is happening because import queue is inconsistant
SAP NOTE 12746
check TP SLOG
TP SLOG : TP System logs
STMS > import overview > goto > tp system log (tp slog) : u can find the location of <SID>.LOB file
kill all the Tp process running from the os level and then
delete QE1.LOB
check out for *.LOB file in the DEV system as well
in stms u can see import monitor and keep the cursor on active transport request and delete. This is under import monitor, it does same thing as ps -ef| grep tp and kill pid
Try to do tranport from OS level using TP command
Tp ADDTOBUFFER <TR> <SAPSID>
tp IMPORT <TR>|ALL <SAPSID> http://options ...
check out entries from tables TRBAT, TRJOB & TMSTLOCKR . Use SE16 to delete the entries or use sqlplus (delete * from sapr3.TRBAT and delete * from sapr3.TRBAT)
also checkout if the TMS job is running or not : recreate RDDIMPDP job
Sapnotes concerning this topic or related to this topic:
818065, 302859, 556941, 556946, 71353, 49242, 323726, 56311, 24800, 486991, 506771, 138200

Multiprovider transport problem

Hello Friends ,
While transporting the multiprovider from BW Development to BW Testing system I am getting following error in the Log display of BW Testing System,
R3TRMPRO***(Multiprovider name) was repaired in this system.
The log display for the Delevelopment system shows messages 'Feedback after export or import'--'Successfully Completed'
But the problem occurs in BW Testing system ,
and we are getting the above error message ,
Import--(8) Ended with errors
please suggest solution .
Thanks in advance.

Hello A.H.P ,
Thanks for valuable suggestion.
I think someone has directly repair this multiprovider in Testing system.
I will do the required steps as suggested by you.
Agains thanks very much .
Message was edited by: Amol Kulkarni

Transfer Structure - Transport Problem

Hi Experts,
I am transporting infosource from BW DEV to BW QA ( Datasource is transported and it is replicated) but when the request is imported in QA it gives me error saying " Transfer structure does not exist " . This Infosource is used for Remote Cube .
Could anyone help me in this as in QA I see Infosource in Deactivated state even though remote cube( based on this Infosource) is active .
Regards,
Vijay.

hi Vijay,
seems transfer structure not collected, maybe source system not choose/assigned. try in bw dev, with infosource selected for transport, choose grouping 'in dataflow before' and collection mode 'manual', click 'source system assignment' and make sure your source system is marked. then execute to collect objects. after finished, expand the infosource, and make sure there is transfer structure and marked. then create transport request, stms and transport again. hope this helps.

Source System Does Not Exist - Transport Problem

Hi
We have the next Landscape in BW 7.0 (Netweaver 2004's)
LRDCLNT300     is R3 DEV
LRQCLNT700     is R3 QA
LBDCLNT100     is BW DEV
LBQCLNT700     is BW QA
The connections are
LBDCLNT100 (BW Dev) use as source system        LRDCLNT300 (R3 Dev)
LBQCLNT700 (BW QA) use as source system        LRQCLNT700 (R3 QA)
In RSA1->TOOLS -> Conversion of Logical System Names
In Conversion of source system after the transport we have these entries
Source System                    Target System
LBDCLNT100 (BW Dev)         LBQCLNT700 (BW QA)
LRDCLNT300 (R3   Dev)         LRQCLNT700 (BW QA)
But when we transport an order from BW DEV to BW QA show the error "source system LRDCLNT300 does not exist"
Never made the conversion of source system after the transport.
Can you help us please.

Thanks Edwin
     I create a RFC for LRDCLNT300 (R3 Dev) in my BW QA system (Target System).
I try an order again but it didn't work, also I try to check 7.0 checkbox but I got the message "No entry exists for original source system LBDCLNT100 for 3.x object"
and I have to uncheck again.
I still have the same problem the objects are associated to R3 Dev, never make the conversion to R3 QA.

STMS - transport problem

Similar Messages

Maybe you are looking for