This section contains instructions that you must follow before installing DB2.
Preparing for the installation of DB2
Install the pdksh-5.2.14-1.i386.rpm package from the Caldera OpenLinux CD-ROM in the /Packages/RPMS/ directory. For example, log in as root, mount the CD-ROM, and enter the following command to install the pdksh package:
bash# rpm -ivh /mnt/cdrom/Packages/RPMS/pdksh-5.2.14-1.i386.rpm |
Remove the jdk package, (JDK 1.2.2 from Sun), since it will conflict with the IBM Developer Kit for Java that you will install in the next step. To remove Sun's JDK, issue the following command as root:
bash# rpm -e jdk |
Install the IBM Developer Kit for Java. A brief set of installation directions is included in Section 10.
Edit the JAVA_HOME and PATH entries in /etc/config.d/shells/bashrc to remove the references to the JDK from Sun and update them to reflect the IBM Developer Kit for Java. The section that I changed started as:
[ -z "$JAVA_HOME" ]&& [ -d /usr/java ] && (
export JAVA_HOME=/usr/java
[ -r $JAVA_HOME/lib/classes.zip ] &&
export CLASSPATH=$JAVA_HOME/lib/classes.zip
) |
Replace it with the following section to reflect the default locations for the IBM Developer Kit for Java:
[ -z "$JAVA_HOME" ]&& [ -d /usr/jdk118 ] && (
export JAVA_HOME=/usr/jdk118
export PATH=$PATH:$JAVA_HOME/bin
[ -r $JAVA_HOME/lib/classes.zip ] &&
export CLASSPATH=$JAVA_HOME/lib/classes.zip
) |
Follow the instructions in Section 4 the generic section on installing DB2, and go ahead and create the instances. It's probably a good idea at this point to read through Section 3.1.3 to keep in mind the steps that you need to take after installing DB2.
It means something went slightly wrong, but it's okay. You may get this message splashed across your installation screen one or more times during the DB2 installation process, but other than not looking pretty, DB2 still installs correctly. Caldera apparently doesn't include a /etc/login.defs configuration file. The file controls the default options for the useradd command for adding new users, including policies like how many days before the new user's password expires and whether a home directory should be created for a new user. For more information on the /etc/login.defs file, refer to the man page for useradd.
This section contains instructions that you must follow after installing DB2.
The most important step is to manually add the instance user ID to the corresponding instance group you defined during the instance creation step. DB2 and Caldera OpenLinux don't get this part of the DB2 instance creation process right, so you have to do it yourself. You can add an instance user ID to an instance group in two ways:
Edit /etc/group to add the appropriate instance user ID to the last field for each group.
Use the COAS utility to manage your groups by selecting KDE menu, Settings, COAS, System, Accounts, then selecting the Groups submenu and the Manage Groups menu item.
The DB2 Control Center and the DB2 Information Center use the Netscape browser to display help and documentation. This works for the first document you display in the browser, but if you try to switch to a different DB2 document (for example, from one book to another), you may instead be redirected to the default home page set by the Caldera OpenLinux installation process. I found that this problem went away as soon as I changed the default home page in the Edit menu, Preferences menu item.
Add a file called .hushlogin to the home directory of each of your instance user IDs. This should prevent the Welcome to your OpenLinux system! messages while running DB2 commands.
DB2 generates these messages on Caldera because the DB2 commands run under the root user ID, which in turn becomes the instance owner to invoke commands. Part of this su process calls one or both of /etc/config.d/shells/csh.login and /etc/config.d/shells/profile, which in turn call the /etc/config.d/shells/OL-greeting script that contains the offensive string.
Instead of adding .hushlogin to every user's home directory, you could probably edit /etc/config.d/shells/OL-greeting to remove the message (or change it to something else, if you want). I haven't tried it myself, so let me know what works best.
Preparing for the installation of DB2
Install the pdksh-5.2.14-2.i386.rpm package from the Red Hat CD-ROM in the /RedHat/RPMS/ directory. For example, log in as root, mount the CD-ROM, and enter the following command to install the pdksh package:
bash# rpm -ivh /mnt/cdrom/RedHat/RPMS/pdksh-5.2.14-2.i386.rpm |
Follow the instructions in Section 4, the generic section on installing DB2 and creating instances.
With Red Hat 6.2, you don't need to take any special steps after installing DB2 Version 7.1. It works.
SuSE 6.3 includes all of the required packages at or above the minimum required levels for DB2 Version 7.1. If you have a choice between installing SuSE 6.3 or 6.2, I would strongly recommend installing 6.3.
SuSE 6.2, ships with a glibc level of 2.1.1 and a kernel level of 2.2.10; however, in my tests this did not cause any problems with installation, running the DB2 Control Center, or creating and running Java and C applications for DB2.
Follow the instructions in Section 4, the generic section on installing DB2. When you create the instances, keep in mind the following information about creating instances on SuSE.
The default installation packages in the SuSE distribution include an old beta version of DB2. This means that the default DB2 user IDs and groups used by the Create Instance menu are already created when you try to create an instance for DB2 Version 7.1, causing the following problems:
Default user name already exists
Because the default user name already exists, the DB2 Create Instance panel places the corresponding user ID in the "User ID" field. This can cause a problem when you change the value of the User Name field to reflect the name of the new instance, because the value of the "User ID" still reflects the original user name.
Ensure that you select the "Use default UID" check box to automatically associate the new user name with its corresponding user ID.
Default group name already exists
Because the default group name already exists, the DB2 Create Instance panel places the corresponding group ID in the Group ID field. This can cause a problem when you change the value of the Group Name field to reflect the name of the new instance, because the value of the Group ID still reflects the original group name.
Ensure that you select the "Use default GID" check box to automatically associate the new group name with its corresponding group ID.
Default home directory points to /usr/lib/db2/
Because the default user name already exists and was created in the /usr/lib/db2/ directory, you have to manually specify the location of the new instance. The default home directory is /home/.
With SuSE 6.2 or above, I have not needed to take any special steps after installing DB2 Version 7.1. It just works—and that's nice.
TurboLinux 6.0 includes all of the required packages at or above the minimum required levels for DB2 Version 7.1.
Follow the instructions in Section 4, the generic section on installing DB2.
When you run the DB2 Control Center with TurboLinux 6.0, the console window may display a number of map failed messages. These messages do not indicate a serious problem, so do not worry about them.