Page History
Updating from v9.0.1 to v9.6.1
This section includes the following topics:
- About the update to Precise v9.6.1
- Planning the update
- Performing the update from Precise v9.0 to Precise v9.6.1
NOTE | This document describes the update procedure when updating from a Precise v9.0.1 installation to Precise v9.6.1. Therefore, if you are updating from an earlier Precise installation, see the relevant Upgrade Guide, or if you are installing Precise v9.6.1 on a clean system, see instead the Precise Installation Guide. |
About the update to Precise v9.6.1
Updating to Precise v9.6.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 update process involves downtime of the Precise product.
To ensure an efficient and successful update process, verify that you read about and implement the preparations for the update, as they appear in Planning the update on page 7.
Once all preparations have been completed, perform the update, as detailed in Performing the update from Precise v9.0.1 to Precise v9.6.1 on page 10.
Changes in the Precise for Web logic
In version 9.6.1, we have made changes in the Precise for Web logic with regards to the Collector settings. They have been changed from Domain related to Instance and Cluster related.
During the conversion, we analyze per instance the usage of each domain and apply the existing settings based on the results. This may result in the loss of some non-recently used domain settings for that specific instance.
The default parameter settings after the update for all instances & clusters will be "Parameter name only", regardless of the previous definitions.
The maximum amount of entries in the Exceptions table will be 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. Should you have defined them in the 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 version 9.6.1.
Planning the update
The update process should be planned in advance, to ensure both the full benefit from your v9.6.1 system and adherence to your schedules and needs.
To ensure a quick and efficient update, it is necessary to consider the following criteria before beginning the procedure:
- Prerequisites for the update
- The order of the servers update
- Downtime of the monitored technologies
- Downtime of the Precise product
- Update planning checklist
Prerequisites for the update
Before planning the update process, verify that:
- All minimum requirements were met before updating to v9.0.1, as per the Pre cise Minimum Requiremen ts for Ins tallation g uide.
- The Precise installation that is going to be updated is fully updated to v9.0.1. If it still has agents that were not yet updated to v9.0.1, complete the update to v9.0.1 prior to starting to update to v9.6.1.
- There is free disk space on the servers that have Precise v9.0.1 installed, as follows:
- 0.5GB on each server with Precise Agents
- 2.5 GB on the Precise Framework server
- There is 0.5GB free disk space on the client server that the update will be executed from.
- You do not have Precise for Tuxedo in your environment.
The order of the servers update
Your existing Precise installation typically spans many servers. Since the update to Precise v9.6.1 is performed per server, you should plan in advance the order in which you will update all servers comprising your existing Precise installation.
If you are not able to update all servers at once, but will update a few servers at a time, take note of the implications described in The implications of a phased update to Precise v9.6.1 on page 8.
The order of the server update is:
- First all FocalPoint servers need to be updated.
- Then all other servers can be updated.
When starting the update, you must select all the FocalPoints servers. You can add additional servers for the update later (once the FocalPoints servers are updated), or as part of the FocalPoint update (in this case the server update will start once the FocalPoint servers are completely updated).
The implications of a phased update to Precise v9.6.1
If you are not updating all servers at once, but are updating a few servers at a time, the following limitations will apply to your Precise system functionality:
- After an update has started, a server that has not fully completed the update cannot have instances installed, edited, or uninstalled.
- For installed Web and J2EE Clusters, new instances will not be installed until the cluster's servers are updated.
- If you have created a Template Listener as part of you server’s image, new Template Listener installations will fail after the update. You must recreate the Template Listener once the framework update has been completed.
Downtime of the monitored technologies
The update process does not require any downtime of the monitored technologies.
Downtime of the Precise product
The update process involves downtime of the Precise product itself as described below.
FocalPoints
When updating the servers with the Precise FocalPoints, your installed Precise performance monitoring system will not be in operation. Once the Precise Framework update is complete, Precise v9.6.1 will resume all performance monitoring previously provided by Precise v9.0.1.
The time required for updating a server with the Precise FocalPoints may vary depending on the strength of the server with the FocalPoint, the strength of the server where you are using AdminPoint to apply the update, the file transfer speed, the amount of Precise technologies monitored by Precise, and the time it takes to perform post-application action items. In general, updating a server with a Precise FocalPoint is estimated at one hour.
Updating a server with a FocalPoint will be fastest when application of the update is performed using AdminPoint on the Main node server with the Precise FocalPoint, and the update is located on storage providing good response time to that server.
If you have a federated Precise deployment, then when updating the servers with the FocalPoint of the Main node, your entire Precise federated deployment will not be operable for performance monitoring. When updating another node's servers with a FocalPoint, only that node will not be operable for performance monitoring.
Non-FocalPoint agents
Precise agents will not collect performance data while they are being updated. The time it takes to update a server running Precise agents varies depending on the technology type and the amount of Precise agents on that server, as well as the factors described above regarding updating the server with the Precise FocalPoints. In general, updating a Precise agents server is estimated at 20 minutes.
Update planning checklist
The following checklist can be used to verify that you are ready to start performing the update to Precise v9.6.1:
q my.precise.com was reviewed for a newer version of this document. If there is a newer version, download it and use it instead of this one.
q Minimum requirements for installation were all met prior to updating to v9.6.1.
q The update order of the Precise installation was planned according to The order of the servers update on page 7.
q Planning according to Planning the update on page 7 was completed.
q my.precise.com was reviewed for product updates.
q Downtime has been coordinated for the Precise product.
Performing the update from Precise v9.0.1 to Precise v9.6.1
The update is performed by downloading Precise v9.6.1, applying the update on the desired server(s), and performing additional actions that appear in AdminPoint before and after application.
NOTE | Before starting the update, it is recommended to download the latest infra hotfix for version 9.0.1 and install it on the Precise FocalPoint. Verify that you complete all action items before starting the update. |
To update from v9.0.1 to v9.6.1
- Verify that all planning and preparations as listed in Planning the update on page 7 have been completed.
- Download Precise v9.6.1 from http://my.precise.com.
NOTE | If you are updating to Precise v9.6.1 from the DVD provided by Precise, downloading and unzipping the product is not needed. |
- Complete the update procedure on the desired server(s). See “Applying the v9.0.1 to v9.6 update” on page 9.
OR
Complete the update procedure on the desired server(s) using the Precise CLI utility. See “Applying the update with the CLI utility” on page 10. - Verify that your Precise system is working properly. If you experience any problems, see http://my.precise.com or contact Precise Customer Support.
Applying the v9.0.1 to v9.6.1 update
To apply the update on Precise servers
- Go to AdminPoint >Setup> U pd ates and select Apply U pdat es. The Update Installation wizard opens.
- In the “Select Updates” screen, click Add U pdate and enter the \Upgrade v9.0.0 to v9.0.1\Upgrade\Upgrade to v9.6.1\Upgrade.zip file path from the folder you unzipped the v9.6.1 download to, or click the browse button and select the path, then click OK. The update will appear in the “Available Updates” table.
- Select the V961_UPGRADE update from the Available Updates table and, using the arrows between the tables, move it to the Updates to apply table.
NOTE | Once this step has been successfully completed, the update is saved in the Available Updates table. If, after this step has been successfully completed, the application process is restarted or repeated for any reason, skip this step. |
- Click Ne xt. The Select servers screen will appear. This screen displays all the servers to be updated.
NOTE | By default, all displayed servers will be selected to be updated. According to your preparation, as mentioned in The order of the servers update on page 7, you can choose to exclude servers which you do not want to update at this point by clearing their selection. |
- Click Ne xt. The update preparation will begin. If there are pre-action items screen (depends on your installation configuration) to be performed, they will appear on your screen. Perform the action items and mark them as done.
NOTE | At this point, while the Precise FocalPoint is being restarted, an empty screen may appear. |
- Once all pre-action items are completed, or if no pre-action items are required, the update will continue automatically. The Applying update screen will appear, displaying a progress bar for the update.
- After the update application is complete, additional steps appear on screen. It is recommended, but not mandatory, to perform each action item shown on screen before progressing to the next step.
- Click Ne xt. The “Finish” screen appears, announcing that the application is complete.
Applying the update with the CLI utility
The update can also be applied with the CLI utility. Before applying the update using the CLI utility, verify that you follow the planning and preparations mentioned above. To apply the update with the CLI utility, see Applying the v9.0.1 to v9.6.1 update using the CLI utility on page 11.
NOTE | All steps in Performing the update from Precise v9.0.1 to Precise v9.6.1 on page 10, except for those involving AdminPoint, are also relevant when applying the update with the CLI utility. |
About Precise Business Storage Optimizer
The Precise Business Storage Optimizer v9.6, included in the \Business Storage Optimizer folder of the Precise v9.6.1 download or DVD, is fully compatible with Precise v9.6.1.
2
Updating from v9.0.1 to v9.6.1 using the CLI utility
This section includes the following topic:
Applying the v9.0.1 to v9.6.1 update using the CLI utility
NOTE | Before starting the update using the CLI utility, you must download the latest infra hotfix for version 9.0.1 and install it on the Precise FocalPoint. Verify that you completed all action items before starting the update. |
To apply the upgrade update
- Run the CLI i3-update-load command to load the upgrade.zip file:
Windows infra\bin\psin_cli.bat
-action i3-update-load
-i3-user admin
-i3-clear-password admin
-zip-file Pr ecise DVD\Upg rade to v9.6.0\U pgrade.zip
UNIX ./infra/bin/psin_cli.sh
-action i3-update-load
-i3-user admin
-i3-clear-password admin
-zip-file Pr ecise DVD\Upg rade to v9.6.0\U pgrade.zip - Run the CLI i3-update-prepare command to prepare the update:
Windows infra\bin\psin_cli.bat
-action i3-update-prepare
-i3-user admin
-i3-clear-password admin
-{-servers “<ser ver s>” | -all-servers true}
-updates-ids V960_UPGRADE
UNIX ./infra/bin/psin_cli.sh
-action i3-update-prepare
-i3-user admin
-i3-clear-password admin
-{-servers “<ser ver s>” | -all-servers true}
-updates-ids V960_UPGRADE - Run the CLI i3-update-install command to apply the update:
Windows infra\bin\psin_cli.bat
-action i3-update-install
-i3-user admin
-i3-clear-password admin
{-servers "<servers>" | -all-servers true}
-updates-ids V960_UPGRADE
UNIX ./infra/bin/psin_cli.sh
-action i3-update-install
-i3-user admin
-i3-clear-password admin
{-servers "<servers>" | -all-servers true}
-updates-ids V960_UPGRADE - Perform the post-update action items that appear.
Troubleshooting
This section describes:
Troubleshooting the Precise Update
This section describes a number problems and solutions on how to solve problems that occur during the update of Precise.
An error occurs when running the prepare stage on the Precise FocalPoint server
When an error occurs during the prepare stage on the Precise FocalPoint, you may be asked to reopen the user interface. Using the “regular” URL will result in an error. Therefore use <precise-url>/admin.
When starting the update, a message appears to uninstall Precise for Tuxedo
This message indicates the environments in which Precise for Tuxedo is found. Precise for Tuxedo is no longer supported in Precise version 9.6.1 and therefore it needs to be uninstalled should you decide to perform update.
Glossary
abandonment rate | In Web, a counter that keeps track of the percentage of users that abandon the loading of the Web page before it completes downloading. |
action | An operation that Alerts FocalPoint automatically performs when detecting a warning or critical status for a specific metric. According to the defined action, Alerts FocalPoint opens a message box, sends an email or SNMP trap, or executes a program. |
action item (manual) | Some installation steps cannot be executed automatically by Precise Installer. The administrator is required to execute them manually. Action Items are presented (when necessary) at end of installation or product update. |
AdminPoint | The central administration console of Precise that facilitates the maintenance, configuration, and management of all installed Precise components, such as monitoring the status of all Precise agents and PMDB processes, getting license information, starting and stopping the agents, getting log data on agents and events, changing PMDB settings, and installing patches. See also PMDB and agent. |
advice | In Oracle, an algorithm that is designed to recommend on gathering statistics, creating new indexes, change existing indexes, and add or delete hints to make Oracle's Optimizer choose a better access path and make the statement perform better. Can be activated from any DML (Data Manipulation Language) statement. |
agent | A program that runs on a server machine to collect, process, or communicate performance information. The Precise installation consists of multiple agents. |
alert | The state of an Alerts metric that has reached a near-critical or critical status. An alert is issued by Alerts, triggering an action and informing of a problem that has occurred or is likely to occur within the area sampled by the specific metric. See also action. |
Alerts | These products provide alerts to problematic conditions before they turn into performance problems, based on predefined metrics and thresholds. Alerts can automatically perform an action, such as displaying a pop-up message, sending an email message or SNMP trap, or running a program. |
Alerts FocalPoint | An agent that receives data from the InformPoint agents, stores it, and performs any action that has been user-defined for that specific alert, such as displaying a pop-up message, sending an email message or SNMP trap, or running a program. See also InformPoint. |
alert type | In Alerts, the status of all metrics belonging to a metric group or a monitored instance, indicating the current performance level through colors. See also alert and metric. |
application server metric | In J2EE, a metrics that is provided by the application server or by customer code. This can include metrics published by the Java Management Extension (JMX) APIs or vendor-specific APIs, such as IBM's Performance Management Interface (PMI). |
...
summary table | A container that stores the information collected by the Precise agents and loads it into the PMDB. Summary tables store the same data at different levels of granularity: time slice, hourly, daily, weekly, and monthly. By storing data in multiple summary tables, Precise can present a detailed view and progressively higher-level views of the same data. Summary tables are particularly useful for data aging. A data purging policy can be implemented for each summary table so that detailed data is retained for short-term historical analyses while more summarized data is used for long-term analyses and trending. |
technology | A technology identifies the monitored object. For example, Oracle, SQL Server, Sybase, and DB2 are different technologies, while all Web servers (such as: Apache, IIS, and WebSphere) are defined as a single Web technology. A single monitored object can be monitored by two different technology's Collectors. For example, WebLogic server can be monitored by both a Web Collector and a J2EE Collector. |
throughput | The number of average completions per second that are observed during an interval. |
time slice | A unit used to break up long sessions into smaller time periods. The length of a time slice is preset and cannot be changed. It represents the maximum time that passes before the data collected can be displayed. For example, if the length of a time slice is 15 minutes, the collection is only updated at 15-minute intervals.
The length of a time slice is different for each technology: In Oracle, SQL Server, Sybase, DB2, Web, .NET, MQ, Tuxedo, Network, and OS, a time slice is 15 minutes. In J2EE and SmartLink, a time slice is either 30 seconds or 5 minutes. In Precise for SAP, a time slice is 5 minutes. See also collector slice size. |
URI (Uniform Resource Identifier) | The relative path to a resource after the location (network node) is found. |
URL mapping | In Web, a function that defines rules that map URLs (Uniform Resource Locators) with dynamic parameters originating from a specific domain to a format that identifies the Web pages and prevents them from having different URLs. |
Web client browser side | In Web, the gathering of performance data from the browser running on the desktop of the Web application's user, through the static or dynamic instrumentation of Web pages. |
Web server | A program that receives client requests for Web pages, retrieves the static pages and/or issues a request for dynamic page creation to an application server, and sends the pages to the client. In Web, a computer that delivers (serves up) Web pages. Every Web server has an IP address and possibly a domain name. |
work time | The time spent in the specific entity excluding time spent by called (other) entities. In J2EE, work time of a method is calculated as the service time of that method minus the service time of the methods it invoked. |
work type | In Web, a counter that keeps track of the type of the Web instance, such as Web, PeopleSoft, SAP, or Siebel. |
workspace | A display unit in Precise products. All workspaces display data from different perspectives. For example, in Oracle, SQL Server, and Sybase, the Current workspace shows information on the sessions currently active in an application, and the Objects workspace displays information on Oracle or SQL Server database objects that can be used to understand relationships and associations between database schema objects. |
Precise. Performance intelligence from click to storage. Learn more > >