Chatta subito con l'assistenza
Chat con il supporto

Foglight for Oracle (Cartridge) 5.9.3.20 - User Guide

Installing and Configuring Agents Using Foglight for Oracle
Viewing the Databases Dashboard Assigning Instances to Users Selecting an Instance to Monitor Foglight for Oracle Overview Dashboard Overview view Advisories view SQL Performance Investigator (SQL PI) Oracle Activity Drilldown Pluggable Databases Drilldown Storage Drilldown Reviewing Configuration Settings Reviewing the Alert Log Reviewing Monitored Data Guard Environments Reviewing ASM Instances Reviewing Exadata-related Information
Administering Foglight for Oracle Reporting Reference Glossary

Overview

Overview

Any upgrade of Foglight for Oracle to the latest version, which is not met by similar upgrade of the database cartridge components, is detected upon opening the Databases dashboard, when the upgrade wizard starts automatically.

Selecting the check box at the bottom left of the screen prevents this wizard from appearing when entering the Databases dashboard. Nevertheless, if several database cartridge components still require upgrade, the need to upgrade them is indicated in the dashboard. The indication is evident both in the caption Upgrade required, which is displayed in red to the right of the requested instance, and in the button Upgrade, which appears only if upgrade is required.

 
* 
NOTE: Even though instances whose components need to be upgraded appear in the Databases table, such instances cannot be accessed by clicking them, until they have been fully upgraded.

Running the Upgrade Wizard

Running the Upgrade Wizard
To upgrade the requested instances:
1
Click Upgrade.
The screen that appears now is the same screen that appears by default upon entering the Databases dashboard when one or more database cartridge components require upgrading. While the need for upgrade is indicated for both Foglight for Oracle and Foglight for Oracle, the upgrade is carried out separately for each database cartridge type.
2
Click Foglight for Oracle.
A Welcome page displays What’s New in this release, including bug fixes. At the bottom of the New Features table, is a link to the Rule Modification Overview page, where you can review the list of rules that have been modified and are in the following states:
•
Removed — The rule is obsolete and was deleted from the Management Server.
•
New — The rule is new in this release. To review its definition, click View new rule.
•
Updated — The rule was updated in this release. To review the updated rule, click View updated rule. If a rule targeted for update was modified by a user, the user’s modified rule is copied and disabled before the updated rule is installed. To review the modified rule, click View user-updated rule.
 
* 
TIP: To avoid having to repeat rule modifications after an upgrade, do not edit rules with the DBO prefix in the Rule Management dashboard. Use the Alarms view on the Databases Administration dashboard instead. When you make your edits on the Alarms view, the edits are saved separately and applied over the predefined rules. For instructions, see Customizing Alarms for Foglight for Oracle Rules .
3
If SQL Performance Investigator is not configured, proceed to Step 5.
4
If SQL Performance Investigator is configured, the SQL PI repository must be upgraded prior the agents upgrade.
5
Select the Agent Managers to upgrade.
 
* 
NOTE: The Other Agents column in the table indicates whether the specified Foglight Agent Manager runs agents of other cartridge types. If a value is displayed in this column, go to Dashboards > Administration > Agents > Agent Status to view which other agents run under the specified Foglight Agent Manager. If the other agents appear in the list below, upgrading Foglight Agent Manager to the latest version is safe. For agents of any other cartridge type, consult the documentation of the respective cartridge types.
•
DB_DB2_*
•
DB_SQL_Server_*
•
DB_Oracle_*
•
Sybase_MDA
•
UnixAgent
•
WindowsAgent
6
Click Upgrade the selected Foglight Agent Managers.
A progress bar appears.
7
After the upgrade is complete, click Next.
The next screen is used for granting privileges to users that were detected as possibly requiring additional privileges to ensure full functionality.
8
Select the agents displayed in the table and click Validate connectivity.
9
If the status row of one or more agents displays the status Insufficient privileges, complete the following steps:
a
Select all agents that require privileges updates, and click Grant privileges.
b
In the Grant Database Privileges dialog box, enter a SYSADMIN user name and password.
c
To view the script used for granting the privileges, click View script.
 
* 
IMPORTANT: The script for granting privileges is invoked using a popup. To view the script, ensure that pop ups are not blocked on the page.
d
Click Grant database privileges.
10
Foglight Performance Analysis is no longer supported and has been replace by the SQL Performance Investigator. All Instances that are configured to use Foglight Performance Analysis will be deprecated and replace with the SQL Performance Investigator capabilities.
During this process you are prompted to select a dedicated Agent Manager on which to install an external database repository. The SQL PI configuration will take into account the resources needed for monitoring with SQL PI and will prompt you with further information.
All information regarding the resource allocations needed for SQL PI monitoring can be found in the Foglight for Databases Deployment Guide.

Migrating Agents

The SQL Performance Investigator extension is only supported on Windows 64-bit and Linux 64 (Red-Hat 6, SUSE 11 and CentOS 6). As a result, you may need to migrate Oracle agents from an Agent Manager running on Linux to a Windows Agent Manager.

In addition, the migration tool allows you to perform resource balancing between the agent managers running Oracle agents with and without the SQL PI extension installed.

To migrate an agent to a different Agent Manager:
1
Open the migration wizard by navigating to Dashboards > Databases> Support Dashboard.
2
Select the Agent Manager that will be the destination host for the migrated Oracle Agents. Click Next.
3
On the Oracle Agents for Migration pane, the left-hand column displays a list of available Agent Managers. Select an Agent Manager to view a list of the agents installed on it.
4
From the list, select the agents that you want to migrate and move them to the Agent Manager Destination column.
5
If required, select agents and set the Windows credentials.
6
Click Next to migrate the agents.
7
When migration has completed, click Finish to exit the Wizard.

About Monitoring Extensions

During the installation process you can choose to install and configure one or more of the monitoring extensions. The monitoring extensions provide a more in-depth analysis of the monitored instance and the environment it is running on, creating a whole and unified status.

SQL Performance Investigator Extension

SQL Performance Investigator allows you to rapidly identify bottlenecks, anomalies, and application trends by focusing on top resource consumers and providing multi-dimensional SQL domain drilldowns. SQL PI allows you to:

•
Monitor real-time Oracle database performance at a glance
•
Gather and diagnose historical views
•
Identify and anticipate performance issues
•
Analyze and optimize execution plan changes
•
Compare day-to-day values to identify anomalies and application changes
 
* 
NOTE: SQL Performance Investigator requires a license. If you are using a trial version and would like to request pricing, contact https://www.quest.com/register/57891.
* 
NOTE: SQL PI requires a repository database that is installed automatically on the Agent Manager.
Operating System Extension

Monitoring the operating system allows you to identify resource consumption and provides a full view of the server health. An Infrastructure agent, which is created automatically as part of the monitoring process, monitors the operating system.

 
* 
NOTE: The Operating System extension is enabled by default.
VMWare Extension

Monitoring the VMWare system allows you to identify resource consumption and provides a full view of the data center and ESX health when the server is part of a VMWare environment.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione