Updated Supported Foglight Version & Supported Agent Manager Versions in the About Foglight for Databases dialog box.

FOGDG-615

Changed "Microsoft Visual C++ 2010 Redistributable or later" to "Microsoft Visual C++ 2010 Redistributable" in the Databases > Upgrade Wizard Oracle/SQL Server dashboard.

GVFOG-82

Fixed the issue where TopologyObjectNotFound exception occurs on the Databases dashboard.

ORAFOG-565

When switching from other dashboards to the Summary dashboard the default timeline remains last 8 hours instead of last one hour.

ORAFOG-614

Primary database agent should not be displayed in the "Choose Standby Agent" list.

ORAFOG-615

A error occurs on the Summary page when setting up Data Guard on FMS 5.7.0 due to java.util.ArrayList.removeIf().

ORAFOG-627

There is missing data in the Data Guard dashboards when standby database service name differs from its database name.

ORAFOG-628

When converting data from JDBC resultset to int, the collection of DBODataGuardDestinationStatusRmi failed due to numeric overflow.

ORAFOG-632

Timestamp column was sorted according to the wrong order in the Alert Log dashboard.

ORAFOG-638

Fails to enable the Oracle DB cartridge and the "Failed to run Oracle Topology DBO_Data_Guard_Destination_Status upgrade script" error was thrown.

After the upgrade from previous versions of Oracle cartridge to the version 5.9.2.1, Flashback data was missing due to non-sufficient permissions.

After the upgrade from previous versions of Oracle cartridge to the version 5.9.2.1, some metrics of Data Guard were missing due to non-sufficient permissions.

The Upgrade Wizard does not display a grant permission dialog popup.

ORAFOG-681

"DBO - Usability Connection Availability" alarm is not fired when database is not available.

ORAFOG-687

Adding the check permissions script to the DB_Oracle_CLI_Installer.zip and the DB_Oracle_CLI_Upgrade.zip.

PIFOG-55

SPI Long Lock Running rule shows incorrect value for "blocked user".

PIFOG-61

Added the option for capturing wait events on the instance level in PI for Oracle. This option should be enabled by user through groovy script.

PIFOG-69

Use a connection of PDB service name when generating execution plan for PDB instance.

PIFOG-80

Disable SQL PI Statistics debug messages by default.

PIFOG-84

"ORA-00942: table or view does not exist Error Code" was thrown when examining object details in Plan Analysis.

GVFOG-79

The user access configuration does not work for the instance which agent name is created manually.

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.

DB agents need be re-upgraded after upgrading the Foglight Management Server.

 Workaround: Make sure to wait for more than 10 minutes between upgrade of the Foglight Management Server and Foglight for Oracle.

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-644

DBO_Undo_Summary collection is not supported for Oracle databases with the multitenant option since 12.2 version.

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-680

Oracle PI Execution Plan progressTracker repeatedly calls the function running in the background.

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.

n/a

Partial support of Logical Standby database.

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.

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.

ORAFOG-661

Workload metrics sometimes disappears when user navigates to the Databases Dashboard with PI enabled.

Workaround: See the Knowledge Article 235918 for details.

PIFOG-79

Unsupported platform error occurs when adding an Oracle agent with SQL PI enabled.

PIFOG-92

Scheduled Infobright restarts unexpectedly due to resource negotiation.

PIFOG-93

Workload is missing because DBO_SPI_Instance_Statistics collection hangs when getting JDBC connection.

PIFOG-100

Failed to retrieve data from SQL PI repository due to invalid JDBC connection returned.

Workaround: Refresh your browser.

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, 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

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:

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.

FOGDG-650

If the monitored DB host is down, upgrade of the Agent Manager hangs and the Agent Manager throws the error "Could not obtain a deployment lock. Will try again in 30,000 ms".

Workaround: Use either of the following solutions:

• (Recommended) Restore the DB host before starting the upgrade.

• When the upgrade hangs, restore the DB host to ensure DB agent is able to connect with DB instance correctly, and then proceed the upgrade again.

• When the upgrade hangs, delete the problematic DB agent from the Agent Status dashboard, restart the Agent Manager, and then proceed the upgrade again.

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

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

Foglight Management Server

5.7.5.x

5.9.1

5.9.2

5.9.3

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.8.5.x

5.9.1

5.9.2

5.9.3 

All platforms supported by this version of the Foglight Agent Manager