The symptoms and the resolution are described in Resolution section herein for ease of understanding.
The activation finished fine in that there was an active config as shown by “list config”:
sp_ctrl > list config
File Name State Datasource
-------------------------------------------------- ---------- ---------------
.
.
R12_config_v3 Active o.SourceSID
Last Modified At: 11-Dec-18 14:02 Size: 16463 Internal Name: .conf.3
However, there was no Capture process and consequently there were no downstream processes like Read, Export, etc:
sp_ctrl > status
Brief Status for source_server
Process State PID Running Since
--------------- ------------------------------ -------- --------------------
Cop Running 49856 11-Dec-18 13:33:18
Cmd & Ctrl Running 92651 11-Dec-18 14:02:20
The “show config” also suggested there were 0 tables in replication:
sp_ctrl > show config
File Name :R12_config_v3
Datasource :SourceSID
Activated :11-Dec-18 15:54:25
Actid :3
Total Objects :50600
Total Objects Replicating :0
Total Objects Not Replicating :50600
View config summary in /u01/shareplex/vardir/log/ SourceSID_config_log
The statusdb showed that there was a valid activation entry in it yet it missed an entry for spawning of Capture process, presumably due to log wrap. The following is an actual activation entry taken from one of our test server:
[ORA11GR2@alvsupl14]/home/paul/p9141-11g/var/data> cat statusdb
.
3|15|14|1|IN|0|1542401878|Replication active from "asdf", actid 3, for database o.ORA11GR2|asdf|o.ORA11GR2||3|0|0|0x0a01174f+PF+*+sp_tconf+o.ORA11GR2
(here the name of the active config file is asdf, and the name of the source SID is ORA11GR2)
.
The following is how the statusdb entry for spawning of Capture would have looked, had the Capture spawned successfully:
4|20|35|1|IN|0|1542401879|Capture now replicating actid 3, for database o.ORA11GR2|o.ORA11GR2|||3|0|0|0x0a01174f+PA+o.ORA11GR2+sp_ocap+o.ORA11GR2
If the above conditions hold:
* There is an active config as seen in the “list config”
* There is an activation entry in the statusdb file
* There is a missing entry for spawn of Capture process in the statusdb file
THEN, the issue can be resolved by issuing the following command at the sp_ctrl:
sp_ctrl>start Capture
The above will spawn the Capture and would also create the entry for Capture in statusdb.
If the above does not help, then shutdown and restart SharePlex which should help.
If, for any reason the above workaround do not help, then contact Support to see if the activation can salvaged.
