|
DB2 Version 7.1 for Linux HOWTO
3. Preparing your distribution for DB2
3.1. Caldera OpenLinux 2.4
3.1.1. Before installing DB2 on Caldera OpenLinux
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 PackagesRPMS directory. For example, log in as root, mount the CD-ROM, and enter the following command to install the pdksh package bash# rpm -ivh mntcdromPackagesRPMSpdksh-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 11.
Edit the JAVA_HOME and PATH entries in etcconfig.dshellsbashrc 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 usrjava ] && (
export JAVA_HOME=usrjava
[ -r $JAVA_HOMElibclasses.zip ] &&
export CLASSPATH=$JAVA_HOMElibclasses.zip
)
Replace it with the following section to reflect the default locations for the IBM Developer Kit for Java [ -z $JAVA_HOME ]&& [ -d usrjdk118 ] && (
export JAVA_HOME=usrjdk118
export PATH=$PATH$JAVA_HOMEbin
[ -r $JAVA_HOMElibclasses.zip ] &&
export CLASSPATH=$JAVA_HOMElibclasses.zip
)
3.1.2. Installing DB2 and creating instances on Caldera
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.
3.1.2.1. What does etclogin.defs not accessible, using defaults mean
3.1.2.2. Okay, DB2 is installed and I created the instances. Now what do I do
3.1.2.1. What does etclogin.defs not accessible, using defaults mean
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 etclogin.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 etclogin.defs file, refer to the man page for useradd.
3.1.2.2. Okay, DB2 is installed and I created the instances. Now what do I do
Now that you've installed DB2, you have to perform some steps to configure your instances correctly. Keep reading.
3.1.3. After installing DB2 on Caldera
This section contains instructions that you must follow after installing DB2.
3.1.3.1. Adding instance user IDs to their groups
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 etcgroup 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.
3.1.3.2. Changing the default home page in Netscape
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.
3.1.3.3. Removing the Caldera login greeting
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 etcconfig.dshellscsh.login and etcconfig.dshellsprofile, which in turn call the etcconfig.dshellsOL-greeting script that contains the offensive string.
Instead of adding .hushlogin to every user's home directory, you could probably edit etcconfig.dshellsOL-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.
3.2. Linux-Mandrake 7.2
The DB2 server and command line DB2 client works on Linux-Mandrake 7.2, and I was able to successfully start and use the DB2 Control Center with IBM JDK 1.1.8 (build 20000713).
3.2.1. Before installing DB2 on Linux-Mandrake
Preparing for the installation of DB2
Install the pdksh-5.2.14-8mdk.i586.rpm package from the Linux-Mandrake CD-ROM in the MandrakeRPMS directory. For example, log in as root, mount the CD-ROM, and enter the following command to install the pdksh package bash# rpm -ivh mntcdromMandrakeRPMSpdksh-5.2.14-8mdk.i586.rpm
3.2.2. Installing DB2 and creating instances on Linux-Mandrake
When you run db2setup, you may receive the following error ksh etcprofile.dtmdir.sh[9] source not found This is only a warning message and you can continue installing DB2. If the message interferes with the db2setup menu, press CTRL-L to clear the screen.
Otherwise, follow the instructions in Section 4, the generic section on installing DB2 and creating instances.
3.2.3. After installing DB2 on Linux-Mandrake
With Linux-Mandrake 7.2, there are no special steps to take after installing DB2 Version 7.1. The DB2 server and command line client work out of the box, and the DB2 Control Center worked with IBM JDK 1.1.8 (build 20000713).
3.3. Red Hat Linux 6.2
3.3.1. Before installing DB2 on Red Hat
Preparing for the installation of DB2
Install the pdksh-5.2.14-2.i386.rpm package from the Red Hat CD-ROM in the RedHatRPMS directory. For example, log in as root, mount the CD-ROM, and enter the following command to install the pdksh package bash# rpm -ivh mntcdromRedHatRPMSpdksh-5.2.14-2.i386.rpm
3.3.2. Installing DB2 and creating instances on Red Hat
Follow the instructions in Section 4, the generic section on installing DB2 and creating instances.
3.3.3. After installing DB2 on Red Hat
With Red Hat 6.2, you don't need to take any special steps after installing DB2 Version 7.1. It works.
3.4. Red Hat Linux 7.1
3.4.1. Before installing DB2 on Red Hat
Preparing for the installation of DB2
Install the pdksh-5.2.14-12.i386.rpm package from Red Hat CD-ROM (2) in the RedHatRPMS directory. For example, log in as root, mount the CD-ROM, and enter the following command to install the pdksh package bash# rpm -ivh mntcdromRedHatRPMSpdksh-5.2.14-12.i386.rpm
For a compatible version of the libstdc++ library, install the compat-egcs-c++-6.2-1.1.2.14.i386.rpm package from Red Hat CD-ROM (2) in the RedHatRPMS directory. For example, log in as root, mount the CD-ROM, and enter the following command to install the compat-egcs-c++ package bash# rpm -ivh mntcdromRedHatRPMScompat-egcs-c++-6.2-1.1.2.14.i386.rpm
Install the compat-libs-6.2-3.i386.rpm package from Red Hat CD-ROM (2) in the RedHatRPMS directory. For example, log in as root, mount the CD-ROM, and enter the following command to install the compat-libs package bash# rpm -ivh mntcdromRedHatRPMScompat-libs-6.2-3.i386.rpm
The db2setup command looks for a file called usrliblibncurses.so.4 and will not proceed unless it exists, so create a symbolic link from the ncurses4.0 library in usri386-glibc21-linuxlib to your usrlib directory. bash# ln -sf usri386-glibc21-linuxliblibncurses.so.4.0 usrliblibncurses.so.4
The default setting for the msgmni kernel parameter only allows a couple of simultaneous connections to DB2. To set this value at at boot time, append the following lines to etcsysctl.conf # Sets maximum number of message queues to 128
# Set this to 1024 or higher on production systems
kernel.msgmni = 128
3.4.2. Installing DB2 and creating instances on Red Hat
Follow the instructions in Section 4, the generic section on installing DB2 and creating instances.
3.4.3. After installing DB2 on Red Hat
Red Hat 7.1 enabled the floating point stack feature of the glibc library. Unfortunately, this causes Java programs using IBM JDK 1.1.8, includ [1] [2] 下一页
没有相关教程
| 
注：本站部分文章源于互联网，版权归原作者所有！如有侵权，请原作者与本站联系，本站将立即删除！ 本站文章除特别注明外均可转载，但需注明出处！ [MinTao学以致用网] 
