Foglight® for Oracle 5.9.5.20
Developed and tested for Foglight Management Server 5.9.2, 5.9.3, 5.9.4, 5.9.5, and 5.9.7
Release Notes Revision 1
April 2020
Revision 1:
Foglight for Oracle 5.9.5.20 Release Notes Revision 1 is a re-release of the Foglight for Oracle 5.9.5.20 Release Notes with the following change:
Welcome to Foglight for Oracle
Resolved issues and enhancements
Getting started with 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 5.9.5.20 release of Foglight for Oracle. Review all sections before starting installation.
Version 5.9.5.20 contains the following new features and updates:
The following is a list of issues addressed and enhancements implemented in this release.
Defect ID |
Resolved Issue |
FOGDG-1298 |
Fixed an issue that failed to load the SQL-Server-Rules.csv by "AbstractRuleManagment". |
FOGDG-1323 |
Fixed an issue that the potential email notification string combination is incorrect. |
PIFOG-670 |
Fixed an issue that the Object Analysis tab in Analyze Plan dashboard cannot display or cannot display object detail. |
PIFOG-697 |
Fixed the duplicate instance keys found in the agent ASP. |
PIFOG-704 |
Fixed an issue when the authentication type has been changed, the JDBC connection pool did not refresh. |
PIFOG-705 |
Fixed an issue when accessing PI admin screen, the agents do not appear immediately. |
ORAFOG-432 |
Fixed an issue that the Oracle CPU metric displayed in Global View is discrepant from that displayed in Overview. |
ORAFOG-839 |
Fixed an issue that user cannot migrate agents monitored with user sys. |
ORAFOG-893 |
Fixed an issue that the instance name is wrong when opening Locks dashboard through Blocked Sessions link at Overview page. |
ORAFOG-899 |
Fixed an issue that the bar chart in the alert log dashboard does not use integer type to display message count (e.g. 6.0 messages). |
ORAFOG-903 |
Fixed double calling to the RMI when retrieving trace (.trc) file content for Oracle. |
ORAFOG-904 |
Fixed an issue when retrieving a big trace file from Amazon RDS Oracle in Alert log dashboard, it takes too much time (about 65 secs for 4000 rows). |
ORAFOG-917 |
Fixed an issue that agents are not collecting Oracle Tablespace data. |
ORAFOG-918 |
Fixed an issue when Oracle RAC connection using sysdba user, it cannot pass test connection in connection detail page. |
The following is a list of issues known to exist at the time of this release.
Defect ID |
Known Issue |
FOGDG-858 |
DB instance is still synchronized and displayed in FMS federation master even when it is stopped for some reason and not displayed in the FMS federation child. |
ODB-2829 |
When running user-defined collections on dynamic tables, deleted items are still kept in the topology. As a result, the number of rows displayed on the user-defined collections table will exceed the configured value for maximum allowed rows. |
ODB-2984 |
In the Global Administration > User-defined Collections screen, it is possible to create two collections that bear the same name with a different capitalization (for example: MyCollection and Mycollection); however, only one collection will appear in the topology, and be displayed on the User-defined Collections panel. |
ODB-3029 |
Creation of user-defined collections for a RAC database should be executed by selecting the RAC agent itself and not the RAC and its nodes. |
ODB-4002 |
Using the administration module to configure the sessions screen parameters for a single node in a RAC environment will result in all the RAC nodes being configured with the same parameter. |
ODB-4417 |
User-defined collections that return a variant number of columns (such as select * from ...) will only retrieve the columns that existed during its creation. Any additional columns added at a later time will be ignored. |
ODB-6784 |
Version 5.6.4 and above of the product uses only SSH to connect to Unix hosts. Customers upgrading from previous versions of the product that were using telnet will now be converted to use SSH |
ODB-6939 |
Customers that are monitoring instances using nslookup/IP and are upgrading to the new version of the product should create the infrastructure cartridge agents themselves manually. |
ODB-7064 |
"Challenge response" credentials do not appear in the advanced lockbox pop up. |
ODB-7171 |
The following metrics display NA when monitoring a RAC one node:
|
ODB-7208, ODB-7169 |
The current implementation does not support collecting listener data from remote Windows hosts using Windows local execution (the user that is currently running the agent manager). |
ODB-7427 |
The Listener graphs under the Usability dashboard are not populated with data when monitoring RAC One Node. |
ODB-7446 |
The following alarms are displayed in the RAC level instead of the instance level:
|
ODB-7452 |
Setting the connection details of a RAC One Node and failing the validation, will result in failure to save the changes. |
ODB-7454 |
The invalid objects exclude list is not supported for RAC and RAC One Node. |
ODB-7457 |
When converting RAC One Node to RAC the OS cluster failover alarm is triggered. |
ODB-7463 |
Upgrading an instance that has a legacy OS cartridge installed on its host will result in creation of the database agent without the creation of the infrastructure agent. Workaround: create the infrastructure agent manually. |
ODB-8272, ODB-8128 |
Foglight for Oracle supports monitoring OS clusters residing on VMware machines only in the configuration of one OS cluster node per data center; monitoring is not possible if two or more cluster nodes are located on different data center, to provide disaster recovery. |
ODB-8298 |
Upgrading an ASM agent that was created manually will result in a malfunctioning ASM agent that requires reconfiguration, unless the following fields in the agent settings are cloned: ASM Instances, Host Details, Environment Variables, Collection Details, and Exclude Diskgroups. |
ODB-8697 |
The Exclude Tablespace feature allows inserting tablespaces only by using the Java regular expression syntax, rather than wildcards. |
ODB-9129, ODB-9337 |
When selecting the RSA key connection type in the Exadata, ASM, and CRS installers, after loading the id_rsa file, the dialog box Add Cells is automatically refreshed, thereby resetting all other fields in the dialog box (Host name, User, Passphrase, Port, and sudo) leaving them empty. |
ODB-9143 |
Exadata, ASM and CRS agents are marked in the upgrade process as 'other agents', even though they are Oracle agents and should be marked as such. |
ODB-9215 |
The Global Administration does not support the CRS, Exadata and ASM agents. As a result, any modification of the settings of the collection frequencies, retention policies, alarms and email notifications for these agents can be carried out only using the default Foglight tools. |
ODB-9290 |
The CRS installation wizard does not support using the connection type Local user, when the monitored host runs on UNIX. Workaround: use command line installation (CLI) through the Silent Installer tool, which supports this configuration. |
ODB-9291 |
Using a virtual name when creating a CRS agent is not supported by either the CRS installation wizard or the Silent Installer tool (command line installation); both tools only support using a physical name or an IP address. |
ODB-9738 |
In an environment that includes a Foglight Agent Manager concentrator, when upgrading the environment where the concentrator does not contain any regular agents, the concentrator is not upgraded. Therefore, after the upgrade process takes place the Foglight Agent Manager concentrator has to be deployed manually. |
ODB-9739 |
When editing the properties of the Foglight Agent Manager concentrator (Dashboards > Administration > Agents > Agent Status), the name of the Foglight Agent Managers should be entered in the Downstream FglAMs section exactly as they appear in the topology, under Home > Agents > All agents > <Agent name> > RMI data > Fglam host property. |
ODB-9950 |
Oracle monitoring installer does not support validation for the required sudo commands. Therefore, the sudo user should be prepared before using it. For details, see Foglight for Oracle User Guide. |
ODB-10015 |
The following secondary parameters are not cloned when creating an agent using the Oracle Monitoring Installer:
Unless these parameters and cloned and modified by the user, the upgrade process will override them with the default values. |
ODB-10060 |
When a UNIX-based Foglight Agent Manager, which is selected for monitoring a Windows-based Oracle or ASM cluster, is using virtual IP to connect to the Oracle or ASM instance, the OS connection validation fails. Workaround: Use the virtual IP /physical IP/physical host name. |
ODB-10154 |
In order to allow the agent to connect to the remote Windows Management Instrumentation (WMI) components on Windows Server 2008 R2 or Windows 7 systems, special registry settings are required. For details, see section Configuring Registry Settings for Windows Server 2008 R2 and Windows 7 in Agent Manager Guide. |
ODB-10907 |
The following dashboards and views may be less responsive than others due to their complexity:
|
ODB-10918 |
Support for Oracle 12c has the following restrictions:
|
ODB-11467 |
In environments configured to use Agent Manager in High Availability mode the chosen Agent Manager hosting the SQL PI repository will host watchdog and maintenance agents that cannot participate in the Agent Manager high availability utility. |
ODB-12520 |
The following homepages were removed from the custom dashboards: Interconnect/GCS, Cluster Overview, Sessions, Instance identification and usability and Workload. |
ORAFOG-197 |
The offloadEfficiency metric has been changed to be internal and inaccessible as of Exadata software version 12.1.2.3.0, which causes the Exadata dashboard shows 'n/a' in ID, Name, and Status columns. |
ORAFOG-267 |
The Databases Global View dashboard shows negative and over 100% values for OS CPU metrics. |
ORAFOG-308 |
History data is missing if user upgrades the Foglight for Oracle cartridge 5.7.5.37 using the SPM installer. |
ORAFOG-313 |
The Activity > Storage dashboard stopped responding after clicking any chart in the Tablespaces view in FMS 5.7.1. Workaround: Upgrade the Management Server to version 5.7.5 or later. |
ORAFOG-315 |
Some error messages showed in the Management Server log, after disabling or enabling Alert log Groups. |
ORAFOG-323 |
The error "No views match input type of DBO_Drill_RealTime_InitializationParameters_Instance" shows on the Databases > Overview > Configuration dashboard. Workaround: This error only occurs on the Foglight Management Server 5.7.0. Upgrade your Management Server to a higher version. |
ORAFOG-324 |
The error "For the value "Parameters", no view is set" shows on the Databases > ASM dashboard. Workaround: This error only occurs on the Foglight Management Server 5.7.0. Upgrade your Management Server to a higher version. |
ORAFOG-342 |
The 'ibprintca.pl -l' command has been deprecated, which causes the infiniband switch operation fails. |
ORAFOG-564 |
After switchover occurs in the Data Guard environment it takes one hour to see data in the Primary Redo Generation Rate/Standby Apply Rate/Transport Rate charts in the Performance dashboard when database is monitored with SYSDBA credentials. |
ORAFOG-639 |
The Oracle agent fails to collect some OS related metrics after disabling and re-enabling the Foglight for Oracle cartridge. Workaround: On the Agent Status dashboard, deactivate and re-activate the agent, and then wait for five minutes. |
ORAFOG-643 |
The destination_name property in the Data Guard dashboard is missing after disabling and re-enabling the Foglight for Oracle cartridge. |
ORAFOG-660 |
Metrics of the monitored Host display n/a when an inactive host object binds to "OracleInstance.participatingHosts". |
ORAFOG-668 |
In Monitor Oracle Instance dialog box, Agent Manager Host cannot be retrieved when the default FglAM is null and FglAM list contains the Agent Manager which version is lower than system required version. |
ORAFOG-676 |
The Oracle upsince duration is miscalculated when FMS/FglAM and Oracle DB locate in different timezone. |
ORAFOG-714 |
Foglight for Oracle fails to validate the connection and grant privileges to data guard agents during the upgrade. Workaround: Skip the validation in upgrade page and go to the Administration > Connection Details dashboard. Change the user role from "Normal" to "SYSDBA", verify the connection and grant the privileges, and then save your changes. |
ORAFOG-721 |
Unable to create agents to monitor RAC via Installer Wizard when RAC nodes only support connection with service name. Workaround: Create an agent manually in the Agent Status dashboard, and then change its "monForceSid" in ASP to false. |
ORAFOG-734 |
If there are two credentials with the same account name existing in the Foglight Management Server, picking one credential in "Set Credential" and "Test connection" might cause the other credential to be updated as well. |
ORAFOG-753 |
If you select either of DB_Oracle, DB_Oracle_UI, DB_Global_View_UI, SPIRepository* cartridges then click Reset on the Cartridge Inventory dashboard, the upgrade wizard will prompt again. Workaround: Do the following: 1. Navigate to the Administration > Rules & Notifications > Manage Registry Variables dashboard. 2. Search for "DBO_Is_Fglams_Required_Upgrade registry". 3. Change its value to "-1". |
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:
|
Defect ID |
Known Issue |
|||||||||||||||
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. |
|||||||||||||||
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. | |||||||||||||||
PIFOG-725 |
SQL PI related agents are not added to FglAM HA deployment white list
by default. |
|||||||||||||||
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. |
|||||||||||||||
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:
|
Defect ID |
Known Issue |
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.
|
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. |
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 |
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:
|
n/a |
Monitoring an Oracle instance that resides on a
Windows 2008R2 or higher requires a workaround as follows:
|
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. |
n/a |
Oracle Bug 19509076: V$SEGSTAT table performance issues with Oracle version 12.1.0.x.x. |
A direct upgrade to Foglight for Oracle 5.9.5.20 is only available from version 5.7.5.x or later. 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.5.20. 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 5.9.5.20, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x (or later) > 5.9.5.20.
Foglight for Oracle 5.9.5.20 requires:
To upgrade Foglight for Oracle to version 5.9.5.20:
OR
Notes:
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 |
Platform |
Foglight Management Server |
5.9.2 5.9.3 5.9.4 5.9.5 5.9.7 |
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.9.2 5.9.3 5.9.4 5.9.5 5.9.7 |
All platforms supported by this version of the Foglight Agent Manager |
Before installing Foglight for Oracle, ensure your system meets the following minimum 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 20 agents) should consult the Foglight for Databases Deployment Guide.
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:
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:
For information on the required privileges, refer to the Foglight for Databases Deployment Guide.
This version of Foglight for Oracle supports usage of direct NFS client.
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.
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:
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:
The Foglight for Oracle 5.9.5.20 release package contains the following:
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 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.
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 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.
For sales or other inquiries, visit https://www.quest.com/company/contact-us.aspx.
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:
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.