Chatta subito con l'assistenza
Chat con il supporto

Foglight for Oracle (Cartridge) 5.9.5.10 - Release Notes

Resolved issues and enhancements

Resolved issues and enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Defect ID

Resolved Issue

GVFOG-177

Fixed an issue that in Databases - SQL PI dashboard, Workload line bars may display as blank even when Workload has value.

GVFOG-182

Fixed an issue that the Workload chart in Global view has different unit (sessions/s) from the one (seconds/s) in Overview.

FOGDG-1222

Fixed an issue that the CSV input file may be locked due to I/O has not been closed after executing CLI commands.

FOGDG-1234

Fixed an issue that when trying to migrate DB agent with IC agent monitoring, it failed an error message.

PIFOG-519

Fixed an issue that PI causes hundreds of sessions in the monitored Oracle database instance.

PIFOG-525

Fixed an issue when estimating agents total memory failed because of wrong function name.

PIFOG-532

Fixed an issue that the PI Engine uses incorrect 1m table name when the OS is using Thai Year Format.

ORAFOG-476

Fixed an issue that Foglight cannot save Oracle alarm configuration when choosing more than ten Oracle instances.

ORAFOG-820

Fixed an issue when editing a UDC in DBO cartridge version 5.9.4.10 failed.

ORAFOG-836

Fixed the temporary tablespace reports negative value on the tablespaces dashboard.

ORAFOG-847

Fixed an issue when creating a CRS agent for Oracle 18c installation failed.

ORAFOG-852

Fixed an issue when the setup agent in CLI mode has a lower-case instance name, it failed to add instance to data group.

ORAFOG-854

Fixed an issue that the Space Used (%) of recovery file sometimes is greater than 100% at Fast Recovery Area page.

ORAFOG-859

Fixed an issue that the rule ASM - Usability Connection Availability is not working for ASM agent.

ORAFOG-860

Fixed an issue during migration if only Oracle RAC agents was deployed in the FglAM, detecting Oracle RAC agents failed.

ORAFOG-861

Fixed an issue after generating to PDF, the Time Range in Oracle Instance Comparison report is not correct.

ORAFOG-862

Fixed the wrong client name in DB lock alarm (DB host is displayed instead of blocking client).

ORAFOG-877

Fixed an issue that monitoring CRS 19c failure due to alter.log cannot be found.

ORAFOG-881

Fixed an issue when Oracle has blocking lock in progress for 12C and above pluggable database, Blocking Lock dashboards display no data.


Known issues

Known issues

The following is a list of issues known to exist at the time of this release.

Cartridge-related issues

 

Defect ID

Known Issue

FOGDG-858

DB instance is still synchronized and displayed in FMS federation master even when it is stopped for some reason and not displayed in the FMS federation child.

ODB-2829

When running user-defined collections on dynamic tables, deleted items are still kept in the topology. As a result, the number of rows displayed on the user-defined collections table will exceed the configured value for maximum allowed rows.

ODB-2984

In the Global Administration > User-defined Collections screen, it is possible to create two collections that bear the same name with a different capitalization (for example: MyCollection and Mycollection); however, only one collection will appear in the topology, and be displayed on the User-defined Collections panel.

ODB-3029

Creation of user-defined collections for a RAC database should be executed by selecting the RAC agent itself and not the RAC and its nodes.

ODB-4002

Using the administration module to configure the sessions screen parameters for a single node in a RAC environment will result in all the RAC nodes being configured with the same parameter.

ODB-4417

User-defined collections that return a variant number of columns (such as select * from ...) will only retrieve the columns that existed during its creation. Any additional columns will be ignored.

ODB-6784

Version 5.6.4 and above of the product uses only SSH to connect to Unix hosts. Customers upgrading from previous versions of the product that were using telnet will now be converted to use SSH

ODB-6939

Customers that are monitoring instances using nslookup/IP and are upgrading to the new version of the product should create the infrastructure cartridge agents themselves manually.

ODB-7064

"Challenge response" credentials do not appear in the advanced lockbox pop up.

ODB-7171

The following metrics display NA when monitoring a RAC one node:

  • Paging

  • Page in

  • Page out

ODB-7208, ODB-7169

The current implementation does not support collecting listener data from remote Windows hosts using Windows local execution (the user that is currently running the agent manager).

ODB-7427

