Error: "System call error: Bad file number Can't write..o.orac-marker " (4220045)

Get the following error in the event log:

Process exited sp_ordr (for o.orac) [pid = 12411] - exit(1)
Notice: Exiting due to failure updating marker file [sp_ordr/12411]
System call error: Bad file number Can't write /u01/app/oracle/product/splex/var2230/state/o.orac-marker [sp_ordr(utl)/12411]

The sp_sys_vardir was mounted on OCFS2 with the no interrupt mount option

NOTE: This resolution only applies to the specific cause listed in this solution.

1) If sp_sys_vardir is on OCFS2, make sure that the mount point is mounted with system no interrupt.

2)make sure the shareplex vardir mountpoint has datavolume and nointr mount option for OCFS2.Datavolumn, nointr mount options are required by Oracle.

3) Bounce SharePlex


ADDITIONAL INFORMATION:

Extract from OCFS2 User Guide:
Oracle database users must mount the volumes containing the Voting Disk file (CRS), Cluster Registry (OCR), Data files, Redo logs, Archive logs and Control files with the datavolume,nointr mount options. The datavolume mount option ensures that the Oracle processes open the files with the o_direct flag. The nointr mount option ensures that the reads and writes on that device are not interrupted by signals.