a. User Processes

Notify users in advance that LeasePak will be unavailable during the upgrade. At the scheduled start time, stop any remaining LeasePak server processes. The following command will identify LeasePak server processes, including End of Period and LeasePak Utilities processes:

% ps -ef | grep lpa

Also use the appropriate procedures to stop any LeasePak-related processes on the DBMS server.

b. System Backups (optional)

Perform backups of your systems as needed.

a. Database Snapshot (optional)

For each LeasePak database you wish to backup, log on to the 7.7a server as $NSTDBA and run db_snapshot.

** NOTE ** Ensure that your $NSTDBA user account is pointing to the 7.7a version by running the whatami command prior to running the db_snapshot command. If the whatami output shows that the $NSTDBA user account is not pointing to the 7.7a version, you will need to copy in the correct startup files so that it is pointing to the 7.7a version before running the db_snapshot command.

b. LeasePak 7.7a Server Maintenance Release Update

Follow the instructions in LeasePak Server Preparation and Installation on how to execute the 7.7a server software. In this case, we will run setup with the -b option:

• -b  Use this option to update the LeasePak build
• -s7  Use this option to update the Queue Manager version
• -l (the letter l)  Use this option to update the license file

Run setup with the -b option. Do not use the -s7 option or the -l option. The -b option will install the latest server build and move the $live symbolic link to the latest build software.

c. LeasePak 7.7a User License

Move or copy the lplicense.dat file from the previous build $uexe directory into the new build $uexe directory. For example:

% cp /opt/nst/v77a/bld/bld7.70.2201/exe/ora/lplicense.dat /opt/nst/v77a/bld/bld7.70.2233/exe/ora

d. Reload LeasePak stored packages, stored procedures, triggers, and views

Run the db_load_code script as the $NSTDBA user. This script will re-create the LeasePak stored packages, stored procedures, triggers, and views.

% db_load_code environment-name

For example, if the environment name is "prod":

% db_load_code prod

The script will prompt for the DBO password.

e. Grant privileges on LeasePak database objects

Run the db_set_security script as the $NSTDBA user. This script will grant privileges on LeasePak database objects, including the reloaded stored packages, stored procedures, and views.

% db_set_security environment-name

For example, if the environment name is "prod":

% db_set_security prod

The script will prompt for the DBO password.

f. Validate LeasePak indexes and triggers

The LeasePak indexes and triggers should be validated after the db_load_code and db_set_security scripts have been executed. The following LeasePak Utility option to validate te indexes and triggers needs to run on the Linux application server by an account that has access to the LeasePak software.

** NOTE ** Ensure that you are pointing to the 7.7a release by running the whatami command prior to running the lease /util command. If you are not, then you will need to copy in the correct startup files so that you are now pointing to the 7.7a release before running the aforementioned executable.

% lease /util 216
This utility option verifies that all indexes and triggers required by LeasePak
are defined and accessible.  If any are found to be missing or inaccessible,
their names will be displayed on the screen.

Do you wish to continue (Y/N)? y
Client Password?

Checking for undefined indexes...
  Total number of undefined indexes: 0

Checking for unusable indexes...
  Total number of unusable indexes: 0

Checking for invisible indexes...
  Total number of invisible indexes: 0

Checking for undefined triggers...
  Total number of undefined triggers: 0

Checking for disabled triggers...
  Total number of disabled triggers: 0

** NOTE ** If the utility detected any undefined/unusable/invisible indexes or undefined/disabled triggers, contact your help desk representative for next steps.

g. Reload the msg table

The msg table needs to be reloaded with the latest informational, warning, and error messages. To reload the msg table, use the db_restore script with the -t option, which will load the latest messages from the shipped dataset named seed. The db_restore script should be run as the $NSTDBA user.

db_restore environment-name seed -t msg

For example, if the environment name is "prod":

% db_restore prod seed -t msg

The script will prompt for the DBO password.

** WARNING ** If the above db_restore command is entered incorrectly, it could mistakenly overwrite the entire database contents with the seed dataset. Please be sure to specify the "-t msg" option when running the command.

h. LeasePak 7.7a Client Upgrade

Follow the procedures in the Upgrade and Conversion section of the LeasePak client documentation to upgrade the LeasePak client software.