Chatee ahora con Soporte
Chat con el soporte

Foglight for Oracle (Cartridge) 7.1.0 - Release Notes

SQL PI Repository



When there are many DB agents with PI enabled in FMS environment and you want to upgrade the cartridge to the latest version, the SQL PI component update might fail.

Workaround: Click Cancel on Update SQL PI Failed and click Update SQL PI Components to update again.


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.


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.


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


Incomprehensible error message is displayed when using local account without hostname prefix to setup PI Repository.

Workaround: Use hostname\username to setup PI Repository instead of only using username.


Enabling SQL PI is only supported when the SQL PI agent manager is installed on one of the following operating systems:



“Context infos” display null in the Comparison Parameter dashboard.


When 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.


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.


Antivirus exclusions is required for the SQL Server-based SQL PI repository. For more information refer to the Microsoft’s official article


When monitoring several database installations on one physical server, the physical hostname may be used in Database dashboards instead of the databases virtual hostname.

Workaround: Follow the procedure described in KB article 233194.


When creating a new user account to monitor an instance, If the same account is used as PI repository login to enable PI, the process will failed showing no permission error.

Workaround: Manually grant the database user the db_owner role for the new created PI repository database.

For more information, refer to KB article 331530.

Foglight-related issues


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.


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:


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.


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.


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



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.


An error log showed in FMS log for loading heatmap component in FMS version before 5.9.3.


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


The Windows System Center Endpoint Protection (SCEP) tool and Anti-Virus Protection tools installed on Windows® may negatively impact CPU and system performance of machines running Foglight, Foglight Agent Manager, and the SQL PI repository.

To reduce resource consumption, it is highly recommended that you exclude the following directory from being scanned by the protection tools:


Anti-virus software may negatively impact the CPU and system performance of machines running Foglight. To reduce resource consumption, it is highly recommended to exclude the relevant directory, processes, and executables from being scanned by the anti-virus software. For detailed information, refer to the “Configuring anti-virus exclusion settings” in Installing Foglight on Windows with an Embedded PostgreSQL Database.


When upgrading Foglight, if the FMS is upgraded to version 6.0.0 and the database cartridge is not, the dashboard will display “There is no data to display”.

Workaround: When upgrading Foglight to 6.0.0, first upgrade the FMS to 6.0.0, then directly upgrade the cartridges.

Third party known issues

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


Cannot import license into installer with license file name XXX.lic.



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.


When trying to create an Oracle DB agent using FglAM deployed on an Ubuntu server, the connection will fail with the error “timezone region not found”.

Workaround: Restart FglAM with the command below


In FIPS-compliant mode, it is required to use at least 2048 RSA and DSA key size to do OS monitoring via SSH connection in DB cartridge.

When FglAM version is lower than, FglAM will not check RSA/DSA key size < 2048, and the connection is non-FIPS compliant.

Workaround: Upgrade the FglAM version to or later.


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


WMI-related issue

Problem: WMI support is affected by the firewall.

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

For Windows Vista and Windows Server 2008:

According to Microsoft (, 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:


Monitoring an Oracle instance that resides on a Windows 2008R2 or higher requires a workaround as follows:

- Browse to and log in

- Perform solution SOL65870


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,


Oracle Bug 19509076: V$SEGSTAT table performance issues with Oracle version 12.1.0.x.x.


MES patch should be applied to support TLS 1.1 and TLS 1.2 protocols in Oracle Database

Workaround: Apply the MES patch# for Database. The patch can be found in MOS Note 2274242.1. Source:

Upgrade and Compatibility

A direct upgrade to Foglight for Oracle 7.1.x is only available from version 6.1 or later. Customers that are running older versions of the product must first upgrade to version 6.1 and then upgrade to version 7.1.x.

Foglight for Oracle 7.1.x requires:

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación