BI ABAP + Java in MSCS Windows Oracle

[Former Member]

Hello,

I have just finished the installation of a SAP Netweaver 7.0 EHP1 BI Abap + Java in a MSCS cluster with Oracle.

The installation has gone ok, all the HA inistallations steps has finished successfully, but now, when starting the dialog instance in the second mscs node, the disp+work.exe status says:

"Runnning, Message server connection OK, Dialog Queue time: 0.00 sec, J2EE status info unavailable"

Any idea of the reason?

I have run sapstartsrv.exe and register the service and COM interface again, but the problem is still the same.

With the issue, if I move the SAP cluster service to the second node, the java instance does not work.

Thanks and best regards,

Ana.

[former_member184473 · Accepted solution]

Hello Ana,

Check if note [877795|http://service.sap.com/sap/support/notes/877795|Problems w/ sapstartsrv as of Release 7.00 & 6.40 patch 169] point 35 is applicable to your case.

Regards,

Eduardo

[Former Member · Accepted solution]

Thanks Eduardo,

I already have kernel 701 32, that is bigger that 701_30, mentioned in the note.

Any other idea?

Thanks and regards,

Ana

[Former Member · Accepted solution]

I understood that your CI & DB is up and you want to start the additional dialog instance.

Can you please check the disp+work, dev_w0 logs?

[Former Member · Accepted solution]

Yes,

The CI and the DB are up and working fine. The problem is starting the dialog instance. The installation process finished succefully and it started the ABAP and the JAva dialog instance properly. After the installation I stoppen the dialog instance and when I tried to start the DI again, the java message appeared.

The dev_disp file shows the following:

DpCommInitTable: init table for 500 entries

rdisp/queue_size_check_value : -> off

ThTaskStatus: rdisp/reset_online_during_debug 0

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 4096 kByte.

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

<ES> 6140 blocks reserved for free list.

ES initialized.

J2EE server info

start = TRUE

state = STARTED

pid = 9020

argv[0] = C:\usr\sap\OPB\D30\exe\jcontrol.EXE

argv[1] = C:\usr\sap\OPB\D30\exe\jcontrol.EXE

argv[2] = pf=
SAPOPB\sapmnt\OPB\SYS\profile\OPB_D30_oneslmprd

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=65000

argv[5] = -DSAPSYSTEM=30

argv[6] = -DSAPSYSTEMNAME=OPB

argv[7] = -DSAPMYNAME=oneslmprd_OPB_30

argv[8] = -DSAPPROFILE=
SAPOPB\sapmnt\OPB\SYS\profile\OPB_D30_oneslmprd

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1681]

***LOG Q0K=> DpMsAttach, mscon ( SAPOPB) [dpxxdisp.c 12483]

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

DpStartStopMsg: start msg sent to message server o.k.

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 60000000 for monitoring segment.

CCMS: Checking Downtime Configuration of Monitoring Segment.

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

DpJ2eeLogin: j2ee state = CONNECTED

Release check o.K.

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

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

Thu Dec 02 13:40:00 2010

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4436]

• ERROR => NiIRead: SiRecv failed for hdl 4 / sock 992

(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:50457) [nixxi.cpp 4436]

• ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

MBUF state ACTIVE

DpModState: change server state from STARTING to ACTIVE

Thu Dec 02 13:40:37 2010

DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Thu Dec 02 13:40:57 2010

J2EE server info

start = TRUE

state = STARTED

pid = 8052

argv[0] = C:\usr\sap\OPB\D30\exe\jcontrol.EXE

argv[1] = C:\usr\sap\OPB\D30\exe\jcontrol.EXE

argv[2] = pf=
SAPOPB\sapmnt\OPB\SYS\profile\OPB_D30_oneslmprd

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64999

argv[5] = -DSAPSYSTEM=30

argv[6] = -DSAPSYSTEMNAME=OPB

argv[7] = -DSAPMYNAME=oneslmprd_OPB_30

argv[8] = -DSAPPROFILE=
SAPOPB\sapmnt\OPB\SYS\profile\OPB_D30_oneslmprd

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Dec 02 13:40:58 2010

DpJ2eeLogin: j2ee state = CONNECTED

Thu Dec 02 13:41:00 2010

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4436]

• ERROR => NiIRead: SiRecv failed for hdl 4 / sock 856

(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:50560) [nixxi.cpp 4436]

• ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

Thu Dec 02 13:41:17 2010

DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Thu Dec 02 13:41:37 2010

J2EE server info

start = TRUE

state = STARTED

pid = 8744

argv[0] = C:\usr\sap\OPB\D30\exe\jcontrol.EXE

argv[1] = C:\usr\sap\OPB\D30\exe\jcontrol.EXE

argv[2] = pf=
SAPOPB\sapmnt\OPB\SYS\profile\OPB_D30_oneslmprd

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64997

argv[5] = -DSAPSYSTEM=30

argv[6] = -DSAPSYSTEMNAME=OPB

argv[7] = -DSAPMYNAME=oneslmprd_OPB_30

argv[8] = -DSAPPROFILE=
SAPOPB\sapmnt\OPB\SYS\profile\OPB_D30_oneslmprd

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Dec 02 13:41:38 2010

DpJ2eeLogin: j2ee state = CONNECTED

Thu Dec 02 13:41:40 2010

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4436]

• ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1008

(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:50574) [nixxi.cpp 4436]

• ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

Thu Dec 02 13:41:58 2010

DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Thu Dec 02 13:42:18 2010

J2EE server info

start = TRUE

state = STARTED

pid = 7212

argv[0] = C:\usr\sap\OPB\D30\exe\jcontrol.EXE

argv[1] = C:\usr\sap\OPB\D30\exe\jcontrol.EXE

argv[2] = pf=
SAPOPB\sapmnt\OPB\SYS\profile\OPB_D30_oneslmprd

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64996

argv[5] = -DSAPSYSTEM=30

argv[6] = -DSAPSYSTEMNAME=OPB

argv[7] = -DSAPMYNAME=oneslmprd_OPB_30

argv[8] = -DSAPPROFILE=
SAPOPB\sapmnt\OPB\SYS\profile\OPB_D30_oneslmprd

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

DpJ2eeLogin: j2ee state = CONNECTED

Thu Dec 02 13:42:20 2010

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4436]

• ERROR => NiIRead: SiRecv failed for hdl 4 / sock 856

(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:50597) [nixxi.cpp 4436]

• ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

Thu Dec 02 13:42:38 2010

DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Thu Dec 02 13:42:58 2010

J2EE server info

start = TRUE

state = STARTED

pid = 1336

argv[0] = C:\usr\sap\OPB\D30\exe\jcontrol.EXE

argv[1] = C:\usr\sap\OPB\D30\exe\jcontrol.EXE

argv[2] = pf=
SAPOPB\sapmnt\OPB\SYS\profile\OPB_D30_oneslmprd

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64995

argv[5] = -DSAPSYSTEM=30

argv[6] = -DSAPSYSTEMNAME=OPB

argv[7] = -DSAPMYNAME=oneslmprd_OPB_30

argv[8] = -DSAPPROFILE=
SAPOPB\sapmnt\OPB\SYS\profile\OPB_D30_oneslmprd

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

DpJ2eeLogin: j2ee state = CONNECTED

Thu Dec 02 13:43:00 2010

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4436]

• ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1008

(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:50606) [nixxi.cpp 4436]

• ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

Thu Dec 02 13:43:18 2010

DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Thu Dec 02 13:43:38 2010

DpEnvCheckJ2ee: switch off j2ee start flag

The dev_w0 has no error messages.

Hope this helps.

Thansk and best regards,

Ana

[Former Member]

Hello,

Finally I have uninstalled the DI and installed it again and now it works.

Thanks to all.

Ana.

[Former Member]

Hello,

I think the problem is caused by domething related with Oracle, because the file C:\usr\sap\<SID>\DXX\j2ee\cluster\bootstrap\system.log says in the last line:

#1.5 #866F20524153000000000007000016B40004966CC305DFBE#1291293779425#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory#######Thread[main,5,main]##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0019#com.sap.sql.log.OpenSQLResourceBundle#Exception of type caught: .#2#com.sap.sql.log.OpenSQLException#Could not load class oracle.jdbc.driver.OracleDriver.#

Besides, the config.properties file has a path error. I think it copuld be caused because I did the installation of the DI with the shared disks in this node of the cluster, so, the entries of the file are:

#Generated by Config Tool

#Wed Dec 01 15:05:06 CET 2010

rdbms.maximum_connections=5

system.name=<SID>

secstorefs.keyfile=

SAP<SID>
sapmnt
<SID>
SYS
global
security
data
SecStore.key

secstorefs.secfile=

SAP<SID>
sapmnt
<SID>
SYS
global
security
data
SecStore.properties

secstorefs.lib=

SAP<SID>
sapmnt
<SID>
SYS
global
security
lib

rdbms.driverLocation=P\:
usr
sap
<SID>
DXX
exe
ojdbc14.jar

rdbms.connection=jdbc/pool/<SID>

rdbms.initial_connections=1

The rdbms.driver.location points to drive P, but this is a shared drive that in normal operation is attache to the first node. I have change it, but the error is still happening.

In the Central instance, the paramenter is pointing to drive C:.

HOw can I change it? In the second node in which the DI is running (almost running) the configtool.bat file does not exist so I cannot run the configtool. I think this behaviour is right because in other systems is the same way.

Do you think my analysis is right? Can you help me?

Thanks and best regards,

Ana