Collecting Data for Reports › Empty Chart or Table

Empty Chart or Table

If a chart or table contains no data, the reasons vary depending upon the product you are using.

Empty CA NetMaster NM for TCP/IP Chart or Table

If you generate a report and a chart or table contains no data, check the following on each data feed region:

• Are you collecting the right type of data for this report?
• Are you collecting the data for the right resource name?

  Ensure that you have set the Send to ReportCenter field to YES for the resource.

• Are you collecting all the attributes that this chart or table needs?

  Note: For more information, see the technical document, Collecting ReportCenter Data, in the CA Support Online knowledge base.

• Can you see the actual hourly summary data values on the data feed regions?

If the hourly summary data values do not appear on the data feed regions, do the following:

• Check any data sampling errors with this resource. Check if it is in a DEGRADED status on the IP Resource Monitor or IP Node Monitor.
• Look at the Transient Log for any error details, such as SNMP errors.
• Run a SELFTEST on the data region.
• Try any available display or diagnostic commands for the resource.

If the hourly summary data values look healthy, then the data is being collected and the problem is elsewhere, either with ReportCenter, or between the data feed region and ReportCenter.

Empty CA NetMaster FTM Chart or Table

If you generate a report and a chart or table contains no data, check the Activity Log and ILOG of RFEVENTS group.

Problems with the Data Feed

Note: These instructions apply to both the CA NetMaster NM for TCP/IP and CA NetMaster FTM regions after you have established that there are no errors in those regions.

If there are problems with the data feed, do the following:

• Check the data feed between the CA NetMaster region and the ReportCenter Java Task. In the data feed region, enter /DWS and verify that the link is active, and any queued data is being sent.
• Run a REPTEST command from OCS on the ReportCenter control region, and verify that the Java Task is connected to the database.
• Review the Java Task log for error messages from the Data Warehouse Service, and any evidence of socket errors between the Java Task and this data region, or database errors.