Using the Sync Log Monitor

Prerequisites

You are in the Start of the navigation pathTroubleshooting Next navigation step Database Next navigation step Open SQL Monitors Next navigation step Sync Log MonitorEnd of the navigation path function of SAP NetWeaver Administrator.

Context

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.

For more information, see:

The Sync Log monitor enables you to view the contents of this table.

Procedure

  • You can specify the log entries to be displayed using the Show field, the Get field, or the Advanced Search .
  • To check the total number of log entries, choose Show Number of Log Records . A log record may contain several sync log entries.
  • On the Available Sync Log Entries screen, you can view the following details about all synchronization requests pertaining to a single database transaction:

    Parameter

    Description

    Timestamp

    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.