Persistence File Could not Be Locked Error Trying to Start OC4J Instances in an AS Installed in an NFS System (Doc ID 736651.1)

Last updated on AUGUST 02, 2017

Applies to:

Oracle Containers for J2EE - Version 10.1.2.0.2 to 10.1.3.4.0 [Release AS10gR2 to AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 17-Set-2014***
***Checked for relevance on 02-March-2016***

Symptoms

When trying to start any OC4J instance, the following error occurs in the $ORACLE_HOME/opmn/logs/<instance_name>_default_group_1 log file  and the instance does not come up.

ERROR
<ORACLE_HOME>/j2ee/<oc4j_instance_name>/persistence/home_default_group_1/jms.state]: persistence file could not be locked. Resolve the sharing violation by ending the process currently holding the file lock or by using a different persistence directory for one or both processes.

Changes

The AS is installed in a shared NFS file system.

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