Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight for Oracle (Cartridge) 5.9.7.22 - Release Notes

Foglight-related issues

 
Table 5. Foglight-related known issues
Issue 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.

GVFOG-207

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

n/a

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

n/a

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:

<installation directory>:\Quest\<FoglightAgentManager>

n/a

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.

Third party known issues

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

 
Table 6. Third-party known issues
Issue ID
Known issue

FGL-20596

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

Workaround:

1
When importing license into installer, change license file name to XXX.license.
2
Install xxx.lic after login FMS.
3
Change license file name to XXX.license and put it into license folder before FMS start up.

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.

FAM-7722

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 5.9.7.1, FglAM will not check RSA/DSA key size < 2048, and the connection is non-FIPS compliant.

Workaround: Upgrade the FglAM version to 5.9.7.1 or later.

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

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 https://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, https://support.microsoft.com/kb/961435/en-us.

n/a

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

n/a

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

Workaround: Apply the MES patch# for 11.2.0.4 Database. The patch can be found in MOS Note 2274242.1. Source: https://www.oracle.com/webfolder/community/oracle_database/3923204.html.

Upgrade and Compatibility

A direct upgrade to Foglight for Oracle 5.9.7.22 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.7.22. 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.7.22, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x (or later) > 5.9.7.22.

Foglight for Oracle 5.9.7.22 requires:

•
Management Server version 5.9.2, 5.9.3, 5.9.4, 5.9.5, or 5.9.7
•
Agent Manager version 5.9.2, 5.9.3, 5.9.4, 5.9.5, or 5.9.7
To upgrade Foglight for Oracle to version 5.9.7.22:

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

OR

1
Upgrade the Management Server to version 5.9.2 or higher.
2
Install version 5.9.7.22 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.7.22 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.
•
Foglight for Oracle does not support the upgrade method of placing the new version in the folder <foglight_home>/upgrade/cartridge/.
•
Starting from version 5.9.5.20, Infobright is no longer supported. It is necessary to move existing agents to the SQL Server-based PI repository. We have provided a data migration utility for customers who want to keep their historical performance data. For more information, refer to How to migrate database agents to a SQL Server-based PI repository.

 

* 
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
5.9.7

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
5.9.7

All platforms supported by this version of the Foglight Agent Manager

System requirements

Before installing or upgrading Foglight for Oracle 5.9.7.22, ensure that your system meets the following minimum hardware and software requirements.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation