Forum Stats

  • 3,781,244 Users
  • 2,254,495 Discussions


Out of memory error in silent installation of ODAC x64

VDA Member Posts: 2
edited Sep 17, 2020 9:20AM in ODBC

Hi everyone,

I was wondering whether someone can shed a bit more light on the issue we are experiencing. Recently we switched from a x86 ODAC to x64 (version, and we are seeing somewhat random installation failures when the software is being deployed via SCCM/MECM. Namely, the hs_err_pidXXXX file states that an "Out of memory" error has occurred (I submitted a shortened version of the log because I did not find a way to attach a file):


# There is insufficient memory for the Java Runtime Environment to continue.

# Native memory allocation (malloc) failed to allocate 32744 bytes for ChunkPool::allocate

# Possible reasons:

#   The system is out of physical RAM or swap space

#   In 32 bit mode, the process size limit was hit

# Possible solutions:

#   Reduce memory load on the system

#   Increase physical memory or swap space

#   Check if swap backing store is full

#   Use 64 bit Java on a 64 bit OS

#   Decrease Java heap size (-Xmx/-Xms)

#   Decrease number of Java threads

#   Decrease Java thread stack sizes (-Xss)

#   Set larger code cache with -XX:ReservedCodeCacheSize=

# This output file may be truncated or incomplete.


#  Out of Memory Error (allocation.cpp:273), pid=6736, tid=7312


# JRE version: Java(TM) SE Runtime Environment (8.0_91-b61) (build 1.8.0_91-b61)

# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b61 mixed mode windows-amd64 compressed oops)

# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows


The interesting part is that this happens randomly when the installation is run under the system account (as is default with SCCM/MECM). Whenever I trigger the installation manually with the same command line with an admin account, the installation finishes without any issue whatsoever. We are using the same command line parameters as we did with the x86 version, where we had no issues of this kind. I tried changing the -xmx parameter in oraparam.ini to lower and higher settings, but this does not seem to do the trick. Is there any way of troubleshooting this further, or a way to resolve it?





  • VDA
    VDA Member Posts: 2
    edited Sep 17, 2020 9:20AM

    To anyone who may have stumbled upon this: if you are using SCCM/MECM, tick the "Run installation and uninstall program as 32-bit process on 64-bit clients" in the deployment type. Note that if you are using some registry tweaks, this might need to be changed as well, because of the Wow6432 node redirection.