Upgrade the Data Aggregator

To upgrade the Data Aggregator, complete the following steps:
capm320
To upgrade the Data Aggregator, complete the following steps:
2
If you enabled FIPS-compliant encryption, and you upgrade
Performance Center
before the Data Aggregator, temporary FIPS compatibility synchronization errors occur. These errors occur until the Data Aggregator is upgraded. To avoid this temporary condition, upgrade the Data Aggregator before upgrading
Performance Center
.
Before you upgrade, verify the zip and unzip packages are installed. If these packages are not installed, use the following command to install them:
yum -y install zip unzip
For the Data Aggregator and the Data Collectors, the default maximum memory is 80% of the total system memory. AMQ uses 20% of total memory on both components. Both components reserve 2 GB of memory for the operating system. These maximum values can be modified, however the modifications are not preserved during an upgrade. For more information, see Modify Maximum Memory Usage for Data Aggregator and Data Collector Components.
Verify the Limit on the Number of Open Files on Data Aggregator
Verify that the user that is installing Data Aggregator has a limit of at least 65536 on the number of open files. Set this value permanently.
Follow these steps:
  1. As the root user or a sudo user, log in to the Data Aggregator host.  
  2. Change the ulimit for the open files limit to at least 65536:
    ulimit -n 
    ulimit_number
    For example:
    ulimit -n 65536
  3. Open the following file:
    /etc/security/limits.conf
  4. Add the following lines:
    # Added by Data Aggregator
    * soft nofile 65536
    # Added by Data Aggregator
    * hard nofile 65536
    Restart Data Aggregator for these changes to take effect. If you are upgrading, the upgrade process automatically restarts Data Aggregator.
  5. Verify that the number of open files is set properly:
    ulimit -n
    The command returns the limit that you specified earlier.
Verify That the Data Repository Is Running
The Data Aggregator Upgrade requires that the Data Repository is running.
Follow these steps:
  1. Log in to the Data Repository host.
  2. Verify that the Data Repository is running:
    /opt/vertica/bin/vsql -U
    dauser
    -w
    dapass
    -c 'select version()'
    The expected return shows the version of the Data Repository:
                  version
    ------------------------------------
     Vertica Analytic Database vx.x.x-x
Upgrade the Data Aggregator
If you launch the Data Aggregator installer from a secure shell or console and you are not running an X Window System, the installer launches in console mode.
Follow these steps:
  1. Log in to the Data Aggregator host as the root user or a sudo user.
  2. Copy the installDA.bin file to the /tmp directory.
  3. Change to the /tmp directory:
    cd /tmp
  4. Change permissions for the installation file:
    chmod a+x installDA.bin
  5. To run the upgrade, do one of the following steps:
    • Run the installation as the root user:
      ./installDA.bin -i console
    • Run the installation as the sudo user:
      sudo ./installDA.bin -i console
      For environments that support a GUI, remove the following argument to run the upgrade in GUI mode:
      -i console
      To generate a response file for silent upgrade, add the following argument:
      -r
      response_file
      response_file_directory
      specifies the directory the directory path and file name for the response file.
      Example:
      /temp/installer.properties
      To run the upgrade in silent mode, use the following command:
      ./installDA.bin -i silent -f 
      response_file
      response_file
      is the directory path and file name of the previously generated response file.
  6. Follow the instructions in the console.
    If the Data Repository was migrated, follow the Data Aggregator upgrade instructions in the console, and answer NO when prompted to drop the schema and the upgrade continues. If you answer YES, you lose your migrated data.
    Data Aggregator is upgraded. The console displays a confirmation message.
    The installer restarts Data Aggregator automatically when the upgrade is complete.
    Wait for Data Aggregator to synchronize automatically with CA
    Performance Center
    . This process can take 30 minutes or longer.
  7. Verify that Data Aggregator is running:
    service dadaemon status
  8. Verify access to the Data Aggregator REST endpoints. Open a web browser on a computer with HTTP access to Data Aggregator. Navigate to the following address:
    http://
    data_aggregator
    :port/rest
    data_aggregator:port
    specifies the Data Aggregator host name and the required port number.
    The return is a list of hyperlinks for available web services. When you click a link, the XML content describing the selection displays.
    Table segmentation is required for systems where the original installation was a release earlier than 2.3.3. Segmentation is a one-time task that improves database performance and reduces the required disk space. If you received a message during the upgrade that the database tables require segmentation, complete table segmentation after the upgrade. For more information, see Segment Database Tables.
    The Karaf log on the Data Aggregator includes the following error after upgrading the installation:
    ERROR | tenderThread-178 | 2013-01-24 13:36:40,431 | ndorCertificationPriorityManager | nager.core.cert-mgr.impl |
          | Failed to load the MetricFamilyVendorPriority for bundle: BundleURLEntry [bundle=198, resourceURL=file:/opt/IMDataAggregator/apache-karaf-<
    vers
    >/data/cache/resources/198--xml-vendorpriorities-ReachabilityVendorPriorities.xml
    This error for Reachability is expected and harmless. Other occurrences of this error are not expected.