Chatta subito con l'assistenza
Chat con il supporto

Foglight for Oracle (Cartridge) 7.3.0 - 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

Adding CRS Agents for Monitoring Clusterware

Receiving alarms about the CRS software, which is used for monitoring Oracle Clusterware, requires creating CRS agents.

* 
NOTE: The Monitor More Clusterwares wizard supports the monitoring of a single CRS cluster. Configuring multiple CRS clusters for monitoring requires re-running the wizard for each cluster.
To add agents for monitoring Clusterware:
1
Click the Oracle tile.
2
Go to the CRS tab.
3
Click Monitor more Clusterwares at the upper left corner above of the Databases table.
The Monitor More Clusterwares wizard opens.
4
In the Configure CRS Agent screen, use the CRS agent name field to set a user-defined name for the agent. Alternatively, accept the default name provided for the CRS agent.
5
Select the requested platform for the CRS nodes: either UNIX or Windows.
6
Click Next.
7
Use the Configure Nodes for Monitoring screen to add the requested CRS nodes, using either of the following methods:
•
Adding the nodes manually — go to Step 14 on page 16.
* 
IMPORTANT: Adding the nodes manually requires specifying the CRS_HOME.
•
Discovering the nodes — proceed to Step 8.
8
Click Add Nodes, and from the menu select Discover by cluster node.
The Discover Nodes dialog box opens.
9
Use the Node Details section to enter the following details:
•
Node name — the name of one of the nodes, through which all other nodes in the cluster are to be discovered.
•
CRS_HOME (optional) — the path to the CRS Home directory.
If this field is left empty, the installer automatically detects the path (recommended).
10
Use the OS Credentials section to enter the OS credentials of the requested user.
* 
IMPORTANT: Ensure providing a user that has permissions to execute CRS utilities.
e
To select existing credentials using the Foglight lockbox mechanism, click Select from stored credentials...
The Stored Credentials dialog box that appears now allows reviewing the login credentials and authentication methods used for logging in to Foglight.
f
Foglight stores encrypted credentials in lockboxes, which may be password-protected for added security. The default lockbox is DB-Agent Lockbox. If credentials have already been entered in another lockbox, use the Lockbox list to select from that lockbox
11
Fill in the other details (optional) and click Apply.
12
The wizard tries to connect to the node specified, and through this node to all other nodes that take part in the CRS cluster. All nodes are validated for OS connectivity and the permissions of the provided user are verified.
After this process completes, nodes that were successfully validated appear in the table with the status Connection verified, while other nodes display the relevant error message (for example: Failed to establish connection to host).
13
Click the error message to view the error. To handle the issues indicated in the message, click Set credentials, enter the correct details and click Apply, then proceed to Step 19 on page 16.
* 
IMPORTANT: If the error results from specifying the wrong host, click Remove and repeat the node addition process.
14
Start the process of manually adding cluster nodes for monitoring by entering the CRS_HOME of the requested cluster.
Click the CRS_HOME link at the bottom of the screen.
The Edit CRS Home dialog box opens.
15
Enter the path of the requested CRS_HOME, then click OK.
16
Click Add nodes.
17
Select the option Add manually.
The Add CRS Nodes dialog box opens. This dialog box is similar to the Discover Nodes dialog box, with the exception of the CRS_HOME parameter that has already been configured.
18
Follow Step 9 to Step 13, then proceed to Step 19.
19
Click Next.
The agent is now created, based only on nodes that have been validated.
After the agent’s creation completes, monitoring starts automatically, and the Summary screen appears, displaying the newly created agent with all its components.
20
Click Finish to return to the Databases dashboard.
The CRS tab now displays data about all newly monitored nodes.
Modifying the Clusterware Monitoring Settings

After the CRS agents have been configured for monitoring, their monitoring settings can be modified using the Agent Settings button.

* 
IMPORTANT: Unlike Foglight for Oracle instances, the agent properties of CRS agents cannot be modified using the Databases Administration dashboard, but only through the default Foglight tools (see Foglight Administration and Configuration Guide). Clicking Agent settings and selecting the Administration option only allows re-running the wizard used for configuring the instances for monitoring, and changing the options defined using this wizard.
To modify the CRS monitoring settings:
1
Select the requested CRS agents.
2
Click Settings.
3
Select Configure CRS agent to re-run the wizard used for configuring the agents for monitoring, and change the options defined using this wizard.
4
Select the requested option for changing the agent’s monitoring:
•
Start monitoring
•
Stop monitoring
•
Remove from monitoring

Adding Agents for Monitoring Exadata Environments

To add agents for monitoring Exadata environments:
1
Click the Oracle tile.
2
Go to the Exadata tab.
3
Click Monitor at the upper left corner above of the Databases table.
The Monitor More Exadata Environments wizard opens.
On the first screen of this wizard, Monitor Exadata, use the Exadata agent name field to set a user-defined name for the agent. Alternatively, accept the default name provided for the Exadata agent.
4
Click Next.
Use the next screen, Monitor InifiniBand Switches, to configure the InfiniBand switches for monitoring, either by adding the switches manually or by discovering by switch name. Configuring the switches for monitoring allows retrieving InfiniBand topology information, as well as automatically detecting the Exadata cells.
* 
IMPORTANT: This screen is optional; if you prefer not to monitor the InfiniBand switches, you can skip this stage by clicking Next and proceeding directly to configure the Exadata cells for monitoring. In such a case, go to step 13.
5
Click Add switches.
6
From the menu that appears now, choose the requested option:
•
Add manually — go to Step 7 on page 18.
•
Discover by switch name — go to Step 9 on page 18.
7
Select the option Add manually.
The Add InfiniBand Switch dialog box opens.
Use this dialog box to add all requested InfiniBand switches that are monitored by the same credentials (user name and password), by entering a comma-separated list of all the names of the hosts on which these switches reside.
To add switches that would be monitored by a different credentials set, click Apply and repeat the process with the other credentials.
To edit the credentials of an existing switch, use either of the following methods:
•
For a single switch, click Set credentials on the switch’s Status row.
•
For multiple switches, select the check boxes near the requested switch and click Set credentials.
The Set credentials dialog box opens. This dialog box is identical to the Add InfiniBand Switch dialog box, except for the host name that cannot be modified after it was set.
To edit a single switch name, click the Switch name column. In the Edit Switch Name dialog box that appears, use the Switch name field to enter a new name for the switch.
* 
IMPORTANT: The switch name specified must be taken from the list displayed by running the ibswitches command.
8
After adding all requested switches, click Next to proceed to Step 12.
9
Select the option Discover by switch name.
The Discover InfiniBand Switches and Cells dialog box opens.
10
Use this dialog box to enter the host name and login credentials of a single InfiniBand switch, to be used for the discovery of all switches and cells.
11
After adding all requested details, click Apply and then click Next to proceed to Step 12.
12
The following screen, Monitor Exadata Cells, contains a table that lists all of the Exadata Cells that were automatically discovered when the InfiniBand switches were configured for monitoring. If the stage of configuring InfiniBand switches was skipped, this table is empty and cells need to be added manually.
13
Click Add cells.
The Add Cells dialog box opens.
Use this dialog box to add all of the requested Exadata cells that are monitored by the same credentials (user name and password), by entering a comma-separated list of all the names of the hosts on which these cells reside.
To add cells that would be monitored by a different credentials set, click Apply and repeat the process with the other credentials.
To edit the credentials of an existing cell, use either of the following methods:
•
For a single cell, click anywhere on the switch’s Status row.
•
For multiple cells, select the check boxes near the requested cells and click Set credentials.
The Set credentials dialog box opens. This dialog box is identical to the Add Cells dialog box, except for the host name that cannot be modified after it was set.
14
Click Apply.
After the connectivity and credentials were successfully validated, all cells appear with the status Connection Verified.
15
Click Next.
The agent is now created, based only on switches and cells that have been validated.
After the agent’s creation completes, monitoring starts automatically, and the Summary screen appears, displaying the newly created agent with all its components.
16
Click Finish to return to the Databases dashboard.
The Exadata tab now displays all newly monitored cells, along with partial monitoring data. To view in-depth data about the Exadata environment, click the Home page button on the Exadata tab to access the Exadata drilldown. For details, see Reviewing Exadata-related Information .

