Sync Log Monitor 
Each Java instance in the AS Java cluster works with a separate table and catalog buffer. That is why, it is necessary to synchronize the buffer instances on a regular basis to avoid data inconsistencies throughout the cluster. For this purpose, the changes to the database tables (content and structure) are logged to the BC_SYNCLOG table. In order to improve performance, only the key part of the change is stored which is sufficient to perform the invalidation operation on the remote buffers.
The Sync Log Monitor enables you to view the contents of this table.
Prerequisites
You are in Problem Management 
Database 
Open SQL Monitors Sync Log Monitor. 
Activities
On the Available Sync Log Entries screen, you can view the following details about all synchronization requests pertaining to a single database transaction:
Parameter Name |
Description |
|---|---|
Time Stamp |
Creation timestamp of the BC_SYNCLOG table rows; the timestamps are generated by the underlying database server. |
Cluster Node |
The cluster node on which the synchronization request is triggered. |
Buffer Handler Id |
Unique identifier for the buffer handlers, which consists of the category (table or catalog buffer), host, instance, and DataSource name. |
Request Length (B) |
Synchronization request length in bytes |
Request |
Synchronization request string |