OPatch fails with 'Java could not be located' & 'Could not reserve enough space for object heap'

(Doc ID 2408523.1)

Last updated on JUNE 12, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 to 12.2.0.1 [Release 11.2 to 12.2]
Information in this document applies to any platform.

Symptoms

'opatch lsinventory' fails with error:

$ opatch lsinventory
Java could not be located. OPatch cannot proceed!
OPatch returns with error code = 1

But it gives results when database is shut down.

 

$ORACLE_HOME/OPatch/jdk/bin/java -version
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms