Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

This document describes the procedure when upgrading to Precise 10.2. You must first upgrade to version 10.1 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 Installing Precise Installation GuideComponents.

About the upgrade to Precise 10.2

...

The Version Upgrade Verifier utility is a standalone utility that should be you must run prior to the upgrade upgrading to the latest 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 tasks:

  • Verifies that Precise FocalPoint is up
  • Connects to Performance Warehouse and all Oracle instances connection pools and warns in case of if a problem occurs
  • Removes all dangling lines from INFRA DB as follows:
    • Checks that an AppTier is connected to the environment
    • Checks that an instance is connected to an AppTier
    • Checks that an instance is connected to a server
    • Checks that an installation is connected to a server
    • Checks that an the installation-instance connection is valid
    • Checks that an the instance dependency connection is valid
    • Checks that an instance SLA is connected to the instance
    • Checks that the downtime calendar is connected to the downtime rule
  • Warns about any dangling instances (ones instances without a server or without an AppTier)
  • Warns in case if any Precise Listener is down
  • Warns in case if an 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
  • Checks for unsupported instances
  • Checks that there are no pending action items
  • Checks for sufficient disk space
    • On Precise FocalPoint machine: 3GB required disk space
    • On any other Precise listener: 1GB required disk space
  • Checks 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
  • Checks for de-supported installation:
    • Web static instrumentation
  • Monitor view permissions using AppTier, instance or technology scopes are no longer supported. Instead, upgrade the role to use environment scope.
  • 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
  • Checks patches that are required for pre/post upgrade
  • Checks if the PMDB tablespace folder specified in the registry exists (only for Oracle based PMDB)
  • Checks if <hsql-upgraded> tag exists in pools.xml. If it does, remove it
  • Checks for uninstalled ddml files under <Precise root>/products/dbms/files/tables_definition/ and renames any relevant file to *.uninstall
  • Checking .NET version on Windows servers
  • Checking for missing column (TPTN_SHORTST_RESPONSE_TIME_MIN) in tablesPW_TPTN_TRAN_STATS_B and PW_TPTN_USERS_STATS_B and adding it if necessary
  • Checking for federation dependency
  • Checking for custom alerts in federation

...