The Listener graphs under the Usability dashboard are not populated with data when monitoring RAC One Node.

ODB-7446

The following alarms are displayed in the RAC level instead of the instance level:

  • Usability Availability Single

  • Collection status

ODB-7452

Setting the connection details of a RAC One Node and failing the validation, will result in failure to save the changes.

ODB-7454

The invalid objects exclude list is not supported for RAC and RAC One Node.

ODB-7457

When converting RAC One Node to RAC the OS cluster failover alarm is triggered.

ODB-7463

Upgrading an instance that has a legacy OS cartridge installed on its host will result in creation of the database agent without the creation of the infrastructure agent.

Workaround: create the infrastructure agent manually.

ODB-8272, ODB-8128

Foglight for Oracle supports monitoring OS clusters residing on VMware machines only in the configuration of one OS cluster node per data center; monitoring is not possible if two or more cluster nodes are located on different data center, to provide disaster recovery.

ODB-8298

Upgrading an ASM agent that was created manually will result in a malfunctioning ASM agent that requires reconfiguration, unless the following fields in the agent settings are cloned: ASM Instances, Host Details, Environment Variables, Collection Details, and Exclude Diskgroups.

ODB-8697

The Exclude Tablespace feature allows inserting tablespaces only by using the Java regular expression syntax, rather than wildcards.

ODB-9129, ODB-9337

When selecting the RSA key connection type in the Exadata, ASM, and CRS installers, after loading the id_rsa file, the dialog box Add Cells is automatically refreshed, thereby resetting all other fields in the dialog box (Host name, User, Passphrase, Port, and sudo) and leaving them empty.

ODB-9143

Exadata, ASM and CRS agents are marked in the upgrade process as 'other agents', even thought they are Oracle agents and should be marked as such.

ODB-9215

The Global Administration does not support the CRS, Exadata and ASM agents. As a result, any modification of the settings of the collection frequencies, retention policies, alarms and email notifications for these agents can be carried out only using the default Foglight tools.

ODB-9290

The CRS installation wizard does not support using the connection type Local user, when the monitored host runs on UNIX.

Workaround: use command line installation (CLI) through the Silent Installer tool, which supports this configuration.

ODB-9291

Using a virtual name when creating a CRS agent is not supported by either the CRS installation wizard or the Silent Installer tool (command line installation); both tools only support using a physical name or an IP address.

ODB-9738

In an environment that includes a Foglight Agent Manager concentrator, when upgrading the environment where the concentrator does not contain any regular agents, the concentrator is not upgraded. Therefore, after the upgrade process takes place the Foglight Agent Manager concentrator has to be deployed manually.

ODB-9739

When editing the properties of the Foglight Agent Manager concentrator (Dashboards > Administration > Agents > Agent Status), the name of the Foglight Agent Managers should be entered in the Downstream FglAMs section exactly as they appear in the topology, under Home > Agents > All agents > <Agent name> > RMI data > Fglam host property.

ODB-9950

Oracle monitoring installer does not support validation for the required sudo commands. Therefore, the sudo user should be prepared before using it. For details, see Foglight for Oracle User Guide.

ODB-10015

The following secondary parameters are not cloned when creating an agent using the Oracle Monitoring Installer:

  • Collection Details and Environment Variables parameters in Exadata agent

  • Exclude Diskgroups parameter in ASM agent

Unless these parameters and cloned and modified by the user, the upgrade process will override them with the default values.

ODB-10060

When a UNIX-based Foglight Agent Manager, which is selected for monitoring a Windows-based Oracle or ASM cluster, is using virtual IP to connect to the Oracle or ASM instance, the OS connection validation fails.

Workaround: Use the virtual IP /physical IP/physical host name.

ODB-10154

In order to allow the agent to connect to the remote Windows Management Instrumentation (WMI) components on Windows Server 2008 R2 or Windows 7 systems, special registry settings are required. For details, see section Configuring Registry Settings for Windows Server 2008 R2 and Windows 7 in Agent Manager Guide.

ODB-10907

The following dashboards and views may be less responsive than others due to their complexity:

  • Storage > Tablespaces and Datafiles > Tablespace details > Free Space Fragmentation

  • Storage > Tablespaces and Datafiles > Datafile I/O Details > Fragmentation

  • Activity > Locks > Locks Tree (Current) tab & Locks Historical Tree tab

ODB-10918

Support for Oracle 12c has the following restrictions:

  • Oracle 12c Flex ASM is not supported.

  • On the database agents' Administration > Oracle > Collection Settings screen, the Tablespace Settings tab is disabled. Tablespace Storage collection settings cannot be edited for Oracle 12c.

ODB-11467

In environments configured to use Agent Manager in High Availability mode the chosen Agent Manager hosting the SQL PI repository will host watchdog and maintenance agents that cannot participate in the Agent Manager high availability utility.

ODB-12520

The following homepages were removed from the custom dashboards: Interconnect/GCS, Cluster Overview, Sessions, Instance identification and usability and Workload.

ORAFOG-197

The offloadEfficiency metric has been changed to be internal and inaccessible as of Exadata software version 12.1.2.3.0, which causes the Exadata dashboard shows 'n/a' in ID, Name, and Status columns.

ORAFOG-267

The Databases Global View dashboard shows negative and over 100% values for OS CPU metrics.

ORAFOG-308

History data is missing if user upgrades the Foglight for Oracle cartridge 5.7.5.37 using the SPM installer.

ORAFOG-313

The Activity > Storage dashboard stopped responding after clicking any chart in the Tablespaces view in FMS 5.7.1.

Workaround: Upgrade the Management Server to version 5.7.5 or later.

ORAFOG-315

Some error messages showed in the Management Server log, after disabling or enabling Alert log Groups. 

ORAFOG-323

The error "No views match input type of DBO_Drill_RealTime_InitializationParameters_Instance" shows on the Databases > Overview > Configuration  dashboard.

Workaround: This error only occurs on the Foglight Management Server 5.7.0. Upgrade your Management Server to a higher version.

ORAFOG-324

The error "For the value "Parameters", no view is set" shows on the Databases > ASM dashboard.

Workaround: This error only occurs on the Foglight Management Server 5.7.0. Upgrade your Management Server to a higher version.

ORAFOG-342

The 'ibprintca.pl -l' command has been deprecated, which causes the infiniband switch operation fails. 

ORAFOG-564

After switchover occurs in the Data Guard environment it takes one hour to see data in the Primary Redo Generation Rate/Standby Apply Rate/Transport Rate charts in the Performance dashboard when database is monitored with SYSDBA credentials.

ORAFOG-639

The Oracle agent fails to collect some OS related metrics after disabling and re-enabling the Foglight for Oracle cartridge.

Workaround: On the Agent Status dashboard, deactivate and re-activate the agent, and then wait for five minutes.  

ORAFOG-643

The destination_name property in the Data Guard dashboard is missing after disabling and re-enabling the Foglight for Oracle cartridge.

ORAFOG-660

Metrics of the monitored Host display n/a when an inactive host object binds to "OracleInstance.participatingHosts".

ORAFOG-668

In Monitor Oracle Instance dialog box, Agent Manager Host cannot be retrieved when the default FglAM is null and FglAM list contains the Agent Manager which version is lower than system required version.

ORAFOG-676

The Oracle upsince duration is miscalculated when FMS/FglAM and Oracle DB locate in different timezone.

ORAFOG-714

Foglight for Oracle fails to validate the connection and grant privileges to data guard agents during the upgrade.

Workaround: Skip the validation in upgrade page and go to the Administration > Connection Details dashboard. Change the user role from "Normal" to "SYSDBA", verify the connection and grant the privileges, and then save your changes.

ORAFOG-721

Unable to create agents to monitor RAC via Installer Wizard when RAC nodes only support connection with service name.

Workaround: Create an agent manually in the Agent Status dashboard, and then change its "monForceSid" in ASP to false. 

ORAFOG-734

If there are two credentials with the same account name existing in the Foglight Management Server, picking one credential in "Set Credential" and "Test connection" might cause the other credential to be updated as well.

ORAFOG-753

If you select either of DB_Oracle, DB_Oracle_UI, DB_Global_View_UI, SPIRepository* cartridges then click Reset on the Cartridge Inventory dashboard, the upgrade wizard will prompt again.

Workaround: Do the following:

1. Navigate to the Administration > Rules & Notifications > Manage Registry Variables dashboard.

2. Search for "DBO_Is_Fglams_Required_Upgrade registry".

3. Change its value to "-1".

ORAFOG-815

It fails to set up an agent to connect Oracle Dataguard 10g.
Note: Currently we only support Oracle Dataguard 11g and above.

