Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Enterprise Integration Manager Administration Guide > Running EIM > Viewing the EIM Log File > Trace Flag SettingsThis topic provides Trace Flag setting information as follows: Trace Flag 1Setting 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: Loading configuration file imacct.ifb 0s Opening server database ora_dev 6s 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 7: finding new foreign keys 4s Step 9: inserting new rows S_ORG_EXT 2s Step 10: updating primary keys S_ORG_EXT 3s Trace Flag 2Setting 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] SESSIONSQL = DELETE FROM DEV50.EIM_ACCOUNT WHERE IF_ROW_BATCH_NUM=21 [TRC01] DELETE MATCHES = EIM_ACCOUNT,(NAME LIKE 'EIM ins_acct Test%') [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 Trace Flag 4Setting 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 8Setting 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 32Setting 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. 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 |
![]() ![]() |
Siebel Enterprise Integration Manager Administration Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |