EHPI installer: Error while reading a dynpro. Stuck at Start Shadow First.

[Former Member]

Hi Everyone,

I am dead in the water with my test install of EhP5 using the most current installer. This small test is on an older iseries, V5R4 with 8G memory. The SAP version is ECC 6.0 at sp Basis 23 and Applications at 19.

The install stops at Start Shadow First, but the instance and work processes are up on the server. The log- SAPehpiConsole reads:

Severe error(s) occured in phase MAIN_SHADOW/START_SHDI_FIRST!

Last error code set: RFC call to upg_is_shadow_system failed with key

RFC_ERROR_SYSTEM_FAILURE (open): Error while reading a dynpro

Please refer to these logs in the posted replys following this post for readability.

The shadow system work process wp01 log showsan RFC error as follows:

Wed Sep 14 11:29:58 2011

ABAP Program SAPMSSY2 .

Source Line 0.

Error Code DYNPRO_READ_FAILED.

Module $Id: //bas/720_REL/src/krn/dynp/dyrdypdb.c#3 $ SAP.

Function dy_dbread Line 100.

• RABAX: level LEV_RX_STDERR completed.

• RABAX: level LEV_RX_RFC_ERROR entered.

• RABAX: level LEV_RX_RFC_ERROR completed.

• RABAX: level LEV_RX_RFC_CLOSE entered.

• RABAX: level LEV_RX_RFC_CLOSE completed.

• RABAX: level LEV_RX_ERROR_SAVE entered.

• RABAX: level LEV_RX_ERROR_SAVE completed.

• RABAX: level LEV_RX_ERROR_TPDA entered.

• RABAX: level LEV_RX_ERROR_TPDA completed.

• RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

• RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

• RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

• RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

• RABAX: level LEV_RX_END entered.

• RABAX: level LEV_RX_END completed.

• RABAX: end no http/smtp

• RABAX: end RX_BTCHLOG RX_VBLOG

Error while reading a dynpro.

C Wed Sep 14 11:33:59 2011

C *** ERROR => SQL-Error -204 in function db_open (dbsldb4.cpp 10630)

C {root-id=4E6F19A9A5F02851E10080020A7F0064}_{conn-id=}_0

• RABAX: level LEV_RX_IMC_ERROR entered.

• RABAX: level LEV_RX_IMC_ERROR completed.

• RABAX: level LEV_RX_DATASET_CLOSE entered.

• RABAX: level LEV_RX_DATASET_CLOSE completed.

C Reopen: FALSE

B *** ERROR => dbdynpdb2: dbdd_dbtab_columns (DYNPSOURCE) failed with rc = 4

dbdynpdb2.c 2506]

B {root-id=4E6F19A9A5F02851E10080020A7F0064}_{conn-id=00000000000000000000000000000000}_0

B ***LOG BZY=> unexpected return code 4 calling dbdd_dbtab [dbdynpdb 2508]

---

So I have a problem communicating with the shadow. Or is it a problem with the db_open?

From the test system I have an entry in SM59 to the shadow and I get this error when trying a connection test.

Error Details Error while reading a dynpro.

And trying to logon to the client sends the same message, it does not bring up the login screen.

OK. So in the 3 weeks that I have restarted, re-set and completely restored and restarted the install, I have always come to this point. I have search for similar issues and have done a review of pertinent notes etcu2026 Just as a comment, last year I successfully did the Ehp 4 upgrade without many problems on this same system using last years SAP system. In the month that I have been trying to do this, SAP has replaced the EHPI installer 3 times which indicates some problems on their part.

Any comments or suggestions would be greatly appreciated.

Pat

[Former Member]

I get this Error while i am upgrading to ERP 6 EHP 7 ON iSeries

Could not create SQL Collection R3<SID>SHD on DB host

and the solution is :

STRSQL

Create collection F4 R3<SID>SHD AND THE ASP NO. then continue SUM process.

Shehab Ahmed

SAP Basis Admin

[volker_gldenpfennig]

Hi,

ok, now, your problem got solved by this ...

good news,

Regards,

Volker Gueldenpfennig, consolut international ag

[Former Member]

Yes the issue is solved by this

[Former Member]

Hi All,

My response from support seems unlikely to work.

The usual command on the iseries comes back with this message.

call qsys2/qsqxrlf parm(DLT R3TEHSHD)

Object QSQJRN in library R3TEHSHD not found.

It is suggested that I delete the test and retry. (I have done that 3 times already before contacting them).

Also it is suggested to recreate the catalogs in the shadow. Here is the full response. Can anyone offer comments on the catalog?

***************************

Here is the full response from support:

*****

the problem is that your shadow library R3TEHSHD is missing the

system catalog files.

Joblog is full with: SYSCOLUMNS in R3TEHSHD type *FILE not found.

>> this explains the SQL -204 error messages.

In the older logs I found:

>> 2011/09/23 13:19:20 START OF PHASE PREP_INSTALL/SHDINST_DB_PREP

>> 2011/09/23 13:19:21 END OF PHASE PREP_INSTALL/SHDINST_DB_PREP

>>>> Repeat Phase <(><<)><(><<)><(><<)><(><<)>

Checks after phase PREP_INSTALL/SHDINST_DB_PREP were negative|

Last error code set: Could not create SQL Collection R3TEHSHD on DB host

omni.

: Error 0

03) - Exit this program

Choose action: Repeat phase PREP_INSTALL/SHDINST_DB_PREP to continue at

the point it stopped

>> 2011/09/23 13:29:57 START OF PHASE PREP_INSTALL/SHDINST_DB_PREP

>> 2011/09/23 13:29:57 END OF PHASE PREP_INSTALL/SHDINST_DB_PREP

>> 2011/09/23 13:29:57 START OF PHASE PREP_INSTALL/SHDINST_SWT_HOST

For any reason the SQL Collection was not created in that step. I only

could imagine that library R3TEHSHD already existed at this upgrade step

(maybe from a former upgrade try...).

So either you start again from scratch by considering to delete

R3TEHSHD first or you try to manually repair the situation. If you

prefer to repiar it, you will need to rename R3TEHSHD first, and then

start SQL and run the CREATE COLLECTION R3TEHSHD. Afterwards you need

copy all objects from the renamed R3TEHSHD into R3TEHSHD.

[dorothea_stein]

Hi Patricia,

from what I read, I think support's suspicion is correct: It sounds like CREATE COLLECTION failed during the very first installation, and artefacts got never cleaned up properly such that any attempts to retry the installation would fail as well.

From the CSN ticket I see that the schema seems to be completely empty (no journal, no system catalogs), explaining all the errors you've seen so far. (SQL0204: no table SYSTABLES. Without journal you can't create the system catalogs, and so on.)

I suggest you delete the schema and start over one more time. If that doesn't help, something fundamental is wrong either with the SAP logic to create the shadow schema, or with the IBM command utilized. But with fresh trace data we have a chance to find the root cause. I will watch the ticket.

Best regards,

Dorothea Stein

[Former Member]

Hi All,

I followed the suggestion to rename my library so that I could run the create collection statement. I wrote a cl to move all of the objects back into the new library.

My update did progress beyond the point of failure so I want to acknowledge the correct advice from SAP support as well as Dortheas' comments.

I was surprised at the strange problem because I have not had experience with sql on the iseries very much and didn't recognize that the familiar command "call qsys2/qsqxrlf" would not work in this case.

Pat

[dorothea_stein]

Hi Patricia,

glad to hear that it works.

Since you followed the path to repair the schema and to continue, I recommend you to check two more things, because the installer might not have been able to do this for you:

1) Check your current journal settings according to SAP Note [1449715|https://css.wdf.sap.corp/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=0001449715]. Unless you have specific requirements from old OS versions or high availability solutions, you can blindly apply all settings suggested there using the following command:

CHGJRN JRN(R3<sid>DATA/QSQJRN)
       JRNRCV(*GEN)
       <your_options>

2) Run the following command to fix table attributes:

AS4FIXFILE DBLIB(R3<sid>DATA) 
           CHGOWN(*YES)
           ENDJRN(*YES)
           CHGFILE(*YES)
           NEWOWN(*SIDOWNER)
           FILES(*ALL)

Best regards,

Dorothea

[Former Member]

Hi All,

I increased buffer sizes as suggested, and continue to read any logs I can find. Below is another that troubles me, that somehow I have a Unicode setting somewhere.

This iseries has the 2 system values set just as the iseries with 3 SAP partitions:

QCCSID = 65535

QCHRID = 697

These are old default settings. When I did the codepage I may have had them set differently but we change servers every few years and it reverted back.

-

---

LOG

CLIENT=000 USER=DDIC PASSWD=******* LANG=E ASHOST=omni SYSNR=15 GWHOST=omni GWSERV=sapgw15 TRACE

Send RFCHEADER: 01/BIG/IEEE/SPACE/1100

Send UNICODE-RFCHEADER: cp:4102/ce:IGNORE/et:5/cs:2/rc:0x00000023

L-CodePages: default=4102, logon_lang=4102, curr_locale=4102, front_locale=4102, default_pcs=1100

DT ERROR> ab_dtrfcSendInfo (rc: 1 {root-id= }_{conn-id= }_0-

{root-id=00000000000000000000000000000000}_{conn-id=4E7B00269F4C4E71E10080030A7F0064}_1

-

---

My customer trouble ticket number is 9000152955, and I have requested that they change the component and send it to SAP, which they did.

Thanks for the comments, I will update this posting if anything changes.

Pat

[Former Member]

Hello All,

As my bad luck continues, I am still searching for the answer. I have cleared everything and downloaded all of it again. I entered a message to our support, but that usually leads to weeks of reading notes, they have no experience on OS400.

In my reading of notes and forums, I closely look at the profile parameters that were built by SAPehpi.

This system is an older OS V5.4 because of a legacy program, and the shadow is not using XDN even though the principal system is. The profile parameters were not there. And limited main memory of 7G may be a problem but the principal system runs fine.

Another question is about some new profile parameters.

This one is new to me:

DIR_CT_RUN = /usr/sap/TEH/EHPI/abap/exe which I can accept without knowing what it is.

This one:

ES/TABLE = UNIX_STD confuses me. I have 30 years experience on OS400 and never received notice that this was now a UNIX system. Any comments? The alternative

(in note 923610) is For AIX: SHM_SEGS which is mentioned in an iseries note 1605920. But note 1505378 about SAPehpi says they inserted it for the shadow.

Again, the shadow starts and from the server looks good. But even the QP2TERM SAPehpi startshd eventually shows this error:

FATAL ERROR: RFC call to upg_is_shadow_system failed with key RFC_ERROR_SYSTEM_FAILURE (open): Error while reading a dynpro $

Any comments are appreciated.

[Former Member]

Hi Pat,

tja ... at least, SAP is making use of the AIX environment (calles PASE - so, that you not directly feel AIX) since 6.40 kernel ...

I do not think, that your issue will be solved by the mentiones profile parameters ... I would logon and check ST02 for EM & Heap and perhaps increase that ... as you are in the shadow, you might not know, that you typically need at least 5 GB (better 10GB) heap during ACT_UPG is needed, but only 800MB is configured ...

ABAP-Buffer needs to be at 800-1000MB as well and there was an error that it had 80MB only ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

[Former Member]

Hi Pat,

I've been reading through this thread and I think that the best advice I can give you is to open an SAP customer message for your problems and to direct it straight to IBM i support. The correct component in this case is BC-INS-AS4. My colleagues and myself will be more than happy to logon and take a look at the system and the logs and we have plenty of "OS400 experience" to fall back on. If you already have a message open, then please ask for it to be redirected to the component given above.

Kind regards,

Sally Power

For SAP on IBM i Development Support

[Former Member]

Hi Pat,

sounds like bad luck here ...

Did you investigate the SQL0204 ? There is a field missing ... Either you current DB is corupt or you are using a "bad kernel" ... are you sure, that you are using a 7.20 kernel of ascii or unicode (the right one, that you typically use) ?

Because, this sounds to me, that the kernel doesn't understand the 7.02 DB ...

Either wrong kernel release, wrong codepage or bad luck with a bad patch ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

[Former Member]

Hi Volker,

Funny that you mention that. On my first try, back in August, I allowed solution manager to pick all of the kernels because I wasn't understanding that I had to select the correct one.

That test actually went beyond where I am today. But I cleared all that I know to clear before starting from the solution manager selection to this point. I was very careful to select the correct kernel.

I do notice that the shadow does not use XDN but I was not concerned about that.

I am ready to start deleting it all again. I wish I had room on my newer system, I think I would have better luck.

Thanks for the very quick response, I will continue to look for clues.

Pat

[Former Member]

The 2 logs from the installer are here.

The STARTSFI is as follows:

1 ETQ201 Entering upgrade-phase "START_SHDI_FIRST" ("20110913144811")

4 ETQ399 Set environment for standard connect:

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '14', GwService = 'sapgw14'

4 ETQ399 Environment variables:

4 ETQ399 dbs_db4_schema=SAPR3

4 ETQ399 auth_shadow_upgrade=0

1 ETQ206 Executing pre-phase DB specific actions.

3 ETQ399 Fixing IFS authorities for '/usr/sap/TEH/EHPI/abap/exe'

1 ETQ206 Executing pre-phase DB specific actions.

1 ETQ200 Executing actual phase 'MAIN_SHADOW/START_SHDI_FIRST'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'DEVTRACE.LOG'

4 ETQ399 Set environment for shadow connect:

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '15', GwService = 'sapgw15'

4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"

4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"

4 ETQ383 translates to path "exe"

4 ETQ383 translates to path "exe"

4 ETQ399 Set tool parameters for shadow connect:

4 ETQ399 default TPPARAM: SHADOW.TPP

4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"

4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWI

4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"

4 ETQ383 translates to path "exe"

4 ETQ383 translates to path "exe"

2 ETQ399 Starting shadow instance

4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"

2 ETQ231 RFC Login failed

repeats the rfc call with a fail until this final entry.

2EETQ399 Starting shadow instance failed

2EETQ399 Test RFC failed finally

-

---

The DEVTRACE.LOG is here:

$ Directory: /usr/sap/TEH/EHPI/abap/log

Name: DEVTRACE.LOG

trc file: "dev_disp.new", trc level: 1, release: "720"

sysno 15

sid TEH

systemid 327 (IBM i with OS400)

relno 7200

patchlevel 0

patchno 100

intno 20020600

make single threaded, ASCII, 64 bit, optimized

profile /usr/sap/TEH/EHPI/abap/TEH/SYS/profile/TEH_DVEBMGS15_omni

pid 75851

kernel runs with dp version 131(ext=118) (@(#) DPLIB-INT-VERSION-131)

length of sys_adm_ext is 376 bytes

• SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (15 75851) [dpxxdisp.c 1287]

#shared lib "dw_xml.so" version 100 successfully loaded

#shared lib "dw_xtc.so" version 100 successfully loaded

#shared lib "dw_stl.so" version 100 successfully loaded

#shared lib "dw_gui.so" version 100 successfully loaded

#shared lib "dw_mdm.so" version 100 successfully loaded

#shared lib "dw_rndrt.so" version 100 successfully loaded

#shared lib "dw_abp.so" version 100 successfully loaded

#shared lib "dw_sym.so" version 100 successfully loaded

#shared lib "dw_aci.so" version 100 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

rdisp/dynamic_wp_check : 0

rdisp/calculateLoadAverage : 1

Tue Sep 13 14:48:58 2011

• WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 6404]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: write dp-profile-values into sys_adm_ext

DpIPCInit2: start server >omni_TEH_15 <

DpShMCreate: sizeof(wp_adm)##17440#(1744)

DpShMCreate: sizeof(tm_adm)##4976768#(24760)

DpShMCreate: sizeof(wp_ca_adm)##56000#(56)

DpShMCreate: sizeof(appc_ca_adm)#56000#(56)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/576048/576064

DpShMCreate: sizeof(comm_adm)##576064#(1136)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm)##0#(104)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm)##0#(80)

DpShMCreate: sizeof(vmc_adm)##0#(1856)

DpShMCreate: sizeof(wall_adm)##(25648/36736/64/104)

DpShMCreate: sizeof(gw_adm)#48

DpShMCreate: sizeof(j2ee_adm)#2032

DpShMCreate: SHM_DP_ADM_KEY##(addr: 700000050000000, size: 5759216)

DpShMCreate: allocated sys_adm at 700000050000010

DpShMCreate: allocated wp_adm_list at 700000050002970

DpShMCreate: allocated wp_adm at 700000050002b60

DpShMCreate: allocated tm_adm_list at 700000050006f90

DpShMCreate: allocated tm_adm at 700000050006fe0

DpShMCreate: allocated wp_ca_adm at 7000000504c6070

DpShMCreate: allocated appc_ca_adm at 7000000504d3b40

Directory: /usr/sap/TEH/EHPI/abap/log

Name: DEVTRACE.LOG

DpShMCreate: allocated comm_adm at 7000000504e1610

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 70000005056e060

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated gw_adm at 70000005056e110

DpShMCreate: allocated j2ee_adm at 70000005056e150

DpShMCreate: allocated ca_info at 70000005056e950

DpShMCreate: allocated wall_adm at 70000005056e9d0

DpCommAttachTable: attached comm table (header=7000000504e1610/ft=7000000504e1620)

DpSysAdmIntInit: initialize sys_adm

rdisp/test_roll : roll strategy is DP_NORMAL_ROLL

dia token check not active (3 token)

MBUF state OFF

DpCommInitTable: init table for 500 entries

DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm

rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 4096 kByte.

Using implementation std

EsStdUnamFileMapInit: ES base = 0x7000000a0000000

EsStdInit: Extended Memory 4096 MB allocated

<ES> 1023 blocks reserved for free list.

ES initialized.

mm.dump: set maximum dump mem to 96 MB

DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE

MPI: dynamic quotas disabled.

MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

Tue Sep 13 14:48:59 2011

• WARNING => System running without ICM - check rdisp/start_icman [dpxxdisp.c 13097]

Tue Sep 13 14:49:02 2011

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG Q0K=> DpMsAttach, mscon ( omni) [dpxxdisp.c 12339]

MBUF state LOADING

DpStartStopMsg: send start message (myname is >omni_TEH_15 <)

DpStartStopMsg: start msg sent

Tue Sep 13 14:49:11 2011

CCMS uses Shared Memory Key 73 for monitoring.

CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.

CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

Tue Sep 13 14:49:13 2011

CCMS: start to initalize 3.X shared alert area (first segment).

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296]

MBUF state ACTIVE

DpWpBlksLow: max wp blocks in queue is 800 (80 %)

MBUF component UP

DpMsgProcess: 1 server in MBUF

DpAppcBlksLow: max appc blocks in queue is 500 (50 %)

Tue Sep 13 14:50:24 2011

DpModState: change server state from STARTING to ACTIVE

trc file: "dev_ms.new", trc level: 1, release: "720"

[Thr 01] Tue Sep 13 14:48:39 2011

[Thr 01] MsSOsPrivInit: Run priority adjusted to 12

[Thr 01] ms/http_max_clients = 500 -> 500

[Thr 01] MsSSetTrcLog: trc logging active, max size = 52428800 bytes

systemid 327 (IBM i with OS400)

relno 7200

patchlevel 0

patchno 92

intno 20020600

make multithreaded, ASCII, 64 bit, optimized

pid 75850

[Thr 01] Tue Sep 13 14:48:40 2011

[Thr 01] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 75850) [msxxserv_mt. 2274]

