SAP Knowledge Base Article - Preview

1987286 - "A fatal error has been detected by the SAP Java Virtual Machine" error running Software Provisioning Manager


  • The Software Provisioning Manager crashes with a fatal error.
  • The error message is:

    # A fatal error has been detected by the SAP Java Virtual Machine:
    # SIGSEGV (0xb) at pc=0x000000000000f4d4, pid=20447436, tid=258
    # accessing faulting address: 0x0000000000000000
    # JRE version: 6.0_45-b05
    # Java VM: SAP Java Server VM (6.1.051 23.5-b02 May 30 2013 05:04:21 -61_REL - optU - aix ppc64 - 6 - bas2:197575 (mixed mode) compressedoops)
    # Problematic frame:
    # C 0x000000000000f4d4 (sp=0x000000011081e190) (pc=0x000000000000f4d4)
    # Will write core dump when quitting, defaultlocation: /tmp/sapinst_instdir/NW70/DSS/MoveDB/DB6/OneHost/RemoveJava/core or core.20447436
    # An error report file with more information is saved as:
    # /tmp/sapinst_instdir/NW70/DSS/MoveDB/DB6/OneHost/RemoveJava/hs_err_pid20447436.log
  • The operating system limits are set according to the Guide
  • In the sapinst_dev.log, the operating system limits are reported as below those recommended in the guide



  • AIX
  • Java 1.6


SAP NetWeaver all versions


0x30000000, ulimit, RLIMIT_DATA, INS KBA , KBA , BC-INS-DSS , Dual-Stack Split Tool , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.