Hi All,

We are in a process of installing CRM  EHP2 on Linux MAXDB.

I  have successfully installed Central Instance with out any issues.

Now when i am trying to install ASCS Instance on top of central instance, in the last phase start central service  instance it  ended up with an error.

I have started and stopped SAP, and try to retry but error still persists

I am able to Login to  ABAP using GUI .

I have verified R3trans -d  it says (0000)

I have also verified Process list its up and running

sapcontrol -nr 77 -function GetProcessList

22.08.2013 04:42:09

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

msg_server, MessageServer, GRAY, Stopped, , , 32173

disp+work, Dispatcher, GREEN, Running, Message Server connection ok, Dialog Queue time: 0.00 sec, 2013 08 22 03:58:06, 0:44:03, 32174

igswd_mt, IGS Watchdog, GREEN, Running, 2013 08 22 03:58:06, 0:44:03, 32175

sapcontrol -nr 79 -function GetProcessList

22.08.2013 04:50:54

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

msg_server, MessageServer, GREEN, Running, 2013 08 22 04:42:36, 0:08:18, 6019

enserver, EnqueueServer, GREEN, Running, 2013 08 22 04:42:36, 0:08:18, 6020

In my temporary directory i see error

##/tmp/sapinst_instdir/CRMEhP2/AS-ABAP/ADA/HA/ASCS

cat dev_sap_kernel

[Thr 139860832577296] Thu Aug 22 04:45:05 2013

[Thr 139860832577296] ***LOG Q0I=> NiPConnect2: 10.1.1.220:3979: connect (111: Connection refused) [nixxi.cpp 3271]

[Thr 139860832577296] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4/sock 17

    (SI_ECONN_REFUSE/111; I4; ST; 10.1.1.220:3979) [nixxi.cpp    3271]

[Thr 139860832577296] *** ERROR => MsIAttachEx: NiBufConnect to sgtr-s-devcr2/3979 failed (rc=NIECONN_REFUSED) [msxxi_mt.c   718]

[Thr 139860832577296] ***LOG Q0I=> NiPConnect2: 10.1.1.220:3979: connect (111: Connection refused) [nixxi.cpp 3271]

[Thr 139860832577296] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 5/sock 17

    (SI_ECONN_REFUSE/111; I4; ST; 10.1.1.220:3979) [nixxi.cpp    3271]

[Thr 139860832577296] *** ERROR => MsIAttachEx: NiBufConnect to sgtr-s-devcr2/3979 failed (rc=NIECONN_REFUSED) [msxxi_mt.c   718]

Here is my sapinst.log

WARNING 2013-08-22 04:47:46.292

Execution of the command "/usr/sap/CR2/DVEBMGS77/exe/sapcontrol -prot NI_HTTP -nr 79 -function GetProcessList" finished with return code 3. Output:

22.08.2013 04:47:46

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

msg_server, MessageServer, GREEN, Running, 2013 08 22 04:42:36, 0:05:10, 6019

enserver, EnqueueServer, GREEN, Running, 2013 08 22 04:42:36, 0:05:10, 6020

ERROR 2013-08-22 04:47:46.296

CJS-30086  Instance CR2/ASCS79 [PARTIAL] did not start after 5:10 minutes. Giving up.

ERROR 2013-08-22 04:47:46.510

FCO-00011  The step startInstance with step key |NW_ABAP_ASCS|ind|ind|ind|ind|0|0|NW_SCS_Instance|ind|ind|ind|ind|ascs|0|startInstance was executed with status ERROR ( Last error reported by the step: Instance CR2/ASCS79 [PARTIAL] did not start after 5:10 minutes. Giving up.).

INFO 2013-08-22 04:47:46.733

Creating file /tmp/sapinst_instdir/CRMEhP2/AS-ABAP/ADA/HA/ASCS/__instana_tmp.xml.

Please help me in moving forward.

Thanks in Advance

Regards,

Vardhan.

Hi Experts

we have sol7.1 we are able to start abap instance but when we are try to start Java instance SERVER0 stopped exitcode -2

following are the logs for the same of dev_ server0

---------------------------------------------------
trc file: "dev_server0", trc level: 1, release: "720"
---------------------------------------------------
node name   : ID15272050
pid         : 7044
system name : AFS
system nr.  : 01
started at  : Thu Aug 22 13:02:24 2013
arguments   :
   arg[00] : D:\usr\sap\AFS\DVEBMGS01\exe\jlaunch.exe
   arg[01] : pf=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[02] : -DSAPINFO=AFS_01_server
   arg[03] : pf=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[04] : -DSAPSTART=1
   arg[05] : -DCONNECT_PORT=51026
   arg[06] : -DSAPSYSTEM=01
   arg[07] : -DSAPSYSTEMNAME=AFS
   arg[08] : -DSAPMYNAME=IDESSOLMAN_AFS_01
   arg[09] : -DSAPPROFILE=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[10] : -DFRFC_FALLBACK=ON
   arg[11] : -DFRFC_FALLBACK_HOST=localhost

**********************************************************************
Used property files
-> files [00] : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Bootstrap nodes
-> [00] bootstrap            : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID15272000 : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID15272050 : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Worker nodes
-> [00] ID15272000           : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] ID15272050           : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties]
-> ms host    : IDESSOLMAN
-> ms port    : 3902
-> OS libs    : D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs
-> Admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
**********************************************************************

[Thr 5212] Thu Aug 22 13:02:24 2013
[Thr 5212] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 5212] JLaunchRequestQueueInit: create pipe listener thread
[Thr 3932] JLaunchRequestFunc: Thread 3932 started as listener thread for np messages.
[Thr 3708] WaitSyncSemThread: Thread 3708 started as semaphore monitor thread.
[Thr 5212] JLaunchInitSignalHandling: signal handling is disabled
[Thr 5212] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
[Thr 5212] MPI: dynamic quotas disabled.
[Thr 5212] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
[Thr 5212] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
[Thr 5212] CCMS uses Shared Memory Key 73 for monitoring.
[Thr 5212] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
[Thr 5212] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
[Thr 5212] CCMS: CCMS Monitoring Initialization finished, rc=0.
[Thr 5212] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [ID15272050]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4
-> java parameters    : -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=256M -XX:PermSize=256M -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dsun.io.useCanonCaches=false -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.sap.jvm.scenario=j2ee -Dcom.wily.introscope.agentProfile=D:/usr/sap/ccms/wily/IntroscopeAgent.profile -Dcom.wily.introscope.agent.agentName=AFS_DVEBMGS01_server0 -Xbootclasspath/p:D:/usr/sap/ccms/wily/connectors/connector.jar:D:/usr/sap/ccms
-> java vm version    : 4.1.024 1.6-b04
-> java vm vendor     : SAP Java Server VM (SAP AG)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 512M
-> init heap size     : 1024M
-> stack size         : 2M
-> root path          : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : D:\usr\sap\AFS\DVEBMGS01\exe\jstartup.jar;D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50121
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 5212] JLaunchISetDebugMode: set debug mode [no]
[Thr 4604] JLaunchIStartFunc: Thread 4604 started as Java VM thread.

**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 2097152 Bytes
-> arg[  0]: exit
-> arg[  1]: abort
-> arg[  2]: vfprintf
-> arg[  3]: -XX:MaxNewSize=600M
-> arg[  4]: -XX:NewSize=600M
-> arg[  5]: -XX:MaxPermSize=256M
-> arg[  6]: -XX:PermSize=256M
-> arg[  7]: -XX:+UseConcMarkSweepGC
-> arg[  8]: -XX:+DisableExplicitGC
-> arg[  9]: -XX:TargetSurvivorRatio=90
-> arg[ 10]: -XX:SurvivorRatio=4
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -verbose:gc
-> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 15]: -XX:HeapDumpPath=OOM.hprof
-> arg[ 16]: -XX:+HeapDumpOnOutOfMemoryError
-> arg[ 17]: -Djco.jarm=1
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Djava.security.policy=./java.policy
-> arg[ 20]: -Djava.security.egd=file:/dev/urandom
-> arg[ 21]: -Dsun.io.useCanonCaches=false
-> arg[ 22]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 23]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 24]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 25]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 26]: -Dcom.sap.jvm.scenario=j2ee
-> arg[ 27]: -Dcom.wily.introscope.agentProfile=D:/usr/sap/ccms/wily/IntroscopeAgent.profile
-> arg[ 28]: -Dcom.wily.introscope.agent.agentName=AFS_DVEBMGS01_server0
-> arg[ 29]: -Xbootclasspath/p:D:/usr/sap/ccms/wily/connectors/connector.jar:D:/usr/sap/ccms
-> arg[ 30]: -Dsys.global.dir=D:\usr\sap\AFS\SYS\global
-> arg[ 31]: -Dapplication.home=D:\usr\sap\AFS\DVEBMGS01\exe
-> arg[ 32]: -Djava.class.path=D:\usr\sap\AFS\DVEBMGS01\exe\jstartup.jar;D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 33]: -Djava.library.path=D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin\server;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\bin;D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin\server;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\bin;D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs;D:\usr\sap\AFS\DVEBMGS01\exe;D:\app\administrator\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Kaspersky Lab\Kaspersky Endpoint Security 10 for Windows\;D:\usr\sap\AFS\SCS02\exe;C:\j2sdk1.4.2_17-x64\bin;usr\sap\AFS\sys\profile\START_DVEBMGS01;D:\usr\sap\AFS\SYS\exe\uc\NTAMD64
-> arg[ 34]: -Dmemory.manager=512M
-> arg[ 35]: -Xmx512M
-> arg[ 36]: -Xms1024M
-> arg[ 37]: -Xss2M
-> arg[ 38]: -DLoadBalanceRestricted=no
-> arg[ 39]: -Djstartup.mode=JCONTROL
-> arg[ 40]: -Djstartup.ownProcessId=7044
-> arg[ 41]: -Djstartup.ownHardwareId=D0676929139
-> arg[ 42]: -Djstartup.whoami=server
-> arg[ 43]: -Djstartup.debuggable=no
-> arg[ 44]: -DSAPINFO=AFS_01_server
-> arg[ 45]: -DSAPSTART=1
-> arg[ 46]: -DCONNECT_PORT=51026
-> arg[ 47]: -DSAPSYSTEM=01
-> arg[ 48]: -DSAPSYSTEMNAME=AFS
-> arg[ 49]: -DSAPMYNAME=IDESSOLMAN_AFS_01
-> arg[ 50]: -DSAPPROFILE=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
-> arg[ 51]: -DFRFC_FALLBACK=ON
-> arg[ 52]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 53]: -DSAPSTARTUP=1
-> arg[ 54]: -DSAPSYSTEM=01
-> arg[ 55]: -DSAPSYSTEMNAME=AFS
-> arg[ 56]: -DSAPMYNAME=IDESSOLMAN_AFS_01
-> arg[ 57]: -DSAPDBHOST=IDESSOLMAN
-> arg[ 58]: -Dj2ee.dbhost=IDESSOLMAN
**********************************************************************

Error occurred during initialization of VM
Incompatible minimum and maximum heap sizes specified: min=1073741824 bytes, max=635437056 bytes
[Thr 4604] JLaunchIAbortJava: abort hook is called
[Thr 4604] **********************************************************************
[Thr 4604] *** ERROR => The Java VM aborted unexpectedly.
[Thr 4604] *** Please see SAP Note 943602 , section 'Java VM crashes'
[Thr 4604] *** for additional information and trouble shooting.
[Thr 4604] **********************************************************************
[Thr 4604] JLaunchCloseProgram: good bye (exitcode = -2)

---------------------------------------------------
trc file: "dev_server0", trc level: 1, release: "720"
---------------------------------------------------
node name   : ID15272050
pid         : 7936
system name : AFS
system nr.  : 01
started at  : Thu Aug 22 13:02:29 2013
arguments   :
   arg[00] : D:\usr\sap\AFS\DVEBMGS01\exe\jlaunch.exe
   arg[01] : pf=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[02] : -DSAPINFO=AFS_01_server
   arg[03] : pf=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[04] : -DSAPSTART=1
   arg[05] : -DCONNECT_PORT=51026
   arg[06] : -DSAPSYSTEM=01
   arg[07] : -DSAPSYSTEMNAME=AFS
   arg[08] : -DSAPMYNAME=IDESSOLMAN_AFS_01
   arg[09] : -DSAPPROFILE=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[10] : -DFRFC_FALLBACK=ON
   arg[11] : -DFRFC_FALLBACK_HOST=localhost

**********************************************************************
Used property files
-> files [00] : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Bootstrap nodes
-> [00] bootstrap            : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID15272000 : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID15272050 : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Worker nodes
-> [00] ID15272000           : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] ID15272050           : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties]
-> ms host    : IDESSOLMAN
-> ms port    : 3902
-> OS libs    : D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs
-> Admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
**********************************************************************

[Thr 7712] Thu Aug 22 13:02:29 2013
[Thr 7712] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 7712] JLaunchRequestQueueInit: create pipe listener thread
[Thr 4312] JLaunchRequestFunc: Thread 4312 started as listener thread for np messages.
[Thr 2164] WaitSyncSemThread: Thread 2164 started as semaphore monitor thread.
[Thr 7712] JLaunchInitSignalHandling: signal handling is disabled
[Thr 7712] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
[Thr 7712] MPI: dynamic quotas disabled.
[Thr 7712] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
[Thr 7712] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
[Thr 7712] CCMS uses Shared Memory Key 73 for monitoring.
[Thr 7712] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
[Thr 7712] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
[Thr 7712] CCMS: CCMS Monitoring Initialization finished, rc=0.
[Thr 7712] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [ID15272050]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4
-> java parameters    : -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=256M -XX:PermSize=256M -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dsun.io.useCanonCaches=false -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.sap.jvm.scenario=j2ee -Dcom.wily.introscope.agentProfile=D:/usr/sap/ccms/wily/IntroscopeAgent.profile -Dcom.wily.introscope.agent.agentName=AFS_DVEBMGS01_server0 -Xbootclasspath/p:D:/usr/sap/ccms/wily/connectors/connector.jar:D:/usr/sap/ccms
-> java vm version    : 4.1.024 1.6-b04
-> java vm vendor     : SAP Java Server VM (SAP AG)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 512M
-> init heap size     : 1024M
-> stack size         : 2M
-> root path          : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : D:\usr\sap\AFS\DVEBMGS01\exe\jstartup.jar;D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50121
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 7712] JLaunchISetDebugMode: set debug mode [no]
[Thr 7940] JLaunchIStartFunc: Thread 7940 started as Java VM thread.

**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 2097152 Bytes
-> arg[  0]: exit
-> arg[  1]: abort
-> arg[  2]: vfprintf
-> arg[  3]: -XX:MaxNewSize=600M
-> arg[  4]: -XX:NewSize=600M
-> arg[  5]: -XX:MaxPermSize=256M
-> arg[  6]: -XX:PermSize=256M
-> arg[  7]: -XX:+UseConcMarkSweepGC
-> arg[  8]: -XX:+DisableExplicitGC
-> arg[  9]: -XX:TargetSurvivorRatio=90
-> arg[ 10]: -XX:SurvivorRatio=4
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -verbose:gc
-> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 15]: -XX:HeapDumpPath=OOM.hprof
-> arg[ 16]: -XX:+HeapDumpOnOutOfMemoryError
-> arg[ 17]: -Djco.jarm=1
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Djava.security.policy=./java.policy
-> arg[ 20]: -Djava.security.egd=file:/dev/urandom
-> arg[ 21]: -Dsun.io.useCanonCaches=false
-> arg[ 22]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 23]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 24]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 25]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 26]: -Dcom.sap.jvm.scenario=j2ee
-> arg[ 27]: -Dcom.wily.introscope.agentProfile=D:/usr/sap/ccms/wily/IntroscopeAgent.profile
-> arg[ 28]: -Dcom.wily.introscope.agent.agentName=AFS_DVEBMGS01_server0
-> arg[ 29]: -Xbootclasspath/p:D:/usr/sap/ccms/wily/connectors/connector.jar:D:/usr/sap/ccms
-> arg[ 30]: -Dsys.global.dir=D:\usr\sap\AFS\SYS\global
-> arg[ 31]: -Dapplication.home=D:\usr\sap\AFS\DVEBMGS01\exe
-> arg[ 32]: -Djava.class.path=D:\usr\sap\AFS\DVEBMGS01\exe\jstartup.jar;D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 33]: -Djava.library.path=D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin\server;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\bin;D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin\server;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\bin;D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs;D:\usr\sap\AFS\DVEBMGS01\exe;D:\app\administrator\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Kaspersky Lab\Kaspersky Endpoint Security 10 for Windows\;D:\usr\sap\AFS\SCS02\exe;C:\j2sdk1.4.2_17-x64\bin;usr\sap\AFS\sys\profile\START_DVEBMGS01;D:\usr\sap\AFS\SYS\exe\uc\NTAMD64
-> arg[ 34]: -Dmemory.manager=512M
-> arg[ 35]: -Xmx512M
-> arg[ 36]: -Xms1024M
-> arg[ 37]: -Xss2M
-> arg[ 38]: -DLoadBalanceRestricted=no
-> arg[ 39]: -Djstartup.mode=JCONTROL
-> arg[ 40]: -Djstartup.ownProcessId=7936
-> arg[ 41]: -Djstartup.ownHardwareId=D0676929139
-> arg[ 42]: -Djstartup.whoami=server
-> arg[ 43]: -Djstartup.debuggable=no
-> arg[ 44]: -DSAPINFO=AFS_01_server
-> arg[ 45]: -DSAPSTART=1
-> arg[ 46]: -DCONNECT_PORT=51026
-> arg[ 47]: -DSAPSYSTEM=01
-> arg[ 48]: -DSAPSYSTEMNAME=AFS
-> arg[ 49]: -DSAPMYNAME=IDESSOLMAN_AFS_01
-> arg[ 50]: -DSAPPROFILE=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
-> arg[ 51]: -DFRFC_FALLBACK=ON
-> arg[ 52]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 53]: -DSAPSTARTUP=1
-> arg[ 54]: -DSAPSYSTEM=01
-> arg[ 55]: -DSAPSYSTEMNAME=AFS
-> arg[ 56]: -DSAPMYNAME=IDESSOLMAN_AFS_01
-> arg[ 57]: -DSAPDBHOST=IDESSOLMAN
-> arg[ 58]: -Dj2ee.dbhost=IDESSOLMAN
**********************************************************************

Error occurred during initialization of VM
Incompatible minimum and maximum heap sizes specified: min=1073741824 bytes, max=635437056 bytes
[Thr 7940] JLaunchIAbortJava: abort hook is called
[Thr 7940] **********************************************************************
[Thr 7940] *** ERROR => The Java VM aborted unexpectedly.
[Thr 7940] *** Please see SAP Note 943602 , section 'Java VM crashes'
[Thr 7940] *** for additional information and trouble shooting.
[Thr 7940] **********************************************************************
[Thr 7940] JLaunchCloseProgram: good bye (exitcode = -2)

---------------------------------------------------
trc file: "dev_server0", trc level: 1, release: "720"
---------------------------------------------------
node name   : ID15272050
pid         : 4348
system name : AFS
system nr.  : 01
started at  : Thu Aug 22 13:02:35 2013
arguments   :
   arg[00] : D:\usr\sap\AFS\DVEBMGS01\exe\jlaunch.exe
   arg[01] : pf=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[02] : -DSAPINFO=AFS_01_server
   arg[03] : pf=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[04] : -DSAPSTART=1
   arg[05] : -DCONNECT_PORT=51026
   arg[06] : -DSAPSYSTEM=01
   arg[07] : -DSAPSYSTEMNAME=AFS
   arg[08] : -DSAPMYNAME=IDESSOLMAN_AFS_01
   arg[09] : -DSAPPROFILE=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[10] : -DFRFC_FALLBACK=ON
   arg[11] : -DFRFC_FALLBACK_HOST=localhost

**********************************************************************
Used property files
-> files [00] : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Bootstrap nodes
-> [00] bootstrap            : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID15272000 : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID15272050 : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Worker nodes
-> [00] ID15272000           : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] ID15272050           : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties]
-> ms host    : IDESSOLMAN
-> ms port    : 3902
-> OS libs    : D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs
-> Admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
**********************************************************************

[Thr 5376] Thu Aug 22 13:02:35 2013
[Thr 5376] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 5376] JLaunchRequestQueueInit: create pipe listener thread
[Thr 6504] JLaunchRequestFunc: Thread 6504 started as listener thread for np messages.
[Thr 6472] WaitSyncSemThread: Thread 6472 started as semaphore monitor thread.
[Thr 5376] JLaunchInitSignalHandling: signal handling is disabled
[Thr 5376] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
[Thr 5376] MPI: dynamic quotas disabled.
[Thr 5376] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
[Thr 5376] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
[Thr 5376] CCMS uses Shared Memory Key 73 for monitoring.
[Thr 5376] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
[Thr 5376] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
[Thr 5376] CCMS: CCMS Monitoring Initialization finished, rc=0.
[Thr 5376] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [ID15272050]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4
-> java parameters    : -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=256M -XX:PermSize=256M -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dsun.io.useCanonCaches=false -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.sap.jvm.scenario=j2ee -Dcom.wily.introscope.agentProfile=D:/usr/sap/ccms/wily/IntroscopeAgent.profile -Dcom.wily.introscope.agent.agentName=AFS_DVEBMGS01_server0 -Xbootclasspath/p:D:/usr/sap/ccms/wily/connectors/connector.jar:D:/usr/sap/ccms
-> java vm version    : 4.1.024 1.6-b04
-> java vm vendor     : SAP Java Server VM (SAP AG)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 512M
-> init heap size     : 1024M
-> stack size         : 2M
-> root path          : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : D:\usr\sap\AFS\DVEBMGS01\exe\jstartup.jar;D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50121
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 5376] JLaunchISetDebugMode: set debug mode [no]
[Thr 7956] JLaunchIStartFunc: Thread 7956 started as Java VM thread.

**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 2097152 Bytes
-> arg[  0]: exit
-> arg[  1]: abort
-> arg[  2]: vfprintf
-> arg[  3]: -XX:MaxNewSize=600M
-> arg[  4]: -XX:NewSize=600M
-> arg[  5]: -XX:MaxPermSize=256M
-> arg[  6]: -XX:PermSize=256M
-> arg[  7]: -XX:+UseConcMarkSweepGC
-> arg[  8]: -XX:+DisableExplicitGC
-> arg[  9]: -XX:TargetSurvivorRatio=90
-> arg[ 10]: -XX:SurvivorRatio=4
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -verbose:gc
-> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 15]: -XX:HeapDumpPath=OOM.hprof
-> arg[ 16]: -XX:+HeapDumpOnOutOfMemoryError
-> arg[ 17]: -Djco.jarm=1
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Djava.security.policy=./java.policy
-> arg[ 20]: -Djava.security.egd=file:/dev/urandom
-> arg[ 21]: -Dsun.io.useCanonCaches=false
-> arg[ 22]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 23]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 24]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 25]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 26]: -Dcom.sap.jvm.scenario=j2ee
-> arg[ 27]: -Dcom.wily.introscope.agentProfile=D:/usr/sap/ccms/wily/IntroscopeAgent.profile
-> arg[ 28]: -Dcom.wily.introscope.agent.agentName=AFS_DVEBMGS01_server0
-> arg[ 29]: -Xbootclasspath/p:D:/usr/sap/ccms/wily/connectors/connector.jar:D:/usr/sap/ccms
-> arg[ 30]: -Dsys.global.dir=D:\usr\sap\AFS\SYS\global
-> arg[ 31]: -Dapplication.home=D:\usr\sap\AFS\DVEBMGS01\exe
-> arg[ 32]: -Djava.class.path=D:\usr\sap\AFS\DVEBMGS01\exe\jstartup.jar;D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 33]: -Djava.library.path=D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin\server;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\bin;D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin\server;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\bin;D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs;D:\usr\sap\AFS\DVEBMGS01\exe;D:\app\administrator\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Kaspersky Lab\Kaspersky Endpoint Security 10 for Windows\;D:\usr\sap\AFS\SCS02\exe;C:\j2sdk1.4.2_17-x64\bin;usr\sap\AFS\sys\profile\START_DVEBMGS01;D:\usr\sap\AFS\SYS\exe\uc\NTAMD64
-> arg[ 34]: -Dmemory.manager=512M
-> arg[ 35]: -Xmx512M
-> arg[ 36]: -Xms1024M
-> arg[ 37]: -Xss2M
-> arg[ 38]: -DLoadBalanceRestricted=no
-> arg[ 39]: -Djstartup.mode=JCONTROL
-> arg[ 40]: -Djstartup.ownProcessId=4348
-> arg[ 41]: -Djstartup.ownHardwareId=D0676929139
-> arg[ 42]: -Djstartup.whoami=server
-> arg[ 43]: -Djstartup.debuggable=no
-> arg[ 44]: -DSAPINFO=AFS_01_server
-> arg[ 45]: -DSAPSTART=1
-> arg[ 46]: -DCONNECT_PORT=51026
-> arg[ 47]: -DSAPSYSTEM=01
-> arg[ 48]: -DSAPSYSTEMNAME=AFS
-> arg[ 49]: -DSAPMYNAME=IDESSOLMAN_AFS_01
-> arg[ 50]: -DSAPPROFILE=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
-> arg[ 51]: -DFRFC_FALLBACK=ON
-> arg[ 52]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 53]: -DSAPSTARTUP=1
-> arg[ 54]: -DSAPSYSTEM=01
-> arg[ 55]: -DSAPSYSTEMNAME=AFS
-> arg[ 56]: -DSAPMYNAME=IDESSOLMAN_AFS_01
-> arg[ 57]: -DSAPDBHOST=IDESSOLMAN
-> arg[ 58]: -Dj2ee.dbhost=IDESSOLMAN
**********************************************************************

Error occurred during initialization of VM
Incompatible minimum and maximum heap sizes specified: min=1073741824 bytes, max=635437056 bytes
[Thr 7956] JLaunchIAbortJava: abort hook is called
[Thr 7956] **********************************************************************
[Thr 7956] *** ERROR => The Java VM aborted unexpectedly.
[Thr 7956] *** Please see SAP Note 943602 , section 'Java VM crashes'
[Thr 7956] *** for additional information and trouble shooting.
[Thr 7956] **********************************************************************
[Thr 7956] JLaunchCloseProgram: good bye (exitcode = -2)

---------------------------------------------------
trc file: "dev_server0", trc level: 1, release: "720"
---------------------------------------------------
node name   : ID15272050
pid         : 6768
system name : AFS
system nr.  : 01
started at  : Thu Aug 22 13:02:40 2013
arguments   :
   arg[00] : D:\usr\sap\AFS\DVEBMGS01\exe\jlaunch.exe
   arg[01] : pf=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[02] : -DSAPINFO=AFS_01_server
   arg[03] : pf=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[04] : -DSAPSTART=1
   arg[05] : -DCONNECT_PORT=51026
   arg[06] : -DSAPSYSTEM=01
   arg[07] : -DSAPSYSTEMNAME=AFS
   arg[08] : -DSAPMYNAME=IDESSOLMAN_AFS_01
   arg[09] : -DSAPPROFILE=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
   arg[10] : -DFRFC_FALLBACK=ON
   arg[11] : -DFRFC_FALLBACK_HOST=localhost

**********************************************************************
Used property files
-> files [00] : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Bootstrap nodes
-> [00] bootstrap            : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] bootstrap_ID15272000 : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [02] bootstrap_ID15272050 : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Worker nodes
-> [00] ID15272000           : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
-> [01] ID15272050           : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\instance.properties]
-> ms host    : IDESSOLMAN
-> ms port    : 3902
-> OS libs    : D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs
-> Admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
**********************************************************************

[Thr 6976] Thu Aug 22 13:02:40 2013
[Thr 6976] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 6976] JLaunchRequestQueueInit: create pipe listener thread
[Thr 5344] JLaunchRequestFunc: Thread 5344 started as listener thread for np messages.
[Thr 6748] WaitSyncSemThread: Thread 6748 started as semaphore monitor thread.
[Thr 6976] JLaunchInitSignalHandling: signal handling is disabled
[Thr 6976] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
[Thr 6976] MPI: dynamic quotas disabled.
[Thr 6976] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
[Thr 6976] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
[Thr 6976] CCMS uses Shared Memory Key 73 for monitoring.
[Thr 6976] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
[Thr 6976] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
[Thr 6976] CCMS: CCMS Monitoring Initialization finished, rc=0.
[Thr 6976] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [ID15272050]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4
-> java parameters    : -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=256M -XX:PermSize=256M -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dsun.io.useCanonCaches=false -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.sap.jvm.scenario=j2ee -Dcom.wily.introscope.agentProfile=D:/usr/sap/ccms/wily/IntroscopeAgent.profile -Dcom.wily.introscope.agent.agentName=AFS_DVEBMGS01_server0 -Xbootclasspath/p:D:/usr/sap/ccms/wily/connectors/connector.jar:D:/usr/sap/ccms
-> java vm version    : 4.1.024 1.6-b04
-> java vm vendor     : SAP Java Server VM (SAP AG)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 512M
-> init heap size     : 1024M
-> stack size         : 2M
-> root path          : D:\usr\sap\AFS\DVEBMGS01\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : D:\usr\sap\AFS\DVEBMGS01\exe\jstartup.jar;D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50121
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 6976] JLaunchISetDebugMode: set debug mode [no]
[Thr 5976] JLaunchIStartFunc: Thread 5976 started as Java VM thread.

**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 2097152 Bytes
-> arg[  0]: exit
-> arg[  1]: abort
-> arg[  2]: vfprintf
-> arg[  3]: -XX:MaxNewSize=600M
-> arg[  4]: -XX:NewSize=600M
-> arg[  5]: -XX:MaxPermSize=256M
-> arg[  6]: -XX:PermSize=256M
-> arg[  7]: -XX:+UseConcMarkSweepGC
-> arg[  8]: -XX:+DisableExplicitGC
-> arg[  9]: -XX:TargetSurvivorRatio=90
-> arg[ 10]: -XX:SurvivorRatio=4
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -verbose:gc
-> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 15]: -XX:HeapDumpPath=OOM.hprof
-> arg[ 16]: -XX:+HeapDumpOnOutOfMemoryError
-> arg[ 17]: -Djco.jarm=1
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Djava.security.policy=./java.policy
-> arg[ 20]: -Djava.security.egd=file:/dev/urandom
-> arg[ 21]: -Dsun.io.useCanonCaches=false
-> arg[ 22]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 23]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 24]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 25]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 26]: -Dcom.sap.jvm.scenario=j2ee
-> arg[ 27]: -Dcom.wily.introscope.agentProfile=D:/usr/sap/ccms/wily/IntroscopeAgent.profile
-> arg[ 28]: -Dcom.wily.introscope.agent.agentName=AFS_DVEBMGS01_server0
-> arg[ 29]: -Xbootclasspath/p:D:/usr/sap/ccms/wily/connectors/connector.jar:D:/usr/sap/ccms
-> arg[ 30]: -Dsys.global.dir=D:\usr\sap\AFS\SYS\global
-> arg[ 31]: -Dapplication.home=D:\usr\sap\AFS\DVEBMGS01\exe
-> arg[ 32]: -Djava.class.path=D:\usr\sap\AFS\DVEBMGS01\exe\jstartup.jar;D:\usr\sap\AFS\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 33]: -Djava.library.path=D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin\server;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\bin;D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin\server;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\jre\bin;D:\usr\sap\AFS\DVEBMGS01\exe\sapjvm_4\bin;D:\usr\sap\AFS\DVEBMGS01\j2ee\os_libs;D:\usr\sap\AFS\DVEBMGS01\exe;D:\app\administrator\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Kaspersky Lab\Kaspersky Endpoint Security 10 for Windows\;D:\usr\sap\AFS\SCS02\exe;C:\j2sdk1.4.2_17-x64\bin;usr\sap\AFS\sys\profile\START_DVEBMGS01;D:\usr\sap\AFS\SYS\exe\uc\NTAMD64
-> arg[ 34]: -Dmemory.manager=512M
-> arg[ 35]: -Xmx512M
-> arg[ 36]: -Xms1024M
-> arg[ 37]: -Xss2M
-> arg[ 38]: -DLoadBalanceRestricted=no
-> arg[ 39]: -Djstartup.mode=JCONTROL
-> arg[ 40]: -Djstartup.ownProcessId=6768
-> arg[ 41]: -Djstartup.ownHardwareId=D0676929139
-> arg[ 42]: -Djstartup.whoami=server
-> arg[ 43]: -Djstartup.debuggable=no
-> arg[ 44]: -DSAPINFO=AFS_01_server
-> arg[ 45]: -DSAPSTART=1
-> arg[ 46]: -DCONNECT_PORT=51026
-> arg[ 47]: -DSAPSYSTEM=01
-> arg[ 48]: -DSAPSYSTEMNAME=AFS
-> arg[ 49]: -DSAPMYNAME=IDESSOLMAN_AFS_01
-> arg[ 50]: -DSAPPROFILE=\\IDESSOLMAN\sapmnt\AFS\SYS\profile\AFS_DVEBMGS01_IDESSOLMAN
-> arg[ 51]: -DFRFC_FALLBACK=ON
-> arg[ 52]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 53]: -DSAPSTARTUP=1
-> arg[ 54]: -DSAPSYSTEM=01
-> arg[ 55]: -DSAPSYSTEMNAME=AFS
-> arg[ 56]: -DSAPMYNAME=IDESSOLMAN_AFS_01
-> arg[ 57]: -DSAPDBHOST=IDESSOLMAN
-> arg[ 58]: -Dj2ee.dbhost=IDESSOLMAN
**********************************************************************

Error occurred during initialization of VM
Incompatible minimum and maximum heap sizes specified: min=1073741824 bytes, max=635437056 bytes
[Thr 5976] JLaunchIAbortJava: abort hook is called
[Thr 5976] **********************************************************************
[Thr 5976] *** ERROR => The Java VM aborted unexpectedly.
[Thr 5976] *** Please see SAP Note 943602 , section 'Java VM crashes'
[Thr 5976] *** for additional information and trouble shooting.
[Thr 5976] **********************************************************************
[Thr 5976] JLaunchCloseProgram: good bye (exitcode = -2)

Thanks & Regards

Hello Colleagues,

We need to generate stack xml with the help of SOLMAN system for upgrade in system PTN.

But while pushing data from our ABAP system to our SOLMAN SLD(Centralized SLD) using TA RZ70 we are getting following error.

================================================================

0: ldciptn_PTN_33                            : Collection of SLD data finished

0: ldciptn_PTN_33                            : Data collected successfully

0: ldciptn_PTN_33                            : RFC data prepared

0: ldciptn_PTN_33                            : Used RFC destination: SLD_UC

0: ldciptn_PTN_33                            : RFC call failed: Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=20 thRc=2

===============================================================

I have checked my SLD using transaction TA SLDAPICUST. SLD is running

fine.

  SLD destination settings:

  Alias:       SBM

  Host name:   ldcisbm.wdf.sap.corp

  Port number: 57700

  User:        j2ee_admin

We have checked SLD_UC RFC(TA SM59 and of TCP/IP type T) in out ABAP system.While doing connection test we are getting following error

================================================================

Please check attached screenshot.

We found a relevant SAP Note Note 353597 - Registering RFC server programs.

As per SAP Note configuration from ABAP end is correct in out system. But i am not able to find the config file(saprfc.ini) at OS level. Can anyone please let me know where exactly this file resides. All these RFC's are working fine till yesterday evening.

There are two different types of type T RFC named SLD_UC(Send data of Unicode system) and SLD_NUC(Send data of Non unicode system). My system is UC(SLD_UC is failing) where as SLD_NUC connection test is working fine

Regards,

Surojit

Hi Gurus,

I am using NW AS Java 7.3. I have a problem with the jsessionid as is not renew when a new session is created when a HTTP request with a URL contains the jsessionid. I have created a simple test case:

HTTP request (GET):

http://127.0.0.1:50000/login.do;jsessionid=gYArgRJKi-vPaGaS5Pm6FJ0rBFiiPwGK8H8A_SAPEnAYRDDZbFI4us7UI9Xyyn;saplb_*=(J2EE8114620)8114650

Login.java:

    protected void doGet(HttpServletRequest request, HttpServletResponse response)

        throws ServletException, IOException {

        response.setContentType("text/html");

        PrintWriter out = response.getWriter();

        out.println("<html><body>Logging on");

        HttpSession session = request.getSession(false);

        if (session != null) {

            session.invalidate();

        }

        out.println("</p>request.getSession(true);</p>");

        session = request.getSession(true);

        out.println("</p>session.getId()=</p>" + session.getId());

        out.println("</body></html>");

    }

Result:

    Logging on

    request.getSession(true);

    session.getId()=

    gYArgRJKi-vPaGaS5Pm6FJ0rBFiiPwGK8H8A_SAP

Meaning with the same URL, the exact same jsessionid (gYArgRJKi-vPaGaS5Pm6FJ0rBFiiPwGK8H8A_SAP) will be created always. Additionally, my business requirement requires to always use URL session tracking. Hence, I have web-j2ee-engine.xml:

    <url-session-tracking>true</url-session-tracking>

I have checked SAP note 1310561. It states that such session fixation issue have been resolved in NW 7.3. How to have the jsessionid renew when a session is created even though it is jsessionid is specified in the URL and url session tracking is always enabled?

Or it is the SessionIdRegenerationEnabled is not applicable to 'url-session-tracking = true' scenario?

Thanks a lot first. Any help will be appreciated greatly.

Hi Basis Guru's,

I am planing to install SAP Netweaver7.31 standalone java system.

Kindly let me know any one have step by step procedure documents to install fresh System on Windows OS and MSSQL database.

I have little knowledge on installation but need file system setup and how to media download from market place and parameters need to set before and after installation .

Regards,

Surendra.

i install the ecc ides sr3  oracle X64 on win  2003 X64 .using install master.   at the last  check ddic password step.message error.   thank you.

Test logon to SAP System XXX failed.   SOLUTION: Make sure that the system is started, that the user DDIC exists and that the password of user DDIC is correct.

the log is

INFO       2043-08-22 21:56:43.453 [iaxxrfcimp.cpp:380]

           CAbRfcImpl::setRfcConnectParam

RFC parameter SYSNR set to value 00.

INFO       2043-08-22 21:56:43.453 [iaxxrfcimp.cpp:520]

           CAbRfcImpl::checkConnectInfo

RFC connection information checked successfully.

WARNING[E] 2043-08-22 21:57:21.203 [iaxxrfcimp.cpp:433]

           CAbRfcImpl::openRfcConn

FRF-00007  Unable to open RFC connection.

TRACE      2043-08-22 21:57:21.203 [iaxxrfcimp.cpp:434]

           CAbRfcImpl::openRfcConn

Failed to open RFC connection

TRACE      2043-08-22 21:57:21.203 [iaxxrfcimp.cpp:436]

           CAbRfcImpl::openRfcConn

connection closed without message (CM_NO_DATA_RECEIVED)

TRACE      2043-08-22 21:57:21.203 [iaxxgenimp.cpp:752]

            CGuiEngineImp::showMessageBox

<html> <head> </head> <body> Test logon to SAP System LTB failed. <p> SOLUTION: Make sure that the system is started, that the user DDIC exists and that the password of user DDIC is correct. </p> </body></html>

TRACE      2043-08-22 21:57:21.203 [iaxxgenimp.cpp:1255]

           CGuiEngineImp::acceptAnswerForBlockingRequest

Waiting for an answer from GUI

  Hi Experts.

I would like to install Sap Content Server 6.40 on Windows Server 2003.

In "Installation Guide - SAP Content Server for Windows" is written: "Insert the SAP Installation Master DVD" but it is impossible to find it on SAP marketplace any more.

Could you tell me what I have to download form marketplace to install Content Server or give some current tutorial.

Regards,

Michal

Hello,

I would like to known some other information about "Certificate Expiration Notification " http://help.sap.com/saphelp_nw70ehp1/helpdata/en/d4/5b1140d72dc442e10000000a1550b0/content.htm

Do you known how can I activate this in CCMS. Under DISP ->Services a have not "Certificate Expiration Notification " in RY20 ...:-(

Thanks a lot.

Best regards

Capek Martin

We are SAP Customers ? But how do i get SMP Login ?

Rgds

PR

Hi,

I am new to SAP. I was trying to download the trial version for SAP Netweaver and ABAP. It asks for SMP login. What is it and how to get the same?

Please guide me how to download the trial version.

Thanks,

Shilpa

I am using SAP webdispatcher 7.20. This hosts 3 systems. 1 portal and 2 abap.  When accessing portal I am getting the mask of webdispatcher host so my backend is hidden. But when I use that for SRM systems, the dispatcher takes me to the real host name. How to aviod that?

so when I say disphost.domain.com  it takes me to portal which is sapxyzjava.domain.com  but still shows hosts in IE as disphost.domain.com   but for abap which I am using forward as /srm it shows me  realhost:realport/sap/bc/bsp/sap/srmsus/default.htm  but in reality it should show   disphost.domain.com/srm always.   What is that I am missing in this config?

My webdisp params

icm/server_port_0 = PROT=HTTP,PORT=80, EXTBIND=1

icm/server_port_1 = PROT=HTTPS,PORT=443, EXTBIND=1

exe/icmbnd = /sapmnt/WD1/exe/uc/linuxx86_64/icmbnd.new

icm/server_port_2 = PROT=HTTP,PORT=8000

icm/server_port_3 = PROT=HTTPS,PORT=8050

icm/server_port_4 = PROT=HTTP,PORT=8888

wdisp/system_0 = SID=xyz, MSHOST=sapxyzjava.domain.com, MSPORT=8112, SRCURL=/irj/;/webdynpro/;/bd/;/logon/, SRCSRV=*:80,
wdisp/system_1 = SID=xyz, MSHOST=sapxyzjava.domain.com, MSPORT=8112, SRCURL=/irj/;/webdynpro/;/bd/;/logon/, SRCSRV=*:443

wdisp/system_2 = SID=SRQ, MSHOST=sapabcabap.domain.com, MSPORT=8103,  SRCURL=/sap/;/logon/, SRCSRV=*:8000

icm/HTTP/redirect_0 = PREFIX=/,TO=/irj/portal,HOST=disphost.domain.com
icm/HTTP/redirect_1 = PREFIX=/srm, TO=/sap/bc/bsp/sap/srmsus/default.htm,HOST=disphost.domain.com:8000
icm/HTTP/redirect_2 = PREFIX=/bd , TO=/bd/public/frameset_top_html.jsp, HOST=disphost.domain.com

Regards,

Kedar

Dear experts,

I wonder if anybody is facing similar issues. I want to implement LSSM (Loadable SAP Support Monitors) into DBACOCKPIT.

As per SAP notes 1314689 and 1299493 this is possible per Excel which does not work for me since I have Excel 2010 and the macros in the excel sheet do not work in Excel 2010 but just in Excel 2007.

So I tried the other way which is described in 1299493 and add an entry to table ORA_FEAT_USED

REMSYS     <Database-ID>

FEATURE    LSSM

IS USED    X

I also tried to left REMSYS blank hoping that system will notice that I was meaning the local database but still no help. I still cant see the Loadable SAP Support Monitors in DBACOCKPIT.

Any ideas?

P.S: We are on SAP_BASIS 701 SP07, so this should not be the problem.

Hi,

In our landscape we are facing an issues related with hostname. in SM51 transaction where we see the list of application servers,there is entry "localhost" instead of it's value which we see in hosts file (/etc/hosts).I want to add one important thing that SAP is on  virtual machines.From the OS level we can see the hostname and it's showing us the correct name.

Any clue would be appreciated.

Thanks,

Rakesh

Hello,

I was wondering if somebody could clarify the Term u201CHigh Availabilityu201D (HA) in an SAP Context.

I installed a PI 7.11 (SID=ABC) system as part of an HA Cluster Failover.

The u201CABCu201D system is running on Server Host u201C123u201D. 

I have another Server Host, u201C456u201D, that is part of the HA Cluster Failover.  This server has two other SAP Instances u201CDEFu201D and u201CGHIu201D installed on it.

When u201CABCu201D needs to failover, due to Hardware failure, etc, the two Instances u201CDEFu201D & u201CGHIu201D are shut down by the HA Cluster Software on host u201C456u201D, and then u201CABCu201D fails over to server u201C456u201D, and runs on it until the original host, u201C123u201D is available again for u201CABCu201D to run on.

I was reading OSS Note 1052984, u201CProcess Integration 7.1- High Availabilityu201D, and in this noteu2019s context it seems like HA is referring to an Instance where the

ASCS u2013 (ABAP System Central Services)

SCS u2013 (JAVA System Central Services)

DVEBMGS u2013 (Primary Application)

DB u2013 (Database Instance)

Are all installed on separate servers, and not necessarily on an u201CHAu201D cluster, where one SAP instance resides on one server and can failover to another node B server, when the need arises.

Any insight in to what context Note1052984 is referring to would be very helpful.

Thank you.

Regards.

In a recent support case with SAP, I was asked to replace the ACF up/down applet in the MIME Repository. Normally one would apply a SAP note containing the MIME object. In this case I had to locate the JAR file in the MIME Repository and replace it with "Upload and Replace", which I did. After finding out that the new version didn't fix the reported problem, I tried to restore the previous version which I had downloaded and stored on my local drive. After not getting any confirmation in the MIME Repository Explorer and the fact that the previous version was not restored (more on that later), I tried to delete the JAR file from the MIME Repository. THAT IS A BIG NO, NEVER. All MIME objects are identified by a unique ID called LOIO or the complete path. Since I deleted the JAR file from MIME Repository the LOIO was gone and I wasn't able to import the SAP note containing the latest (the previous) version of the JAR file, attempting to do so returned an internal error in INT_SMIM_ADD.

Before I go into the details on how to restore the LOIO, an explanation is required why I thought the previous JAR file didn't get restored. It turns out it is not sufficient to empty the ICM cache and the browser cache; one has to also empty the Java cache with the Control Panel applet. You can also play with the Expiration Time settings for the MIME object but at least my tests indicate that playing with them won't cause the Java cache to be invalidated.

I used the program WDG_MAINTAIN_UR_MIMES as reference and implemented only the parts required to recreate the MIME object with the correct LOIO. The form UPLOAD_FILE can be just about anything, as long as it provides the JAR file content. I used the one in report WDG_MAINTAIN_UR_MIMES.

report  zrecreate_mime_object.

constants c_zip_file_filter type string value '*.jar'. "#EC NOTEXT

data mr                       type ref to if_mr_api.
data zip                       type xstring.
data zip_file_name     type string.
data zip_path              type string.
data c_mime_zip_loio type skwf_io.
data zip_local_path     type string.

mr = cl_mime_repository_api=>get_api( ).

c_mime_zip_loio-objtype = 'L'.
c_mime_zip_loio-class   = 'M_APP_L'.
c_mime_zip_loio-objid   = '80000E2515CB1DDCA8C7953F5D7A0BC0'.

zip_file_name = 'com_sap_acf_updown.jar'.
zip_path = '/SAP/BC/WebDynpro/SAP/PUBLIC/BC/SSR/uuielibs/active_component/com_sap_acf_updown.jar'.

clear zip.
perform upload_file using zip_file_name changing zip.
check zip is not initial.

mr->put(  exporting    i_url                     = zip_path    i_content                 = zip    i_language                = 'D'    i_new_loio                = c_mime_zip_loio    i_dev_package             = 'SWDP_UIEL_ACTIVE_COMPONENT'  exceptions    others                    = 1 ).

if sy-subrc <> 0.  message id sy-msgid type sy-msgty number sy-msgno             with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.

The most important parts in the program are the LOIO, filename, path and development package. By changing those parts of the program and uploading a different file, you could recreate any MIME object in the MIME Repository.

A useful program for troubleshooting MIME objects is MR_CHECK_MIMES.

Upgrading a kernel was an easy move. But the growing complexity of SAP-systems, makes an
upgrade of the kernel more difficult than it was in the past.

I was motivated to change the kernel by the PAM on the SAP service marketplace. I checked the "lifetime" of the kernel by:

http://service.sap.com/pam

  PAM-page

searching my sap product

Hmm bad news A System without supported kernel? No way !

I needed a new kernel and the newest was 7.21 EXT I looked at the PAM and found:

In order to be able to do the kernel upgrade in a proper way, I searched for the necessary
notes. I found 3 essential notes for the kernel upgrade.

Note 1716826 - Usage of the downward compatible kernel 721 (EXT)

Note 1728283 - SAP Kernel 721: General Information

Note 1713986 - Installation of kernel 721 (EXT)

Now I had all the information I needed. The next task was to download the new kernel.

http://service.sap.com/patches -> Support Packages and Patches -> A - Z Index -> ....

And now a little happy question time:

Question: When I search the kernel for a SAP PI 7.1 EHP 1 system, where do I have to search?

1. S for SAP?

2. P for PI?

3. Z for Zorro?

Answer: No,  it's N for Netweaver -> 1 hour lost for the answer of this question

http://service.sap.com/patches -> Support Packages and Patches -> A - Z Index -> SAP NETWEAVER PI 7.1X -> SAP EHP1 FOR SAP NW PI 7.1 -> Entry by Component -> Application Server ABAP

I downloaded the following archives:

SAPCAR_315-20010445.EXE                 SAPCAR
DBATL720O10_31-20006704.SAR             DBATOOLS Package for Oracle 10g and 11g
SAPEXE_100-10011322.SAR                 Kernel Part I (database independent)
SAPEXEDB_100-10011323.SAR               Kernel Part II (database specific)
igsexe_5-20007786.sar                   Internet Graphic Server (IGS)
igshelper_3-10010245.sar                IGS Helper
sapwebdisp_421-20008606.sar             SAP Webdispatcher
SAPCRYPTOLIB_34-10010842.SAR            SAP Kryptolib
SAPHOSTAGENT147_147-20005726.SAR        SAPhostagent 7.20

After analyzing the 3 notes, I identified the next tasks:

1. ) check Note 1610716 - Correcting runtime objects with incorrect alignment
2.) update SAPJVM 5.1.047 to 5.1.084
3.) implement the latest SBP (SAP bundle patch)
4.) Upgrade the kernel

ok 4 tasks to do. Let's do it:

Task 1: check Note 1610716 - Correcting runtime objects with incorrect alignment

I had to implement Note 1610716 with the transaction SNOTE and I got the report RUT_NOTE_1610716. I started the report first with option check and after that with option repair. It ran several minutes. Task was done.

Task 2:  update SAPJVM 5.1.047 to 5.1.084

Ok, now I need to search all relevant notes for patching a SAPJVM. I found:

1683392 - SAP JVM 5.1 Patch-Collection 58 (Build 5.1.074)
1434916 - How to find out the SAP JVM build version
1367498 - Installationsvoraussetzungen für SAP JVM
1025085 - How to manually patch the SAPJVM
1133020 - Importieren eines SAP-JVM-Patchs in Application Server Java

With note 1434916 I was able to identify the SAPJVM-Version. I was not able to identify the version of sapjvm on the system information page:( In my opinion the system information page of NW 7.0 is much better than on NW 7.1! The system information page of NW 7.0 is more simple, but the information is well-arranged.

Note 1025085 states:
"Patching the SAP JVM on an SAP NetWeaver system is only supported using the Software Update Manager (SUM) or the Java Support Package Manager (JSPM)."
I chose the JSPM.

After patching sapjvm I started the system and... it started without any error and... no java page could be displayed

I posted my problem and a guru (big thanx to Reagan Benjamin) found the solution see:
http://scn.sap.com/thread/3388835 (No http page available after upgrade of SAPJVM)
After implementing Note 1625051 - "Wily Introscope agent: IllegalAccessError" the system runs fine again

ok next step:

Task 3) implement the latest SBP (SAP bundle patch)

Where can I find the SBP?
http://service.sap.com/patches -> Database and Database Patches (from other vendors) -> Oracle -> Oracle Patches 11.2.0.2.0

a) Checks
orasid> cd /oracle/SID/11203; bdf .
orasid> cd /oracle/stage/11203/database/SAP; bdf .
both filesystems should be 1GB free

b) Patche Opatch and MOPatch
orasid> setenv IHRDBMS /oracle/SID/11203; setenv OHRDBMS /oracle/SID/112_64; setenv ORACLE_HOME /oracle/SID/11203
orasid> cd /oracle/stage/11203/database/SAP
orasid> cp -p /inst_cd_sap/IA64/Oracle110203/updates/SAP_112035_201303/SAP_112035_201303_HPUXIA64.zip .
orasid> /inst_cd_sap/IA64/SOLMAN_71/unzip -qd $IHRDBMS/sapbundle SAP_112035_201303_HPUXIA64.zip 'SBP_112035_201303/OPatch/*'
orasid> mv $IHRDBMS/OPatch $IHRDBMS/OPatch-pre-SBP_112035_201303
orasid> mv $IHRDBMS/sapbundle/SBP_112035_201303/OPatch $IHRDBMS/OPatch
orasid> unzip -qd $IHRDBMS/sapbundle SAP_112035_201303_HPUXIA64.zip 'SBP_112035_201303/MOPatch/*'
orasid> test -d $IHRDBMS/MOPatch && mv $IHRDBMS/MOPatch $IHRDBMS/MOPatch-pre-SBP_112035_201303
orasid> mv $IHRDBMS/sapbundle/SBP_112035_201303/MOPatch $IHRDBMS/MOPatch

orasid> $ORACLE_HOME/OPatch/opatch version

  orasid> $ORACLE_HOME/MOPatch/mopatch.sh -h

The following versinos should be displayed:
OPatch version 11.2.0.3.1
MOPatch version 2.1.13

c) stop the system
sidadm> stopsap
orasid> lsnrctl stop
orasid> ps -efax | grep ora
no ora process should run!

d) install SBP

orasid> setenv ORACLE_HOME /oracle/SID/11203
orasid> cd /oracle/stage/11203/database/SAP
orasid> /bin/sh $ORACLE_HOME/MOPatch/mopatch.sh -v -s SAP_112035_201303_HPUXIA64.zip

orasid> lsnrctl start

<open a new session>
oraSID> sqlplus "/as sysdba"
SQL> startup

<old session>
oraSID> cd $OHRDBMS/rdbms/admin
oraSID> env ORACLE_HOME=$OHRDBMS $OHRDBMS/bin/sqlplus "/as sysdba"

SQL> @?/sapbundle/SBP_112035_201303/catsbp.sql

Hmmmm, INCOMPLETE. This is a word sap administrators don't like! After reading Note 1509324 I did as it was recommended in the note.

SQL> select action_time from registry$history group by action_time having count(*) > 1;

If rows appear then read OSS-Note: 1508602.

no rows, great.

SQL> @?/rdbms/admin/utlrp.sql;

SQL> shutdown

SQL> startup

SQL> @?/sapbundle/SBP_112035_201303/catsbp.sql

No errors and two COMPLETEs. That was good.

I had to set two parameters ->

SQL> ALTER SYSTEM SET "_FIX_CONTROL"=
     '5099019:ON','5705630:ON','6055658:OFF','6399597:ON','6430500:ON',
     '6440977:ON','6626018:ON','6972291:ON','7168184:OFF','8937971:ON',
     '9196440:ON','9495669:ON','13077335:ON','13627489:ON','14255600:OFF',
     '14595273:ON' COMMENT='SAP_112035_201302 RECOMMENDED SETTINGS' SCOPE=SPFILE;

SQL> ALTER SYSTEM SET EVENT=
     '10027',
     '10028',
     '10142',
     '10183',
     '10191',
     '10995 level 2',
     '31991',
     '38068 level 100',
     '38085',
     '38087',
     '44951 level 1024'
     COMMENT='SAP_112035_201302 RECOMMENDED SETTINGS' SCOPE=SPFILE;

SQL> shutdown immediate
SQL> startup
SQL> shutdown immediate
SBP is installed, Task done!

Task 4: Upgrade the kernel

This is not as easy as it was in the good old days! Now you have to do some more steps. In the good old  days (when SAP ERP was R/3) you patched the system between 12:00 and 12:30 when users were at lunch! (Is it lunch or dinner? Hmm I don't know. Please excuse my bad English!) But today you have to do it on weekend.

So let's start.

Step 1: saphostagent upgrade

root> cd /tmp

root> mkdir saphostagent; cd saphostagent

root> /sapmnt/SID/SAPCAR -xvf /inst_cd_sap/IA64/kernel/PI_721_EXT_100/SAPHOSTAGENT147_147-20005726.SAR

root> ./saphostexec -upgrade

Step 2: stop the system

Stopping the saphostagent:
root> /usr/sap/hostctrl/exe/saphostexec -stop
root> /usr/sap/hostctrl/exe/saposcol -k

Stopping the sapwebdisp:

<user of sapwebdisp> stopsap all W90

Stopping sapstartsrv:

sidadm> sapcontrol -nr <Systemnummer Instanz z.B. 00> -prot NI_HTTP -function StopService;

sidadm> sapcontrol -nr <Systemnummer ASCS> -prot NI_HTTP -function StopService;

sidadm> sapcontrol -nr <Systemnummer SCS> -prot NI_HTTP -function StopService;

sidadm> sapcontrol -nr <Systemnummer ERS> -prot NI_HTTP -function StopService;

Deregister and stop CCMS-Agenten:

sidadm> cd /usr/sap/SID/SYS/exe/run/
sidadm> ./sapccm4x -u pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS<Sy.Nr.>_<host>
sidadm> ./ccmsping -u pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS<Sy.Nr.>_<host> -push -n<Sy.Nr>

stop Diagnosticagent
<D-Agentuser> stopsap SMDA90

Step 3: Clear shared memory

sidadm> /usr/sap/SID/SYS/exe/run/showipc all
Shows all shared memorys of all systems.

sidadm> /usr/sap/SID/SYS/exe/run/cleanipc <SystemNrIPC> remove
Now check for open shared memory segments. There should be no segment
sidadm> /usr/sap/SID/SYS/exe/run/showipc all

Step 4: get SAPCAR

sidadm> mkdir /tmp/sapcar
sidadm> cd /tmp/sapcar
sidadm> SAPCAR -xfv /<directory of sar-files>/SAPEXE_100-10011322.SAR
sidadm> cp SAPCAR /sapmnt/SID/

Step 5: removing the old kernel

root> cd /usr/sap/SID/SYS/exe/run/
root> rm -rf *

Step 6: implement the new kernel

sidadm> cd /usr/sap/SID/SYS/exe/run/
sidadm> /sapmnt/SID/SAPCAR -xfv /<directory of sar-files>/SAPEXE_100-10011322.SAR
sidadm> /sapmnt/SID/SAPCAR -xfv /<directory of sar-files>/SAPEXEDB_100-10011323.SAR
sidadm> /sapmnt/SID/SAPCAR -xfv /<directory of sar-files>/DBATL720O10_31-20006704.SAR
sidadm> /sapmnt/SID/SAPCAR -xfv /<directory of sar-files>/igsexe_5-20007786.sar

Step 7: implement sapcryprtolib

sidadm> mkdir /tmp/sapcrypto
sidadm> cd /tmp/sapcrypto
sidadm> /sapmnt/SID/SAPCAR -xfv /<directory of sar-files>/SAPCRYPTOLIB_34-10010842.SAR
sidadm> cp -p hpia64-11.31-64/* /usr/sap/SID/SYS/exe/run/
sidadm> cp -p hpia64-11.31-64/ticket /usr/sap/SID/DVEBMGS<Sy.Nr>/sec

Step 8: start saproot

root> cd /usr/sap/SID/SYS/exe/run/
root> ./saproot.sh SID

Step 9: install igshelper

sidadm> cd /usr/sap/SID/DVEBMGS<Sy.Nr.>; mv igs igs_old;
sidadm> /sapmnt/SID/SAPCAR -xfv /<directory of sar-files>/igshelper_3-10010245.sar

Step 10: new kernel for sapwebdisp

<user of sapwebdisp> cd /usr/sap/SWP_SID/SYS/exe/run
<user of sapwebdisp> rm -rf *
<user of sapwebdisp> /sapmnt/SID/SAPCAR -xfv /<directory of sar-files>/sapwebdisp_421-20008606.sar

Step 11: delete the exe-directories of all instances

root> cd /usr/sap/SID/DVEBMGS<Sy.Nr. of instance>/exe
root> rm -rf *

root> cd /usr/sap/SID/ASCS<Sy.Nr. of ASCS>/exe
root> rm -rf *

root> cd /usr/sap/SID/SCS<Sy.Nr. of SCS/exe
root> rm -rf *

root> cd /usr/sap/SID/ERS<Sy.Nr.of ERS>/exe
root> rm -rf *

Step 12: execute SAPCPE

It is recommended by sap to start sapcpe for every instance. Be aware to use the scs.lst file for the central services and the ERS!

For the central instance:

sidadm> cd /usr/sap/SID/DVEBMGS<Sy.Nr. instance>/work
sidadm> sapcpe pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS<Sy.Nr. instance>_<host>

For the central services:

sidadm> cd /usr/sap/SID/SCS<Sy.Nr. SCS>/work
sidadm> sapcpe pf=/usr/sap/SID/SYS/profile/SID_SCS<Sy.Nr. SCS>_<host> list:/usr/sap/SID/SYS/exe/run/scs.lst

sidadm> cd /usr/sap/SID/ASCS<Sy.Nr. ASCS>/work
sidadm> sapcpe pf=/usr/sap/SID/SYS/profile/SID_ASCS<Sy.Nr. ASCS>_<host> list:/usr/sap/SID/SYS/exe/run/scs.lst

And for the Enhanced Replication Services (I only show it for one ERS because I'm too lazy;))

sidadm> cd /usr/sap/SID/ERS<Sy.Nr. ERS>/work
sidadm> sapcpe pf=/usr/sap/SID/SYS/profile/SID_ERS<Sy.Nr. ERS>_<host> list:/usr/sap/SID/SYS/exe/run/scs.lst

Last but not least the jvm needs it's binaries too:

sidadm> sapcpe /usr/sap/SID/SYS/profile/SID_DVEBMGS<Sy.Nr. instance>_<host> source:/sapmnt/SID/exe/jvm/hpia64/sapjvm_5.1.084 list:/sapmnt/SID/exe/jvm/hpia64/sapjvm_5.1.084/sapjvm_5.lst

Step 12:  post activities

Enter line 
rslg/new_layout = 9
in file /usr/sap/SIS/SYS/profile/DEFAULT.PFL
Then you have to delete the files of the syslog.

Final Step (13):  startsap

Puhhh 13 steps…I entered

sidam> startsap

Sometimes startsap is a layer, so verified it:

sidadm> ps -efax | grep sap

ok. ABAP was running, but J2EE is a diva. I took a look at the dev_server0 and…

Thanx god java (the beast) is up and running

That was my adventure kernel patching a PI system. Finally I leaved the office and tried to relax at the rest of Sunday

Best regards

Willi Eimler

Hi everybody,

we 're planning to upgrade our ERP systems from version ERP 6.0 Ehp4 to ERP 6.0 Ehp6. Our landscape consists of 3 systems (DEV - QAS - PRD) and all the installations are distributed. The operating system of all 6 systems (3 application servers + 3 database servers) is RED HAT Linux Enterprise 5.5 and Oracle Database version is 11.2.0.3.

In order to upgrade to ERP 6.0 Ehp6 on Netweaver 7.0 Ehp3 we have to use SAP Kernel 720/721EXT that is not supported on RED HAT Linux 5.5. So we have to upgrade our Systems to RHEL 6. The question is if we can keep our Database systems on RHEL 5.5 without upgrade their O.S to RHEL 6 and upgrade only the operating system of SAP Application Servers.

Thank you in advance

Hi Folks,

we are planning to install an ECC 6.0 EHP7. CI and database on the same box (RHEL). 

we are going to configure a virtual hostname for the ci and the database (sapinst SAPINST_USE_HOSTNAME...).

Configuration:

CNAME:

ci=sap-sid

db=sap-sid-db

A-Record

hostname=servera 

in DNS we created a cname record for sap-sid and sap-sid-db, they are linked to servera, not the ip.

during dedicated installation (2nd part the database part) we got the error that the record sap-sid-db resolves to sap-sid, because we have just one ip adress for servera, which ends in a error message during installation.

in such a configuration, is it necessary to configure two ip adresses for the host "servera"? one ip for ci and one for database?

thanks in advanced.

regards

Hi

We have planned to homogenous copy of our APO 3.1. So we have installed windows 2003 32 bit server. and installed software and central instance. and successfully restored the database also.

now when we try to connect to the database it hangs

when we tried in command prompt it could login as

sqlplus "/as sysdba" bu it does not able to login as

sqlplus /@APP or sqlplus sapr3/sap@APP these two methods of connecting it fails. if we start the sap in mmc ity hangs and the dev_w0 details as follows

-

trc file: "dev_w0", trc level: 1, release: "46D"

-

*

• ACTIVE TRACE LEVEL           1

• ACTIVE TRACE COMPONENTS      all, M

*

B 

B Tue Oct 21 14:59:14 2008

B  create_con (con_name=R/3)

B  Loading DB library 'F:\usr\sap\APP\SYS\exe\run\dboraslib.dll' ...

B  Library 'F:\usr\sap\APP\SYS\exe\run\dboraslib.dll' loaded

B  Version of library 'F:\usr\sap\APP\SYS\exe\run\dboraslib.dll' is "46D.00", patchlevel (0.2311)

B  New connection 0 created

M  relno      4640

M  patchlevel 0

M  patchno    2415

M  intno      0

M  pid        3820

M 

M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3820) [dpxxdisp.c   976]

I  MtxInit: -2 0 0

I  *** ERROR => New Process with the same PID

               [semnt.c      1513]

I  *** ERROR => New Process with the same PID

               [semnt.c      1513]

X  EmInit: MmSetImplementation( 2 ).

X  <ES> client 0 initializing ....

X  Using implementation std

M  <ES> Memory Reset enabled

X  ES initialized.

M  ThSysUsrCheck: clear T0

M  calling db_connect ...

C  Got NLS_LANG=AMERICAN_AMERICA.WE8DEC from environment

C  Logon as OPS$-user to get SAPR3's password

C  Connecting as /@APP on connection 0 ... (dbsl BIN 150808)

then it hangs . p

please check whether is there nay things to be checked.

regards

bala

When I try to apply DMIS addon using SAINT, I got the following error.

Error in phase: IMPORT_PROPER

Reason for error: TP_CANNOT_CONNECT_SYSTEM

Return code: 0232

Error message: connect failed

Please suggest how can we resolve this error?