Skip to Content

Performing the upgrade

This section describes how to upgrade BMC PATROL for DB2 from earlier version.

Migrating customizations manually

Before migrating customizations, you must determine whether or not your customizations to PATROL for DB2 UDB can be migrated to the new version of PATROL for DB2 UDB. See the following table to determine whether migration is supported for your current version of PATROL for DB2 UDB. 

 Versions that you can migrate

Use the following table to help you select an upgrade procedure.  Use the following procedures to manually migrate customization from a earlier version of PATROL for DB2 UDB to the new version.

To migrate customizations manually

  1. Move the old PATROL for DB2 UDB to a directory that is different from PATROL_HOME.
  2. Identify the customizations in PATROL for DB2 UDB by comparing the content of the text file of the KM in the newly installed PATROL for DB2 UDB version with the content of the text file for your customized KM, which is what you just moved to a new directory.
  3. Incorporate your customizations to the new PATROL for DB2 UDB by performing the following steps:
    1. Restart the PATROL console.
    2. Load the newly installed PATROL for DB2 UDB.
    3. Using a PATROL developer console, enter the customizations that you identified in step 2, one by one.

To migrate customized PATROL Script Language code

Customizations made to PATROL Script Language (PSL) code are not automatically migrated. These customizations might be embedded in .km files or stored in separate .psl files. Migrate these customizations manually, using the following guidelines:

  • If you modified .psl files that were shipped by BMC, you must manually re-edit the PSL code in the new KM by using a PATROL developer console to reapply your changes.
  • If you modified PSL code embedded in a .km file, that code will be overwritten when you install a later version of the product. You must manually edit the new .km files by using a PATROL developer console to reapply your changes.
  • If you created a new PSL file (not shipped by BMC) outside of a .km file, or if you created new PSL code (not shipped by BMC) and embedded it in a .km file that was shipped by BMC, use the pslsearch utility to search your .km, .psl, and .ctg files for terms that you might have used that have because been adopted by BMC as PSL keywords. Rename any terms that pslsearch identifies as matching existing keywords. Reapply your changes by using a PATROL developer console.
Warning

Note

If you have a customized PSL library that was compiled with an earlier version of the PSL compiler than the version that was provided with PATROL 3.2.09i, you must manually recompile the library by using the PATROL 3.4.11 compiler.

Upgrading and saving customizations

Besides the manual instructions for upgrading and saving customizations given in Installing for the first time or upgrading over an existing installation or Migrating customizations manually you can also migrate your KM customizations to a later version of the KM and distribute those migrated customizations to PATROL Agents throughout your enterprise by using the Distribution Server.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for DB2 Universal Database 9.0