Foglight^® for SQL Server 5.9.4.10

Developed and tested for Foglight Management Server 5.9.2, 5.9.3, and 5.9.4

Release Notes

April 2019

Welcome to Foglight for SQL Server

New in this release

Resolved issues and enhancements

Known issues

Upgrade and compatibility

System requirements

Troubleshooting

Product licensing

Getting started with Foglight for SQL Server

About Us

Welcome to Foglight for SQL Server

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

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

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

New in this release

Version 5.9.4.10 contains the following new features and updates:

Enhance backup alarms not to fired on offline or backup database.
Enhance "DBSS-Hours-Since Last Log Backup" alarm to include full backups.
Eliminate the length limit of User-defined collection.
Enhance PI performance to drastically reduce query timeouts.
Enhance SQL PI to be able to identify SQL statements that are waiting on Latch.
Enhance SQL PI to eliminate the chance of missing workload metrics.
Updated the TLSv1.2 drop-down list to check box in single installer monitor wizard.
Changed to use the different OS credential as default when creating SSAS agent.

Resolved issues and enhancements

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

Defect ID	Resolved Issue
PIFOG-32	Unable to detect Agent Manager OS type and version when installing Infobright PI repository.
PIFOG-270	Lots of “dataprocessor.exe” processes get hung over time on Agent Manager and it causes the PI data submission failure.
PIFOG-292	Unable to enable PI when monitor Oracle instance as a sysdba user.
SSFOG-480	"NullPointerException" Error is thrown in the log when executing "Logical Disk Collection" in Windows environment which has dynamic disks and volumes.
SSFOG-898	Instance Availability displays n/a on SSIS Overview when SQL Server 2016 or later version is being monitored.
SSFOG-929	Unable to enable OS monitoring with "Local User" Authentication type when setting up SQL Server DB agents by CLI.
SSFOG-931	Unable to enable OS monitoring with "SSH (login credentials)" Authentication type when setting up SQL Server DB agents by CLI.
SSFOG-1095	Unable to get correct session ID when "parent_connection_id" is null.
FOGDG-785	The error message showed up on User Level Access page after adding a new user.

Known issues

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

General Issues

Defect ID	Known Issue
FOGDG-858	DB instance is still synchronized and displayed in FMS federation master even though it is stopped for some reason and not displayed in the FMS federation child.
PIFOG-431	After DB agent restarts, there will be a 5 minutes data gap in the SQL PI baseline view.
PIFOG-386	When using SSAS agent to monitor SSAS cluster environment, "Unavailable SSAS service" alert may show up even the SSAS service is actually up.
SSFOG-1031	When SQL Server cluster on Linux does fail-over, IC agent may not be auto created when the host name of the node is different with previous node.
SSFOG-956	Creating Infrastructure agent automatically after failover occurs on Linux-based SQL Server cluster may fail.
SSFOG-949	If you select either of DB_SQL_Server, DB_SQL_Server_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. 2. Search for "DBSS_Is_Fglams_Required_Upgrade". 3. Change its value to "-1".
SSFOG-943	Using CLI to create multiple SQL Server instances with OS monitoring might result in failure to activate some host agents. Workaround: Either activate those host agents manually on the Agent Status dashboard or re-create those host agents.
SSFOG-844	When using IP address to create a SQL server agent, Disk metric and Host metric will be missing in the Global view.
SSFOG-770	Alarm is not triggered while the error has been collected on the "DBSS - SQL Server Error Log" page.
SSFOG-775	If AD authentication has been used to monitor SQL Server instance, the default option 'Log in to the host using the same account used for monitoring SQL Server' cannot be used to monitor Linux Operating System (OS). Workaround: Switch to use the option 'Log in to the host using different login credentials', then choose either of the following Linux authentication types: input AD account info, input other Linux account info, or use 'Select from stored credentials...'.
SSFOG-739	Logical Disk metrics of SUSE showing on the SQL Server Overview dashboard is different from its value showing in the Infrastructure dashboard.
SSFOG-736	DBSS_Error_Log_List collection fails if SQL Server 2017 Agent is not running on Linux.
SSFOG-645	It fails to run DBSSSQLAgentErrorLogProcessor processor of DBSS_SQL_Agent_Error_Log collection if the SQL Server Agent Service is not started. Workaround: Start the SQL Server Agent Service.
SSFOG-551	Due to the metric collection interval, value of Data files, log files, and disk space metrics will be occasionally missing on the Databases > Temdb dashboard. Workaround: Wait for 3 minutes, then you will see these metrics on the dashboard.
SSFOG-456	If two SQL Server instances running in different hosts but these two hosts have the same short name, these two hosts shows same on the Home page. Workaround: Contact Quest support to get the scripts for updating the loadGVData function.
SSDB-16097	In case the privilege of OS monitoring is not set to the Local Administrator group on the host being monitored, see the Knowledge Article 215054 available at https://support.quest.com/kb/215054.
SSDB-15192	SQL BI - Reporting services, integration services and Analysis services are not supported on cluster configuration.
SSDB-14323	The SQL Server Error log collection requires you to use WinShell. Follow the instructions below to configure the correct settings: Configuring the Command-Shell Connection Settings Configuring Windows Management Instrumentation
SSDB-13479	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.
SSDB-13199	Selecting a batch text in the lock tree may navigate to a non-equal batch in the TSQL Batches dimension.
SSDB-9277	In SQL Server® 2012, when a database is part of an availability group and is currently accessible for connections, when the application intent is set to read only, several collections will fail.
SSDB-9138	Cluster data can be collected only if the xp_cmdshell parameter is configured. To configure this parameter, run the following commands: `EXEC sp_configure ‘show advanced options’,1 GO --To update the currently configured value for advanced options. RECONFIGURE GO —- To enable the feature. EXEC sp_configure ‘xp_cmdshell’, 1 GO —- To update the currently configured value for this feature. RECONFIGURE GO`
SSDB-8987, SSDB-7326	On Microsoft® Windows® 2008 R2, a SQL Server version 2012 instance with a name that contains inverted commas (''; (for example:'X641_ENT1') can encounter issues with the retrieval of WMI data. This is by design on the part of Microsoft. Workaround: If WMI data is not retrieved, the instance name without the '' should be added in the field Service Name in the Agent Properties dashboard.
SSDB-8949	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.
SSDB-5542	Creating a user-defined collection with more than one SQL in it will not alert the user, however, only the first SQL in the collection will be executed.
SSDB-5248	Editing a user-defined collection results in periodic overlap of data.
SSDB-3061	Changes made in the Global Administrations > Alarms screen are saved when switching to another global administration screen, even if selecting "Yes" in the dialog box that asks whether to exit without saving changes.
SSDB-3039	The DBSS- Deadlock Details alarm is disabled by default.
SSDB-2455	User-defined collection names and fields must be entered in Latin characters (A to Z), without any special symbols.
SSDB-2379	When working with Global View while the screen resolution is set to 1024 by 768 pixels, it is advisable to switch to the browser's full view (F11 toggles between full and normal views in all browsers).
SSDB-2060	On SQL Server 2008, deadlocks on two different databases of the same instance become one chained deadlock. Workaround: Implement trace flag -T1234
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, the more recently created collection will not appear in the topology, nor will it be displayed on the User-defined Collections panel.
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-1606	Performing an upgrade process on a large environment (more than 50 agents) takes time to complete.
n/a	Need to wait for more than ten minutes between the upgrade of the Foglight Management Server and Foglight for SQL Server.
n/a	In environments configured to monitor SSAS agent only, when upgrading to version 5.9.2.1 or later, the upgrade process will fail. Workaround: In the Administration > Agents > Agent Status dashboard, click Deploy Agent Package, then follow on-screen instructions to deploy the SSAS package manually.
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 or later, redo this procedure.
n/a	Monitoring Analysis services is supported only on Agent Managers running on Windows which must have a version of .NET 3.5 installed.
n/a	If the WMI exception "Format specifier '%s' " is entered in agent log the following workaround is recommended: Workaround: For Windows® Vista® and Windows Server 2008: According to http://support.microsoft.com/kb/929851, the default dynamic port range for TCP/IP has changed in both 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. For Windows versions prior to Windows 2008/Vista: Open TCP port: 135. WMI by default uses the port range 1024 to 5000. 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. 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: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet For more information, see the Knowledge Article 114559 available at https://support.quest.com/kb/114559.
n/a	In cases when Foglight or the Agent Manager are installed on a VM the following need to be reserved: Memory - the full amount of the required machine memory CPU - the amount of CPU MHz

Execution Plan

Defect ID	Known Issue
SSDB-11283	Execution plan may not be resolved
SSDB-11582	Sometimes, query_hash is changed by SQL Server and generating a plan using the Generate button fails. SQLhash isn't found in XML so the screen displays No operation was found and the execution plan changes are missing.
SSDB-11657	Time range changes are not effecting the execution plan dashboard.
n/a	In the Execution Plan comparison popup, the date of the selected plan is the insert time to the SQL PI repository and not the execution time.
n/a	In the Execution Plan Comparison popup for statement - the estimated plan appears only as the selected plan on the left side. It cannot be selected from the list.

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
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.
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	WMI-related issue Problem: WMI support is affected by the firewall Workaround: For Windows versions prior to Windows 2008/Vista, use the following steps: Open TCP port: 135. WMI by default uses the port range 1024 to 5000. 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. 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: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet 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: 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.
n/a	As a result of the change introduced in Java 6 update 29 to how data is sent to databases, users may experience connection failures when using the Microsoft JDBC Driver for SQL Server® to connect to SQL Server. This interoperability enhancement is available in the following SQL Server versions: SQL Server 2012 Production version and later SQL Server 2008 Service Pack 3 Cumulative Update 4 SQL Server 2008R2 Service Pack 1 Cumulative Update 6 SQL Server 2008R2 Service Pack 2
n/a	Third Party Limitations Monitoring an SQL Server 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 https://support.quest.com/kb/SOL65870
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, http://support.microsoft.com/kb/961435/en-us.
n/a	Due to a known Microsoft issue (https://support.microsoft.com/en-us/kb/3036328), on SQL Server instances version 2014 the SQL text presented may be truncated.
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	SQL's and execution plans may not be collected on SQL Server 2014 as a result of a Microsoft bug "The values of column query_hash and query_plan_hash are NULL for DMV sys.dm_exec_requests in SQL Server 2014" http://support.microsoft.com/kb/2953592
n/a	The Foglight Time Bar Chart click event does not work with Chrome version 40.x.x.x and 39.x.x.x. https://code.google.com/p/chromium/issues/detail?id=428308

Workaround for all missing WMI metric cases

In some cases, running the command: %windir%\system32\wbem\wmiadap.exe /f in Windows' command-line (CMD) may solve the problem of missing WMI classes. This command parses all the performance libraries on the system and refreshes the Performance Counter Classes. For further details, see http://msdn.microsoft.com/en-us/library/aa394528%28VS.85%29.aspx

Upgrade and compatibility

A direct upgrade to Foglight For SQL Server 5.9.4.10 is only available from version 5.7.5.x or above. Customers that are running 5.7.x of the product must first upgrade to version 5.7.5.x and then upgrade to version 5.9.4.10. A direct upgrade to Foglight for SQL Server 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 SQL Server is version 5.5.8 and you are going to upgrade to version 5.9.4.10, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x (or above) > 5.9.4.10.

Foglight for SQL Server 5.9.4.10 requires:

Management Server version 5.9.2, 5.9.3, or 5.9.4
Agent Manager version 5.9.2, 5.9.3, or 5.9.4

To upgrade Foglight for SQL Server:

Install version 5.9.4.10 of the cartridge as you would install a new Foglight for SQL Server cartridge. Do not delete the older version of the .car file. Install version 5.9.4.10 over the older version.
For cartridge installation instructions, see the Foglight for Databases Deployment Guide.

Once you have upgraded the cartridge, to deploy the agent package, navigate to the Global View dashboard and follow the upgrade wizard instructions. For a procedure describing how to deploy the agent package, see the Foglight for Databases Deployment Guide.

Note: Foglight for SQL Server 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 SQL Server 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

Platform

Foglight Management Server

5.9.2

5.9.3

5.9.4

All platforms supported by these versions of the Foglight Management Server

Foglight Agent Manager

Note: The monitoring agents available in this version of Foglight for SQL Server support the Agent Manager HA failover mode, except for the Agent Manager monitoring SQL PI agents. For more information about this mode, see the Agent Manager Guide.

5.9.2

5.9.3

5.9.4

All platforms supported by these versions of the Foglight Agent Manager

System requirements

Before installing Foglight for SQL Server, ensure that your system meets the hardware and software requirements detailed in Foglight System Requirements and Platform Support Guide. Customers running large deployments (more than 20 agents) should consult the Foglight for Databases Deployment Guide.

Supported Platforms

Foglight for SQL Server supports monitoring the following platforms:

Supported SQL Server versions:
- SQL Server 2005 through 2017
Supported Operating Systems:
- All Operating Systems supported by Microsoft® SQL Server

Notes:

Foglight for SQL Server also supports the Express and Developer editions of Microsoft^® SQL Server.
Virtualization monitoring requires installing the VMware tools service on the monitored VM.
SQL Server on AWS VM (IaaS) is supported and can be monitored as long as the Instance port is opened and the OS is configured as described in: Configuring Windows Remote Management (WinRM)

Final Browser Support Notice

Support for Microsoft® Internet Explorer® 8, 9, and 10 has been discontinued in this Foglight release.

Microsoft ended the support for these browsers on January 12, 2016. For more information, visit https://support.microsoft.com/en-us/lifecycle?p1=13418.

Troubleshooting

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:

To verify TCP/IP connectivity for SQL statement collections, Management Studio (SSMS) cannot be used as other protocols may be leveraged. Instead, verify connectivity using a UDL as detailed here: http://support.microsoft.com/kb/308075/
To verify the WMI connectivity using a Microsoft® Windows® built-in utility, see http://technet.microsoft.com/en-us/library/cc180684.aspx
To troubleshoot WMI access permissions, see http://blogs.technet.com/b/askperf/archive/2007/08/14/wmi-troubleshooting-permissions.aspx
For information about WMI connectivity from Windows Server® 2003/ Windows Vista® and later versions, see http://msdn.microsoft.com/en-us/library/aa822854(VS.85).aspx
For WMI troubleshooting tips and techniques, see http://msdn.microsoft.com/en-us/library/aa394603(VS.85).aspx
For PI troubleshooting tips: exclude the SQL PI repository directory (named Infobright™) from real-time scanning (for example, Antivirus
software). For a virtual machine, the CPU and memory allocations must be reserved.

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 SQL Server 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:

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

Getting started with Foglight for SQL Server

Contents of the release package

The Foglight for SQL Server 5.9.4.10 release package contains the following:

Foglight for SQL Server cartridge:
- DB_SQL_Server-5_9_4_10.car
Product documentation, including:
- Foglight for SQL Server User and Reference Guide (PDF and online help)
  Note: This guide has not been updated for this release. The previous version of this document is relevant for the current release as well.
- Foglight for Databases Deployment Guide (PDF)
- Foglight for SQL Server Release Notes (this document)

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:

Online product documentation (http://documents.quest.com/ProductsAZ.aspx#F)
Foglight Community https://www.quest.com/community/products/foglight/

Globalization

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 https://www.quest.com/company/contact-us.aspx/.

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 https://support.quest.com.

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:

Submit and manage a Service Request.
View Knowledge Base articles.
Sign up for product notifications.
Download software and technical documentation.
View how-to-videos.
Engage in community discussions.
Chat with support engineers online.
View services to assist you with your product.

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 www.quest.com/legal. 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 Amazon.com, 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.

General Issues

Execution Plan

Supported Platforms

Contents of the release package

Installation instructions

Globalization

Copyright© 2019 Quest Software Inc.