PMDF Installation Guide
Linux Edition
Previous Contents Index

1.5 Post-Installation Tasks for Upgrades
  1. Run the script /pmdf/bin/upgrade_all_dbs.sh . This script performs the following actions (which can also be performed by hand if desired):
    1. If you are using a compiled configuration, it is recompiled with the command: 


      # pmdf cnbuild

    2. If necessary, the MessageStore user database is rebuilt with the command: 


      # pmdf msgstore x-build-user-db

    3. If you are upgrading from PMDF V6.4 or earlier, all other databases in the /pmdf tree are found and converted to the format used in V6.5 and later using the command: 


      # pmdf convertdb <old-database> <new-database>
      Note that the defragment database /pmdf/table/defragment_cache.* is excluded from this process. It does not need to be converted as the defragment channel will rebuild the database if necessary from the messages in the /pmdf/queue/defragment directory the first time it runs. Also note that databases outside the /pmdf tree, such as personal alias databases in users' home directories, are not found and converted by upgrade_all_dbs.sh .

    4. The Berkeley DB (SleepyCat) environment files are no longer used, so they are deleted if necessary, using the commands: 


      # rm /pmdf/tmp/__db.0*
# rm /pmdf/table/__db.0*
# rm /pmdf/table/queue_cache/__db.0*

  2. If necessary, rebuild or convert all remaining databases.
    If you are upgrading from PMDF V6.4 or earlier, all databases must be rebuilt or converted in order for PMDF V6.5 or later to be able to read them. PMDF V6.5 and later cannot read any databases in V6.4 or earlier formats.
    Note that PMDF V6.5 and later uses PBL as its database software. PMDF's PBL databases consist of three files: database.pbl which contains the data, database.idx which contains the index, and database.lck which is used for locking the database.
    1. All databases for which you have sources (including those sources you created before the upgrade using the pmdf dumpdb command) can be rebuilt using the pmdf crdb command.
    2. All databases created by pmdf db should be rebuilt. This includes the personal alias databases located in users' home directories (which are not converted by upgrade_all_dbs.sh ). Before doing the upgrade, you should have generated source files for these databases by using the pmdf db write command. At this time, you should rebuild these databases from those source files using the pmdf db run command. If you do not have a source file, the database can be recreated by using the pmdf db utility and adding each entry back in by hand. If you cannot rebuild these databases, they can be converted using the pmdf convertdb command if necessary.
    3. Databases created by utilities such as pmdf profile or pmdf password , and the databases created by MessageStore/popstore such as the forward database and the group names database must either be converted using pmdf convertdb or recreated by running the corresponding utility and adding each entry back in by hand.
  3. Check the contents of the PMDF tailor file /etc/pmdf_tailor that was supplied by this installation. Merge in any changes that you made to the file, using the copy that you saved before you started the upgrade.
  4. Start up the PMDF Job Controller and PMDF Service Dispatcher using the command: 


    # pmdf startup

    PMDF supports the systemctl method used in modern versions of Linux. To enable PMDF to be started at system boottime, issue the following comamnds: 


    # systemctl enable pmdf
# systemctl start pmdf

Previous Next Contents Index