Siebel Enterprise Integration Manager Administration Guide > Running EIM > Viewing the EIM Log File >

Using Trace Flags, SQL Trace Flags, and Error Flags

You can activate trace flags and error flags to log transactions. This topic covers the following types of flags:

• Error flags. See Error Flags.
• SQL Trace flags. See SQL Trace Flags.
• Trace flags. See Trace Flags.

NOTE:  Activating flags will have a direct effect on performance. Typically, activating flags should only be done when testing EIM processes. Avoid activating flags in a production environment unless absolutely necessary.

Recommended settings for error flags, SQL trace flags, and trace flags include the following:

• To display errors and unused foreign keys. Start with the following setting combination. The setting Trace Flag=1 provides a summary (after each batch) of the elapsed time in EIM steps 10 and 11.

  Error Flag	1
  SQL Trace Flag	1
  Trace Flag	1

• To determine SQL performance. The following setting combination produces a log file with SQL statements including the elapsed time for each statement.

  Error Flag	1
  SQL Trace Flag	8
  Trace Flag	3

• To determine optimal batch size and monitor performance in a particular step. The following setting combination produces a log file showing the elapsed time for each EIM step.

  Error Flag	0
  SQL Trace Flag	0
  Trace Flag	1

Error Flags

To activate error flags, you must complete Step 6 when running an EIM process. Setting the Error Flags parameter to 1 produces a detailed explanation of rows that were not successfully processed.

There are a variety of reasons why rows might not be processed. The following sample shows an excerpt from an EIM Error Flag 1 trace. The log begins with a header that describes an export failure that occurred during Step 2, Pass 101.

2001-04-04 03:47:59 4/4/01 3:47 Warning: No rows in S_ORG_EXT matched by expressions for export.

2001-04-04 03:47:59 Process [Export Old Accounts] had all rows fail

2001-04-04 03:47:59 on EIM_ACCOUNT for ] 2001 in step 2, pass 101:

2001-04-04 03:47:59 No base table rows matched expressions. (severity 5)

2001-04-04 03:47:59 Base table:

2001-04-04 03:47:59 S_ORG_EXT (Account)

2001-04-04 03:47:59 The match expressions specified for exporting rows through this interface table

2001-04-04 03:47:59 did not match any of the rows currently in the target base table.

2001-04-04 03:47:59 Since there were no matches for the given match expressions, processing for

2001-04-04 03:47:59 this interface table was discontinued. However, processing of other interface

2001-04-04 03:47:59 tables will continue.

2001-04-04 03:47:59 Recorded 1 group of failures.

SQL Trace Flags

To activate SQL trace flags, you must complete Step 6 when running an EIM process.

Setting the SQL Trace Flags parameter to 8 creates a log of all SQL statements that make up the EIM task. The lower values for SQL Debug Flags (1, 2, and 4) are used for logging at the ODBC level.

Trace Flags

Trace flags contain logs of various EIM operations. To activate trace flags, you must complete Step 6 when running an EIM process. If you are using Siebel 7.x, you also need to set event logging for the EIM component, as described in Setting Event Logging from the Graphical User Interface (GUI).

Trace flags are bit-based. Available trace flags include 1, 2, 4, 8, and 32. To activate multiple trace flags, set the Trace Flags parameter to the sum of individual trace flag numbers. For example, to log trace flags 2 and 4, set the Trace Flags parameter to 6.