Database Doctor

Use this window to start and stop the Database Doctor and view its diagnoses. This window has the following sections:

Status
Diagnoses
Parameters

Status section

This section displays the status of the Database Doctor and enables you to stop and restart it. If the green light on the left is lit, then the Database Doctor is running. If the red light on the right is lit, then the Database Doctor is stopped.

The Database Doctor is defined for this partition	Indicates that the Database Doctor has been defined for the current partition
The Database Doctor is running on node <node_name>	Indicates that the Database Doctor has been defined for the specified node

Diagnoses section

Diagnosis date	Indicates the dates when the Database Doctor ran and produced a diagnosis. Select the diagnosis date that you want to view.
View	Displays the diagnosis for the selected date

Parameters section

Run the Database Doctor on this day	Indicates the day of the week that you want the Database Doctor to run on a weekly basis
Run the Database Doctor at this time	Indicates the time of day that you want to run the Database Doctor
Diagnosis level	Indicates the level of detail to include in the diagnosis. Cursory includes only database-level diagnostics, including index health, and storage limits. Basic includes common problems that can be diagnosed by simple queries. Thorough includes any problem that can be diagnosed by a simple database query. Exhaustive includes any problem that requires the execution of a query for diagnosis.
Save	Saves your changes
Cancel	Discards your changes

The following parameters are available for Oracle databases only. For other databases, these options are disabled.

Use histograms for non-uniform columns	Indicates whether Oracle should build histograms to clarify the distribution of values for columns that are nonuniform
Sample statistics for large tables	Indicates whether to use a small sample of data from larger tables for statistical analysis
Sample percent	Indicates the percent to use when sampling statistics from large tables
Rebuild all indexes during next run	Indicates whether to rebuild all indexes the next time the Database Doctor runs. The default setting for this parameter is off, because rebuilding indexes should not be required frequently. Select this parameter if you want to rebuild the indexes. KANA Response turns the parameter off again after the next run.
Rebuild monotone indexes during next run	Indicates whether to rebuild indexes for columns whose entries are consistently increasing or decreasing. This parameter singles these indexes out because they are more likely to become unbalanced. The default setting for this parameter is off. Select this parameter if you want to rebuild the indexes. KANA Response turns the parameter off again after the next run.

The following parameters are available if LDAP is enabled.

Check LDAP Users and Groups next run

This is only applicable when server side LDAP integration is enabled with Kana DS. This is for the case of Response integrated with KANA SEM Chat. This button ensures that the same users and groups exist in Response as in LDAP and that each user in Response is in the same groups in LDAP

Learn about the database doctor.

Learn about System Administration.

Learn about rule processors.

Learn about e-mail log files.