Siebel Remote and Replication Manager Administration Guide > Monitoring and Reporting > Monitoring and Logging for Siebel Remote >

Configuring Traces for a Server Component

Beginning with Siebel CRM version 7.5, Siebel Remote includes tracing capability for Remote and Replication Manager server components that improves system diagnostics. Trace files track SQL statements that a server component sends. They include some information about the task or function that is in progress.

Configuring Traces for a Server Component by Using an Administrative Screen

This topic describes how to set tracing for a server component by using an administrative screen.

To configure traces for a server component by using an administrative screen

1. Locate the record for the server component you must trace.

   For more information, see Server Components That You Can Use with Tracing and Locating the Record for a Server Component.

2. In the Events list, choose the Event Type you must trace.

   To help determine the Event Type to choose, you can use the Description field. For more information, see Using Event Logging with Server Components.

3. Set the value in the Log Level field to 4.

   The log file for the server component you choose in Step 2 will contain the tracing information.

Configuring Traces for a Server Component by Using a Command Line

This topic describes how to set tracing for a server component by using the command line.

To configure traces for a server component by using a command line

• From the Server Manager command line, enter the following command:

  srvrmgr: change evtloglvl event type = 4 for server component name

  where:

  • event type is the type of event that the Siebel Server traces
  • server component name is the name of the server component that the Siebel Server traces

    For more information, see Opening the Command Line Interface for Server Manager.

How the Siebel Server Traces a Lock

A lock is a handle that a server component uses to identify the server component that can access an object, such as a DX file that resides in the folder of the Transaction Processor. A lock on the tracing feature displays the reason why the lock is set or released for the server component. A lock in the trace file provides information than you can use to troubleshoot a problem to reduce the contention between critical server components for Remote and Replication Manager.

For example, assume there is a problem with the Transaction Processor. It might be locking an object, such as a DX file that resides in the docking folder but not releasing it. If you set the Log Level to 4 or 5, then the Siebel Server logs information about the lock in the Transaction Processor log file. This functionality applies to the Remote and Replication Manager server components on the headquarters or regional nodes. It is not available to the user. For more information, see Overview of Replication Manager.

Tracing and logging of locks for server components includes the following objects on the Siebel Server:

• Dobjinst.dbf
• DX files
• Inbox
• Outbox
• Visdata.dbf

To enable the tracing for these locks, you can use the predefined Siebel event tracing features. The trace level of the server component controls logging. It is not necessary to restart the Siebel Server. For help with reducing contention, see Getting Help from Oracle.

For more information, see Naming Conventions for Log Files.

Server Components That You Can Use with Tracing

You can use the following server components with tracing:

• Database Extract
• Generate New Database
• Parallel Database Extract
• Transaction Merger
• Transaction Processor
• Transaction Router
• Replication Agent
• Synchronization Manager

For more information, see Server Component Parameters.

Using Event Logging with Server Components

Event logs provide helpful information for diagnosing problems. For example, to log information for the Database Extract server component, you can enter the following command in the Server Manager command line interface:

change evtloglvl GenericLog=5, Trace=5, SQL=5, EVENT_GENERIC_PROFILE=5 for comp dbxtract

start task for comp dbxtract server server_name with Client=client_name, SQLFlags=2, TraceFlags=7

Information Sources for Tracing

Table 22 describes sources that you can access to get more information about tracing.