[CR #276758] When using Adaptive Server row-level locking for System Table Services (STS) tables, Replication Server can report that an STS object does not exist when in fact it does exist in the RSSD. This happens because with Adaptive Server row-level locking, when there are two concurrent transactions, one transaction deletes and then inserts a row, while the other transaction tries to select the same row. When this occurs, the select command fails to retrieve the row.
Workaround: You can either restart Replication Server, or use the following command for the appropriate table when it has a row that exists in the RSSD but is missing from the cache:
sysadmin stscache, fillcache, tablename
