Procedure for upgrading a customer site

To upgrade a customer from Release<A> to Release<B>

Note: Release<A> should be Release<B> - 1. Never skip over a Release. If you have to, repeat the procedures for each release. 1. Create a test environment. In the event a test environment is not practial/feasible refer to AllphonesRel9UpgradePlan.

1. mkdir /u/cc.<B>/

2. mkdir /u/cc.<B>/TEST<B>

3. cp /u/cc/<CUSTOMER>/*.* /u/cc.<B>/TEST<B>

4. cp -r /u/cc/adm /u/cc.<B>

5. Create a new user called test<B>.

6. Edit test<B>'s .bash_profile to export CCDIR=/u/cc.<B>

7. Perform upgrade on test environment.

1. Ask customer to test the test environment.
2. When customer is happy with test environment, arrange time to perform upgrade. Preferably overnight.
3. Notify customer of upgrade and hope nothing went horribly wrong !!

To upgrade data and programs from Release<A> to Release<B>

1. Send all Release<B> programs, customised Release<B> programs, libraries, Release<B> standard company, the upgra<A> script and the upgra<B> script. Do NOT install. Place in a convienent location.

2. Disable all cron jobs (remember which ones so you can distinguish it later from those already disabled).
3. Ensure that all stores are fully synchronized with head office via polling.
4. Disable polling at store and head office.
5. Backup existing data and programs.

6. Send and install the latest Release<A> utitliy and update programs.

7. Check that running the upgra<A> script will not be a problem and run. If running the whole script may cause problems, manually run the appropriate steps. To check if the script will cause problems, check /u/ccr.A/std/update.log and /u/ccr.A/std/update.txt.

8. Check that the data is okay. Some functionalitiy may not work correctly due to changes in data updates.
9. Backup the company. This can useful if the following steps fail.
10. Backup the current programs.

11. Install new Release<B> programs, libraries and standard company.

12. Run the upgra<B> script.

13. Perform basic checks (eg. run sieat, run an aad program, etc.)
14. Set permissions of data files to be writable by ALL users
15. Re-enable and test polling
16. Reenable all cron jobs you disabled earlier.

Common Problems

• Missing library files. You will typically see an error message like this:

  # drcont
    drcont: error while loading shared libraries: XXXXX.so.XX: cannot open shared object file: No                 such file or directory

  To fix this:
  • Find the RPM package that contains the required library file and install. In Fedora Core 3 onwards, use Yum.
  • Copy the file libupgrade_sam.tgz from Sam and extract to $CCDIR/lib/. Be careful as it will overwrite existing library files.
  • Edit the LD_LIBRARY_PATH variable in $CCDIR/usr/common.sh to include $CCDIR/lib/
• Incorrect version of libstdc++.so.6 To fix this:
  • Edit the LD_LIBRARY_PATH variable in $CCDIR/usr/common.sh to use library files in $CCDIR/lib/ first
  • Edit the LD_LIBRARY_PATH variable in $CCDIR/usr/common.sh to use library files in $CCDIR/lib/ last