Invalid Truncation Page

The secondary truncation point identifies the page that contains the begin transaction statement of the most recent transaction that was sent to the Replication Server.

The RepAgent executes the dbcc settrunc command on the Adaptive Server to set the secondary truncation point in the database log. If the RepAgent specifies an invalid page to the Adaptive Server, an error is recorded and the RepAgent aborts. You may see Adaptive Server error 4213:

Message: 4213, State: 1, Severity: 16 -- ’Page 2561 in
database ‘MY_DB’ cannot be used as a truncation page
because the page is not allocated.’

The rs_locater table in the Replication Server system database tells the RepAgent where to set the secondary truncation point in the Adaptive Server log. This error is expected if the truncation state is set to ignore and the log is truncated. The RepAgent then restarts without resetting rs_locater.

To solve this problem, set rs_locater to zero and restart the RepAgent.