displayLogsquery=ECID equals Logging-Related WLST Commands

24-24 Publishing Reports to the Web with Oracle Reports Services Example The following command displays all audit events: wls:domain52domainRuntime listAuditEvents; Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root. For more help, use helpdomainRuntime Components: DIP JPS OIF OWSM-AGENT OWSM-PM-EJB ReportsServer WS-PolicyAttachment WebCache WebServices Attributes applicable to all components: ComponentType InstanceId HostId HostNwaddr ModuleId ProcessId OracleHome HomeInstance ECID RID ...

24.3.7 Tracing Report Execution

Enabling report tracing generates a text file that describes the series of steps completed during the execution of the report. The trace file provides abundant information, which is useful not only for performance tuning but also for debugging reports and identifying performance bottlenecks. ■ For Reports Builder rwbuilder and Reports Runtime rwrun, specify tracing options in the logging.xml file. For example: In ORACLE_ INSTANCEdiagnosticslogsReportsToolsComponentReportsTools logging.xml, specify the trace level to Trace 32. ■ For Reports Server rwserver, specify tracing options in the logging.xml file. Separate trace files are generated for Reports Server and the engines. For example: – In ORACLE_ INSTANCEconfigReportsServerComponentservernameloggin g.xml, specify tracing level to Trace 32. componentType Specifies the component type. Argument Definition Diagnosing and Tuning Oracle Reports 24-25 In 11g, job level tracing for an individual report does not exist. Instead, users can only search for a job in Enterprise Manager based on the job’s ECID. ■ For Oracle Reports Servlet rwservlet, specify tracing options in the logging xml file present at the following location: FMW_HOMEuser_ projectsdomainsdomainnameconfigfmwconfigserversWLS_ REPORTSlogging.xml ■ For Oracle Reports Bridge tracing, specify tracing options in Oracle Enterprise Manager. You can also manually specify the tracing options in the logging.xml file present at the following location: ORACLE_ INSTANCEconfigReportsBridgeComponentReportsBridgeNamelo gging.xml Following is the outline of the information output to the logging file. Example 24–1 Oracle Reports Builder +------------------------------------------+ | Report Builder Profiler statistics | +------------------------------------------+ Total Elapsed Time: 8.00 seconds Reports Time: 7.00 seconds 87.50 of TOTAL ORACLE Time: 1.00 seconds 12.50 of TOTAL UPI: 0.00 seconds SQL: 1.00 seconds TOTAL CPU Time used by process: NA In Example 24–1 , focus your tuning efforts on time formatting Reports Time the data rather than on querying and fetching it. Table 24–18 Oracle Reports Builder Field Description Total Elapsed Time Time spent in executing the report. Reports Time Time spent in formatting the retrieved data. Also displayed as a percentage of Total Elapsed Time. ORACLE Time Time spent in retrieving the data. Also displayed as a percentage of Total Elapsed Time. UPI SQL queries only. Time spent in establishing a database connection, then parsing and executing the SQL. SQL Time taken by the database server to fetch the data percent of time spent executing SRW.DO_SQL statements, EXEC_SQL statements, PLSQL cursors, and so on. Note: If your data source is a non-SQL data source such as Text or an XML pluggable data source, the values for ORACLE Time, UPI, and SQL display as 0.