SUM startup.bat - SAPJVM EXCEPTION_INT_DIVIDE_BY_ZERO

[Former Member]

Hello.

I am running into the following error message while running startup.bat in SUM directory (1.0 SP5 patch7).

Has anyone got any idea what this is about ?

I just recently executed the same procedure on another similar system (host) and did not have any problems there.

The system is a NW7.0 ABAP system running on Oracle 10g, Windows 2k3 SP2 x64, VMware vSphere.

# A fatal error has been detected by SAP Java Virtual Machine:

#

#  EXCEPTION_INT_DIVIDE_BY_ZERO (0xc0000094) at pc=0x000000006de3bc3c, pid=188, tid=2636

#

# JRE version: 6.0_31

# Java VM: SAP Java Server VM (6.1.038 1.6-b04 Feb 14 2012 11:04:31 - 61_REL - optU - windows amd64 - 6 - bas2:166762 (mixed mode) compressed oops)

# Problematic frame:

# V  [jvm.dll+0x7cbc3c]  SAPJVM_oswrp_creat+0x11858c (sp=0x0000000001f8f510) (pc=0x000000006de3bc3c)

#

# If you would like to submit a bug report, please visit:

#   http://service.sap.com/message

#

Date: 2012-10-19 Time: 01:06:31

---------------  B u i l d   I n f o ---------------

compile date/time:     Feb 14 2012 10:46:34

sapjvm release:        6

sap_platform:          NTAMD64

platform:              windows

arch:                  amd64

codeline:              61_REL

hs bld trgt:           "product"

flags:                 !DEBUG, !ASSERT, PRODUCT

build user:            "makefact"

last change:           166762

build id:              6.1.038

_WIN32

_WIN64

_M_AMD64

Compiler (_MSC_VER): 1400

C-Runtime: multithreaded dynamic release

BR Gerhard Andreassen.

hs_err_pid188.txt.zip

[tomas_black · Accepted solution]

Hello Gerhard,

this is not a problem of SUM, it is an error of SAP Java VM. Please update it to the very last patch level for your Windows, this should resolve the problem. Please refer to note #1442124 for this.

Best regards,

Tomas Black

[Former Member · Accepted solution]

Hello.

I downloaded the latest sapjvm_6 patch from SMP and tested it, same error.

Further testing revealed that it was actually a problem on a specific VMware-host, possibly cpu-mismatch or invalid configuration, i don't know. I managed to reproduce the error on several guests on that same host.

Problem solved by migrating guest-os to another VMware host.

BR Gerhard Andreassen.