Filter
Top Products
6320ch_DEV_installation.fm Draft Document for Review July 28, 2004 7:33 pm
84 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
2. When the Launchpad window opens, click Install Product.
3. Click Next to start the installation.
If a warning dialog is displayed warning you that DB2 is currently running,
click No to exit the installation. Stop all running DB2 processes from the
Services console and start the installation again.
4. On the welcome screen, click Next to continue.
5. After a while, the Wizard will indicate that setup is complete. Click Finish to
exit the wizard.
After a few seconds, the First Steps window will appear.
6. Restart Windows.
You can confirm that the fixpack properly installed by opening a DB2 command
window and running the db2level command. The output should be similar to that
shown in Example 5-2.
Example 5-2 Sample output from db2level after applying fixpack 5
DB21-85I Instance “DB2” uses “32” bits and DB2 code release “SQL08015” with
level identifier “02060106”.
Informational tokens are “DB2 v8.1.5.449”, “s040212”, “WR21334”, and FixPak
“5”.
Product is installed at “D:\WebSphere\sqllib”.
Important: You will need at least 500MB of free space on the drive where
the TEMP environment variable points to. This is typically the Windows
installation drive.
Note: The Launchpad window is identical to the original DB2 Universal
Database V8.1 Launchpad window, although it is in fact the fixpack 5
Launchpad window.
Important: DB2 should be stopped cleanly before installing the fixpack.
While it is possible to let the installation wizard kill the DB2 processes, this
is not recommended as it could lead to unpredictable results.