|
IBM SecureWay Directory: Upgrading to a new version of DB2 UDB
Preface
This document describes the steps necessary to upgrade the version of
DB2 Universal DataBase used with SecureWay Directory.
Who can upgrade to DB2 UDB version 7
If you are running SecureWay Directory 3.2 or 3.2.1, and you
want to upgrade the version of DB2 you are using, you can follow the steps
below to do so. If you are
running a version of SecureWay Directory earlier than 3.2, you will need
to migrate your SecureWay Directory installation to be able to use DB2
version 7. In that case, we recommend you move up
to version 3.2.2 of SecureWay Directory.
When you download and install SecureWay Directory 3.2.2 from this
website, DB2 version 7 is included.
Where to
get DB2 UDB version 7
If you do not already have a copy of the new version of DB2
UDB that you wish to upgrade to, you may download DB2 UDB Version 7 from
the SecureWay directory webpage at
http://www.ibm.com/software/network/directory/downloads/. Under the “Code” section,
follow the link for Version 3.2.2 for your platform of interest. The DB2 install package is one of the files available to download
with SecureWay Directory 3.2.2, but you can always download only the DB2
file without the others. Before
you get the option to download the file, you will be asked to register
and accept the license agreement related to use of SecureWay Directory
and DB2. When you get to the list of files available
for download, the DB2 package is named udb72XX_<platform>, where
XX is either PE for Personal Edition, or EE for Enterprise Edition and
the name indicates the platform – such as aix, sun, or win. If you are planning to upgrade DB2, but not the rest of SecureWay
Directory, this is the only file you will need to download. If you decide to upgrade to SecureWay
Directory 3.2.2 as well, you should download all the files. Once the file has been copied to your
local system, untar or unzip it into a local filesystem directory.
Upgrading
on Windows platforms
All commands below show “ldapdb2”
as the instance name and database name.
These are the defaults, but if you have created your own custom
database you will need to substitute in the appropriate names based on
your setup.
1.
Start a DB2 command window.
2.
Set the DB2INSTANCE environment variable to the name
of the instance in use with LDAP.
set DB2INSTANCE=ldapdb2
3.
Stop slapd.
4.
Backup your existing database, just in case anything
goes wrong with the migration to the new version. db2 backup database ldapdb2 to <dir/dev>
5.
Stop the DB2
instance. db2stop
6.
Go to
the Services window and stop all related DB2 services.
DB2-DB2DAS00
DB2JDBC AppletServer – Control
DB2JDBC AppletServer
DB2 Security Server
DB2 Governor
7.
Run the db2ckmig.exe included with the DB2 install files,
specifying the DB2 instance name and the name of a file to log errors
in.
db2ckmig ldapdb2 –L <log_file_name>
This should respond as follows: “db2ckmig was successful. Databases(s) can be migrated.”
8.
If db2ckmig identifies any problem with your instance
or database, you will need to correct those problems before proceeding.
9.
Now install DB2 UDB version 7. As part of the install process, your instance and database(s)
will be migrated.
Upgrading
on Unix platforms
All commands below show “ldapdb2”
as the instance name and database name.
These are the defaults, but if you have created your own custom
database you will need to substitute in the appropriate names based on
your setup.
1. Source the
db2profile for your instance to set your path so that DB2 commands can
be found. The example below
gives the default path to the instance profile on AIX. The location may vary in your installation.
“. /home/ldapdb2/sqllib/db2profile”
Note that this command starts
with a dot “.” and a space “ “.
This is important in order to set the DB2 environment for the current
process.
2.
Stop slapd.
3.
Backup
your existing database, just in case anything goes wrong with the
migration to the new version. db2
backup database ldapdb2 to <dir/dev>
4.
Stop the
DB2 instance. db2stop
5.
Install
DB2 UDB version 7.
6.
Migrate
your DB2 instance.
[on AIX]
# /usr/lpp/db2_07_01/instance/db2imigr
–u ldapdb2 ldapdb2
[on Solaris]
# ln -fs /opt/IBMdb2/V7.1/instance/db2imigr
–u ldapdb2 ldapdb2
[on Linux]
# ln -fs /usr/IBMdb2/V7.1/instance/db2imigr
–u ldapdb2 ldapdb2
7.
Start
the migrated DB2 instance. db2start
8.
Migrate
your LDAP directory database. db2 migrate database ldapdb2
9.
If you
have a change log database, migrate it as well.
db2 migrate database
ldapclog
10. Update links to the new DB2 version 7 libraries:
[on AIX]
# ln -fs /usr/lpp/db2_07_01
/usr/ldap/db2
# ln -fs /usr/ldap/db2/lib/libdb2.a
/usr/ldap/lib
[on Solaris]
# ln -fs /opt/IBMdb2/V7.1
/usr/ldap/db2
# ln -fs /usr/ldap/db2/lib/libdb2.so
/usr/ldap/lib
# ln -fs /usr/ldap/db2/lib/libdb2.so.1 /usr/ldap/lib
[on Linux]
# ln -fs /usr/IBMdb2/V7.1
/usr/ldap/db2
# ln -fs /usr/ldap/db2/lib/libdb2.so
/usr/ldap/lib
11. At this point the upgrade is complete, and you
could uninstall your old version of DB2.
|
