Chat now with support
Chat with Support

Foglight for Oracle (Cartridge) 6.3.0 - Release Notes

Monitoring an Instance that is Part of a Data Guard Environment

To monitor a data guard environment with a physical standby (Redo Apply):
1
Make sure that the Standby Database is in receiving mode.
2
Use SQLPLUS to connect to the Primary Database as SYS user.
3
Create the standby Foglight schema owner.
4
From the Primary Database, run the grant privileges script on the standby user created in Step 3 to stay in that mode after the check.
5
Open a web browser and run the Oracle Monitoring Installer wizard.
6
Select Add a New Instance.
7
Specify the Standby Database credentials and connection details (the user that was created in Step 3).
8
Click Verify Connectivity.
9
If the Standby Database is mounted, click on validate standby button.
10
After the verify process is complete, the next step is to monitor the physical Standby Database.
To monitor a data guard environment with logical standby (SQL Apply):
1
Use SQLPLUS to connect to the logical standby as SYS user.
2
Create the standby Foglight schema owner.
3
Open a web browser and run the Oracle Monitoring Installer wizard.
4
Continue the discovery process as usual, using the logical standby user credentials and connection details.
5
Click Verify Connectivity.
6
Once the connectivity verification is completed, the next step is to monitor the logical standby database.

Supported platforms

Foglight for Oracle supports monitoring the following platforms:

•
Supported Oracle® Database Versions:
•
10g and above
•
Supported Oracle Editions (all):
•
Enterprise Edition
•
Standard Edition
•
Standard Edition One
•
Standard Edition 2
•
Express Edition
•
Personal Edition
•
Supported Operating Systems:
•
All Operating systems supported by Oracle.

 

* 
NOTE:  
•
Foglight for Oracle supports monitoring the Amazon Relational Database Service (Amazon RDS™).
•
SQL PI extension supports Oracle versions 11gR1 and later.

Linux on System Z (z/Linux) support

Foglight for Oracle fully supports monitoring of instances that are installed on a z/Linux operating system. The supported monitored instances versions are the same as specified in the list.

Troubleshooting

This section provides a list of references which address the most commonly faced issues relating to remote connectivity, allowing for easy troubleshooting using the vendor's information knowledge base:

•
To verify TCP/IP connectivity for SQL statement collections, Management Studio (SSMS) cannot be used as other protocols may be leveraged. Instead, verify connectivity using a UDL as detailed here: https://support.microsoft.com/kb/308075/.
•
To verify the WMI connectivity using a Microsoft Windows built-in utility, see https://technet.microsoft.com/en-us/library/cc180684.aspx.
•
To troubleshoot WMI access permissions, see http://blogs.technet.com/b/askperf/archive/2007/08/14/wmi-troubleshooting-permissions.aspx.
•
For information about WMI connectivity from Windows Server 2003/Vista and later versions, see http://msdn.microsoft.com/en-us/library/aa822854(VS.85).aspx.
•
For WMI troubleshooting tips and techniques, see http://msdn.microsoft.com/en-us/library/aa394603(VS.85).aspx.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating