Known issues for the Oracle cartridge (4381534)

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: 4229543 

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:

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:

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:

FOG-1758

When applying an alarm template to an agent, the Inconsistent Values indication may appear. This indication can be ignored.

FOG-1862

After upgrading your FMS and Foglight for Oracle cartridge to version 6.0.0, the global search results will not include Oracle DataGuard objects.

Workaround: Refer to KB 4311966 for a script that can be run to create the required topology object.

FOM-800

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.

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.

PIFOG-405

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.

PIFOG-431

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

PIFOG-666

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.

PIFOG-701

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

PIFOG-723

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

n/a

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.

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

Antivirus exclusions is required for the SQL Server-based SQL PI repository. For more information refer to the Microsoft’s official article https://support.microsoft.com/en-us/help/309422/choosing-antivirus-software-for-computers-that-run-sql-server.

FOG-518

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

FOG-728

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

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:

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:

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:

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. 

n/a

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.

FGL-20596

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

Workaround:

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.

FOG-667

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

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:

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:

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 4229811 

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.