STMS stuck at SET VERSION FLAGS state

[Former Member]

Hi Expert,

We are importing TR from Dev to Qty server by stms_import tx.

When we start import one TR... it takes 15 to 20 min to import where as it should take max 1 min. as per program.

I checked import monitor which is showing stuck in phase "start of action SET VERSION FLAGS" since 15 min.

All TR stuck in same phase but after 15-20 min each TR imported fine without error.

We are using ERP 6.0 (no ecc package) on windows with MS SQL db.

I want to know what is this phase called "SET VERSION FLAGS" and why it takes long time to import.

Is I need to change any parameter setting?

How to resolve issue?

Thanks in advance.

regards,

Dev

[Former Member]

Hi Eric,

Find below log

ALOG:

DEVK902005	PRD.ALL L 0000 20150409121631 USERABAP	TMSADM	PRDSAPDB 20150409121631145
DVEK902005	PRD.ALL w 0000 20150409122019 USERABAP	TMSADM	PRDSAPDB 20150409121631145
ALL	PRD.ALL 6 0000 20150409122518	TMSADM	PRDSAPDB 20150409121631145
DEVK902005	PRD:666 I 0000 20150409122523 USERABAP	TMSADM	PRDSAPDB 20150409121631145
DEVK902005	PRD	< 0000 20150409122523 USERABAP	TMSADM	PRDSAPDB 20150409121631145
DEVK902005	PRD.ALL v 0000 20150409123020 USERABAP	TMSADM

SLOG:

START TRANSMIT BUFFER ENTR PRD g	20150409121556	TMSADM	PRDSAPDB
STOP  TRANSMIT BUFFER ENTR PRD g 0000 20150409121556	TMSADM	PRDSAPDB
START imp single	PRD	20150409121631	TMSADM	PRDSAPDB 20150409121631145
START CMDIMPORT	PRD L	20150409121631	TMSADM	PRDSAPDB 20150409121631145
STOP  CMDIMPORT	PRD L	20150409121631	TMSADM	PRDSAPDB 20150409121631145
START CREATE VERSIONS BEFO PRD w	20150409121632	TMSADM	PRDSAPDB 20150409121631145
START tp_getprots	PRD W	20150409121632	TMSADM	PRDSAPDB 20150409121631145
STOP  tp_getprots	PRD W	20150409122027	TMSADM	PRDSAPDB 20150409121631145
STOP  CREATE VERSIONS BEFO PRD w	20150409122027	TMSADM	PRDSAPDB 20150409121631145
INFO  TBATG CONVERSION OF  PRD N	not needed	TMSADM	PRDSAPDB 20150409121631145
START MOVE NAMETABS	PRD 6	20150409122027	TMSADM	PRDSAPDB 20150409121631145
START tp_getprots	PRD P	20150409122027	TMSADM	PRDSAPDB 20150409121631145
STOP  tp_getprots	PRD P	20150409122522	TMSADM	PRDSAPDB 20150409121631145
STOP  MOVE NAMETABS	PRD 6	20150409122522	TMSADM	PRDSAPDB 20150409121631145
START MAIN IMPORT	PRD I	20150409122522	TMSADM	PRDSAPDB 20150409121631145
STOP  MAIN IMPORT	PRD I	20150409122523	TMSADM	PRDSAPDB 20150409121631145
INFO  TBATG CREATION OF EN PRD n	not needed	TMSADM	PRDSAPDB 20150409121631145
START CREATE VERSIONS AFTE PRD v	20150409122524	TMSADM	PRDSAPDB 20150409121631145
START tp_getprots	PRD F	20150409122524	TMSADM	PRDSAPDB 20150409121631145
STOP  tp_getprots	PRD F	20150409123029	TMSADM	PRDSAPDB 20150409121631145
STOP  CREATE VERSIONS AFTE PRD v	20150409123029	TMSADM	PRDSAPDB 20150409121631145
START GENERATION OF REPORT PRD G	20150409123029	TMSADM	PRDSAPDB 20150409121631145
START tp_getprots	PRD G	20150409123029	TMSADM	PRDSAPDB 20150409121631145
STOP  tp_getprots	PRD G	20150409123524	TMSADM	PRDSAPDB 20150409121631145
STOP  GENERATION OF REPORT PRD G	20150409123524	TMSADM	PRDSAPDB 20150409121631145
STOP  imp single	PRD   0000 20150409123524	TMSADM	PRDSAPDB 20150409121631145

