cancel
Showing results for 
Search instead for 
Did you mean: 

tp hangs on start tp_getprots

Former Member
0 Kudos

Hi All

While importing tp import using STMS the transport hangs.

After doing a little research I found that that the tp creates a RDDDISOL

job (function rddgenbb with variant DIST) and it keeps failing and

creating dumps in the system.

The dump is "MESSAGE_TYPE_X" and comes from the function sdb2fmss after

it calls the mss_get_index_storpars function and it raises an "internal

error exception (2)".

The tp log last row is "start tp_getprots..." and it stays there forever.

Any idea what to do?

Accepted Solutions (0)

Answers (3)

Answers (3)

markus_doehr2
Active Contributor
0 Kudos

If you get a dump in ST22 please check that one.

Markus

Former Member
0 Kudos

Hi,

Tp hangs due to the following reasons

1) when RDDIMPDP is not working then you have to login with ddic user and run rddnewpp in se38 select the priority of the job

and say continue this will schedule the rddimpdp.

2)check the background jobs if background work process are not available then also it will be in hang.

3)check the performance of your system

4)check the space in the system

5)check whether any db lock waits are there

6)if every thing is fine still if you face problem run this command

tp getprots <sid> u6 pf=" "

Hope fully this will help you.

Regards

Zia

former_member217765
Active Participant
0 Kudos

Hi Yoav,

Return code 12 always means DB or OS error. As the error occured during calling mss_get_index_storpars function, I supposed that the problem happened on DB level. Please help check whether there is any error on database level.

With Best Regards

Julia

paul_power
Active Contributor
0 Kudos

Hi,

Could you please do the following?

1. Please check in transaction SM37 that RDDIMPDP job exist both in client 000 and in the client you want to import the transport. If it does not exist, running RDDNEWPP report should solve the problem.

Please run it as follows:

Check the authorizations of the DDIC user in client 000

and in the client into which you want to import the transport.

Logon to both clients as a DDIC user and execute the RDDNEWPP report

(with transaction SA38 or SE38). If the report does not end with the

following success message:

"PU006 Background job ... was successfully scheduled... in the

client."

then it means that the authorizations of the DDIC user must then be

enhanced in the respective client.

To do this, logon in the respective client under a user that is authorized for user maintenance. Change the authorizations of the DDIC user in user maintenance (Transaction SU01). Give the DDIC user the authorization for scheduling and for starting the background jobs. We deliver the authorization S_BTCH_ALL and S_BTCH_ADM (depending on the release) for this.

2. Remove tp hanging entries from the Import Monitor

3. Ensure that clogged entries does not exist in TRBAT & TRJOB table

entries

4. Now remove these transport requests from the Import queue.

5. Check that any *.LOC/ *.LOB as well as files related to this request

exists in /usr/sap/trans/tmp directory. If exists, Please rename them

6. Check that tp process is not running at the OS level

7. Once the above steps are carried out, Please re-add these requests with the corresponding target clients and import them. It is SAP's recommendation that imports be done asynchrounously rather than synchronously. By doing this you will be conserving system resources.

8. Please read SAP note 71353 Transports hang during background steps

9. What are the details in the long text of the message type X dump?

Regards,

Paul