IBM WebSphere Message Broker Monitoring, WebSphere MQ Monitoring, and WebSphere MQ Configuration agents, Version 7.1

Known problems and workarounds

This section contains problems that might occur when you work with Cognos® reports.

Arithmetic overflow errors in ad hoc querying

If you drag certain columns in an ad hoc query and it returns an arithmetic overflow error, switch to preview with limited data or to preview with no data and add Standard Timestamp to the query.

Certain columns might average or sum up to a number that is larger than the size supported by the database. So the SQL error of arithmetic overflow is returned. If you see the data by hourly timestamp or daily timestamp, or set a query to limit the data, the aggregated value is forced to be within the supported size.

No data available in ad hoc querying on two tables

The No data available message is displayed in an ad hoc querying on two tables, but the resulting data indicates that the two tables are queried.

This error occurs because there is no relationship defined between the two tables. Make sure all your ad hoc queries have at least one identifier.

Errors of missing table or attribute

Make sure that all the prerequisites are met and the warehouse is collecting historical data. If you enable historical data collection appropriately, you are able to use the data model for WebSphere® Message Broker Monitoring agent.

If you have all the required tables but still get this error, it might be because the WebSphere Message Broker Monitoring agent is not compatible with the version that is used in the generic model.

To check the query that runs, open the report in the Report Studio. Click Tools > Show Generated SQL/MDX. The queries in the report are displayed. You can view the native SQL.

The table schema is not ITMUser

If the table schema that you use is not ITMUser, use the framework manager to update the schema to what you used.

  1. Extract the report package to your local system that the framework manager is installed on.
  2. In the model\WebSphere Message Broker Monitoring Agent v7.1 Data Model folder, open the WebSphere Message Broker Monitoring Agent v7.1 Data Model.cpf file with the framework manager.
  3. In the Project Viewer view, expand Data Sources and click TDW.
  4. In the Property view, change the schema property from ITMUser to the schema that you used and save the changes.
  5. In the Project Viewer view, expand Packages, right-click the WebSphere Message Broker Monitoring Agent package and click Publish Packages to publish the package to the Cognos server.

Duplicated broker names for the Broker Name selection

If the managed system node name that is related to a broker is changed, duplicate broker names might exist in the Broker Name field on the Parameter Selection page. This is because the node name change affect the data correlation. The data for the same broker is not correlated for together until after the old node name has rolled out of the warehouse over time.

To distinguish the duplicated broker names, edit the report in the report studio to change the Display Value property of the Broker Name parameter to Origin Node on the Parameter Selection page.

Remember: A change to any of the following values can cause the change of the managed system node name that is associated with the agent data for brokers:
  • WebSphere Message Broker Monitoring agent ID
  • Name of the broker
  • Alias name of the broker


Feedback