BW transport problem - hanging imports from target system

[Former Member]

Hi,

I am working on transports using transaction code STMS. I submitted the imports many hours ago and it seems that they are hanging or stopped. The Trucks are still in the column status. I do see some objects got imported but some did not.

How can I fix this and restart the import because the Trucks are there and I can't restart? Or how do I stop the imports or should I just let it continue? It has been hours now.

I think this is the Basis forum and posting correctly.

Thanks

[Former Member]

Accroding to the log, tp stopped with error code 12, which is a Basis error.

Ask the Basis guys to looks at tp log which gives error code 12.

The problem can be anywhere, inconsistencies in the Transport domain, routes etc. Have them look at it.

Regards

Cyrus

[Former Member]

To check tp log, you need to have authorization for transaction STMS.

Once in STMS, got to the target system and then Go to ->tp system log.

Any error or problem will be shown there.

However, if you are not a Basis guy, then this is not your problem. You cant solve the problem unless you have all the authorizations. So, you should immediately ask your Basis colleagues to look into it.

Regards

Cyrus

[Former Member]

Hi Cyrus,

Here is the error form the tp log. I kinda posted this on another thread.

START tp_getprots BWQ R 20061213220218 saptestbw 20061213215934

ERROR BWDK900124 BWQ R 0012 20061213223718 saptestbw 20061213215934

STOP tp_getprots BWQ R 20061213223721 saptestbw 20061213215934

STOP EXECUTION OF REPORTS BWQ R 20061213223721 saptestbw 20061213215934

ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT

STOP imp single BWQ 0012 20061213223721 saptestbw 20061213215934

START imp single BWQ 20061213223813 saptestbw 20061213223811

INFO TBATG CONVERSION OF BWQ N not needed saptestbw 20061213223811

START MOVE NAMETABS BWQ 6 20061213223813 saptestbw 20061213223811

START tp_getprots BWQ P 20061213223813 saptestbw 20061213223811

STOP tp_getprots BWQ P 20061213223823 saptestbw 20061213223811

STOP MOVE NAMETABS BWQ 6 20061213223823 saptestbw 20061213223811

START MAIN IMPORT BWQ I 20061213223823 saptestbw 20061213223811

STOP MAIN IMPORT BWQ I 20061213223833 saptestbw 20061213223811

INFO TBATG CONVERSION OF BWQ n not needed saptestbw 20061213223811

START SET VERSION FLAGS BWQ V 20061213223833 saptestbw 20061213223811

START tp_getprots BWQ V 20061213223833 saptestbw 20061213223811

STOP tp_getprots BWQ V 20061213223843 saptestbw 20061213223811

STOP SET VERSION FLAGS BWQ V 20061213223843 saptestbw 20061213223811

START EXECUTION OF REPORTS BWQ R 20061213223843 saptestbw 20061213223811

START tp_getprots BWQ R 20061213223843 saptestbw 20061213223811

ERROR BWDK900127 BWQ R 0012 20061213224018 saptestbw 20061213223811

STOP tp_getprots BWQ R 20061213224025 saptestbw 20061213223811

STOP EXECUTION OF REPORTS BWQ R 20061213224025 saptestbw 20061213223811

ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT

STOP imp single BWQ 0012 20061213224025 saptestbw 20061213223811

START imp single BWQ 20061214023034 saptestbw 20061214023032

INFO TBATG CONVERSION OF BWQ N not needed saptestbw 20061214023032

START MOVE NAMETABS BWQ 6 20061214023035 saptestbw 20061214023032

START tp_getprots BWQ P 20061214023035 saptestbw 20061214023032

STOP tp_getprots BWQ P 20061214023045 saptestbw 20061214023032

STOP MOVE NAMETABS BWQ 6 20061214023045 saptestbw 20061214023032

START MAIN IMPORT BWQ I 20061214023045 saptestbw 20061214023032

STOP MAIN IMPORT BWQ I 20061214024003 saptestbw 20061214023032

INFO TBATG CONVERSION OF BWQ n not needed saptestbw 20061214023032

START SET VERSION FLAGS BWQ V 20061214024003 saptestbw 20061214023032

START tp_getprots BWQ V 20061214024003 saptestbw 20061214023032

STOP tp_getprots BWQ V 20061214024014 saptestbw 20061214023032

