SyncLog Monitor 

Use

Since each Java instance in a J2EE Engine cluster works with a separate table and catalog buffer, 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 in 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 SyncLogMonitor enables you to view the contents of this table.

Prerequisites

You must have logged on to the Open SQL Monitors application as a J2EE Engine user from the administrator group.

Activities

To access the SyncLog Monitor, follow the link SyncLogMonitor on the start page of the Open SQL Monitors application.

On the Content of table SYNCLOG screen, details about each row of the BC_SYNCLOG table are displayed. A row of this table contains all synchronization requests pertaining to a single database transaction. The following details are displayed:

BC_SYNCLOG Table Details

Parameter Name	Description
Timestamp	Creation timestamp of the BC_SYNCLOG table rows; the timestamps are generated by the underlying database server.
Server ID	Unique identifier of the Java instance where the synchronization request was issued. If the request has been issued during SDM deployment, the value in this column is -1.
BufferHandlerId	Unique identifier for the buffer handlers, which consists of the category (table or catalog buffer), host, instance, and DataSource name.
Req. Length	Synchronization request length in bytes
Request	Synchronization request string

 

You can view and modify buffer synchronization settings using the Offline Configuration Editor or the runtime screen of the Configuration Adapter Service in the Visual Administrator. You can find the buffer synchronization property sheet for the relevant instance under Configurations ® Open SQL.