A Shareplex process errors out with "System call error: Exec format error exec failed" or "exec f (4331019)

A Shareplex process errors out as follows:

10/09/08 22:29 Process launched: sp_ocap (for o.SID) [pid = 18746]
10/09/08 22:29 System call error: Exec format error exec failed '/splex_bin/prodir/bin/sp_ocap' - exiting [sp_cop/18746]
10/09/08 22:29 Error: process sp_ocap killed due to SIGSEGV [sp_cop/18745]

There is something wrong with the binary associated with that process.

The problem can occur typically when a one-off binary is downloaded and deployed. It can also occur when Shareplex instances (and therefore its binaries) are moved around.

Some of the common reasons (along with the resolution) are:

A. Wrong ownership/permissions on the binary

Solution: Compare the ownership/permission with another running Shareplex instance and correct anomaly, if any. Then restart Shareplex or the respective process.

B. Binary downloaded in ASCII mode

Solution: Issue cksum command (to find the checksum) on the binary and compare it with the value given in the deployment instructions by Support. If the value does not match, then download the binary in correct mode (typically binary mode).

C. Binary compiled for wrong OS, Oracle or Shareplex platform

Solution: If para A and B do not apply, then there is a likelihood that para C applies. Contact Support to see if this is the case, and if so, let Support provide correct binary.