For LeasePak version 6.1a.
Describes the upgrade and conversion procedures from LeasePak version 6.1a to 6.2a
Oracle users on versions 4.3a - 6.0b: you must first upgrade to version 6.1a before upgrading to version 6.2a.
Notify users in advance that the old server (the server running the current version of LeasePak) will be unavailable during the upgrade. At the scheduled start time, use the following steps to stop any remaining user processes
1. Log on the server as root
2. Use the ps command to list LeasePak drivers running on the server
ps -ef | grep lpa
This not only lists instances of the main LeasePak program lpadriver.exe, but also lists other LeasePak processes, such as the End of Period program lpaeopdrvr.exe and the LeasePak utilities program $uexe/lpautil.exe, as well as any Oracle instances running on an Oracle database named according to our recommended standards ('lpak').
3. If any of these LeasePak processes need to be stopped, use the Unix kill command
kill id
where id is the Unix process id number from the ps listing.
Do not use the Unix kill command on the Oracle instance processes.
4. Sybase only: list (and stop, if needed) any remaining processes within Sybase
a. Start isql in 132-column mode
isql -Usa -w132
b. Use sp_who to list user processes. The terminal will display something similar to the following
fid spid status loginame dbname
--- ---- ----------- -------- ----------
0 1 running sa master
0 7 recv sleep ernesto production
c. If any of these processes need to be stopped, use the Sybase kill command
kill spid
where spid is the Sybase process id number from the sp_who listing.
Run End of Period for all portfolios in all environments you are upgrading. After End of Period is finished, do not make changes to any of the databases. You may also want to limit user access to the server and DBMS server once End of Period is complete.
Perform either a full or incremental backup of the server as needed.
New system requirements are in place for version 6.2a. Refer to the System Requirements document for more information.
Install and configure the OS (HP-UX, Linux, or Solaris) and the DBMS (Oracle or Sybase) appropriate to your platform using the instructions listed in LeasePak Server Preparation and Installation and related documents.
Recreate the OS accounts on the new server using the LeasePak user names and OS server passwords. Recreate the DBMS accounts on the new server using the LeasePak user names and DBMS passwords.
Complete the following sections from LeasePak Server Preparation and Installation:
The following procedures use LeasePak 4.6a as the example for the old version and 6.2a as the new LeasePak version.
Old server, old version:Log on to your old server using the msidba account and run snapshot for each LeasePak database you wish to convert to the new version.
Placeholder Environment and Database
For each LeasePak environment/database you wish to upgrade:
New server, old version: Log on to your new server using the admin46a account (the 4.6a msiadmin account on your new server) and create a placeholder environment for the upgrade.
New server, old version:Log on to your new server using the dba46a account (the 4.6a msidba account on your new server) and create a placeholder database for the upgrade.
New server, old version:Still using the dba46a account (the 4.6a msidba account on your new server), use restore to restore the appropriate 4.6a snapshot into the placeholder database.
For each LeasePak environment you wish to upgrade:
New server/new version:
1. Log on the server as msiadmin (for Multiple Concurrent Versions, see note below)
Terminal emulation: you must use one of the supported terminal types. Refer to the System Requirements for more information.
Multiple Concurrent Versions: if you are running more than one version of LeasePak on the same server using separate msiadmin and/or msidba accounts, use the accounts belonging to the new version of LeasePak to run upgrade_env.
2. Run upgrade_env
upgrade_env [new-setup-env-flags] path-to-old-environment-to-upgrade [build-id]where new-setup-env-flags are the optional flags and build-id is the build descriptor as described in the Environment and Database Configuration section of LeasePak Server Configuration and Maintenance. Note that both the new-setup-env-flags and build-id are optional--in most cases, you do not need either to run upgrade_env.
3. The terminal will display something similar to the following
2008-03-06 03:12:23 upgrade_env: Start /opt/msi/v62a/prod2008-03-06 03:12:24 setup_new_env: PRODUCTION prod syb SERVER_SYBASE lpr_prod live; Start2008-03-06 03:12:25 setup_new_env: Creating environment directory structure...2008-03-06 03:12:25 setup_new_env: Creating syb_use...2008-03-06 03:12:25 setup_new_env: Creating logdb.*...2008-03-06 03:12:27 setup_new_env: Creating envdb.msirc...2008-03-06 03:12:28 setup_new_env: Creating msidba placeholders...2008-03-06 03:12:28 setup_new_env: Creating .lp*...2008-03-06 03:12:28 setup_new_env: Setting environment security...
You will need the following for LeasePak PC Client setup:IP Address or name: server
Environment name: prod
Server Port: 6200
2008-03-06 03:12:29 setup_new_env: End2008-03-06 03:12:29 upgrade_env: Cannot delete old environment. Please remove it manually2008-03-06 03:12:29 upgrade_env: End
.lplogin and .lpprofile
If needed, copy the .lplogin and .lpprofile files from the $top/env/environment/etc directory (where environment is the upgraded LeasePak environment to the $HOME directory of the environment's LeasePak administrative user (lpadmin, not msiadmin; you must leave msiadmin tied to the administrative environment) and modify them to create the appropriate startup files, or log on the server as msiadmin and run change_env to switch the environments. For more information on .lplogin and .lpprofile, refer to the lpadmin section of the document LeasePak Server Configuration and Maintenance.
For each v61a LeasePak database you wish to upgrade:
New server/new version:
1. Log on the v62a server as msidba (for Multiple Concurrent Versions, see note below)
Terminal emulation: you must use one of the supported terminal types. Refer to the System Requirements for more information.
Multiple Concurrent Versions: if you are running more than one version of LeasePak on the same server using separate msiadmin and/or msidba accounts, use the accounts belonging to the new version of LeasePak to run ora_v60b_conversion.
2. Run ora_conversion
$top/env/{environment}/conv/ora_conversion {environment} v61a {step-number}where {environment} is the name of the v62a environment whose database you are converting and {step-number} is 1 to run the entire conversion.
The conversion is divided into sections called "steps". The steps are run sequentially. After a step completes successfully, the next step is run. If a step fails, all subsequent steps automatically fail without running. To restart the conversion after resolving a failure, re-execute the ora_conversion script with the {step-number} parameter set to the step at which to restart.
3. The terminal will prompt for the dbo password.
4. Type the dbo password for the database and press Enter. The conversion may take several minutes.
For each LeasePak database you wish to upgrade:
New server/new version:
1. Log on the server as msidba (for Multiple Concurrent Versions, see note below)
Terminal emulation: you must use one of the supported terminal types. Refer to the System Requirements for more information.
Multiple Concurrent Versions: if you are running more than one version of LeasePak on the same server using separate msiadmin and/or msidba accounts, use the accounts belonging to the new version of LeasePak to run sgenlpux_conversion.
2. Run sgenlpux_conversion
sgenlpux_conversion environment starting-release [dbo-password [srvadm-password]]where environment is the name of the environment whose database you are converting, starting-release is your version of LeasePak before the upgrade (for example, v51a), dbo-password is the database owner password, and srvadm-password is the DBMS server administrator password. For the dbo-password and srvadm-password, do not enter these on the command line; LeasePak will prompt you for them if and when necessary.
3. The terminal will display something similar to the following, then prompt for the dbo password (if necessary)
2008-03-03 00:54:10 sgenlpux_conversion: Convert prod environment from v51a to v62a2008-03-03 00:54:10 sgenlpux_conversion: Start2008-03-03 00:54:10 sgenlpux_conversion: Running commands as DBO: lpr_prodDatabase Owner 'lpr_prod' password:
4. Type the dbo password for the database and press Enter. The terminal will prompt for the srvadm password
Server Administrator 'srvadm' password:
5. Type the srvadm password and press Enter. The conversion may take several minutes. To see a complete example of the sgenlpux_conversion output, click here.
Once the upgrade and conversion are complete, you can remove the directories and contents of the old LeasePak and LeasePak queue manager releases. Also remove obsolete listings in the /etc/services, init.d, rc?.d, and inetd (or xinetd for Linux) directories.
Follow the procedures in the Upgrade and Conversion section of LeasePak 6.2a Client to upgrade the LeasePak client software.