n/a

Partial support of Logical Standby database.

 

SQL PI Repository

Defect ID

Known Issue

ODB-13128

PI agents that use the PI repository on Linux® stop working when upgrading the Foglight for Oracle cartridge.

It is recommended to recreate these agents on a Windows®-based PI repository.

ORAFOG-329

PI extension cannot be enabled for DB agents that are deployed on mixed environments (Linux® and Windows®).

Workaround: Use the same version of DLP for both Linux and Windows environments. See the Knowledge Article 215534 for details.

PIFOG-405

When a blocking condition is detected in Oracle monitoring, the SQL text is missing for the blocking session. This is seen in both SQL PI > Blocking History tab and Activity > Locks dashboard.

PIFOG-431

After DB agent restart, there will be a 5 minutes data gap in the SQL PI baseline view.

n/a

In case SQL PI for Oracle is monitored side by side with SQL PI for SQL Server, you must upgrade both Foglight for SQL Server and Foglight for Oracle cartridges to the same version.

n/a

On mixed Windows and Linux environments, SQL PI stops monitoring after upgrading the Foglight database cartridge to 5.7.5.30 and higher.

Workaround: Perform the procedure described in the Knowledge Article 212566. If you are upgrading from 5.7.5.30 (and higher) to version 5.9.2.1 or later, redo this procedure.

n/a

The SQL PI repository is supported for Agent Managers that reside on: 

  • Windows 2008 and later

  • Linux (RHEL 6, CentOS 6, SUSE 11) and later versions

n/a

Installing SQL PI repository is not possible on an Agent Manager installed on Linux with user root.

n/a

In case SQL PI for Oracle is monitored side by side with SQL PI for SQL Server, you must upgrade both Foglight for SQL Server and Foglight for Oracle cartridges to the same version.

n/a

In case of mixed environments (Linux® and Windows®), upgrading Foglight for Oracle to the latest version causes the agent monitored by SQL PI with SQL PI repository on Linux to stop monitoring.

n/a

SQL PI repository and the Agent Manager running the monitoring Oracle agents (with the SQL PI extension), can reside on Windows64 or Linux64 OS platforms in either combination, as follows:

SQL PI Repository

Oracle Agents With SQL PI

Windows64

Windows64

Windows64

Linux64

Linux64

Linux64

Linux64

Windows64

 

Foglight-related issues

Defect ID

Known Issue

CR-2153

Problem: A Validate Win connection failure occurs. If the Win32_PerfRawData_PerfOS_Processor class is invalid, any queries from it will fail. This is used in the OS connections validation.

CR-2987

 

Problem: When the FMS (Foglight Management Server) and FglAM (Foglight Agent Manager) are installed on different time zones, the timestamps in the topology are not accurate. The difference from the real timestamp is:

  • +|time difference between FglAM and FMS|
    or

  • –|time difference between FglAM and FMS|.

ODB-9393

A Foglight Agent Manager (FglAM) residing on a Linux/UNIX machine cannot use Windows Remote Management (WinRM) to establish connection with Windows server. Connection using WinRM can only be carried out by a an Agent Manager residing on a Windows machine.

ODB-9536

If a CRS, Exadata, or ASM agent is created, deleted, and then recreated with the same name, the nodes from the previous installation will be added to the newly created node.

Workaround: Use the relevant tab in the Databases dashboard (ASM, CRS, or Exadata) to delete the nodes.

ORAFOG-230

The 'Agent configuration failed' error prompts by chance when trying to monitor an Oracle instance.

Workaround:

  1. Go to the Agent Status dashboard, then delete the reference agents manually.

  2. Redo the configuration to monitor the Oracle instance.

  3. If the above workaround does not resolve this issue, restart the Foglight Management Server.

SSDB-881

Enabling and disabling an older version of Foglight for Oracle while a newer version is installed may adversely affect the performance of the newer cartridge.

Workaround: Disable the newer cartridge and enable it again, thereby overriding the settings of the older cartridge.

n/a

Agent names must be unique. Foglight does not support the same agent name to be applied to more than one agent.

 


Third party known issues

The following is a list of third party issues known to exist at the time of this release.

Defect ID

Known Issue

FOGDG-650

The Foglight Agent Manager (FglAM) failed to restart when upgrading DB Cartridge, which is due to "Could not obtain a deployment lock" error.

