Bookshelf Home | Contents | Index | Search | PDF

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

Trace Flags

---

Trace flags contain logs of various EIM operations. To activate trace flags, you must complete Step e 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 the following procedure.

To set EVENT LOGGING for an EIM component

1. Click the Server Administration screen tab.
2. From the Show drop-down list, select Component.
3. Select Enterprise Integration Manager as the component.
4. Click Component Event Configuration.
5. Perform a query and enter the Log Level values for the following:

   Event Type	Log Level Value
   SQL Tracing	4
   SQL Summary	4
   Task Configuration	4
   Component Tracing	3

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.

NOTE:  Activating flags will have a direct negative effect on performance since, depending on the amount of data, a lot of information will be recorded in the log file. Typically, activating flags should only be done when testing EIM processes. Avoid activating flags in a production environment unless absolutely necessary.

Trace Flag 1

Setting the Trace Flags parameter to 1 creates a step-oriented log of the task. This can be used to determine the amount of time EIM spends on each step of the EIM task, or for each EIM table processed. The following sample shows an EIM Trace Flag 1 output:

Initializing

Loading configuration file imacct.ifb 0s

Opening server database ora_dev 6s

Loading Siebel dictionary 15s

Initializing 21s

Import Accounts 14

Importing EIM_ACCOUNT

Step 1: initializing IF Table 0s

Step 4: resolving foreign keys S_ORG_EXT 0s

Step 5: locating existing row S_ORG_EXT 0s

Step 6: assigning new row IDs S_ORG_EXT 0s

Step 7: finding new foreign keys 4s

Step 9: inserting new rows S_ORG_EXT 2s

Importing EIM_ACCOUNT 15s

Updating primaries

Step 10: updating primary keys S_ORG_EXT 3s

Updating primaries 3s

Import Accounts 14 18s

Trace Flag 2

Setting the Trace Flags parameter to 2 creates a file log that traces all substitutions of user parameters. The following example shows an EIM Trace Flag 2 output:

[TRC01] Parameter Set << AFTER RESOLUTION >>

[TRC01] UserParams = IFTABLE=EIM_ACCOUNT

[TRC01] [0] $IFTABLE = EIM_ACCOUNT

[TRC01] [1] $CURRENT_USER = wgong

[TRC01] [2] $CURRENT_DATETIME = 4/6/01 13:17

[TRC01] [Siebel Integration Manager]

[TRC01] log transactions = false

[TRC01] $COLUMN_VALUE = 'EIM ins_acct Test%'

[TRC01] [ins_acct_shell]

[TRC01] TYPE = SHELL

[TRC01] INCLUDE = del_acct

[TRC01] INCLUDE = ins_acct

[TRC01] [del_acct]

[TRC01] SESSIONSQL = DELETE FROM DEV50.EIM_ACCOUNT WHERE IF_ROW_BATCH_NUM=21

[TRC01] TYPE = DELETE

[TRC01] BATCH = 20

[TRC01] TABLE = EIM_ACCOUNT

[TRC01] $COLUMN_NAME = NAME

[TRC01] DELETE MATCHES = EIM_ACCOUNT,(NAME LIKE 'EIM ins_acct Test%')

[TRC01] [ins_acct]

[TRC01] SESSIONSQL = INSERT INTO DEV50.EIM_ACCOUNT (IF_ROW_STAT, ROW_ID, IF_ROW_BATCH_NUM, ACCNT_NAME, ACCNT_LOC) SELECT 'X', ROW_ID, 21, 'EIM ins_acct Test ' || ROW_ID, 'Loc' FROM DEV50.S_SYS_PREF

[TRC01] TYPE = IMPORT

[TRC01] BATCH = 21

[TRC01] TABLE = EIM_ACCOUNT

Trace Flag 4

Setting the Trace Flags parameter to 4 creates a file log that traces all user-key overrides. The following example shows an EIM Flag 4 output for a user key override to the EIM_ACCOUNT table:

[TRC02] ------------------------------------------------------

[TRC02] ***** IF TABLE <EIM_ACCOUNT> uses USER_KEY_COL *****

[TRC02] Action: No Move & Insert

[TRC02] overriding UK Index (S_TERR_ITEM_U1) at position (0)

[TRC02] ##### Destination TABLE (S_TERR_ITEM) index vector: [S_TERR_ITEM_U1]

[TRC02] --- Column (T_TERITE_OUID) index vector: [S_TERR_ITEM_U1]

[TRC02] --- Column (T_TERITE_TERID) index vector: [S_TERR_ITEM_U1]

[TRC02] ------------------------------------------------------

Trace Flag 8

Setting the Trace Flags parameter to 8 creates a file log that traces all Interface Mapping warnings. The following example shows an EIM Flag 8 output for an Interface Mapping warning between the EIM_ACCOUNT and S_TERR_ITEM tables:

[TRC03] --------------------------------------------------------

[TRC03] IF table EIM_ACCOUNT destination S_TERR_ITEM

[TRC03] IF column EIM_ACCOUNT.T_TERITE_TERID:

[TRC03] imports to: S_TERR_ITEM.TERR_ID

[TRC03] exports from: S_TERR_ITEM.TERR_ID

[TRC03] Column NAME of join isn't in table!

[TRC03] Missing join to user key NAME

[TRC03] --------------------------------------------------------

Trace Flag 32

Setting the Trace Flags parameter to 32 creates a file log that traces all file attachment status. The trace file contains four labels, three of which are used to trace file attachment processes as described in Table 17.

Table 17.  Flag 32 Trace File Labels 

Label	Description
Attachment Imported	Indicates whether the file attachment was encoded, compressed, and copied to the Siebel file server with the new name.
Attachment (Old) Deleted	This label applies only to updates and indicates whether an existing file was replaced and deleted.
Attachment Not Found	Indicates that the file attachment cannot be found in the input directory.

The following sample shows an EIM Flag 32 output for an opportunity file attachment:

[TRC32] Attachment Imported: E:\V50\output\openpost.doc -> \\BALTO\SIEBFILE\ORADEV50\S_OPTY_ATT_10+413+1_10-41R-0.saf

[TRC32] Attachment (Old) Deleted: \\BALTO\SIEBFILE\ORADEV50\S_OPTY_ATT_10+413+1_10-40Y-0.saf

[TRC32] Attachment Not Found: E:\V50\output\openpost.doc

[TRC32] Attachment Identical: E:\V50\output\openpost.doc IDENTICAL TO \\BALTO\SIEBFILE\ORADEV50\S_OPTY_ATT_10+413+1_10-41R-0.saf

Bookshelf Home | Contents | Index | Search | PDF