[Thr 01] SigISetDefaultAction : default handling for signal SIGCHLD

[Thr 01] load acl file = /usr/sap/TEH/EHPI/abap/TEH/SYS/global/ms_acl_info

[Thr 01] MsGetOwnIpAddr: my host addresses are :

[Thr 01] 1 : [10.127.0.100] omni.plastekgroup.com (HOSTNAME)

[Thr 01] 2 : [127.0.0.1] LOOPBACK (LOCALHOST)

[Thr 01] MsHttpInit: full qualified hostname = omni.plastekgroup.com

[Thr 01] HTTP logging is switch off

[Thr 01] MsHttpOwnDomain: own domain[1] = plastekgroup.com

[Thr 01] *** I listen to port 3615 (3615) ***

[Thr 01] CUSTOMER KEY: >H1357713078<

[Thr 01] build version=720.2011.05.04

trc file: "dev_rd", trc level: 1, release: "720"

Tue Sep 13 14:49:07 2011

***LOG S00=> GwInitReader, gateway started ( 75855) [gwxxrd.c 1758]

systemid 327 (IBM i with OS400)

relno 7200

patchlevel 0

patchno 96

intno 20020600

make single threaded, ASCII, 64 bit, optimized

pid 75855

gateway runs with dp version 131(ext=118) (@(#) DPLIB-INT-VERSION-131)

gateway (version=720.2011.04.20)

Tue Sep 13 14:49:10 2011

gw/reg_no_conn_info = 1

gw/local_addr : 0.0.0.0

gw/reg_no_conn_info = 1

• SWITCH TRC-RESOLUTION from 1 TO 1

CCMS: initialize CCMS Monitoring for ABAP instance with J2EE addin.

CCMS uses Shared Memory Key 73 for monitoring.

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

Tue Sep 13 14:49:13 2011

CCMS: Initalized shared memory of size 40000000 for monitoring segment.

CCMS: Checking Downtime Configuration of Monitoring Segment.

CCMS: AlMsUpload called by wp 1002.

CCMS: AlMsUpload successful for /usr/sap/TEH/EHPI/abap/TEH/DVEBMGS15/log/ALMTTREE (0 MTEs).

Bind service sapgw15 (socket) to port 3315

GwIRegInitRegInfo: reg_info file /usr/sap/TEH/EHPI/abap/TEH/DVEBMGS15/data/reginfo not found

GwPrintMyHostAddr: my host addresses are :

1 : [10.127.0.100] omni.plastekgroup.com (HOSTNAME)

2 : [127.0.0.1] LOOPBACK (LOCALHOST)

Full qualified hostname = omni.plastekgroup.com

DpSysAdmExtCreate: ABAP is active

DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active

DpIPCInit2: read dp-profile-values from sys_adm_ext

DpShMCreate: sizeof(wp_adm)##17440#(1744)

DpShMCreate: sizeof(tm_adm)##4976768#(24760)

DpShMCreate: sizeof(wp_ca_adm)##56000#(56)

DpShMCreate: sizeof(appc_ca_adm)#56000#(56)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/576048/576064

DpShMCreate: sizeof(comm_adm)##576064#(1136)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm)##0#(104)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm)##0#(80)

DpShMCreate: sizeof(vmc_adm)##0#(1856)

DpShMCreate: sizeof(wall_adm)##(25648/36736/64/104)

DpShMCreate: sizeof(gw_adm)#48

DpShMCreate: sizeof(j2ee_adm)#2032

DpShMCreate: SHM_DP_ADM_KEY##(addr: 700000060000000, size: 5759216)

DpShMCreate: allocated sys_adm at 700000060000010

DpShMCreate: allocated wp_adm_list at 700000060002970

DpShMCreate: allocated wp_adm at 700000060002b60

DpShMCreate: allocated tm_adm_list at 700000060006f90

DpShMCreate: allocated tm_adm at 700000060006fe0

DpShMCreate: allocated appc_ca_adm at 7000000604d3b40

DpShMCreate: allocated comm_adm at 7000000604e1610

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 70000006056e060

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated gw_adm at 70000006056e110

DpShMCreate: allocated j2ee_adm at 70000006056e150

DpShMCreate: allocated ca_info at 70000006056e950

DpCommAttachTable: attached comm table (header=7000000604e1

MtxInit: -2 0 0

DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 fro

Tue Sep 13 14:50:14 2011

GwDpInit: attached to gw_adm at 70000006056e110

Tue Sep 13 14:50:16 2011

DpSetProcessPriority: Run priority for gwrd adjusted to 12