Issue fixed in version 5.1.7. The latest version of Shareplex for Oracle can be downloaded at: https://support.quest.com/shareplex/download-new-releases
Each component within SharePlex has its own unique object ID, and cop is no exception. The object ID is created as an environment variable, using the standard library function putenv (envstr), which receives the environment variable assignment as a string parameter. The only requirement the putenv imposes on callers is that the argument supplied to it may not be local to the calling function-i.e., envstr cannot be a variable which goes out of scope when the function that calls putenv ( ) returns.
The problem which shareplex faced had to do with the fact that cop was attempting to establish its own SP_OBJECTID by passing a reference to a local variable to putenv ( ); the environmental setting therefore didn't take effect, exception to which fact was taken by subsequent logic which required it to have been set.
The one-off redresses this problem by declaring envstr to be a static variable (stored in the un-initialized data segment instead of the stack), lending it the kind of permanency that is required in order for it to feature as an argument to putenv ( ).