The following messages are observed in the event_log though the replication is working fine:
The example below is for compare client:
Info 2017-09-07 12:18:15.170000 11352 11036 Compare client exited normally, pid = 34412 [sp_declt]
Info 2017-09-07 12:17:25.888000 28944 13952 Compare client launched, pid = 28944 [sp_declt]
Notice 2017-09-07 12:17:25.885000 28944 13952 Compare client: Parameter SP_OPO_TRACK_CHANGES not found [sp_declt] [module pdb]
The example below is for Post:
Poster launched, pid = 2552 (posting from SID1, queue queue_name, to SID2)
Notice 2017-09-01 18:14:47.377000 2552 5188 Poster: Parameter SP_OPO_TRACK_CHANGES not found (posting from SID1, queue queue_name, to SID2) [module pdb]
The messages “Parameter SP_OPO_TRACK_CHANGES not found” are harmless and are conveying to you that the parameter SP_OPO_TRACK_CHANGES has been set to a non-default value in your environment even though the parameter has been deprecated. The change tracking is now done by Capture if the replication is configured for Change History or Change Data Capture (CDC). To suppress such messages, carry out the following steps:
1. Shutdown SharePlex
2. Comment out the parameter from the paramdb file by inserting a Pound (#) character as the first character in the line containing the parameter. The paramdb file is located in /vardir/data directory (where vardir refers to the SharePlex’s variable directory)
3. Restart SharePlex.
