Application Troubleshooting

Problem

The following section outlines how to gather a summary report for all oracle database instances at the end of each scan. This output can also be extended to provide more details analysis of why a database may have failed to scan. These groupings are based of iQuates interpretation of the various errors that may occur and are a best effort to provide the client with some troubleshooting guidelines.

Solution

From the iQSonar-Data(2.9+) database run:

                      EXEC troubleshooting_se 'application Summary'

This will return results like:

794	Application: Total Targets
454	Application: Total Fully Scanned
241	Application: Total Partially Scanned
99	Application: Total Unscanned
69	Application: Total Unscanned, Access Denied
21	Application: Total Unscanned, Missing Discovery
0	Application: Total Unscanned, Uniqueness Failure
9	Application: Total Unscanned, Generic Failure

Please note that running this stored procedure will delete all contents of the Applicationtroubleshooting table and recreate it with the latest information. The SQL below will run return the results of the querey using cached information only. This query is faster to run as the Applicationtroubleshooting table will not be cleared and rebuilt. The ,1 extension can be used at the end of any execution of the troubleshooting_se strored procedure.

Related articles