| Oracle® Real User Experience Insight Installation Guide 12c Release 1 for Linux x86-64 Part Number E35688-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Real User Experience Insight Installation Guide 12c Release 1 for Linux x86-64 Part Number E35688-02 |
|
|
PDF · Mobi · ePub |
This chapter describes the procedure for upgrading an existing RUEI 11.1 or 12.1..0.0.x installation to release 12.1.0.1. The post-installation configuration procedure is described in Chapter 4, "Configuring RUEI".
Troubleshooting Upgrade or Rollback Problems
The upgrade and rollback scripts log their actions in the files /tmp/ruei-upgrade-x.log and /tmp/ruei-rollback-x.log. If you encountered any problems during the upgrade or rollback, please attach the relevant file to any request to Customer Support.
In previous versions before 12.1.0.0.1, KPI percentage values were sometimes incorrectly reported as a number between 0 and 1, rather than between 0 and 100. The upgrade script prompts you to confirm the correction of suspect KPI historical values and targets. This is described in Upgrading the Reporter System.
Note that while best effort has been made to ensure that historical data and target values are correctly transformed as necessary, it is recommended that you review KPI reporting and target configuration to ensure they meet your requirements.
As of version 11.1, support for the use of XPath queries has been extended to provide full XPath 1.0 functionality for content scanning. This has important implications when upgrading an existing RUEI installation.
The upgrade script reports all namespaces found in the current configuration. These must be explicitly defined upon completion of the upgrade process. Otherwise, your configuration will no longer work correctly.
In addition, be aware that XPath expressions executed against content that is not well-formed XHTML code can return different results than in previous versions. Therefore, it is strongly recommenced that you carefully review all XPath expressions used in your RUEI installation. For further information on XPath support, see the Oracle Real User Experience Insight User's Guide.
This section describes the procedure for upgrading from an existing RUEI 11.1 installation to release 12.1.
Important:
Before proceeding with the upgrade, make a backup of your configuration. Select System, then Maintenance, and then Backup and restore. The configuration backup is required in case of a rollback.The Reporter upgrade procedure described in this section applies to both single server installations as well as dedicated Reporter systems.
Do the following:
Login to the Reporter as root. Within the /root directory, unzip the RUEI zip file, and go to the directory containing the application files. Use the following commands:
cd /root
unzip Vxxxx.zip
Stop all processing on the Reporter and Collector system(s) using the following commands:
cd /root/RUEI/extra chmod +x ruei-upgrade-12.1.0.1.sh ./ruei-upgrade-12.1.0.1.sh stop_ruei
Insert an additional line in the /etc/ruei.conf file:
export RUEI_DB_TNSNAME_CFG=$RUEI_DB_TNSNAME
Perform the necessary pre-upgrade actions by executing the following commands:
cd /root/RUEI/extra ./ruei-upgrade-12.1.0.1.sh rpm_pre_install
Note that, depending on your deployment, the upgrade actions may take a couple of hours to complete.
Make the ruei-prepare-db.sh script available to the Oracle user (for example, by extracting the RUEI distribution zip) on the system where the database resides. Update the RUEI database instance by issuing the following commands:
cd /root/RUEI/121 cp ruei-prepare-db.sh /home/oracle cp -r sql_scripts /home/oracle chmod +x /home/oracle/ruei-*.sh su - oracle export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1Foot 1 ./ruei-prepare-db.sh sql_packages ./ruei-prepare-db.sh user_grants
Upon completion, you should again become the root user.
For each required Collector system, perform the steps indicated in the following section. Upon completion, proceed to step 7.
Install the new versions of the RPMs using the following commands:
cd /root/RUEI/121 chmod +x ruei-install.sh ./ruei-install.sh *.rpm
Perform the necessary post-upgrade actions by executing the following commands:
cd /root/RUEI/extra ./ruei-upgrade-12.1.0.1.sh rpm_post_install
As explained in KPI Values, the upgrade script may prompt you to confirm the convertion of suspect KPI historical values and targets.
In case you want to alter any of the choices you made above, you can re-run this procedure by executing the following command:
./ruei-upgrade-12.1.0.1.sh kpi_convert_percent
Note that the above command must be executed before starting step 9.
Restart processing using the following commands:
cd /root/RUEI/extra ./ruei-upgrade-12.1.0.1.sh reinitialize ./ruei-upgrade-12.1.0.1.sh start_ruei
Note:
During and after the upgrade procedure, if error or information messages appear in the event log (select System, then Status, and then Event log), you should mark them as read after completing the upgrade procedure, and monitor whether new messages are reported. In the event of re-occurring error messages, you should contact Customer Support.For each required remote Collector system, login as root. Within the /root directory, unzip the RUEI zip file, go to the directory containing the application files, and install the new versions of the RPMs. Do the following:
Unzip the RUEI distribution package using the following commands:
cd /root
unzip Vxxxx.zip
Upgrade the Collector RPMs using the following commands:
cd /root/RUEI/121 chmod +x ruei-install.sh ./ruei-install.sh collector
Insert the following line in the /etc/ruei.conf file:
export RUEI_DB_TNSNAME_CFG=$RUEI_DB_TNSNAME
After completing the above procedure for each required Collector system, you should continue with the upgrade of the Reporter system (as described in Upgrading the Reporter System).
This section describes the procedure to rollback to version 11.1 after upgrading to version 12.1.0.1. Note that the Collector included in the Reporter installation is automatically rolled back during the described procedure. However, remote Collector systems must be individually rolled back. The procedure to do this is described later in this section.
Important:
Be aware that it may not be possible to restore your system to its exact state prior to upgrading. It is strongly recommended that you contact Customer Support before rolling back an upgrade.Note that in the following instructions, it is assumed that the 11.1 distribution set is extracted to /root/old, and the 12.1.0.1 distribution set is extracted to /root.
Login to the Reporter system as root. Within the /root/old directory, unzip the RUEI 11.1 distribution zip file, and go to the directory containing the application files. Use the following commands:
mkdir /root/old cd /root/old unzip <path to distribution set>/Vxxx.zip
Stop all processing on the Reporter system by issuing the following commands:
cd /root/RUEI/extra ./ruei-rollback-11.1.sh stop_ruei
Remove the 12.1.0.1 RPMs for Oracle Fusion and the Japanese and Korean language support by issuing the following commands:
rpm -e ux-suites-fus rpm -e ux-lang-ja_jp rpm -e ux-lang-ko_kr
Execute the RPM pre-installation phase by issuing the following command:
./ruei-rollback-11.1.sh rpm_pre_install
Restore the previous RPMs by issuing the following commands:
cd /root/old/RUEI/111 chmod +x ruei-install.sh ./ruei-install.sh *.rpm
Execute the post-installation script by executing the following command:
cd /root/RUEI/extra ./ruei-rollback-11.1.sh rpm_post_install
Rollback all required remote Collectors (using the procedure described in Rolling Back Remote Collector Systems). Upon completion, continue to step 8. If your installation does not make use of a remote Collector, proceed directly to step 8.
Ensure that the backup you created prior to upgrading (by selecting System, then Maintenance, then Backup and restore, and then select Backup system to file) is available to the Reporter system by coping it, for instance, to the /tmp directory. Then issue the following command as the root user to make the backup file readable to the RUEI_USER user:
chmod 644 /tmp/backup_file_name.tar.gz
Restore the backup file by issuing the following command as the RUEI_USER user:
project -restore --all /tmp/backup_file_name.tar.gz
Restart processing by issuing the following commands as the root user:
cd /root/RUEI/extra ./ruei-rollback-11.1.sh start_ruei
Do the following:
Login to the remote Collector system as root. Within the /root/old directory, unzip the 11.1 distribution zip file, and go to the directory containing the application files. Issue the following commands:
mkdir /root/old cd /root/old unzip <path to distribution file>/Vxxx.zip
Restore the previous RPMs by issuing the following commands:
cd /root/old/RUEI/111 chmod +x ruei-install.sh ./ruei-install.sh ux-collector-*.rpm
Upon completion for all required Collectors, return to step 8 in Rolling Back to Version 11.1.
This section describes the procedure for upgrading from an existing RUEI 12.1.0.0.x installation to release 12.1.0.1.
Important:
Before proceeding with the upgrade, make a backup of your configuration. Select System, then Maintenance, and then Backup and restore. The configuration backup is required in case of a rollback.The Reporter upgrade procedure described in this section applies to both single server installations as well as dedicated Reporter systems.
Do the following:
Login to the Reporter as root. Within the /root directory, unzip the RUEI zip file, and go to the directory containing the application files. Use the following commands:
cd /root
unzip Vxxxx.zip
Stop all processing on the Reporter and Collector system(s) using the following commands:
cd /root/RUEI/extra chmod +x ruei-upgrade-12.1.0.1.sh ./ruei-upgrade-12.1.0.1.sh stop_ruei
Perform the necessary pre-upgrade actions by executing the following commands:
cd /root/RUEI/extra ./ruei-upgrade-12.1.0.1.sh rpm_pre_install
Note that, depending on your deployment, the upgrade actions may take a couple of hours to complete.
Make the ruei-prepare-db.sh script available to the Oracle user (for example, by extracting the RUEI distribution zip) on the system where the database resides. Update the RUEI database instance by issuing the following commands:
cd /root/RUEI/121 cp ruei-prepare-db.sh /home/oracle cp -r sql_scripts /home/oracle chmod +x /home/oracle/ruei-*.sh su - oracle export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1Foot 2 ./ruei-prepare-db.sh sql_packages ./ruei-prepare-db.sh user_grants
Upon completion, you should again become the root user.
For each required Collector system, perform the steps indicated in Upgrading the Remote Collector System(s). Upon completion, proceed to step 6.
For each required Processing Engine system, perform the steps described in Upgrading the Processing Engine System(s). Upon completion, proceed to step 7.
Install the new versions of the RPMs using the following commands:
cd /root/RUEI/121 chmod +x ruei-install.sh ./ruei-install.sh *.rpm
Perform the necessary post-upgrade actions by executing the following commands:
cd /root/RUEI/extra ./ruei-upgrade-12.1.0.1.sh rpm_post_install
As explained in KPI Values, the upgrade script may prompt you to confirm the convertion of suspect KPI historical values and targets.
If you are upgrading from version 12.1.0.0.1, this step should not be performed.
In case you want to alter any of the choices you made in the previous step, you can re-run this procedure by executing the following command:
./ruei-upgrade-12.1.0.1.sh kpi_convert_percent
Note that the above command must be executed before starting step 10.
Restart processing using the following commands:
cd /root/RUEI/extra ./ruei-upgrade-12.1.0.1.sh reinitialize ./ruei-upgrade-12.1.0.1.sh start_ruei
Note:
During and after the upgrade procedure, if error or information messages appear in the event log (select System, then Status, and then Event log), you should mark them as read after completing the upgrade procedure, and monitor whether new messages are reported. In the event of re-occurring error messages, you should contact Customer Support.For each required remote Collector system, login as root. Within the /root directory, unzip the RUEI zip file, go to the directory containing the application files, and install the new versions of the RPMs. Do the following:
Unzip the RUEI distribution package using the following commands:
cd /root
unzip Vxxxx.zip
Upgrade the Collector RPMs using the following commands:
cd /root/RUEI/121 chmod +x ruei-install.sh ./ruei-install.sh collector
After completing the above procedure for each required Collector system, you should continue with the upgrade of the Reporter system (as described in Upgrading the Reporter System).
The upgrade procedure described in this section should be performed for each Processing Engine system. Do the following:
Login to the Processing Engine as root. Within the /root directory, unzip the RUEI zip file, and go to the directory containing the application files. Use the following commands:
cd /root
unzip Vxxxx.zip
Perform the necessary pre-upgrade actions by executing the following commands:
cd /root/RUEI/extra ./ruei-upgrade-12.1.0.1.sh rpm_pre_install
Make the ruei-prepare.sh script available to the Oracle user (for example, by extracting the RUEI distribution zip) on the system where the database resides. Update the Processing Engine database instance by issuing the following commands:
cd /root/RUEI/121 cp ruei-prepare-db.sh /home/oracle cp -r sql_scripts /home/oracle chmod +x /home/oracle/ruei-*.sh su - oracle export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1Foot 3 ./ruei-prepare-db.sh sql_packages ./ruei-prepare-db.sh user_grants
Upon completion, you should again become the root user.
Install the new versions of the RPMs using the following commands:
cd /root/RUEI/121 chmod +x ruei-install.sh ./ruei-install.sh processor
After completing the above procedure for each required Processing Engine, you should continue with the upgrade of Reporter system (as described in Upgrading the Reporter System).
This section describes the procedure to rollback to version 12.1.0.0.x after upgrading to version 12.1.0.1. Note that the Collector included in the Reporter installation is automatically rolled back during the described procedure. However, remote Collector systems must be individually rolled back. The procedure to do this is described later in this section.
Important:
Be aware that it may not be possible to restore your system to its exact state prior to upgrading. It is strongly recommended that you contact Customer Support before rolling back an upgrade.Note that in the following instructions, it is assumed that 12.1.0.0.x distribution set is extracted to /root/old, and the 12.1.0.1 distribution set is extracted to /root.
Login to the Reporter system as root. Within the /root/old directory, unzip the RUEI 12.1.0.0.x distribution zip file, and go to the directory containing the application files. Use the following commands:
mkdir /root/old cd /root/old unzip <path to distribution set>/Vxxx.zip
Stop all processing on the Reporter system by issuing the following commands:
cd /root/RUEI/extra ./ruei-rollback-12.1.0.0.x.sh stop_ruei
Execute the RPM pre-installation phase by issuing the following command:
./ruei-rollback-12.1.0.0.x.sh rpm_pre_install
Restore the previous RPMs by issuing the following commands:
cd /root/old/RUEI/121 chmod +x ruei-install.sh ./ruei-install.sh *.rpm
Execute the post-installation script by executing the following command:
cd /root/RUEI/extra ./ruei-rollback-12.1.0.0.x.sh rpm_post_install
Rollback all required remote Collectors (using the procedure described in Rolling Back Remote Collector Systems). Upon completion, continue to step 7. If your installation does not make use of a remote Collector, proceed directly to step 7.
Rollback all required Processing Engine systems (using the procedure described in Rolling Back Processing Engine Systems). Upon completion, continue to step 8. If your installation does not make use of a Processing Engine, proceed directly to step 8.
Ensure that the backup you created prior to upgrading (by selecting System, then Maintenance, then Backup and restore, and then select Backup system to file) is available to the Reporter system by coping it, for instance, to the /tmp directory. Then issue the following command as the root user to make the backup file readable to the RUEI_USER user:
chmod 644 /tmp/backup_file_name.tar.gz
Restore the backup file by issuing the following command as the RUEI_USER user:
project -restore --collectors /tmp/backup_file_name.tar.gz
Restart processing by issuing the following commands as the root user:
cd /root/RUEI/extra ./ruei-rollback-12.1.0.1-11.1.sh start_ruei
Do the following:
Login to the remote Collector system as root. Within the /root/old directory, unzip the 11.1 distribution zip file, and go to the directory containing the application files. Issue the following commands:
mkdir /root/old cd /root/old unzip <path to distribution file>/Vxxx.zip
Restore the previous RPMs by issuing the following commands:
cd /root/old/RUEI/111 chmod +x ruei-install.sh ./ruei-install.sh ux-collector-*.rpm
Upon completion for all required Collectors, return to step 7 of Rolling Back to Version 12.1.0.0.x.
Do the following:
Login to the Processing Engine system as root. Within the /root/old directory, unzip the RUEI 12.1.0.0.x distribution zip file, and go to the directory containing the application files. Use the following commands:
mkdir /root/old cd /root/old unzip <path to distribution set>/Vxxx.zip
Execute the RPM pre-installation phase by issuing the following command:
./ruei-rollback-12.1.0.0.x.sh rpm_pre_install
Restore the previous RPMs by issuing the following commands:
cd /root/old/RUEI/121 chmod +x ruei-install.sh ./ruei-install.sh processor
Execute the post-installation script by executing the following command:
cd /root/RUEI/extra ./ruei-rollback-12.1.0.0.x.sh rpm_post_install
Upon completion for all required Processing Engines, return to step 8 of Rolling Back to Version 12.1.0.0.x.
Footnote Legend
Footnote 1: This line requires customization based on your database version and installation path.
|
 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|