Troubleshooting Analysis, Models, and Reports
Viewing log information
To view logs from the command line:
- Log on to the Application Server running the datahub.
- Navigate to $CPITBASE/web/log and check cpit.log* logs.
You can also use the logGrabber utility to collect these logs. For details on logGrabber, see the knowledge article number 000244652 (Support logon ID required).
To view Golden (scheduled) Analysis/Models logs from the UI:
- Navigate to Administration > ETL & System Tasks > System Tasks.
- Select the view logs button corresponding to the task of type "Golden Producer". Scheduled works are executed by Daily, Monthly or Weekly Reporter tasks according to the selected scheduling.
- From the logs page, you can download the logs using Collect logs option.
To view Report logs from the UI:
- Navigate to Administration > ETL & System Tasks > System Tasks.
- Select the view logs button corresponding to the task of type reporter:
- On demand tasks are executed by "On demand Reports" task.
- Scheduled tasks are executed by Daily, Monthly, or Weekly Reporter tasks according to the selected scheduling.
- From the logs page, you can download the logs using Collect logs option.
Exporting and importing analysis and forecasting models
For details about exporting and importing analysis and forecasting models, see the following Knowledge Articles:
- Export and Import Analyses Data and Settings
- Export and Import Models Data and Settings
- Export Data from a Workspace Domain - Domain extractor
Common issues
Issue | Cause | Resolution |
---|---|---|
Report is not received via email. The following message is reported in the log: BCO_SCH_ERR011: Error sending mail BCO_SCH_ERR016: Error sending mail | SMTP is unreachable or it is incorrectly configured. | |
The scheduled reports are not received via email or the Golden analysis or models are not generated. The following message is reported in the log: $CPITBASE/scheduler/log/scheduler.out or scheduler.err ERROR FATAL - Program abnormally terminated [java.lang.OutOfMemoryError: GC overhead limit exceeded] | Scheduler Java heap size insufficient | Increase the ETL Java heap size. For details, see KA: How to Enlarge Scheduler's Heap. |
The report received via email is empty. | No data for the report to run. |
For details, see How to quickly assess the health of TrueSight Capacity Optimization. |
After running a model, no output is generated. The following message is reported in the UI: No data available | Data set size (number of samples) is insufficient for the model. |
|
When you execute a Performance versus Time Analysis PTA, no data is available. The following message is reported in the UI: No data available | Data set size (number of samples) is insufficient for the PTA to run. | |
When you execute a Performance versus Load Analysis PLA. no data is available. The following message is reported in the UI: No data available | Data set size (number of samples) is insufficient (less than 30 points). |
|