Page History
Before upgrading your Precise installation, be sure to review this topic as well as the following topics:
| Info |
|---|
This document describes the procedure when upgrading to Precise 910. 83.0 and 10.3.1. You must first upgrade to version 910. 7.02 before attempting to upgrade to Precise 10.3.0, and then must be on version 10.3.0 to upgrade to 10.3.1. If version 9.8.0.Therefore, if you are upgrading from an earlier Precise installation, see the relevant Upgrade Guide, or if you are installing Precise 910.83.0 1 on a clean system, see instead the Installing Precise Installation GuideComponents. |
About
...
upgrading to Precise
...
10.
...
3.
...
1
Updating to Precise 10.3.1 is simply an update to Precise
...
10.3.0 already installed in your environment.
To ensure an efficient and successful upgrade, be sure to read and implement the preparations for the update as they appear in Planning the upgrade.
Once all preparations are complete, perform the update as detailed in Performing the upgrade.
About upgrading to Precise 10.3
Updating to Precise 10.3 8.0 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 , be sure to read and implement the preparations for the update , as they appear in Planning the upgrade.
Once all preparations have been completedare complete, perform the update , as detailed in Performing the upgrade.
Changes in the Precise for Web logic
In version 9.6.1, we made changes in Precise for Web logic with regard to the Collector settings. They were changed from Domain related to Instance and Cluster related.
During the conversion, we analyzed per instance the usage of each domain and applied the existing settings based on the results. This process may have resulted in the loss of some non-recently used domain settings for that specific instance.
The default parameter settings after the update for all instances and clusters is Parameter name only regardless of the previous definitions.
The maximum amount of entries in the Exceptions table is 15.
Changes in the Precise for Web configuration
In version 9.6.1, the User-defined configuration changed. We no longer support User Defined 1 and User Defined 2. If you defined them in a previous version and you want to keep using them, you may need to redefine the User Defined 1 and 2 as User Defined Transaction Name. It is also possible that the definition can no longer be used.
Changes in supported platforms
In version 9.6.1, Precise for Tuxedo is no longer supported. If you start the update process and Precise for Tuxedo is detected, you get the following error message:
You have Precise for Tuxedo configured for the environments below
Uninstall Precise for Tuxedo from the following environments:
Uninstall Precise for Tuxedo in the indicated environments and restart the update or refrain from upgrading to Precise 9.6.1 or later.
Discovering any integrity issues
...
| Info |
|---|
The upgrade to version 910.8.0 3 can be done only from version 910.7.02. |
The version Version Upgrade Verifier Utility utility is a standalone utility that should be you must run prior to upgrading to the upgrade to Precise 9.8.0latest version of Precise. The utility will checkchecks, fix fixes (when possible), and report reports on integrity issues in the Precise infrastructure. By running and following its recommendations, it will reduce the chances for reduces the chance of integrity issues when performing the upgrade to the latest version 9.8.0.
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 by checking that:
- Checks that an AppTier is connected to the environment
- Checks that an instance is connected to an AppTierChecks
- 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 validChecks 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 (instances - ones without a server or without an apptierAppTier)
- 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 - Required : 3GB required disk space: 3GB
- On any other Precise listener - Required : 1GB required disk space: 1GB
- Checks for de-supported instances -:
- WEB SAP ABAP instance
- Siebel WEB instance with client side monitoring
- Instances monitored using Web Client Collector
- Microsoft .Net NET SQL Server monitoring
- Oracle version is 9 and below
- Checks for de-supported installation -:
- Web static instrumentation
- SQL Server Hitachi Storage
- Oracle Hitachi Storage
- Oracle Shark Point Storage
- Oracle Veritas Storage
- Precise for Tuxedo environments are no longer supported.
- 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 cannot 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
- Upgrade from SQL Freemium is blocked
- Checking Checks .NET version on Windows servers
- Checking Checks for missing column (
TPTN_SHORTST_RESPONSE_TIME_MIN) in tablesPWtablesPW_TPTN_TRAN_STATS_BandPW_TPTN_USERS_STATS_Band adding adds it, if necessary - Checking Checks for s390 serversChecking for federation dependency
- Checking Checks for Custom Alerts custom alerts in federation
This utility should be executed and its recommendations should be handled prior to starting the upgrade to the latest version 9.8.0.
Trying to upgrade prior to successful completion of this utility will fail.
...
- Download the utility.
- Place UpgradeTo9UpgradeTo10xxVerifier-<latest date>.zip in the Precise root directory on the MAIN Precise FocalPoint server.
- Extract/unzip the UpgradeTo9xxVerifierUpgradeTo10xxVerifier-<latest date>.zip file into the Precise root directory or extract the files, then move them to the Precise root directory.
Execute the verifier:
On Windows:
Windows (Rename UpgradeTo9xxVerifierUpgradeTo10xxVerifier.bat.txt to UpgradeTo9xxVerifierUpgradeTo10xxVerifier.bat)
UpgradeTo9xxVerifier UpgradeTo10xxVerifier.bat
On UNIX:
UNIX (Make sure the UpgradeTo9xxVerifierUpgradeTo10xxVerifier.sh has 'execute' permissions)
./UpgradeTo9xxVerifierUpgradeTo10xxVerifier.shInfo Log file with the output of the utility will be written to: <Precise root>\logs\infra.pre_upgrade_sanity.out.