|
|
The automatic upgrade facility for this release of ViewRunner supports upgrades from versions 2.2.0 or later only. If your current version of ViewRunner is 1.0, you must manually upgrade the Oracle database to this version. (See the "ViewRunner Server Manual Upgrade Process" section for instructions.)
The basic steps for upgrading the software to this release of ViewRunner are as follows:
Step 1 Bring down the ViewRunner server, and then shut down and restart the Oracle database.
Step 2 Backup the Oracle database.
Step 3 Rename the old ViewRunner packages to the new names using the pkgrename script.
Step 4 Install the ViewRunner database package, CSCOvrdb, using the following command:
pkgadd -a admin -d .
Step 5 Backup the Oracle database to the current version.
Step 6 Install the ViewRunner server package, CSCOvrovs, using the following command:
pkgadd -a admin -d .
Step 7 Install the ViewRunner client package, CSCOvrovc, using the following command:
pkgadd -a admin -d .
ViewRunner for HP OpenView includes some new fields in the Oracle Database tables and major changes in the HP OpenView Database elements. See the section named Symbols in Chapter 1 of the ViewRunner for HP OpenView Provisioning and Operation Guide for a table that lists
the changes.
When you upgrade ViewRunner for HP OpenView from an earlier version, you must exit the Oracle and OpenView databases properly or they are useless. Be sure to carefully read and understand this section before you attempt to upgrade ViewRunner for HP OpenView.
Complete the following steps to back up the Oracle database:
 | Caution A backup of the Oracle and OpenView databases is highly recommended. |
Step 1 Log in (or change) to the Oracle user ID in UNIX.
% su - oracle
Step 2 Make sure that ORACLE_HOME and ORACLE_SID are set.
Step 3 Determine where the Oracle data files are located. You can issue the following select commands to determine the location of the data files. You then want to shut down the database before doing the backup.
| % svrmgrl |
|
| SVRMGR>connect internal |
|
| SVRMGR>startup | (if database is not running) |
| SVRMGR>select file_name from dba_data_files; | (to show the Oracle data files and write down locations) |
| SVRMGR>select member from V$logfile; | (to show the redo logs) |
| SVRMGR>select name from V$controlfile; | (to show control files) |
| SVRMGR>shutdown immediate | (to shut down the database) |
| SVRMGR>exit |
|
| % |
|
Step 4 Use your preferred method to backup the database (tar or cpio).
%tar cvf bak_ora.tar /opt/oradata/vrunner
Complete the following steps to backup the HP OpenView database.
Step 1 Make sure the OpenView daemons are not running.
% /opt/OV/bin/ovstop
Step 2 The HP OpenView database is located in $OV_DB/openview. Tar this directory.
% tar -cvf bak_ov.tar $OV_DB/openview
The Oracle database is the master database. The HP OpenView database is synchronized with the Oracle database by ViewMap (a ViewRunner application). The Oracle database is migrated as part of the installation (upgrade) of the ViewRunner. There are two methods for migrating the HP OpenView database.
Complete the following steps to convert the old HP OpenView maps to the new ones. You must be root for most of the following steps:
Step 1 Make sure HP OpenView is running.
#ovstart
Step 2 Make sure the ViewRunner server is not running.
# vrStop
Step 3 Change to the directory where the ViewRunner 2.4.0 CD is mounted.
Step 4 Rename the package name, VRCLIENT/VRSERVER, to CSCOvrovc/CSCOvrovs, using the pkgrename script.
# pkgrename
Step 5 If you are doing an upgrade (that is, reinstalling a package with the same name), you need to specify an installation administration file. Use the -a option on the pkgadd utility. For example:
# pkgadd -a ./admin -d .
Step 6 Install all three packages in the following order:
CSCOvrdb (first)
CSCOvrovs (second)
CSCOvrovc (third)
Step 7 Make sure you source the client environment variables.
#source $VRC_HOME/env/vrc.cshrc
Step 8 HP OpenView should be running and the ViewRunner server should be down.
#ovstart
#vrStop
Step 9 Run the upgrade script.
#$VRC_HOME/mcbin/upgrade.ksh
Step 10 Make a note of the list of maps displayed on the console from which you run upgrade.ksh.
Step 11 Mark the conversion result for each map you noted in Step 10.
Possible values include
Step 12 When all maps return a SUCCESSFUL result in at least one pass, you are finished.
Complete the following steps to troubleshoot maps that do not convert properly (indicated by anything other than a SUCCESSFUL result after several passes):
Step 1 Make a note of the map names that were not properly converted.
Step 2 Stop the ViewRunner server if it is running.
Step 3 Start OVW.
Step 4 Select Cancel at the ViewRunner login prompt.
Step 5 Open the Maps list and delete the maps that were not converted.
Step 6 Log in to ViewRunner.
Step 7 Create new ViewRunner-enabled maps with the names that were previously noted in Step 1. (You should recreate the maps from the Oracle database.)
Some old ViewRunner fields are left in the system. You can delete them by running the
following command:
 | Caution It is strongly recommended that old ViewRunner fields left in the system not be removed until a successful upgrade is confirmed. Once the old fields are deleted, you cannot run upgrade.ksh. |
%$VRC_HOME/mcbin/delfields
Complete the following steps to rebuild the HP OpenView maps from the Oracle database. You must be in root for most of the following steps:
Step 1 Make sure the ViewRunner server is not running.
#vrStop
Step 2 Set the default map to a nonViewRunner map, preferably to a map named default, stop OpenView, and delete the old HP OpenView database.
The following commands delete all maps from the database, including any nonViewRunner maps:
#ovstop
#rm -rf $OV_DB/openview/mapdb/*
#rm -rf $OV_DB/openview/ovwdb/current/*
#rm -rf $OV_DB/openview/topo/*
Step 3 Change to the directory where the ViewRunner 2.4.0 CD is mounted.
#cd /cdrom/cdrom0
Step 4 Rename the package name, VRCLIENT/VRSERVER, to CSCOvrovc/CSCOvrovs, using the pkgrename script.
# pkgrename
Step 5 For an upgrade (that is, reinstalling a package with the same name), you need to specify an installation administration file. Use the -a option on the pkgadd utility. For example:
# pkgadd -a ./admin -d .
Step 6 Install all three packages in the following order:
CSCOvrdb (first)
CSCOvrovs (second)
CSCOvrovc (third)
Step 7 Source the server environment variables.
#source $VRS_HOME/env/vrs.cshrc
Step 8 Run the ViewRunner server.
# vrStart &
Step 9 Change to a user ID with which the earlier maps were created. Source the client variables and run ovw to log in as normal. Create a new map with ViewRunner enabled to rebuild the map from the Oracle database.
%source $VRC_HOME/env/vrc.cshrc
% ovw&
This section explains the ViewRunner database upgrade procedures from version 1.0.1 to version 2.2.0. These procedures should be performed by an experienced database administrator. For more details, please consult an appropriate database administration guide.
Complete the following steps to upgrade the ViewRunner database:
Step 1 Make sure that all users are logged off of ViewRunner.
Step 2 Shut down the ViewRunner servers.
Step 3 Make sure that all users are logged off of Oracle.
Step 4 Use your preferred method for backing up the Oracle database in the event of a failure.
Step 5 Invoke sqlplus. Connect as the user SYSTEM.
Step 6 Add the new ViewRunner for HP OpenView 2.2.0 columns by executing the following script:
add_columns.sql
Step 7 Examine the generated log file for errors.
add_columns.lst
Step 8 Drop the existing table constraints by executing the following script:
drop_constraints.sql
Step 9 Examine the generated log file for errors.
drop_constraints.lst
Step 10 Add the new constraints by executing the following script:
add_constraints.sql
Step 11 Examine the generated log file for errors.
add_constraints.lst
Step 12 Drop unneeded tables by executing the following script:
drop_tables.sql
Step 13 Examine the generated log file for errors.
drop_tables.lst
Step 14 Disable all foreign key constraints by executing the following script:
fkdisable.sql
Step 15 Record the values of the following sequences:
Step 16 Exit the sqlplus session.
Step 17 Export all of the configuration data using the exp.par file.
The command line invocation is exp parfile=exp.par.
Step 18 You must enter the password for the SYSTEM user account. The generated export file name is exp.dmp.
Step 19 Examine the exp.log file for errors.
Step 20 Stop the ViewRunner for HP OpenView Oracle server.
Step 21 Remove the ViewRunner for HP OpenView V1.0.1 VRCLIENT package, using the following script:
pkgrm VRCLIENT
Step 22 Remove the ViewRunner for HP OpenView V1.0.1 VRSERVER package, using the following script:
pkgrm VRSERVER
Step 23 Install the ViewRunner for HP OpenView V2.2.0 VRSERVER package.
Step 24 Install the ViewRunner for HP OpenView V2.2.0 VRCLIENT package.
Step 25 Invoke sqlplus. Connect as user VRUNNERRW.
Step 26 Disable all foreign key constraints by executing the following script:
fkdisable.sql
Step 27 Remove all existing data from the tables by executing the following script:
trunc_table.sql
Step 28 Import all of the configuration data using the imp.par file.
The command line invocation is imp parfile=imp.par.
Step 29 You must enter the password for the SYSTEM user account.
Step 30 Examine the imp.log file for errors.
Step 31 Rebuild all of the table indexes by executing the following script:
rebuild_index.sql
Step 32 Enable the foreign key constraints by executing the following function:
fkenable.sql
Step 33 Invoke the following script to populate the LoopRunnerTable with the necessary data:
lpr_table_update.sql (Commit if you are successful.)
Step 34 Drop the following sequences:
Step 35 Restore the dropped sequences with the preceding starting value. The SUBTEND_DOMAIN_SEQUENCE may have a starting value of 1. You can modify and invoke the create_sequences.sql script.
Step 36 Commit the changes.
Step 37 Exit the sqlplus session.
The backup and recovery procedures in the following sections are documented in more detail in the Oracle database manual.
Go through the following steps to perform a complete physical backup of Oracle database files:
Step 1 Ensure that there are no users logged in to ViewRunner for HP OpenView.
Step 2 Shut down the ViewRunner for HP OpenView servers.
Step 3 Ensure that there are no users logged in to Oracle.
Step 4 Invoke Server Manager in command-line mode.
Step 5 Connect as the user SYSTEM.
Step 6 Shut down the database with the following command:
shutdown immediate
Step 7 Use your preferred method for saving the Oracle init and datafiles.
These files include the data files, on-line redo logs, control files, and .ora files. The following sql commands may be useful for determining the path to the preceding files.
Step 8 Restart the database with the following command:
startup
You can use the preceding procedure to move a database to another machine if all of the following statements are true:
Complete the following steps to perform a logical backup of Oracle configuration data:
Step 1 Ensure that there are no users logged in to ViewRunner for HP OpenView.
Step 2 Shut down the ViewRunner for HP OpenView servers.
Step 3 Ensure that there are no users logged in to Oracle.
Step 4 Invoke sqlplus and connect as the user VRUNNERRW.
Step 5 Disable all foreign key constraints by executing the following script:
fkdisable.sql
Step 6 Export all of the configuration data using the exp.par file.
The command line invocation is exp parfile=bu_exp.par.
Step 7 Submit the password for the VRUNNERRW user account.
The generated export filename is exp.dmp.
Step 8 Examine the exp.log file for errors.
Step 9 Document the value in the following sequences:
Step 10 Enable the foreign key constraints by executing the following function:
fkenable.sql
Complete the following steps to perform a restore.
Step 1 Ensure that there are no users logged in to ViewRunner for HP OpenView.
Step 2 Shut down the ViewRunner for HP OpenView servers.
Step 3 Ensure that there are no users logged in to Oracle.
Step 4 Invoke sqlplus and connect as the user VRUNNERRW.
Step 5 Disable all foreign key constraints by executing the following script:
fkdisable.sql
Step 6 Remove all existing data from the tables by executing the following script:
trunc_table.sql
Step 7 Import all of the configuration data using the imp.par file.
The command line invocation is import parfile=bu_imp.par.
Step 8 Examine the imp.log file for errors.
Step 9 Rebuild all of the table indexes by executing the following script:
rebuild_index.sql
Step 10 Enable the foreign key constraints by executing the following function:
fkenable.sql
Step 11 Drop the following sequences:
Step 12 Restore these sequences with the starting value recorded in the preceding static backup procedures. You may modify and invoke the create_sequences.sql script.
You can use the preceding procedure to transfer ViewRunner for HP OpenView configuration data across platforms.
Posted: Thu Sep 23 13:25:13 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.