For LeasePak version 6.2a.
Describes the upgrade and conversion procedures from LeasePak 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 processes need to be stopped, use the kill command
kill id
where id is the process id number.
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 kill command
kill spid
where spid is the process id number.
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.
Log on the server as msiadmin and stop all batch and print queues
dcl -n $S7DIR/com/stop_qmgr.com
Perform either a full or incremental backup of the server as needed.
Complete the following sections from LeasePak Server Preparation and Installation:
If you are updating a previous installation of LeasePak 6.2a, you can use one of the following options with setup:
-b Use this option to update the LeasePak build only.
-s7 Use this option to update the Queue Manager version only.
-l (The letter el) use this option to update the license file only.
If you installed the new release of LeasePak using the -b option or no options (which includes all by default), you will need to update your LeasePak Databases.
Log on the server as msidba and run the following three scripts in sequence:
db_drop_code environment-name [dbo-password]db_load_code environment-name [dbo-password]db_set_security environment-name [dbo-password]
where environment-name is the name of the environment whose database you are converting and dbo-password is the database owner password.
Sybase only: you may also need to run db_update_statistics. For more information on when to run this script, refer to the Sybase documentation on update statisticsor contact your NetSol representative.
To update the statistics
1. Log on the server as msidba
Terminal emulation: you must use one of the supported terminal types. Refer to the System Requirements for more information.
2. Change to the $top/env/environment/bin directory, where environment is the environment whose database you are converting
3. Run db_update_statistics
db_update_statistics environment-name [dbo-password]
where environment-name is the name of the environment whose database you are converting and dbo-password is the database owner password.
Log on the server as msiadmin and restart all batch and print queues
dcl -n $S7DIR/com/start_qmgr.comdcl -n $S7DIR/com/start_queues.com
Follow the procedures in the Upgrade and Conversion section of LeasePak 6.2a Client to upgrade the LeasePak client software.