When a RepAgent or LTM starts, it uses a locater to determine where to begin scanning the database log. The locater for a database log is stored in the rs_locater table in the RSSD of the Replication Server that controls the database.
This locater is different from the RSI locater. See “Invalid RSI locater” for more information
about the RSI locater.
The locater points to a record on a page in the database log. If the truncation point for the database is turned off, you or Adaptive Server may truncate the page the locater points to, invalidating the locater. When the locater is invalid, the RepAgent writes error message 9215 (see “9215: log truncated (LTM 1079 with ASE 624)”) to the Adaptive Server error log. The LTM writes error message 1079 to the LTM error log:
E. 95/10/30 14:18:13. ERROR #1079 logscan thread(vishy_pds.pdb) - /ltmscan.c(1459) The action for this error is invalid. Internal LTM error. H. 95/10/30 14:18:13. THREAD FATAL ERROR #1078 logscan thread(vishy_pds.pdb) - /ltmscan.c(1459) This CT-Lib or Open Server error is fatal. The server the thread connects to is ‘vishy_pds’. I. 95/10/30 14:18:13. No Sybase library information is available
97/10/17 11:57:19.34 RepAgent (10) Error: 9215, Severity: EX_USER, State: 1 The Secondary Truncation Point is not valid. Please make sure that the Secondary Truncation Point is valid, and then restart the Rep Agent Thread for this database.
To recover, reset the locater to 0x0. This directs the RepAgent or LTM to begin scanning the log from the truncation point.
To reset the locater, update the rs_locater table in the RSSD for the Replication Server controlling the database using the Adaptive Server stored procedure rs_zeroltm:
rs_zeroltm data_server, database
where data_server and database are the respective Adaptive Server and database whose LTM locater value you want to reset.
For example, to reset the LTM locater for the MYDS Adaptive Server and the Parts database, execute;
rs_zeroltm MYDS, Parts
