OPatch fails with 'Java could not be located' & 'Could not reserve enough space for object heap'
(Doc ID 2408523.1)
Last updated on OCTOBER 25, 2019
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
'opatch lsinventory' fails with error:
Java could not be located. OPatch cannot proceed!
OPatch returns with error code = 1
But it gives results when database is shut down.
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
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