Workaround: Perform the procedure described in the Knowledge Article 266110.

n/a

Oracle Bug 18195919: When monitoring Oracle 12C the Activity > Datafiles I/O Activity dashboard does not show tablespaces of type TEMP.

n/a

Anti-Virus Protection tools installed on Windows® may negatively impact CPU and system performance of machines running Foglight the Agent Manager and the SQL PI repository.
To reduce resource consumption it is highly recommended that you exclude the following directories from being scanned by the Anti-Virus tools:

  • <installation directory>:\Quest\<foglight>

  • <installation directory>:\Infobright

  • <installation directory>:\Quest\<FoglightAgentManager>

n/a

The Windows System Center 2012 Endpoint Protection tool may negatively impact CPU and system performance of machines running Foglight and the Agent Manager. To reduce resource consumption it is highly recommended that you exclude the following directories from being scanned by the tool:

  • <installation directory>\Quest\<foglight>

  • <installation directory>\Infobright

  • <installation directory>\Quest\<FoglightAgentManager>

n/a

WMI-related issue

Problem: WMI support is affected by the firewall.

Workaround: For Windows versions prior to Windows 2008/Vista, use the following steps:

  1. Open TCP port: 135.
    WMI by default uses the port range 1024 to 5000.

  2. Open up a range of ports above port 5000.
    Port numbers below 5000 may already be in use by other applications and could cause conflicts with your DCOM applications.
    It is recommended to have at least 100 ports opened, as several system services rely on these RPC ports to communicate with each other.

  3. Add the registry key, including additional ports.

    • Use the RPCCfg.exe (Windows Resource Kits) by running: rpccfg.exe -pe 5009-5009 -d 0

    • Manually add the registry keys under:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

