Tivoli Enterprise Portal troubleshooting
Learn about Tivoli® Enterprise Portal troubleshooting.
Table 1 lists problems
that might occur with the Tivoli Enterprise Portal.
This chapter provides agent-specific troubleshooting information.
See the IBM® Tivoli Monitoring Troubleshooting Guide for
general troubleshooting information.
| Problem | Solution |
|---|---|
| Historical data collection is unavailable because of incorrect queries in the Tivoli Enterprise Portal. | The column, Sort By, Group By, and First/Last functions are not compatible with the historical data collection feature. Use of these advanced functions will make a query ineligible for historical data collection. Even if data collection has been started, you cannot use the time span feature if the query for the chart or table includes any column functions or advanced query options (Sort By, Group By, First / Last). To ensure support of historical data collection, do not use the Sort By, Group By, or First/Last functions in your queries. See the IBM Tivoli Monitoring Administrator's Guide for information about the Historical Data Collection function. |
| When you use a long process name in the situation, the process name is truncated. | Truncation of process names in the portal display is the expected behavior. 64 bytes is the maximum name length. |
| In the Network Info workspace, the value of the listener port column is 0 or -1. | Set the svcename parameter as db2c_Instance in
the database manager configuration of the corresponding DB2® database instance. Where Instance is
the name of the DB2 agent instance. Add
the following line in the services file of the DB2 database instance:
The
services file is located at the following paths:
After these changes take effect, the specified PortNumber is
displayed in the Network Info workspace.
|