cancel
Showing results for 
Search instead for 
Did you mean: 

7.00 Unicode Kernel and TP: Transports hang in MAIN_IMPORT *Bugfix*

Former Member
0 Kudos

Hallo Everybody. A problem has been reported by a number of customers using the 7.00 Unicode kernel with a patch level of 157 or greater and the tp version 372.03.31. Transports and/or Support Packages appear to hang after the MAIN_IMPORT phase and no further processing is done.

The error has now been isolated and has resulted in a patch

to DBSL. The issue is covered in [note 1179020|http://service.sap.com/~IRON/FM/011000358700000431401997E/01179020] which also contains a link to a SAPMats container for the preliminary fix.

All the best,

Sally Power

Development Suppotr for SAP on IBM i

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

We've faced this problem and able to resolve this issue. Please find the reply below from SAP on my massage. I hope this will help others to resolve the same quickly.

-


19.06.2008 - 03:14:05 CET - Reply by SAP

Dear Soumitra,

unfortunately you stepped into a very new problem here. Your transports

fail, because R3TRANS cannot be called. It fails with:

tp CONNECT SND pf=/usr/sap/trans/bin/TP_DOMAIN_SND.PFL

-Dtransdir=/usr/sap/trans

This is tp version 372.04.29 (release 700, unicode enabled)

Connection to Database of SND was successful.

exec(): 0509-036 Cannot load program R3trans because of the following

errors:

rtld: 0712-001 Symbol o4_getpwuid was referenced

from module R3trans(), but a runtime definition

of the symbol was not found.

rtld: 0712-001 Symbol o4_getpwnam was referenced

from module R3trans(), but a runtime definition

of the symbol was not found.

rtld: 0712-002 fatal error: exiting.

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0255

tp finished with return code: 255

meaning:

Could not connect to semaphore server

-


In order to get it working you first need to apply DW patch 164 and

afterwards a lib_dbsl patch larger than 157. The lib_dbsl patch is not

yet officially released on SAP Service Marketplace. But our development

provided a preliminary lib_dbsl patch at SAPMats link:

https://sapmats-de.sap-ag.de/download/download.cgi?id=BSJ7CZDB7G87L5Z7D2ARMSE77EKXU9XR3VBYD9S10Y616B...

After applying DW 164 and the preliminary LIB_DBSL patch we would expectthe transport system to working again.

I am sorry for that. Please let us know your feedback.

Thanks and best regards,

-