Modifying the Exadata Monitoring Settings

After the Exadata agents have been configured for monitoring, their monitoring settings can be modified using the Agent Settings button.

* 
IMPORTANT: Unlike Foglight for Oracle instances, the agent properties of ASM instances cannot be modified using the Databases Administration dashboard, but only through the default Foglight tools (see Foglight Administration and Configuration Guide). Clicking Agent settings and selecting the Administration option only allows re-running the wizard used for configuring the agents for monitoring, and changing the options defined using this wizard.
To modify the Exadata monitoring settings:
1
Select the requested Exadata switch.
2
Click Settings.
3
Select Configure Exadata agent to re-run the wizard used for configuring the agents for monitoring, and change the options defined using this wizard.
4
Select the requested option for changing the switch’s monitoring:
•
Start monitoring
•
Stop monitoring
•
Remove from monitoring

Adding Data Guard Environment

* 
IMPORTANT: Before configuring a new complete Data Guard environment via the Data Guard tab, you should add to monitoring its Primary database and Standby database using the Oracle Instances > Monitor dashboard; otherwise you will not be able to add these databases to the configured Data Guard environment. Creating a new Data Guard environment via the Data Guard tab is an optional feature which provides detailed visibility into your data guard environments performance and stability. For more information about how to add the Primary database and Standby database, refer to Installing and Monitoring a Single Oracle Instance .
To add an Oracle Data Guard environment:
1
On the Databases dashboard, click the Data Guard tab, and then click Monitor.
The Configure Data Guard Environment wizard appears.
2
Configure Data Guard Environment: specify the Data Guard environment name or use a default name, and then click Next.
3
Configure Primary Database, and then click Next.
1
Click Add database. The Add New Primary Database dialog box appears.
2
Choose a database from the Choose Primary Database drop-down list.
3
Specify the login credentials that are used to connect to the Primary database. There are two options:
•
Specify login credentials with sysdba privileges checkbox is not checked: The monitoring of the Primary database will be with already defined db user.
•
Specify login credentials with sysdba privileges checkbox is checked: The monitoring of the Primary database will be with a new user that has SYSDBA privileges. In this case the SYSDBA credentials will be saved in the agent.
* 
NOTE: We recommend to monitor the primary database with sysdba system privilege for better supporting during switchover.
When data guard switch over between primary and standby, standby database agent will be able to connect to the database with sysdba system privilege and retrieve data.
4
Configure Standby Database, and then click Next.
1
Select from the list which Standby databases you want to monitor.
2
For each selected database choose from a list its monitored agent. If the relevant agent is missing in the list, check that this database is already monitored. If not, add this database to monitoring using the Oracle Instances > Monitor dashboard.
3
Specify the login credentials that are used to connect to each Standby database. There are two options:
•
Specify login credentials with sysdba privileges checkbox is not checked: Monitoring the Standby database with already defined db user. You still need to provide an user with SYSDBA privileges for verification. The SYSDBA credentials will not be saved in the agent.
•
Specify login credentials with sysdba privileges checkbox is checked: Monitoring the Standby database with a new user that has SYSDBA privileges. In this case the SYSDBA credentials will be saved in the agent.
* 
NOTE: We recommend to monitor the standby database with sysdba system privilege to enable retrieving data when the standby is in mount mode. Monitoring with a normal user (unchecked sysdba), the agent will not be able to retrieve any data when the standby is in mount mode.
5
Summary: find the list of all databases that were configured for a new Data Guard environment. If all details are correct click Finish.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione