The following is a list of issues known to exist at the time of release.
|
PI engine didn't use new credential changed in Connection Details dashboard. Workaround: Reactive the agent after changing the credential. | |||||||||
|
RAC agents do not collect data after changed credential from sysdba to nosysdba. Workaround: Refer to the KB: https://support.quest.com/foglight-for-databases/kb/317055/rac-agents-do-not-collect-data-after-changed-credential-from-using-sysdba-to-nosysdba. | |||||||||
|
Cannot monitor Extdata due to commands located in folder /usr/sbin. Workaround: Check “Use Sudo” when monitoring Exadata. | |||||||||
|
Cannot receive email of DBO - Invalid Materialized Views alarm when the agent is RAC one node instance.
| |||||||||
|
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. | |||||||||
|
“Challenge response” credentials do not appear in the advanced lockbox pop up. | |||||||||
|
The following metrics display NA when monitoring a RAC one node:
| |||||||||
|
The following alarms are displayed in the RAC level instead of the instance level: | |||||||||
|
The invalid objects exclude list is not supported for RAC and RAC One Node. | |||||||||
|
When converting RAC One Node to RAC the OS cluster failover alarm is triggered. | |||||||||
|
Workaround: Create the infrastructure agent manually. | |||||||||
|
Workaround: Use command line installation (CLI) through the Silent Installer tool, which supports this configuration. | |||||||||
|
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. | |||||||||
|
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. | |||||||||
|
Workaround: Use the virtual IP /physical IP/physical host name. | |||||||||
|
The following dashboards and views may be less responsive than others due to their complexity: | |||||||||
|
Support for Oracle 12c has the following restrictions:
| |||||||||
|
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. | |||||||||
|
The Databases Global View dashboard shows negative and over 100% values for OS CPU metrics. | |||||||||
|
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. | |||||||||
|
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. | |||||||||
|
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. | |||||||||
|
The 'ibprintca.pl -l' command has been deprecated, which causes the infiniband switch operation fails. | |||||||||
|
Workaround: On the Agent Status dashboard, deactivate and re-activate the agent, and then wait for five minutes. | |||||||||
|
The destination_name property in the Data Guard dashboard is missing after disabling and re-enabling the Foglight for Oracle cartridge. | |||||||||
|
Metrics of the monitored Host display n/a when an inactive host object binds to OracleInstance.participatingHosts. | |||||||||
|
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. | |||||||||
|
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. | |||||||||
|
Workaround: Create an agent manually in the Agent Status dashboard, and then change its “monForceSid” in ASP to false. | |||||||||
|
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:
| |||||||||
|
It fails to set up an agent to connect Oracle Dataguard 10g. | |||||||||
|
Change “Connect as” in “Database Agent Migration” dashboard is not supported. | |||||||||
| |||||||||
|
Workaround: Refer to KB 332068 for a script that can be run to create the required topology object. |
|
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: | |
|
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. | |
|
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. | |
|
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. | |
|
Workaround: When upgrading Foglight to 6.0.0, first upgrade the FMS to 6.0.0, then directly upgrade the cartridges. |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
