Migrate the databases, if any Use the migrate database command to migrate your

databases:

db2 migrate database database_alias user username using password

where

N O T E You may want to test DB2 9.5 before migrating an existing DB2 Version 8 copy. You can first install DB2 9.5 on the server that already has DB2 Version 8 installed. Then create a DB2 9.5 instance, and test your applications and environment. When you are satisfied with you testing, you can migrate your instances using the db2imigr

database_aliasis the name or the alias of the database you want to migrate.

usernameandpasswordrefer to a user with SYSADM authority.

3.12 CASE STUDY

Your company has chosen DB2 9.5 Enterprise Server Edition on a Windows machine as your data server. Currently you have DB2 9.5 Personal Edition installed on that machine, because you were learning DB2 on your own time. To install DB2 9.5 Enterprise Server Edition, you do not need to uninstall the DB2 Personal Edition; you can either install a new copy or migrate your existing DB2 9.5 Personal Edition to DB2 9.5 Enterprise Server Edition. You decide to migrate because you want to migrate one of your databases for further testing purposes. When you run

the DB2 9.5 Enterprise Server Edition db2setup command, the installation starts, but you

receive the warning message shown in Figure 3.34.

You click Yes because you were using DB2 PE for training purposes. After this, the installation successfully completes.

Next you issue the command db2licm -l to confirm you installed the right product and to

review the license status. Figure 3.35 shows the output of the command.

The response confirms that you have DB2 Enterprise Server Edition installed, but now you real- ize it is not yet registered. You tell this to your manager, who calls the 1-800-IBM-SERV num- ber to buy a permanent license.

Next, you issue thedb2levelcommand to ensure you are at the latest Fix Pack. Figure

3.36 shows the command’s output.

You notice that you are still at Fix Pack 0 (also known as base level or General Availability [GA] level). Since you know that Fix Pack 1 has just been released, you go to the IBM support Web site and download Fix Pack 1. Figure 3.37 shows the DB2 technical support Web site.

N O T E At the time this book was written, DB2 9.5 was still in open beta; therefore, Fix Pack 1 was not available. We use this Fix Pack number hypothetically to illustrate how to work with Fix Packs.

N O T E Web site content changes constantly. The DB2 Technical Support Web site may change in the future or may not look the same as shown in Figure 3.37.

Figure 3.35 Output from the db2licm command

After applying Fix Pack 1, you again issue the db2level command to confirm it now shows

the right Fix Pack level.

Now your company is ready to start working with DB2!

3.13 SUMMARY

In this chapter we discussed four DB2 installation methods:

• Using the DB2 Setup Wizard • Using a response file

• Using the db2_install script

• Using manual installation of DB2 payload files Figure 3.37 The DB2 technical support Web site

The first two methods are available on all supported platforms; the last two are only available on Linux and UNIX platforms. The recommended method to install DB2 is by using the DB2 Setup Wizard. We also discussed the Version 9.5 non-root installation option on Linux and UNIX plat- forms. Starting with DB2 9.5, you can install products, apply and roll back Fix Packs, configure instances, add features, or uninstall products as a non-root user. If you use the DB2 Setup Wiz- ard or the response file methods, you have the choice to create a DB2 instance and the DAS except during the non-root installation on Linux and UNIX. The instance owner user ID and the DAS user ID are also created. If you use the other two methods in root installations, you must manually create the user IDs and the instance after the installation is completed. If you use the manual install method, you must also install the DB2 license manually.

To install DB2 in a DPF environment with multiple machines, the recommended installation method is the Silent install. Copy the DB2 install image from the CD-ROM to a shared disk; then run the DB2 setup program from each machine to install DB2 locally.

A DB2 copy is a separate installation copy of the DB2 9 code. Each DB2 copy can be at the same or different code levels. The benefits of DB2 copies include

• The ability to run applications that require different DB2 versions on the same machine

at the same time.

• The ability to run independent copies of DB2 products for different functions.

• The ability to test on the same computer before moving the production database to the

latter version of the DB2 product.

A DB2 copy can contain one or more different DB2 products. This refers to the group of DB2 products that are installed at the same location. On Linux and UNIX, non-root installations allow only one DB2 copy for each valid non-root user.

A DB2 Fix Pack contains updates and fixes for problems or defects found during IBM testing, and customer reports. These fixes are also known as Authorized Program Analysis Reports or APARs for short. Fix Packs are cumulative and it is recommended that you keep your DB2 envi- ronment running at the latest Fix Pack level to ensure a low-incident operation.

3.14 REVIEW QUESTIONS