Analytics 7.6 features the following performance improvements:
Analytics 7.6 includes the following new cubes:
Visibility in slot status in terms of used, idle, closed, or down states against the total available slot capacity.
Visibility in slot usage in terms of running, pending, or suspending states against the total available slot capacity.
Using this cube, you can check data latency, which data flow is experiencing problems, and by how many days a problematic data flow is behind.
Analytics 7.6 now includes the following new features for manageability and troubleshooting.
Analytics 7.6 includes the following changes:
The following table describes the supported operating systems for the Analytics server host. The Analytics server host must be a Windows 2003 or Solaris 10 host to install the Cognos tools. For additional requirements, refer to the Cognos documentation.
If you do not wish to generate cubes with the Analytics server, you may proceed with the installation if the host does not meet the Cognos requirements. The Analytics server host can be a Linux, Solaris, or Windows host if you are not installing Cognos tools.
After installing Analytics on a cluster running LSF 6.2, 7.0.4, or 7.0.5, the data loaders do not obtain any job data. This is because, by default, LSF 6.2, 7.0.4, and 7.0.5 do not enable the lsb.stream file for the exporting of LSF job event data, while Analytics requires this to be enabled for the data loaders to obtain job data.
To resolve this issue, you need to enable the lsb.stream file for the exporting of LSF job event data.
When installing Cognos, you must select the default locale (United States) and language (English); otherwise, you cannot open published cube views and you may see an error message stating that "The request failed because there is no valid cube mapping to handle the request".
If you encounter this problem, you must reinstall Cognos using the default locale and language, then reinstall the Analytics server.
If you have an Analytics node running on an AIX or HP-UX host, the LSF event data loader (lsfeventloader) may report "Could not parse the record" in the log.
This issue occurs because the field length for each event is limited to 512 characters, which may not be enough for AIX or HP-UX hosts.
To resolve this issue, download and apply the appropriate patches for LSF 6.2 or LSF 7.0.5 from the Platform FTP site (ftp.platform.com) for LSF. These patches do not work for other versions of LSF.
After installing Analytics using a clean database, if you start the Analytics node before starting the Analytics server, the node will not send events. This problem only occurs the first time after installation.
The EVENT_MANAGER_CONF table for the event locator is not initialized until you start the Analytics server for the first time. Therefore, if you start the Analytics node without first starting the Analytics server after initial installation with a clean database, the event sender does not have access to the EVENT_MANAGER_CONF TABLE until you start the Analytics server.
To resolve this issue, restart the Analytics node after you start the Analytics server.
When upgrading Analytics from version 7.1, if Analytics is installed on a shared file system, the upgrade package may stop responding if the shared file system is not fully stable.
This is an issue with the InstallShield Multiple Platform (ISMP) on which the upgrade package is built.
To work around this issue, kill the upgrade process and run the upgrade package again.
If the database host is disconnected from the network, DLP does not activate within 15 minutes, resulting in data loss. This does not occur if the database goes down, but the database host is still physically connected.
This is an issue with the Oracle JDBC driver. To work around this issue, restart the loader controller after the database host is physically disconnected from the network.
In the FLEXnet events data loader properties file (flexliceventloader.properties), if you defined the LicenseLogFile parameter to point to a Windows UNC file path or to a mapped network drive, the data loader log file shows a "not a valid file" or "does not exist" error for "FlexlmEventParser.java".
The FLEXnet events data loader (flexliceventsloader) does not support mapped network drives and has limited support for UNC file paths.
To work around this issue, use a slash (/) to define a UNC file path or a local Windows file path rather than a backslash (\). For a mapped network drive, use the UNC file path instead of the mapped network file path.
If you have an Analytics node running on a UNIX host, the FLEXnet usage data loader (flexlicusageloader) log may report "Failed to obtain license usage from the license server" and "Not enough space" errors. This problem does not apply to Windows hosts.
This error occurs if you have insufficient disk space allocated to the swap space on that host. To work around this issue, extend the swap space so it has at least 2 GB of free space on that host before starting the Analytics node on the host.
If you have an Analytics node running on a Linux host (running the linux2.4-glibc2.2 platform), the FLEXnet usage data loader (flexlicusageloader) log may report the following lmutil errors:
lmutil: /lib/i686/libc.so.6: version `GLIBC_2.3' not found (required by ./lmutil)lmutil: /lib/i686/libc.so.6: version `GLIBC_2.3.2' not found (required by ./lmutil)
This error occurs because the lmutil utility bundled with Analytics cannot run on linux2.4-glibc2.2 platforms. To work around this issue, either install the Analytics node on a host running linux2.4-glibc2.3 (or newer) platforms, or download an older version of lmutil from the Platform FTP site:
In the Analytics Console, if you click Data Collection Nodes, you may see that the loader controller is Down. However, if you examine the loader controller service (plc) in the Analytics node (using perfadmin list) the loader controller service is STARTED.
This issue may occur because you incorrectly defined the loopback IP address (127.0.0.1) as the name of your host rather than localhost in the /etc/hosts file, or if your host has multiple network interface cards (NICs).
To fix this problem, you need to change the loopback IP address and NSS (Name Service Switch) configuration.
If you have two or more license servers in different time zones, the wi_licutilfeaturemart datamart contains inaccurate information. This issue occurs when you have license servers with the same license feature running in different time zones.
To work around this issue, ensure that license servers with the same license feature are running in the same time zone.
On Solaris hosts, when you stop the Analytics daemons (using daemons.sh stop) the BuildCubes Java process does not stop.
To work around this issue, after stopping the Analytics daemons, find the cube build Java processes by running ps ‑ef | grep ‑i java | grep ‑i cube, then manually kill the relevant Java processes.
Analytics 7.6 includes fixes for the following bugs and known issues:
Contact Platform Computing or your Analytics vendor for technical support. Use one of the following to contact Platform technical support:
You can take advantage of our Web-based self-support available 24 hours per day, 7 days a week ("24x7") by visiting my.platform.com. The Platform eSupport and Support Knowledgebase site enables you to search for solutions, submit your support request, update your request, enquire about your request, as well as download product manuals, binaries, and patches.
To get periodic patch update information, critical bug notification, and general support notification from Platform Support, contact supportnotice‑request@platform.com with the subject line containing the word "subscribe".
To get security related issue notification from Platform Support, contact securenotice‑request@platform.com with the subject line containing the word "subscribe".
© 1994-2010, Platform Computing Inc.
Although the information in this document has been carefully reviewed, Platform Computing Inc. (“Platform”) does not warrant it to be free of errors or omissions. Platform reserves the right to make corrections, updates, revisions or changes to the information in this document.
UNLESS OTHERWISE EXPRESSLY STATED BY PLATFORM, THE PROGRAM DESCRIBED IN THIS DOCUMENT IS PROVIDED “AS IS” AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL PLATFORM COMPUTING BE LIABLE TO ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION ANY LOST PROFITS, DATA, OR SAVINGS, ARISING OUT OF THE USE OF OR INABILITY TO USE THIS PROGRAM.
This document is protected by copyright and you may not redistribute or translate it into another language, in part or in whole.
You may only redistribute this document internally within your organization (for example, on an intranet) provided that you continue to check the Platform Web site for updates and update your version of the documentation. You may not make it available to your organization over the Internet.
LSF is a registered trademark of Platform Computing Corporation in the United States and in other jurisdictions.
POWERING HIGH PERFORMANCE, PLATFORM COMPUTING, PLATFORM SYMPHONY, PLATFORM JOBSCHEDULER, and the PLATFORM and PLATFORM LSF logos are trademarks of Platform Computing Corporation in the United States and in other jurisdictions.
UNIX is a registered trademark of The Open Group in the United States and in other jurisdictions.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Windows is a registered trademark of Microsoft Corporation in the United States and other countries.
Macrovision, Globetrotter, and FLEXnet are registered trademarks or trademarks of Acresso Corporation in the United States of America and/or other countries.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
Intel, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Other products or services mentioned in this document are identified by the trademarks or service marks of their respective owners.