Question Re: STMS - transport problem in Technology Q&A

STMS - transport problem

Former Member — Tue, 20 Apr 2010 13:41:12 GMT

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

Re: STMS - transport problem

Former Member — Tue, 20 Apr 2010 16:54:27 GMT

did you mean the transport request doesn't showup in the import oiverview of QAS or the changes from the transport are not imported in QAS?

When you imported from Solman, did it ask you to login to QAS?

Check the transport history in the import overview and logs can be checked to verify the transports are imported.

Re: STMS - transport problem

Former Member — Wed, 21 Apr 2010 08:32:24 GMT

Hi,

The proble is that the changes from the transport are not imported in QAS. And not I don´t need to log in to QAS to do the transport and in the log no error appears .

Also as we have a usr/sap/trans shared for all systems we have all systems in the same transport group.

So any idea why this is happening?

Best regards, Beatriz

Re: STMS - transport problem

michael_mulvey — Wed, 21 Apr 2010 10:38:25 GMT

Hi Sapera,

Your question is a bit vague. Is there any information in the transport logs ?

Michael

Re: STMS - transport problem

Former Member — Wed, 21 Apr 2010 10:51:17 GMT

Hi,

Your question is bit difficult to understand and confuse.

1) whether your transport request has been imported to QA succesfully or not.

2) Transport request has been imported but changes were not impacted the target systems.

for the first question please post the Transport logs here.

for the the second question there might be the chances of synchronization problem run /$sync.

-Srini

Re: STMS - transport problem

Former Member — Wed, 21 Apr 2010 12:36:27 GMT

Hi,

Ok , let me explain the problem:

I´ve 3 sap systems: solution manager, DEV and QAS, with the same /usr/sap/trans for all enviroments.

I create a transport order in DEV , and this TO contains a role. The problem is that when I import the TO from the solution manager it seems that the order is imported successfully because no errors appears (nothing in the log and it appears int the transport history) and it finishes with RC=0 but when I go to check it into QAS system the new role doesn´t appears, but If I import the TO from STMS in QAS system the TO finishes with RC=0 and the role appear.

Any idea why this is happening?

thanks, thanks, thanks, thanks a lot

Re: STMS - transport problem

Former Member — Wed, 21 Apr 2010 13:51:38 GMT

Hi Sapera,

Go to SE01 and have a look at import logs when you transport from solution manager.

Just see whether any thing is getting imported or not.

If possible try to paste the logs here. So that if we can give you some input we will tryu to do the same.

cheers!!!

Re: STMS - transport problem

Former Member — Wed, 21 Apr 2010 15:00:42 GMT

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'.

Re: STMS - transport problem

Former Member — Wed, 21 Apr 2010 15:02:02 GMT

This is the rest of the log:

R3TRACGRTEST_STMS was not imported in this step

R3TRACGTTEST_STMS was not imported in this step

R3TRTABUAGR_TIMEB was not imported in this step

R3TRTABUSPERS_OBJ was not imported in this step

Table UCUW001 is not in nametab

no entries for UCUW001 will be imported in this step.

R3TRTABUUCUW001 was not imported in this step

Table UCUW011 is not in nametab

no entries for UCUW011 will be imported in this step.

R3TRTABUUCUW011 was not imported in this step

DEVK904676 touched.

0 tables in P-buffer synchronized.

0 tables in R-buffer synchronized.

30446 30446

12738 bytes read.

Transport overhead 62.9 %.

Data compressed to 6.8 %.

Duration: 1 sec (12738 bytes/sec).

0 0

Summary:

1 COMML imported.

1 COMMT imported.

Totally 2 Objects imported.

30446 bytes modified in database.

[dev trc ,00000] Tue Apr 20 12:38:12 2010 1083720 1.083720

[dev trc ,00000] Disconnecting from ALL connections: 29 1.083749

[dev trc ,00000] Disconnecting from connection 0 ... 63 1.083812

But is strange because no error appears only warnings

Edited by: sapera sapera on Apr 21, 2010 5:03 PM

Re: STMS - transport problem

Former Member — Fri, 25 Nov 2011 15:02:23 GMT

hi,

sorry for the delay, we opened an oss to SAP and SAP replied that problem was due a performance problem, because if we wait 20 minutes changes appear on the system

Best regards, sapera

Re: STMS - transport problem

Former Member — Mon, 16 Jan 2012 18:03:01 GMT

It´s a performance issue