Regards,

Dev

[Former Member]

Hi Dev,

Please go through the below sap note

1541076 - Preliminary checks and troubleshooting for transport issues

Also, please add system_pf parameter value either default profile of the server or the transport profile of the domain controller located in /usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL

Regards,

Prithviraj.

[former_member204746]

check in /usr/sap/trans/log

check for most recent files

[Former Member]

HI,

Thanks all of you for reply.

Hi Prithviraj,

As per your provided solution I followed all the step. but issue not resolved.

There is no any previous TR stuck. All TR imported fine.

Hi Eric,

It is found that when I start importing TR.. no temp file generated in tmp folder,

Hi Atul,

I set tp parameter "VERS_AT_IMP" to "NEVER" and also in "ALWAYS". but issue not resolved.

Hi Mahesh,

RSTPTEST takes response time near 2-5 sec which is normal.

One more thing is Production system is in cluster.

There is lot of free space in prd server and log files also cleared from trans directory.

I upgrade Kernel patch to latest one. There is only one TP process shows at OS level during TR import.

What are the other possibilities to resolve issue?

Regards,

Dev

[AtulKumarJain]

Hi Dev,

Please check

Create versions/set version flags


As of Release 4.5A, versions of the objects in the transport requests are created in this step if the transport profile parameter
VERS_AT_IMP is not set to NEVER. Otherwise, version flags are set for all objects in this step.

Please check the paramater in TP profile parameter.

BR

AKJ

[former_member204746]

have you missed this part from my last answer? It may contain the cause of your issue:

while you are importing, please check last few generated files in /usr/sap/trans/tmp . Check the contents

[Former Member]

Hi Dev,

Please check whether we do have objects for other imports steps too.

We might have objects only for Versioning step( will get to know the objects list in Cofile).

Please run report "RSTPTEST" in SE38 and check the response time.

Will get to know if we have network latency with the database.

[former_member204746]

the fact that you are seeing this status means it is the last that worked.

while you are importing, please check last few generated files in /usr/sap/trans/tmp . Check the contents

also, check for any running background jobs starting with RDD* as the job name.

[Former Member]

Thanks Eric for reply.

All TR stuck in same phase "SET VERSION FLAGS".

If I import more than two TR at the same time....it shows above status in import monitor for all TR. this status shows within a few sec and stuck long 15-20 min in same status.

RDD* job shows in sm37 at the time importing TR.

Why TR stuck only one phase "SET VERSION FLAGS" for long time...?

Regards,

Dev

[Former Member]

Please check any hung transport is still lying in the queue. Also check TRBAT table for the entries.

Check for enough background work process.

Check at IOs level for the tp and r3trans processes.

Regards,

Raja. G

[Former Member]

Hi Dev,

Could you follow the below steps and check if that solves the issue?

• Using transaction STMS-> Import overview -> Goto -> Import monitor execute : 'Monitor' -> right click on transport -> delete entry of the transport request that is running
• Kill any TP processes at the OS level, if you do not have an import actively running
• Make sure that the report RDDNEWPP is scheduled through SE38 and is running as a job
• Check the tables TRBAT, TRJOB and TPSTAT
• If there are any entries in TRBAT and TRJOB kindly delete the entries through transaction code SM30->table(TRBAT)->maintain
• If there are any entries in table TPSTAT, delete the entries through transaction se14->give object name->select tables->edit.In the next screen click on delete data and press button activate and adjust database
• Follow the same procedure from se14 for the tables TMSTLOCKR and TMSTLOCKP and delete the entries if any
• Try importing the transport request now

If the bove steps do not solve the issue then please check tp log, slog and alog files for errors and share it here.

Regards,

Prithviraj.