STOP SET VERSION FLAGS BWQ V 20061214024015 saptestbw 20061214023032

START EXECUTION OF REPORTS BWQ R 20061214024015 saptestbw 20061214023032

START tp_getprots BWQ R 20061214024015 saptestbw 20061214023032

ERROR BWDK900108 BWQ R 0012 20061214032314 saptestbw 20061214023032

ERROR BWDK900111 BWQ R 0012 20061214035901 saptestbw 20061214023032

ERROR BWDK900124 BWQ R 0012 20061214043116 saptestbw 20061214023032

ERROR BWDK900129 BWQ R 0012 20061214045324 saptestbw 20061214023032

STOP tp_getprots BWQ R 20061214045330 saptestbw 20061214023032

STOP EXECUTION OF REPORTS BWQ R 20061214045330 saptestbw 20061214023032

ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT

STOP imp single BWQ 0012 20061214045330 saptestbw 20061214023032

Is there anything I can do without requiring other authorizations? I actually have STMS access because I am doing the import.

Thanks

Will

[Former Member]

Hi,

I just went ahead and created another tranport and just imported again. Here is the message from the tp log.

START imp single BWQ 20061214144832 saptestbw 20061214144829

INFO TBATG CONVERSION OF BWQ N not needed saptestbw 20061214144829

START MOVE NAMETABS BWQ 6 20061214144832 saptestbw 20061214144829

START tp_getprots BWQ P 20061214144832 saptestbw 20061214144829

STOP tp_getprots BWQ P 20061214144843 saptestbw 20061214144829

STOP MOVE NAMETABS BWQ 6 20061214144843 saptestbw 20061214144829

START MAIN IMPORT BWQ I 20061214144843 saptestbw 20061214144829

I refreshing the Import Queue and ithe Truck is still there. What should I tell the Basis group about this problem?

Thanks

Will

[Former Member]

Will,

check OS level to see more than one tp is running.if it is , you can kill the old tps ( not a good idea ) . You can also update the tp with latest patch level. Just curious , is the changes getting reflected in BWQ ?

Thanks

Prince Jose

[Former Member]

Hi,

Have you find out the solution?

We are facing same problem.

Appreciating helpful answer.

Thanks,

Regards,

Ganesh

[Former Member]

Sometime BW transport take long, long time to end! this is because really often BW objects have to be activated.

If this is your situation... it's quite simple to check: all the imports related jobs are named RDD....:

RDDEXECL

RDDMASGL

RDDMNTAB

RDDVERSL

the first one usually takes long time (it's related to the activation procedures, method executions).

Anyway you can also check the tp system log: it often indicates the error.

ciao

[Former Member]

Hi

Thanks so much. I checked these jobs from SM37 and they are all finished. I didn't see job RDDMNTAB but the others have finished. I am a BW developer and I have no other authorizations similar to a Basis person to check things. How would I check the tp log. Would I have to go to the OS level to do this?

Thanks

Will

[Former Member]

Which OS do you have?

If unix, ps -ef | grep tp will show the tp processes.

If windows, see task manager-> processes.

In sm37 looks like the transport job is not active...check if there are jobs that are in released state, but if you go in and check their start time, it is in the past...in thsi case yo have tochange the start time so that it starts.

[Former Member]

Hi Cyrus,

What job name should I check or which program? Would it be RDDIMPDP and RDDPNEWPP? I don't have an account on Unix so I will have to ask the basis group to help me.

Thanks,

Will

[Former Member]

There are a few things you can do to diagnose:

1)check if there are atleast 2 background processes free. Maybe thats the problem

2)go to sm37 and check active jobs, there would be one for the transport...try to chane it to class A.

3)check at OS level if there are more than 1 tp process active. Maybe some other process is blocking thsi one.

Killing the tp process would stop this, but its not a good thing. First, check the points I gave you and we will go from there.

Regards

Cyrus

[Former Member]

Hi Cyrus

Item 2. I listed the jobs from SM37 and only BI_WRITE_PROT_TO_APPLLOG is released. There are no other jobs active. What are the programs that should be running in the active state.

Item 3. How would I check the OS level. I am not sure if I have the authorizations to check the OS level. How would I check the tp process active.

I checked these on BWQ.

Thanks and regards

Will

Message was edited by:

Will Ferrell

Message was edited by:

Will Ferrell