Foglight® for Oracle

Developed and tested for Foglight Management Server 5.7.5.x or higher

Release Notes

August 2018


Welcome to Foglight for Oracle

New in this release

Resolved issues and enhancements

Known issues

Third party known issues

Upgrade and compatibility

System requirements


Product licensing

Getting started with Foglight for Oracle

About Us


Welcome to Foglight for Oracle

Foglight® for Oracle allows database administrators (DBAs) to quickly and efficiently identify performance deviations, determine their root cause, perform comprehensive analyses, and resolve performance bottlenecks. This product provides web-enabled dashboards for centralized visibility, management and health checks for the Oracle instances deployed in your environment, as well as proactive alerting and alarm workflows for tracking your responses to critical performance anomalies.

Foglight for Oracle is an n-tier application, which leverages a web-based user interface to ensure having complete visibility into the Oracle infrastructure wherever an Internet connection is available.

This version of Foglight for Oracle is integrated with SQL Performance Investigator.

These Release Notes cover the resolved issues, known issues, workarounds and other important information about release of Foglight for Oracle. Review all sections before starting installation. 


New in this release

Version contains the following new features and updates:

Resolved issues and enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Defect ID

Resolved Issue


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


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


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


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


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


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


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


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


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


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, Flashback data was missing due to non-sufficient permissions.


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


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


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


Adding the check permissions script to the and the


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


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.


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


Disable SQL PI Statistics debug messages by default.


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


Known issues

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

Cartridge-related issues


Defect ID

Known Issue


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


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.


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.


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.


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.


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.


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


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.


"Challenge response" credentials do not appear in the advanced lockbox pop up.


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


The Listener graphs under the Usability dashboard are not populated with data when monitoring RAC One Node.


The following alarms are displayed in the RAC level instead of the instance level:

  • Usability Availability Single

  • Collection status


Setting the connection details of a RAC One Node and failing the validation, will result in failure to save the changes.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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


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.


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.


The following homepages were removed from the custom dashboards: Interconnect/GCS, Cluster Overview, Sessions, Instance identification and usability and Workload.


The offloadEfficiency metric has been changed to be internal and inaccessible as of Exadata software version, 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.


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.


History data is missing if user upgrades the Foglight for Oracle cartridge using the SPM installer.


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.


Some error messages showed in the Management Server log, after disabling or enabling Alert log Groups. 


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 ' -l' command has been deprecated, which causes the infiniband switch operation fails. 


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.


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.  


The destination_name property in the Data Guard dashboard is missing after disabling and re-enabling the Foglight for Oracle cartridge.


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


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.


The Oracle upsince duration is miscalculated when FMS/FglAM and Oracle DB locate in different timezone.


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


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.


Partial support of Logical Standby database.


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.


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.


SQL PI Repository

Defect ID

Known Issue


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.


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.


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

Workaround: See the Knowledge Article 235918 for details.


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


Scheduled Infobright restarts unexpectedly due to resource negotiation.


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


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

Workaround: Refresh your browser.


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.


On mixed Windows and Linux environments, SQL PI stops monitoring after upgrading the Foglight database cartridge to and higher.

Workaround: Perform the procedure described in the Knowledge Article 212566. If you are upgrading from (and higher) to version, redo this procedure.


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


Installing SQL PI repository is not possible on an Agent Manager installed on Linux with user root.


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:

SQL PI Repository Oracle Agents With SQL PI
Windows64 Windows64
Windows64 Linux64
Linux64 Linux64
Linux64 Windows64


Foglight-related issues

Defect ID

Known Issue


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:

  • +|time difference between FglAM and FMS|

  • –|time difference between FglAM and FMS|.


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.


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.


The 'Agent configuration failed' error prompts by chance when trying to monitor an Oracle instance.


  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.


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.


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


Third party known issues

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

Defect ID

Known Issue


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.


Oracle Bug 18195919: When monitoring Oracle 12C the Activity > Datafiles I/O Activity dashboard does not show tablespaces of type TEMP.


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>


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>


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:
For Windows Vista and Windows Server 2008:
According to Microsoft (, 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.


Monitoring an Oracle instance that resides on a Windows 2008R2 or higher requires a workaround as follows:
- Browse to and log in
- Perform solution SOL65870


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,


Upgrade and compatibility

A direct upgrade to Foglight for Oracle is only available from version 5.7.5.x. Customers that are running 5.7.x of the product must first upgrade to version 5.7.5.x and then upgrade to version 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, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x >


Foglight for Oracle requires:


To upgrade Foglight for Oracle to version


  1. Upgrade the Management Server to version 5.7.x or 5.9.x.
  2. Install version 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 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.

Note: Foglight for Oracle does not support the upgrade method of placing the new version in the folder <foglight_home>/upgrade/cartridge/.

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


Foglight Management Server





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.





All platforms supported by this version of the Foglight Agent Manager


System requirements

Before installing Foglight for Oracle, ensure your system meets the following minimum hardware and software requirements:

Hardware and software requirements

Before installing Foglight for Oracle, ensure that your system meets the hardware and software requirements detailed in Foglight System Requirements and Platform Support Guide.

Customers running large deployments (that is, with more than 50 Oracle instances) should consult the Foglight for Databases Deployment Guide.

UNIX server and programs

The following UNIX programs must be accessible to the user logged on to the UNIX and Linux computers:

In addition, the following platform-specific programs must be available:

Programs that should be configured to be run using sudo

The sudo utility allows system administrators to grant specific users (or groups of users) the ability to run certain commands that require administrative privileges as root, without having to log in as administrator.

The programs that can be run using sudo in the various Linux and UNIX operating systems are as follows:

In addition, the following platform-specific programs must be available:

UNIX user permissions and installation settings

Required privileges

For information on the required privileges, refer to the Foglight for Databases Deployment Guide.

Direct NFS client

This version of Foglight for Oracle support usage of direct NFS client.

Monitoring an Instance that Is Part of a Data Guard Environment

To monitor a data guard environment with a physical standby (Redo Apply):

  1. Make sure that the Standby Database is in receiving mode.
  2. Use SQLPLUS to connect to the Primary Database as SYS user.
  3. Create the standby Foglight schema owner.
  4. From the Primary Database, run the grant privileges script on the standby user created in Step 3. to stay in that mode after the check.
  5. Open a web browser and run the Oracle Monitoring Installer wizard.
  6. Select "Add a New Instance".
  7. Specify the Standby Database credentials and connection details (the user that was created in Step 3).
  8. Click Verify Connectivity.
  9. If the Standby Database is mounted, click on validate standby button.
  10. After the verify process is complete, the next step is to monitor the physical Standby Database.

To monitor a data guard environment with logical standby (SQL Apply):

  1. Use SQLPLUS to connect to the logical standby as SYS user.
  2. Create the standby Foglight schema owner.
  3. Open a web browser and run the Oracle Monitoring Installer wizard.
  4. Continue the discovery process as usual, using the logical standby user credentials and connection details.
  5. Click Verify Connectivity.
  6. Once the connectivity verification is completed, the next step is to monitor the logical standby database.

Supported platforms

Foglight for Oracle supports monitoring the following platforms:

Note 1: Foglight for Oracle supports monitoring the Amazon Relational Database Service (Amazon RDS™).

Note 2: SQL PI extension supports Oracle versions 11gR1 and later.

Linux on System Z (z/Linux) support

Foglight for Oracle fully supports monitoring of instances that are installed on a z/Linux operating system. The supported monitored instances versions are the same as specified in the list above for the Linux platform.



This section provides a list of references which address the most commonly faced issues relating to remote connectivity, allowing for easy troubleshooting using the vendor's information knowledgebase:


Product licensing

Foglight includes a licensing capability that restricts access to those features that are defined in the license. Any Management Server installation requires a license that grants access to server-specific parts of the browser interface and the features associated with them. Foglight cartridges are also license-protected. While some cartridges are covered by the base Foglight license (such as Foglight Agent Manager cartridges and the Foglight for Infrastructure), others may require an additional license.

Foglight for Oracle is covered by the base Foglight license that allows cartridges to be installed. The SQL Performance Investigator extension requires a dedicated license.

To activate a trial or a purchased commercial license:

  1. On the navigation panel, under Dashboards, click Administration > Setup > Manage Licenses.
  2. Click Install.
  3. In the Install License dialog box, click Browse.
  4. In the file browser that appears, specify the location of the license file.
  5. In the Install License dialog box, click Install License.


Getting started with Foglight for Oracle

Contents of the release package

The Foglight for Oracle release package contains the following:

  1. Foglight for Oracle cartridge: 
  2. Product documentation, including:

Installation instructions

For installation pre-requisites, permissions, information necessary to determine your environment’s hardware requirements, and for installation instructions, see the Foglight for Databases Deployment Guide.

Additional resources

Additional information is available from the following:


This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations: The server will be enabled for Global Operation, but not localized to any particular locale.


About Us

We are more than just a name

We are on a quest to make your information technology work harder for you. That is why we build community-driven software solutions that help you spend less time on IT administration and more time on business innovation. We help you modernize your data center, get you to the cloud quicker and provide the expertise, security and accessibility you need to grow your data-driven business. Combined with Quest’s invitation to the global community to be a part of its innovation, and our firm commitment to ensuring customer satisfaction, we continue to deliver solutions that have a real impact on our customers today and leave a legacy we are proud of. We are challenging the status quo by transforming into a new software company. And as your partner, we work tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we are in this together. Welcome to a new Quest. You are invited to Join the Innovation™.

Our brand, our vision. Together.

Our logo reflects our story: innovation, community and support. An important part of this story begins with the letter Q. It is a perfect circle, representing our commitment to technological precision and strength. The space in the Q itself symbolizes our need to add the missing piece — you — to the community, to the new Quest.

Contacting Quest

For sales or other inquiries, visit

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:


Copyright© 2018 Quest Software Inc.

Quest, the Quest logo, Foglight, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight,SQL Server, Visual Basic, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to HewlettPackard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and eDirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vSphere, vCenter, vMotion, and vCloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, iPad, iPhone, Mac OS, Safari, Swift, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and "Amazon RDS" are trademarks of, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc. All other marks and names mentioned herein may be trademarks of their respective companies.