Return
-
Title
Error: "System call error: Interrupted system call Can't write /odb1/splex/vardir/state/o.amdsple". -
Description
The Reader will run for approximately a minute, then error out and go into a state of 'Idle'.It will then start up approximately 5 minutes later for another minute before erroring out again."System call error: Interrupted system call Can't write /odb1/splex/vardir/state/o.amdsplex-marker [sp_ordr(utl)/30497]Notice: Exiting due to failure updating marker file [sp_ordr/30497]Process exited sp_ordr (for o.amdsplex) [pid = 30497] - exit(1)Process launched: sp_ordr (for o.amdsplex) [pid = 31245]"" -
Cause
SharePlex vardir is on OCFS2 and it is mounted without nointr option.
-
Resolution
Verify that SharePlex vardir mountpoint has datavolume and nointr mount option for OCFS2.Datavolumn, nointr mount options are required by Oracle.See an excerp 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.NOTE: Issue mainly affecting Linux RHAT AS4 RAC with OCFS2.