For Windows Vista and Windows Server 2008:
According to Microsoft (http://support.microsoft.com/kb/929851), the default dynamic port range for TCP/IP has changed in these versions. The new default start port is 49152 and end port is 65535.
Subsequently, monitoring instances that run under these operation systems can be carried out by using either of the following options:

  • Configure the firewalls to allow traffic between servers in the dynamic port range of 49152 through 65535 (less secure).

  • Limit the port range that is used in each monitored server.

n/a

Monitoring an Oracle instance that resides on a Windows 2008R2 or higher requires a workaround as follows:
- Browse to http://support.quest.com/ and log in
- Perform solution SOL65870

n/a

Some base values are not updated when using the Win32_PerfRawData_PerfDisk_LogicalDisk WMI class to calculate performance data in Windows Vista or in Windows Server 2008, because this class does not contain the PercentDiskTime_Base metric.
Workaround: A hotfix is available on Microsoft site, http://support.microsoft.com/kb/961435/en-us.

 


Upgrade and compatibility

Upgrade and compatibility

A direct upgrade to Foglight for Oracle 5.9.5.10 is only available from version 5.7.5.x or later. Customers that are running 5.7.x of the product must first upgrade to version 5.7.5.x and then upgrade to version 5.9.5.10. A direct upgrade to Foglight for Oracle 5.7.x is only available from version 5.5.8 or later. Customers that are running earlier versions of the product must first upgrade to version 5.5.8 and then upgrade to version 5.7.x.

For example, if your Foglight for Oracle is version 5.5.8 and you are going to upgrade to version 5.9.5.10, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x (or later) > 5.9.5.10.

 

Foglight for Oracle 5.9.5.10 requires:

  • Management Server version 5.9.2, 5.9.3, 5.9.4, or 5.9.5
  • Agent Manager version 5.9.2, 5.9.3, 5.9.4, or 5.9.5

 

To upgrade Foglight for Oracle to version 5.9.5.10:

  • Use the installer file to upgrade both the Foglight Management Server and the Foglight for Oracle cartridge to version 5.9.5.10.

OR

  1. Upgrade the Management Server to version 5.9.2 or higher.
  2. Install version 5.9.5.10 of the cartridge as you would install a new Foglight for Oracle cartridge. Do not delete the older version of the .car file. Install version 5.9.5.10 over the older version.

Note: It is recommended that you ensure the privilege levels of the users that are used to monitor the Oracle® instances after each upgrade. This can easily be done in the following location: Databases > Administration > Connection Details > Test Connection.

For cartridge installation instructions, see the Foglight for Databases Deployment Guide.

Note: Foglight for Oracle does not support the upgrade method of placing the new version in the folder <foglight_home>/upgrade/cartridge/.

Important: If you are upgrading to the current version of Foglight for Oracle in a Federation architecture, the upgrade should be applied first to the Federated Children and then to the Federation Master. If the Federation Master is upgraded first, it will display incorrect information regarding the number of instances being monitored in the Status Summary section.

 

The following Foglight product versions and platforms are compatible with this release.

Product Name

Product Version

Platform

Foglight Management Server

5.9.2

5.9.3

5.9.4

5.9.5

All platforms supported by this version of the Foglight Management Server

Foglight Agent Manager

Note: The monitoring agents available in this version of Foglight for Oracle do not support PI monitoring with the Agent Manager HA failover mode. For more information about this mode, see the Agent Manager Guide.

5.9.2

5.9.3 

5.9.4

5.9.5

All platforms supported by this version of the Foglight Agent Manager

 


System requirements

System requirements

Before installing Foglight for Oracle, ensure your system meets the following minimum hardware and software requirements:

Hardware and software requirements

Before installing Foglight for Oracle, ensure that your system meets the hardware and software requirements detailed in Foglight System Requirements and Platform Support Guide.

Customers running large deployments (that is, with more than 20 agents) should consult the Foglight for Databases Deployment Guide.

UNIX server and programs

The following UNIX programs must be accessible to the user logged on to the UNIX and Linux computers:

  • On all platforms: df, du, awk, iostat, vmstat, uptime, netstat, sed, ps, uname, ls -l

In addition, the following platform-specific programs must be available:

  • On the Linux platform: /proc/vmstat, /proc/net/dev, free, /proc/cpuinfo, getconf
  • On the Solaris platform: /usr/sbin/prtconf, mpstat, pagesize, psrinfo
  • On the AIX platform: lsattr, lsdev, pagesize, bindprocessor, lsdev, oslevel
  • On the HP-UX specific platform: bdf (instead of df), sar, /var/adm/syslog/syslog.log, /usr/sbin/ioscan, getconf, /swapinfo, InfoLog (needs to be enabled)

Programs that should be configured to be run using sudo

The sudo utility allows system administrators to grant specific users (or groups of users) the ability to run certain commands that require administrative privileges as root, without having to log in as administrator.

The programs that can be run using sudo in the various Linux and UNIX operating systems are as follows:

  • On all platforms, when monitoring the Clusterware using the CRS agent:
    • For running the Clusterware monitoring wizard: test, uname, ps, awk, {CRS_HOME}/bin/olsnodes
    • For monitoring the Clusterware: {CRS_HOME}/bin/crs_stat (for versions 10gR1, 10gR2, 11gR1), ${CRS_HOME}/bin/crsctl(for versions 11gR2 and above), tail
  • On all platforms: df, du, awk, iostat, vmstat, uptime, netstat, sed, ps, uname, grep, ls -l

In addition, the following platform-specific programs must be available:

  • On the Linux platform: /proc/vmstat, /proc/net/dev, free, /proc/cpuinfo, getconf
  • On the Solaris platform: /usr/sbin/prtconf, mpstat, pagesize, psrinfo
  • On the AIX platform: lsattr, lsdev, pagesize, lsdev, bindprocessor, oslevel
  • On the HP-UX specific platform: bdf (instead of df), sar, /var/adm/syslog/syslog.log, /usr/sbin/ioscan, getconf, /swapinfo, InfoLog (needs to be enabled)

UNIX user permissions and installation settings

  • On AIX, the user must be a member of the administrator group to be able to run the sar command.
  • On Linux, the sysstat package must be installed to enable the user to get detailed disk I/O information.
  • On Linux the /proc filesystem must be present.
  • For connection using SSH, the sshd daemon must be installed and running.
  • For connection using telnet, a telnet daemon must be installed and running.
  • The UNIX user should have no special processing on log-on. In particular there must be no input required from the user, and nor should any special login banners be displayed.

Required privileges

For information on the required privileges, refer to the Foglight for Databases Deployment Guide.

Direct NFS client

This version of Foglight for Oracle support usage of direct NFS client.

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
    • 11g
    • 12c
    • 18c
    • 19c
  • 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 1: Foglight for Oracle supports monitoring the Amazon Relational Database Service (Amazon RDS™).

Note 2: 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 above for the Linux platform.

 


Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione