Some or all of the Vertica nodes may fail to start up and have the following error:
Large:Memory(KB) Exceeded: Requested = number, Free = number
This error occurs because of an issue with the Resource Manager in Vertica. To resolve this issue, you need to disable the Resource Manager before running the database, then enable the Resource Manager after the database has started up. The resolution method depends on whether all Vertica nodes failed to start up, or if only some Vertica nodes failed to start up.
After installing Platform Analytics using a clean database, if you start the Platform Analytics node before starting the Platform 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 Platform Analytics server for the first time. Therefore, if you start the Platform Analytics node without first starting the Platform 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 Platform Analytics server.
To resolve this issue, restart the Platform Analytics node after you start the Platform Analytics server.
If you have an Platform 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 Platform Analytics node on the host.
In the Platform 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 Platform 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.
This is applicable only for the 7.x cluster.
The Cluster Capacity and Workload Statistics workbook displays parallel job execution hosts as one host and gets the data from the first execution host even though parallel jobs are running on different hosts. For example, if a parallel job execution host is “3*hostA 4*hostB�, the cluster capacity data transformer assumes that 7 slots are occupied by host A.
If you have multiple license vendor daemons on a license server sharing the same port, the license usage data for those license vendor daemons may not be correct. To work around this issue, download the older version of lmutil from the Platform FTP site.
Download the lmutil binary from patches/lsf_analytics/8.0/FLEXlm9.2/<platform> and move it to ANALYTICS_TOP/license/7.0/<platform>/...
The Platform Analytics node installation will fail when the LSF_VERSION defined in the lsf.conf file is not the actual version.
To resolve this issue, before you install the Platform Analytics node, edit lsf.conf to change LSF_VERSION to an appropriate version. For example, if the actual LSF version is 7.x but if the LSF_VERSION in lsf.conf is set to "active", then before you install the node change the LSF_VERSION to 7.0. After installing the node change the LSF_VERSION back to “active�.
Data shown in the table is not accurate in some of the roll-up levels as it considers the sampling points of data instead of whole date period.
For example, the following data shows sampling points of data for slots number with different slot status:
In the Cluster Usage table , average slots number for the RUN status rolled up to the hour 10 is (1 + 1) / 2 = 1. The graph data shows the correct value, which is (1 + 1) / 6= 0.33
As a workaround, refer to the Cluster Usage graph for more accurate data.
In the Projects dashboard of Workload Accounting report, if you select big data and try to sort, the reporting server may display the following error: 'Unexpected Server Error: Session busy, please try later.' For example, if you select data more than 3 years and try to drill down to a specific year that has more than 20K projects and sort as project name, you will see that error.
To avoid the error, narrow down the data range or try to view using the Platform Analytics Designer.