3.5 QDBComponentsHealth

Use this Knowledge Script to monitor the health of NetIQ AppManager repository (QDB) and management server components.

This script monitors SQL Server resources associated with the QDB, including the percentage of database space and log space used, the time taken for a SQL command or query to execute, missing data tables and the status of AppManager scheduled tasks. If a service or job is down, this script can restart it.

This script monitors the data tables in the repository and raises an event if the previously created data tables and the future data tables are missing. An event is raised at the first occurrence of the missing data table and thereafter every 24 hours if the data tables are missing.

NOTE:The Knowledge Script raises an event automatically if the future data tables are missing in the repository.

This script monitors the data available in the Data Rejected table and if the data exceeds the threshold, an event is raised. The Data Rejected table contains data that are unable to link to its corresponding jobs because of the corrupted data headers or the corresponding jobs are missing.

If the QDB does not have an AppManager agent installed on it, Discovery_AMHealth discovers the QDB components on the management server. As a result, the service and database monitoring parameters for this script run remotely. In this situation, you must have sufficient privileges on the service account for the NetIQMC service on the management server so that the service account can remotely access the SQL Server service on the QDB to obtain its status.

If the account does not have proper privileges, the script will be unable to access the service status and will report that the SQL Server service is down even when it is not. If you do not have sufficient access for the service account for the NetIQMC service, deselect the Raise an event if SQL Server services are down and Restart SQL Server services that stop unexpectedly parameters in this script to avoid raising unnecessary events.

You can set this script to raise an event for the following conditions:

SQL Server services are down or have been restarted.
SQL jobs are disabled, missing, or have failed.
Database or log space is low.
The management server isn't connected to the QDB database.
The management server service is down.
SQL Server queries against the QDB are taking too long to process.
Database or log space is low, and there is insufficient disk space for further growth.
Data in the Data Rejected table exceeds the specified threshold value.

When monitoring management server performance, QDBComponentsHealth does not use the standard method of creating events through the management server, because the problem being detected might prevent events from being generated through the management server. As a result, this script generates events for these conditions directly in the QDB, and Action scripts will not operate with certain QDBComponentsHealth parameters to generate actions when the conditions occur. Because these events are generated directly in the QDB, event collapsing is always enabled for these events, and it cannot be turned off.

The following QDBComponentsHealth parameters related to management server monitoring will not generate actions:

Raise an event if the management server service is down?
Raise an event if the management server service fails to restart?
Raise an event if the management server service restarts successfully?
Raise an event if the management server service is not connected to the QDB?
Raise an event if data map file usage exceeds threshold?
Raise an event if event map file usage exceeds threshold?
Raise an event if job map file usage exceeds threshold?

If you do not have an agent installed on the QDB server, the repository component gets discovered on the management server. If you try to remotely monitor the QDB from the management server using the QDBComponentsHealth script, the script will not be able to obtain the disk information remotely.

As a result, if the repository component is monitored remotely from the management server by the QDBComponentsHealth script, the following QDB component monitoring parameters under the SQL Server File Size and Growth Settings Monitoring Event Notification Knowledge Script section will not be available:

Raise an event if insufficient space available for further file growth?
Raise an event if SQL Server maximum file size exceeds available disk space?

3.5.1 Resource Objects

AppManager repository (QDB) server
management server

3.5.2 Default Schedule

The default interval for this script is every thirty minutes.

3.5.3 Setting Parameter Values

Set the following parameters as needed:

Parameter	How to Set It
General Settings
Job Failure Notification
Raise event if job fails unexpectedly?	Select Yes to raise an event if the AMHealth_QDBComponentsHealth fails unexpectedly. The default is Yes.
Event severity when job fails unexpectedly	Set the event severity level, from 1 to 40, to indicate the importance of an event in which this Knowledge Script job fails or any other unexpected event occurs. The default is 5.
Additional Settings
Event Details
Event detail format	Select the format in which you want to display the event detail. You can select from HTML Table or Plain Text. The default is HTML Table.
Event Notification
Raise an event if SQL Server services are down? (Use MC based Action Script for notification)	Select Yes to raise an event if SQL Server services are down. The default is Yes. Tip Use Action Script for notification, as the QDB will not be available.
Event severity when a SQL Server service is down	Set the event severity level, from 1 to 40, to indicate the importance of an event in which a SQL Server service is down. The default is 5.
Restart SQL Server services if the services are stopped unexpectedly?	Select Yes to restart the SQL Server services if the services stop unexpectedly. The default is Yes.
Raise an event if a SQL Server service restart fails?	Select Yes to raise an event if a SQL Server service fails to restart. The default is Yes. Tip Use Action Script for notification, as the QDB will not be available.
Event severity when a SQL Server service fails to restart	Set the event severity level, from 1 to 40, to indicate the importance of an event in which a SQL Server service fails to restart. The default is 5.
Raise an event if a SQL Server service restart succeeds?	Select Yes to raise an event if a SQL Server service restart succeeds. The default is Yes.
Event severity when a SQL Server service restarts succeeds	Set the event severity level, from 1 to 40, to indicate the importance of an event in which a SQL Server service restarts successfully. The default is 30.
Raise an event if the Management Server service is not connected to the QDB?	Select Yes to raise an event if the management server service is not connected to the QDB. The default is Yes.
Event severity when the Management Server service is not connected	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the management server service is not connected. The default is 5.
Raise an event if the QDB SQL jobs are missing?	Select Yes to raise an event if the QDB SQL jobs are missing. The default is Yes.
Event severity for missing QDB SQL jobs	Set the event severity level, from 1 to 40, to indicate the importance of an event in which QDB SQL jobs are missing. The default is 15.
Raise an event if QDB SQL jobs are disabled?	Select Yes to raise an event if QDB SQL jobs are disabled. The default is Yes.
Event severity for disabled QDB SQL jobs	Set the event severity level, from 1 to 40, to indicate the importance of an event in which QDB SQL jobs are disabled. The default is 15.
Enable QDB SQL jobs if they are disabled?	Select Yes to enable QDB SQL jobs if they are disabled The default is No.
Event severity when QDB SQL jobs cannot be enabled	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the QDB SQL jobs cannot be enabled. The default is 15.
Raise an event if attempt to enable QDB SQL jobs succeeds?	Select Yes to raise an event if the attempt to enable the QDB SQL job succeeds. The default is No.
Event severity when attempt to enable QDB SQL job succeeds	Set the event severity level, from 1 to 40, to indicate the importance of an event in which an attempt to enable the QDB SQL job succeeds. The default is 20.
Raise an event if a QDB SQL job fails?	Select Yes to raise an event if a QDB SQL job fails. The default is Yes.
Event severity when a QDB SQL job fails	Set the event severity level, from 1 to 40, to indicate the importance of an event in which a QDB SQL job fails. The default is 20.
Raise an event if QDB disks are fragmented?	Select Yes to raise an event if AppManager detects QDB disk fragmentation. The default is unselected. Tip To avoid errors when running this script on a Windows Server 2008 server, disable User Account Control (UAC).
Event severity for QDB disk fragmentation	Set the event severity level, from 1 to 40, to indicate the importance of an event in which a disk is fragmented. The default is 15.
Raise an event if QDB file size exceeds threshold?	Select Yes to raise an event if the QDB file size exceeds the threshold you set. The default is Yes. NOTE:This parameter is applicable only on AppManager 9.1 running on SQL Server Express edition.
Threshold - Maximum QDB file size	Specify how large the QDB file size can grow before raising an event. If the QDB file size is too small, AppManager performance will not be optimal in larger environments. The default is 8 GBytes.
Event severity when QDB file size exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the QDB file size exceeds the threshold. The default is 20.
Raise an event if the query process time exceeds threshold?	Select Yes to raise an event if the query process time exceeds threshold. The default is Yes.
Threshold -- Maximum process run time	Specify the longest process run time allowed before an event is raised. The default is 300 seconds.
Event severity when query process time exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the query process time exceeds the threshold you set. The default is 5.
Event severity when attempt to retrieve query process time fails	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the attempt to retrieve query process time fails. The default is 10.
Raise an event if unable to retrieve QDB component information?	Select Yes to raise an event if AppManager is unable to retrieve QDB component information. The default is Yes.
Event severity when unable to connect to retrieve QDB component information	Set the event severity level, from 1 to 40, to indicate the importance of an event in which AppManager is unable to connect to retrieve QDB component information. The default is 10.
Raise event if previously created data tables are missing in the repository?	Select Yes to raise an event if the data tables that were created in the repository are missing. The default is No.
Event severity when previously created data tables are missing in the repository	Set the event severity level, from 1 to 40, to indicate the importance of an event in which data tables that were created in the repository are missing. The default is 15.
Management Server Performance Monitoring
Raise an event if the Management Server map file is not enabled?	Select Yes to raise an event if the management server map file is not enabled. The default is Yes.
Threshold -- Current map file size	Specify the current map file size. If the map file size is too small, the management server performance will not be optimal in larger environments. The default is 5 MB.
Event severity if map file is not enabled	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the map file is not enabled. The default is 15.
Raise an event if current data rate per minute exceeds threshold?	Select Yes to raise an event if the current data rate per minute of the management server exceeds the threshold you set. The default is Yes.
Threshold - Maximum current data rate per minute	Specify the maximum data rate that the management server can handle before raising an event. The default is 4000 data rate per minute.
Event severity when current data rate per minute exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the current data rate per minute exceeds the threshold. The default is 15.
Raise an event if current event rate per minute exceeds threshold?	Select Yes to raise an event if the current event rate per minute of the management server exceeds the threshold you set. The default is Yes.
Threshold - Maximum current event rate per minute	Specify the maximum event rate that the management server can handle before raising an event. The default is 2000 events per minute.
Event severity when current event rate per minute exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the current event rate per minute exceeds the threshold. The default is 15.
Raise an event if data map file usage exceeds threshold?	Select Yes to raise an event if the data map file usage exceeds the threshold you set. The default is Yes.
Threshold -- Maximum data map file usage	Specify the highest level of data map file usage that can occur before an event is raised. The default is 80%.
Event severity when data map file usage exceeds the threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the data map file usage exceeds the threshold you set. The default is 15.
Raise an event if event map file usage exceeds threshold?	Select Yes to raise an event if the event map file usage exceeds the threshold you set. The default is Yes.
Threshold -- Maximum event map file utilization	Specify the highest level of event map file utilization that can occur before an event is raised. The default is 80%.
Event severity when event map file utilization exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the event map file utilization exceeds the threshold you set. The default is 15.
Raise an event if job map file usage exceeds threshold?	Select Yes to raise an event if the job map file usage exceeds the threshold you set. The default is Yes.
Threshold -- Maximum job map file utilization	Specify the highest level of job map file utilization before an event is raised. The default is 80%.
Event severity when job map file usage exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the job map file usage exceeds the threshold you set. The default is 15.
Monitoring SQL Server File Size and Growth Settings
Raise an event if insufficient space available for further file growth?	Select Yes to raise an event if there is not enough space for additional file growth on the SQL Server. The default is Yes.
Event severity for insufficient space	Set the event severity level, from 1 to 40, to indicate the importance of an event in which there is not enough space for additional file growth on the SQL Server. The default is 10.
Raise an event if SQL Server file growth rate is lower than the threshold?	Select Yes to raise an event if the SQL Server file growth rate is lower than the threshold you set. The default is Yes.
Threshold -- Minimum growth rate in MB	Specify the lowest possible growth rate for the SQL Server in MB. The default is 256 MB.
Threshold -- Minimum growth rate as a percentage	Specify the lowest possible growth rate for the SQL Server as a percentage. The default is 9%.
Event severity when file growth rate is lower than the threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the file growth rate is lower than the threshold you set. The default is 10.
Raise an event if Autogrowth is not enabled and file utilization exceeds the threshold?	Select Yes to raise an event if Autogrowth is not enabled, and file utilization exceeds the threshold you set. The default is Yes.
Threshold -- Maximum file utilization with Autogrowth disabled	Specify the highest percentage of file utilization with Autogrowth disabled before an event is raised. The default is 90%.
Event severity if Autogrowth disabled and usage exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which usage exceeds the threshold and Autogrowth is disabled. The default is 10.
Raise an event if SQL Server maximum file size exceeds available disk space?	Select Yes to raise an event if the SQL Server maximum file size exceeds the available disk space. The default is Yes.
Event severity when SQL Server file size exceeds disk space	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the SQL Server file size exceeds the available disk space. The default is 15.
Monitoring the Management Server Service
Raise an event if the Management Server service is down?	Select Yes to raise an event if the management server service is down. The default is Yes. NOTE:AppManager cannot create an event for this if the management server is down.
Event severity when the Management Server service is down	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the management server service is down The default is 10.
Restart the Management Server service if the service is down?	Select Yes if you want to restart the management server service if the service is down. The default is Yes.
Raise an event if the Management Server service restarts successfully?	Select Yes to raise an event if the management server service restarts successfully. The default is Yes. NOTE:AppManager cannot create an event for this if the management server is down.
Event severity when the Management Server service restarts successfully	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the management server service restarts successfully. The default is 25.
Raise an event if the Management Server service fails to restart?	Select Yes to raise an event if the management server service fails to restart. The default is Yes. NOTE:AppManager creates an event directly in the QDB if the management server fails to restart.
Event severity when the Management Server service fails to restart	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the management server service fails to restart. The default is 5.
Raise an event if agents are not FIPS- compliant?	Select Yes to raise an event if the agents are not FIPS-compliant. The default is Yes.
Event severity when agents are not FIPS-compliant	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the agents are not FIPS-compliant. The default is 10.
Raise an event if data in DataRejected table exceeds threshold?	Select Yes to raise an event if the job entries in the Data Rejected table exceed the Threshold type that you have selected. The default is Yes. NOTE:This parameter runs every 24 hours irrespective of the default interval of the Knowledge Script.
Threshold type	Select one of the following threshold types: Time duration for a job in the table: This threshold value corresponds to the maximum time period for which a job entry can exists in the Data Rejected table prior to the current iteration. When you select this threshold, you must specify the time in the Threshold- Maximum time for which a job exists in the table parameter. For example: If you specify the threshold as 60 minutes and the current iteration starts at 10 a.m., an event is raised if any job entry exists in the Data Rejected table for more than 60 minutes (1 hour) prior to 10 a.m. Number of job entries: This threshold value corresponds to the maximum number of job entries that can exists in the Data Rejected table. When you select this threshold, you must specify the count in the Threshold- Maximum number of entries of any job parameter.
Threshold- Maximum time for which a job exists in the table	Specify how long a job entry can exists prior to the current iteration in the Data Rejected table before an event is raised. The default is 60 minutes.
Threshold- Maximum number of entries of any job	Specify the maximum number of job entries that can exist in the Data Rejected table before an event is raised. The default is 50 counts.
Event severity when data in DataRejected table exceeds threshold	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the job entries exceed the threshold type that you specified. The default is 10.
Raise an event if job language is not matching with KS language?	Select Yes to raise an event if job language does not match with KS language. The default is Yes.
Threshold - maximum number of mismatches between job language and KS language	Specify the maximum number of mismatches, from 0 to 255, that can exist before an event is raised. Default value is 0.
Event severity when job language is not matching with KS language	Set the event severity level, from 1 to 40, to indicate the importance of an event, in which there is a mismatch between the job language and the KS language. Default severity is 5.
Data Collection
Collect data for database space utilization?	Select Yes to collect data for charts and reports. If enabled, data collection returns the percentage of the database data file currently being used. The default is No.
Collect data for log space utilization?	Select Yes to collect data for charts and reports. If enabled, data collection returns the percentage of the database log file currently being used. The default is No.
Collect data for Management Server connection status?	Select Yes to collect data for charts and reports. If enabled, data collection returns 100 if the management server is connected to the repository and 0 if the management server is not connected. The default is No.
Collect data for SQL Server service status?	Select Yes to collect data for charts and reports. If enabled, data collection returns 100 if the SQL Server service is up and 0 if the service is down. The default is No.
Collect data for Management Server current data rate per minute?	Select Yes to collect data for charts and reports. If enabled, data collection returns the current data rate of the Management Server. The default is No
Collect data for Management Server current event rate per minute?	Select Yes to collect data for charts and reports. If enabled, data collection returns the current event rate of the Management Server. The default is No
Collect data for Management Server data map file utilization?	Select Yes to collect data for charts and reports. If enabled, data collection returns the percentage of the management server data map file currently being utilized. The default is No.
Collect data for Management Server event map file utilization?	Select Yes to collect data for charts and reports. If enabled, data collection returns the percentage of the management server event map file currently being utilized. The default is No.
Collect data for Management Server job map file utilization?	Select Yes to collect data for charts and reports. If enabled, data collection returns the percentage of the management server job map file currently being utilized. The default is No.
Monitoring
SQL username	Specify the user name required to access SQL Server on the Control Center server. The SQL or Windows user must have at least Server Administrator rights in SQL Server. For more information, see the Configuring Security Manager for AM Health section in AppManager for Self Monitoring Management Guide.