Diagnosing Enterprise Command Center Issues

Diagnosing Issues

Administrators can leverage the About ECC section for quick understanding of application version and different configuration settings.

Installation Issues

The installation process leverages a logging mechanism that captures all the events during the installation process of Oracle Enterprise Command Center Framework. A variety of logs are captured at different steps of installation. These logs can be reviewed for diagnosing the situation. ECC Analyzer can be run post-installation to assess if any installation step has been missed or requires attention.

Common steps to diagnose installation issues are:

• Review ECC Analyzer output. For more information on ECC Analyzer, refer to Oracle E-Business Suite Enterprise Command Center (ECC) Analyzer, My Oracle Support Knowledge Document 2587090.1.

• Confirm the Oracle Enterprise Command Center Framework version.

• Confirm that the required patches are applied.

• Rule out security and data load as root causes.

• Confirm that Oracle Enterprise Command Center Framework standalone is working fine before integrating with Oracle E-Business Suite.

• Confirm if applications are successfully imported. Review import.log.

• Confirm that all installation steps are successful, or if the issue occurs after upgrade. Review error messages and corresponding log files such as the setup log, domain log, and Oracle Enterprise Command Center Framework log.

Performance Issues

The data load tracking page provides details regarding the time elapsed at various stages of data load execution. This serves as a robust assessment of performance allowing the administrator to take initiatives related to performance improvement.

The Data Load Tracking page lists data loads, along with a search feature. For a given load, you can access the run ID, load type, status, application name, data set key, language(s), and time of load. For more information, see: Data Load Tracking.

Example of Data Load Tracking

You can expand the Data Set Details region for a link to the Query Details page. This page includes SQL query run, the time it was run, and the number of rows processed, and other information.

Example of a Query Details Page

Common steps to diagnose performance issues are:

• Review if data load is successful.

• Review time taken for data load completion.

• Confirm if data load completion takes very long time.

• Review data load log file and SQL ETL (extract, transform, and load) issues.

ETL Issues

The data load tracking page also details the SQL query that has been executed during the data load operation for each data set, the number of records processed, and the number of records ingested. These details allow administrators to determine if there are any data- or query-related issues so that they can take corrective actions in the proper direction.

Common steps to diagnose ETL issues:

• Review ECC Analyzer Output.

• Confirm if right concurrent manager is triggered.

• Confirm which child job is failing.

• Review concurrent program log for child job.

• Review missing profile options.

• Review logs with debug log level.