Data Gaps in the Reports (Advanced Reporting)

[Anon]

If there are data gaps in the Reports, Check the following:

1. ETL issues (ETL History) Contact DBA for the BDIUC ETL Job log
2. SQL connectivity intermittent between Prognosis and SQL Server. Check WvLog. Look for network errors and contact the DBA, set up a Threshold that monitors connectivity between Prognosis and SQL Server. A Prognosis Record: MSSQLInstanceConnections can be used to build the threshold. There also is a Prognosis Self Monitoring tool available that be deployed which has some of these tools.

3. Bounce SQL Server Reporting service on the SSRS server

4. Check connectivity between Prognosis Reporting Node and its respective Monitoring Node(s).
If there are intermittent connectivity issues, SAF (Store And Forward) can be set up on the Monitoring nodes so that if there is a disconnect between the Monitoring node and the Reporting node, data is temporarily stored on the monitoring node, and when the connection is restored, the data is transferred.

To set up SAF, Access the Network Configuration on the Monitoring node and enter the database node name and the size of data you would like to keep:
SUBSYS NETWORK
SAF-SIZE (database node name, Size MB)

[Christopher_Chi]

Thanks for the info, do you think we can use SAF for anything other than Advanced Reporting? Can we not point the Monitoring nodes directly to the SQL Server through ODBC instead?

[Anon]

SAF is used for remote database collections only, although what you stated is possible: pushing data from each monitoring node into SQL Server individually, it would be repititive steps for each monitoring node, what if there are 10+ monitoring nodes? You will need to edit the password configuration and start the database collection on each node. Better to leverage the managing node as the main consolidation node to configure only once. I hope that helps.