You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

Before upgrading your Precise installation, be sure to review this topic as well as the following topics:

This document describes the procedure when upgrading to Precise 10.1. You must first upgrade to version 10.0 before attempting to upgrade to the latest version.

Therefore, if you are upgrading from an earlier Precise installation, see the relevant Upgrade Guide, or if you are installing Precise 10.1 on a clean system, see instead the Precise Installation Guide.

About the upgrade to Precise 10.1

Updating to Precise 10.1 both updates the existing Precise Framework and agents and replaces the previously existing Precise system, while preserving the previously captured monitored data. As a result, the upgrade process involves downtime of the Precise product.

To ensure an efficient and successful upgrade process, verify that you read about and implement the preparations for the update, as they appear in Planning the upgrade.

Once all preparations have been completed, perform the update, as detailed in Performing the upgrade.

Discovering any integrity issues

The upgrade to version 10.1 can be done only from version 10.0.

The version Upgrade Verifier Utility is a standalone utility that should be run prior to the upgrade to the current version of Precise. The utility checks, fixes (when possible), and reports on integrity issues in the Precise infrastructure. By running and following its recommendations, it reduces the chance of integrity issues when performing the upgrade to the latest version.

The utility performs the following:

  • Verifies that Precise FocalPoint is up
  • Connects to Performance Warehouse and all Oracle instances connection pools and warns in case of problem
  • Removes all dangling lines from INFRA DB:
  • Checks that:
    • an AppTier is connected to environment
    • an instance is connected to AppTier
    • an instance is connected to server
    • an installation is connected to server
    • an installation-instance connection is valid
    • an instance dependency connection is valid
    • an instance SLA is connected to instance
    • downtime calendar is connected to downtime rule
  • Warns:
    • about dangling instances (ones without a server or without an apptier)
    • in case any Precise Listener is down
    • in case invalid registry file (such as Copy of, or not matching file name to XML) is located
  • Checks:
    • that all framework FocalPoints are on the same server
    • for unsupported instances
    • that there are no pending action items
    • for sufficient disk space:
      • on Precise FocalPoint machine: 3GB required disk space
      • on any other Precise listener: 1GB required disk space
    • for de-supported instances:
      • WEB SAP ABAP instance
      • Instances monitored using Web Client Collector
      • Microsoft .Net SQL Server monitoring
      • Oracle version is 9 and below
    • for de-supported installation:
      • Web static instrumentation
  • Monitors view permissions using AppTier, instance or technology scopes are no longer supported. Instead, upgrade the role to use environment scope.
  • Verifies that the proxy relay can't be used during the upgrade process.
  • Backs up all action items
  • Checks:
    • for antiviruses that may cause for locked files errors
    • patches that are required for pre/post upgrade
    • whether the PMDB tablespace folder specified in the registry exists (only for Oracle based PMDB)
    • whether the <hsql-upgraded> tag exists in pools.xml. If it does, remove it
    • for uninstalled ddml files under <Precise root>/products/dbms/files/tables_definition/ and renames any relevant file to *.uninstall
    • the Microsoft .NET version on Windows servers
    • for the missing column (TPTN_SHORTST_RESPONSE_TIME_MIN) in tables PW_TPTN_TRAN_STATS_B and PW_TPTN_USERS_STATS_B and adds it if necessary
    • for federation dependency
    • for Custom Alerts in federation

This utility should be executed and its recommendations should be handled prior to starting the upgrade to the latest version.

Trying to upgrade prior to successful completion of this utility will fail.

Using the Precise Upgrade Verifier Utility

  1. Download the utility.
  2. Place UpgradeTo10xxVerifier-<latest date>.zip in the Precise root directory on the MAIN Precise FocalPoint server
  3. Extract/unzip the UpgradeTo10xxVerifier-<latest date>.zip file into the Precise root directory or extract the files, then move them to the Precise root directory

  4. Execute the verifier:
    On Windows:
    (Rename UpgradeTo10xxVerifier.bat.txt to UpgradeTo10xxVerifier.bat)   
    UpgradeTo10xxVerifier.bat

    On UNIX:
    (Make sure the UpgradeTo10xxVerifier.sh has 'execute' permissions)
    ./UpgradeTo10xxVerifier.sh

    Log file with the output of the utility will be written to: <Precise root>\logs\infra.pre_upgrade_sanity.out.

  • No labels