A. Upgrade to OpenEdge 10.2B08, 11.2, 11.3 or later
The maximum value for -pica has been increased to 1000000.
It is not recommended to use the maximum value as this will cause longer synchronization times at startup or re-connection time after failure. Instead, get the network and the target machine performance checked. Then revisit calculating the optimum -pica value for the environment's high write activity periods. Using a higher -pica value reduces the likelihood of the pica queue becoming full and therefore avoiding this issue of not being able to terminate the RPLS process and otherwise the source database OLTP activity stalling. For example refer to Article: How to calculate the optimum -pica setting for OpenEdge Replication
B. Before terminating the Replication Server
1. First determine if the RPLS-Q is full before terminating the RPLS process:
PROMON > R&D > 1. Status Displays > 16. Database Service Manager
Status: Database Service Manager
Free Message Entries : < this value >
Further detail are provided in Article:
How to monitor the message replication queue set with the -pica parameter. 2a. If there are
Free Message Entries remaining:
Proceed with terminating the Replication Server from the command line, then verify through the PROMON user list (outlined below) that the RPLS process has terminated.
$ dsrutil source -C terminate server
2b. When there are no Free Message Entries remaining:
- The Free Message Entries shows: 0, a small value that keeps resetting to zero or a very low value that could fill in the meantime
- Sending an instruction to terminate the server then Kill the rpserver.exe process (RPLS )
Steps to disconnect and terminate the Replication Server process:
i) instruct the RPLS to terminate so that the database marks it 'todie'
$ dsrutil source -C terminate server
ii) Find the RPLS User ID and PID using PROMON or _Connect VST
promon > 1. User Control > 1. Display All Entries
Find the RPLS process under the "Type" column then lookup the PID
Usr Name Domain Type Wait Table:Part Dbkey Trans PID Sem Srv Login Time
5 dbstart 0 RPLS -- 0 0 0 10400 0 0 02/09/18 12:44Find the RPLS PID using ABL to query the _Connect VST:
FOR EACH _Connect WHERE
_Connect-Usr <> ? AND
_Connect-Type = "RPLS" NO-LOCK:
DISPLAY
LDBNAME("dictdb") FORMAT "x(20)" LABEL "Current DB"
_connect-type
_connect-usr COLUMN-LABEL "Usr#" FORMAT ">>>9"
_connect-pid FORMAT ">>>>9".
END.
iii) Use promon or proshut to disconnect the User ID
$ proshut <dbname> -C disconnect <usernum_of_RPLS>
iv) If the Replication Server PID does not go away only then terminate is OS signals
Terminate the RPLS PID by using the UNIX kill command or on Windows using the Task Manager.
UNIX: kill -15 <pid> ( Before running a kill, verify that the PID is not touching DB files with a command like lsof -p <PID>)
WINDOWS: TASKKILL /PID <pid> /T /F
Note: Kill -9 should be used as a last resort and may result in a DB crash if the PID is still touching database files. If the RPLS process is holding a latch, buffer, or lock then the killing of the RPLS process may force a shutdown of the database.
