Asset ID:	1-72-1019084.1
Update Date:	2011-05-11
Keywords:

---

Solution Type  Problem Resolution Sure

Solution  1019084.1 :   Oracle RAC Listener fail to started when installed on NAS Appliance mount points.  


PreviouslyPublishedAs
234481

Symptoms
With Oracle RAC installed on 5000 NAS Appliance listener may fail to start.
When Oracle RAC is installed on the NFS mount point from NAS Appliance it is possible that Oracle Listener may not start. One of the possible reason is the ownership and permissions set on the CRS home directory path while installing Oracle RAC.

With default Oracle installation the CRS home may have permission and ownership as shown below :

drwxr-xr-x   2 root    oainstall        512 Nov 28 17:09 /oracle/crs/oracle_sw_owner/product/10/app

Where directory /oracle may be a NFS mount point from NAS Appliance.

As per the Oracle Listener architecture, while starting Listener from oracle user, Listener would run "mkdir" on /oracle/crs/oracle_sw_owner/public. However, as per the implementation of "mkdir" with 5000 NAS Appliance the command would fail with return code "EACCESS" (Permission Denied) taking into consideration the default permission and owner ship of the directory path, however for normal working Listener expect a status return of "EEXIST" (File Exists).

To verify if above is the cause :
1. Login as oracle user on the system.
2. Run mkdir on /oracle/crs/oracle_sw_owner/product/10/app
3. If the command fails with "Permission Denied" we are hitting the issue.



Resolution
The solution would be to change the permission on the CRS home.
To overcome the problem, we need to change the permissions on the CRS home so that oracle user would have write permission as shown below :

# chmod -R 775 /mount_point/crs/oracle_sw_owner

The above change would allow the Listener to start normally.


Product
Sun StorageTek 5320 NAS Appliance
Sun StorageTek 5210 NAS Appliance
Sun StorageTek 5310 NAS Appliance
Sun StorageTek 5220 NAS Appliance

Internal Comments
More Information :

Please Check RFE 6665963 for more details.





When compared to mkdir behavior against Solaris UFS, ZFS, and third party NAS Appliance it have been observed that mkdir return "EEXIST" in preference over "EACCESS". However, it have been confirmed by PDE that NFS v3 specification only states which errors are allowed in
response to a request and not the order in which they should be checked.
Both "EACCES" and "EEXIST" are valid return codes (among others) for the
mkdir request.
Oracle RAC, Fail to start, CRS home, NAS Appliance

Attachments

This solution has no attachment