Immediately after starting sp_cop, sp_ctrl or any of the
SharePlex programs such as qview, sp_add_key etc, the process dies and exits
The SharePlex .app-modules/launcher has been zeroed out
Resolution 1
1. Go to PRODDIR
2. cd .app-modules
3. ls -l launcher*
4. Note the size of the file.
For example, in SharePlex 7.5.2:
-rwxrwxrwx 1 oracle oracle 4147 Apr 3 21:20 launcher
If the launcher has been zeroed out it would have zero bytes, example:
-rwxrwxrwx 1 oracle oracle 0 Apr 3 21:20 launcher
5. Look for another SharePlex replication of same version and copy the launcher to the .app-modules
6. Ensure the ownerships and permissions are the same as the original launcher
7. Modify the PRODDIR references in the script in the following lines:
Example Modify:
Line 1: #!/home/oracle/splex/prod75/.meta-inf/tools/bin/ruby
Line 3: ENV["PATH"] = (["/home/oracle/splex/prod75/.meta-inf/tools/bin"] + ENV.to_hash["PATH"].
Line 4: TOP = "/home/oracle/splex/prod75"
8. Save changes
9. Retry starting the SharePlex process that previously failed, such as sp_cop, sp_ctrl, qview, etc.
Resolution 2
If there is no other copy of an existing SharePlex replication, re-install the software in another directory and copy the .app-modules/launcher from the new installation to the existing .app-modules where the launcher has been zeroed out
Resolution 3
Reinstall the SharePlex software
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center