Bookshelf Home | Contents | Index | PDF |
Siebel Performance Tuning Guide > Tuning Siebel EIM > Troubleshooting Siebel EIM Performance > Using the SQLPROFILE ParameterThis topic is part of Troubleshooting Siebel EIM Performance. The inclusion of this parameter greatly simplifies the task of identifying the most time-intensive SQL statements. By inserting the following statement in the header section of the .IFB file, the most time-intensive SQL statements will be placed in the file: SQLPROFILE = c:\temp\eimsql.sql Below is an example of the file eimsql.sql. Start of the file: list of most time-intensive queries: EIM: Integration Manager v6.0.1.2 [2943] ENU SQL profile dump (pid 430). ************************************************************************* Top 34 SQL statements (of 170) by total time: Batch Step Pass Total Rows Per Row What -------- -------- -------- -------- -------- -------- ----------------- 106 10 401 1334.48 5000 0.27 update implicit primaries to child 106 9 114 242.56 5000 0.05 copy Statistics by step and by pass: ************************************************************************* Statements per step by total time: Step Stmts Total Min Max Avg % -------- -------- -------- -------- -------- -------- -------- 10 15 2627.27 0.00 1334.48 175.15 83.73 9 11 329.52 0.00 242.56 29.96 10.50 ...list of statistics continues... SQL statements:************************************************************************* batch 106, step 10, pass 401: "update implicit primaries to child": (total time 22:14m (1334s), 5000 rows affected, time/row 0.27s) (SELECT VALUE(MIN(ROW_ID), 'No Match Row Id') WHERE (CT.PER_ID = BT.ROW_ID)), MODIFICATION_NUM = MODIFICATION_NUM + 1 T_ADDR_PER_PER_ID IS NOT NULL AND (PR_BL_PER_ADDR_ID IS NULL OR PR_BL_PER_ADDR_ID = 'No Match Row Id')) ************************************************************ |
Siebel Performance Tuning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |