|
|
The automatic upgrade facility of this release of ViewRunner will support 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.
The following are the basic steps to upgrading the software to this release of ViewRunner.
Step 1 Bring down the ViewRunner server and bounce the Oracle database.
Step 2 Back up 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, Version 2.3.5 has some new fields in the Oracle Database tables and major changes in the HP OpenView Database elements. See the section on symbols in Chapter 1 of the ViewRunner for HP OpenView Provisioning and Operation Guide for a table that lists the changes. When ViewRunner for HP OpenView is upgraded from an earlier version, existing Oracle and OpenView databases must be properly migrated or will otherwise be useless. This section should be read carefully and properly understood before attempting the upgrade.
Use the following steps to backup the Oracle database.
 | Caution A backup of the Oracle and OpenView databases is highly recommended. |
Step 1 Login (or change) to the Oracle user id in UNIX.
% su - oracle
Step 2 Make sure that ORACLE_HOME and ORACLE_SID is 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 shutdown 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 shutdown the database) |
| SVRMGR>exit |
|
| % |
|
Step 4 Use your favorite method to backup the database (tar or cpio).
%tar cvf bak_ora.tar /opt/oradata/vrunner
Use 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 OV 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 (ViewRunner application). The Oracle database will be migrated as part of the installation (upgrade) of the ViewRunner. There are two methods of migrating the HP OpenView database:
Use 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.3.5 CD is mounted.
Step 4 Rename the package names, VRCLIENT/VRSERVER to CSCOvrovc/CSCOvrovs, using the pkgrename script.
# pkgrename
Step 5 For an upgrade (reinstalling a package with the same name), you will need to specify an installation administration file. Use the -a option on the pkgadd utility. As an 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 where upgrade.ksh has been run.
Step 11 For each map, mark the conversion result. Possible values are:
Step 12 When all maps return a SUCCESSFUL result in at least one pass, you are done.
Use 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 names of maps not properly converted.
Step 2 Stop the ViewRunner server if running.
Step 3 Start OVW.
Step 4 Select Cancel at the ViewRunner login prompt.
Step 5 Open the Maps list and delete maps not converted.
Step 6 Login to ViewRunner.
Step 7 Create new ViewRunner enabled maps with the previously taken names (should recreate the maps from the Oracle database).
Some old ViewRunner fields will be left in the system. They can be deleted by running the command shown below.
 | 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
Use 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 non-ViewRunner map, preferably to a map named default, stop OpenView, and delete the old HP OpenView database. The following commands will delete all maps from the database, including any non-ViewRunner 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.3.5 CD is mounted.
#cd /cdrom/cdrom0
Step 4 Rename the package names VRCLIENT/VRSERVER to CSCOvrovc/CSCOvrovs using the pkgrename script.
# pkgrename
Step 5 For an upgrade (reinstalling a package with the same name), you will 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 login 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.
The following are the instructions for upgrading the ViewRunner database.
Step 1 Make sure all users are logged out of ViewRunner.
Step 2 Shut down the ViewRunner servers.
Step 3 Make sure all users are logged out of Oracle.
Step 4 Use your favorite method for backing up the Oracle database in the event of a failure.
Step 5 Invoke sqlplus. Connect as user SYSTEM.
Step 6 Add the new ViewRunner for HP OpenView 2.2.0 columns by executing: 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.
Step 18 The command line invocation is: exp parfile=exp.par. You must enter the password for the SYSTEM user account. The generated export file name will be 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
pkgrm VRCLIENT.
Step 22 Remove the ViewRunner for HP OpenView V1.0.1 VRSERVER package, using
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.
Step 29 The command line invocation is: imp parfile=imp.par. 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 populate the LoopRunnerTable with the necessary data: lpr_table_update.sql. Commit if successful.
Step 34 Drop the following sequences:
Step 35 Restore the following sequences with the starting value recorded above. The SUBTEND_DOMAIN_SEQUENCE may have a starting value of 1. You may modify and invoke the create_sequences.sql script.
Step 36 Commit the changes.
Step 37 Exit the sqlplus session.
The following procedures are documented in the Oracle DBA Handbook on pp.108-115
The following are the instructions for a complete physical backup of Oracle database files.
Step 1 Ensure there are no users logged into ViewRunner for HP OpenView.
Step 2 Shut down the ViewRunner for HP OpenView servers.
Step 3 Ensure there are no users logged into Oracle.
Step 4 Invoke Server Manager in command line mode.
Step 5 Connect as user SYSTEM.
Step 6 Shut down the database with the following command: shutdown immediate.
Step 7 Use your favorite method for saving off 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 in determining the path to the above files.
Step 8 Restart the database with the following command: startup.
The preceding procedure may be used to move a database across to another machine if:
The following are the instructions for a logical backup of Oracle configuration data.
The following are instructions for backup.
Step 1 Ensure there are no users logged into ViewRunner for HP OpenView.
Step 2 Shut down the ViewRunner for HP OpenView servers.
Step 3 Ensure there are no users logged into Oracle.
Step 4 Invoke sqlplus and connect as 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.
Step 7 The command line invocation is: exp parfile=bu_exp.par. Submit the password for the VRUNNERRW account.
Step 8 The generated export filename will be exp.dmp.
Step 9 Examine the exp.log file for errors.
Step 10 Document the value in the following sequences.
Step 11 Enable the foreign key constraints by executing the following function: fkenable.sql.
The following are instructions for restore.
Step 1 Ensure there are no users logged into ViewRunner for HP OpenView.
Step 2 Shut down the ViewRunner for HP OpenView servers.
Step 3 Ensure there are no users logged into Oracle.
Step 4 Invoke sqlplus and connect as 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.
Step 8 The command line invocation is: import parfile=bu_imp.par.
Step 9 Examine the imp.log file for errors.
Step 10 Rebuild all of the table indexes by executing the following script: rebuild_index.sql.
Step 11 Enable the foreign key constraints by executing the following function: fkenable.sql.
Step 12 Drop the following sequences:
Step 13 Restore the following sequences with the starting value recorded in the static back procedures above. You may modify and invoke the create_sequences.sql script.
The above procedure may be used to transfer ViewRunner for HP OpenView configuration data across platforms.
Posted: Fri Oct 8 12:38:44 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.