|
|
|
|
FAIO-217 |
PI engine didn't use new credential changed in Connection Details dashboard.
Workaround: Reactive the agent after changing the credential. |
|
FOM-76 |
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. |
|
FOM-81 |
Cannot monitor Extdata due to commands located in folder /usr/sbin.
Workaround: Check “Use Sudo” when monitoring Exadata. |
|
FOM-769 |
Cannot receive email of DBO - Invalid Materialized Views alarm when the agent is RAC one node instance.
Workaround:
|
3 |
Select All Alarms or a specific alarm. |
|
4 |
Click Set configuration on selected agents. |
|
6 |
Click Apply to apply the setting to selected RAC agent. | |
|
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 added at a later time 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:
|
|
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:
|
|
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) leaving them empty. |
|
ODB-9143 |
Exadata, ASM, and CRS agents are marked in the upgrade process as 'other agents', even though 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:
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:
|
|
ODB-10918 |
Support for Oracle 12c has the following restrictions:
|
|
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. |
|
|
ORAFOG-815 |
It fails to set up an agent to connect Oracle Dataguard 10g.
|
|
ORAFOG-919 |
Change “Connect as” in “Database Agent Migration” dashboard is not supported. |
|
n/a |
Partial support of Logical Standby databases. |
|
n/a |
When Foglight or the Agent Manager are installed on a VM, it is highly recommended to reserve the following:
|
• |
CPU - for a virtual machine the CPU reservation is highly recommended for better performance. The reservation is expressed in MHz. |
|
• |
RAM- for a virtual machine the memory reservation is highly recommended for better performance. | |
