EM 13.5 Agent Installation Failed On Oracle Solaris SPARC (64-bit) With ERROR: Installer execution failed (1).
(Doc ID 2776163.1)
Last updated on JANUARY 18, 2023
Applies to:
Enterprise Manager Base Platform - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 13.5.0.0.0 version,
Deploying agent from Console Failed with Exit Code 1
Silent Installation failed with below errors.
<LOCATION OF AGENT SOFTWARE>/agentDeploy.sh -ignorePrereqs AGENT_BASE_DIR=/<AGENT_BASE> ORACLE_HOSTNAME=<AGENT HOSTNAME> AGENT_INSTANCE_HOME=/<AGENT_BASE>/agent_inst OMS_HOST=<OMS HOSTNAME> EM_UPLOAD_PORT=<UPLOAD PORT> AGENT_PORT=3872 AGENT_REGISTRATION_PASSWORD=<REGISTRATION_PASSWORD>
# /var/tmp/OraInstall2021-05-10_02-15-15PM/hs_err_pid11399.log
The log(s) can be found here: /var/tmp/OraInstall2021-05-10_02-15-15PM.
ERROR: Installer execution failed (1).
Agent installation failed.
Copying Install logs to /<AGENT_BASE>/agent_13.5.0.0.0/cfgtoollogs/agentDeploy .....
cat: cannot open /<AGENT_BASE>/agent_13.5.0.0.0/oraInst.loc: No such file or directory
/logs: No such file or directory
Check logs at /AGENT_BASE/agent_13.5.0.0.0/cfgtoollogs/agentDeploy .....
hs_err_pid11399.log has below errors.
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 771227648 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# JVM is running with Zero Based Compressed Oops mode in which the Java heap is
# placed in the first 32GB address space. The Java Heap base address is the
# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_solaris.cpp:2563), pid=21196, tid=0x000000000000000d
#
# JRE version: Java(TM) SE Runtime Environment (8.0_261-b12) (build 1.8.0_261-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.261-b12 mixed mode solaris-sparc compressed oops)
# Core dump written. Default location: /var/tmp/OraInstall2021-05-12_10-48-10AM/core or core.21196
#
--------------- T H R E A D ---------------
Current thread (0x00000001002cd800): VMThread [stack: 0xffffffff5ab00000,0xffffffff5ac00000] [id=13]
Stack: [0xffffffff5ab00000,0xffffffff5ac00000], sp=0xffffffff5abfe5b0, free space=1017k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0xccb12c] void VMError::report_and_die()+0x744
V [libjvm.so+0x4e0de4] void report_vm_out_of_memory(const char*,int,unsigned long,VMErrorType,const char*)+0x64
V [libjvm.so+0xa9ff28] bool os::pd_commit_memory(char*,unsigned long,unsigned long,bool)+0x110
V [libjvm.so+0xa94574] bool os::commit_memory(char*,unsigned long,unsigned long,bool)+0x2c
V [libjvm.so+0xb2c038] bool PSVirtualSpace::expand_by(unsigned long)+0x50
V [libjvm.so+0xb2d668] bool PSYoungGen::resize_generation(unsigned long,unsigned long)+0x74
V [libjvm.so+0xb2d5d0] void PSYoungGen::resize(unsigned long,unsigned long)+0x1c
V [libjvm.so+0xb27c00] bool PSScavenge::invoke_no_policy()+0x12c0
V [libjvm.so+0xb2675c] bool PSScavenge::invoke()+0x4c
V [libjvm.so+0xac77c8] HeapWord*ParallelScavengeHeap::failed_mem_allocate(unsigned long)+0x78
V [libjvm.so+0xccdb38] void VM_ParallelGCFailedAllocation::doit()+0xa0
V [libjvm.so+0xcd51cc] void VM_Operation::evaluate()+0x54
V [libjvm.so+0xcd31e4] void VMThread::evaluate_operation(VM_Operation*)+0x11c
V [libjvm.so+0xcd3860] void VMThread::loop()+0x430
V [libjvm.so+0xcd2d94] void VMThread::run()+0xa4
V [libjvm.so+0xa9ac00] java_start+0x380
VM_Operation (0xffffffff1e4feee0): ParallelGCFailedAllocation, mode: safepoint, requested by thread
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |