OUD11g - The "hs_err_pidxxxx.log" is Created During Instance Creation, Can it be Ignored?
(Doc ID 2040528.1)
Last updated on JUNE 07, 2023
Applies to:Oracle Unified Directory - Version 18.104.22.168.0 and later
Oracle Solaris on SPARC (64-bit)
Can hs_err_pidxxxx.log be ignored if instance setup is done successfully?
Problem reported environment:
When setup OUD instance with 'oud-setup'(cli or GUI),then hs_err_pid<PID>.log file is created in
'<install directory>/Oracle_OUD1' directory.
Example of the output of 'hs_err_pid<PID>.log':
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 5762973696 bytes for committing reserved memory.
# 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 (os_solaris.cpp:2893), pid=<PID>, tid=<TID>
# JRE version: (7.0_80-b15) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode solaris-sparc compressed oops)
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document