Before proceeding, please ensure that you have read Section 5, “Installation considerations and planning” and Section 6, “Installing DB2 Express-C”.
Note that IBM does not officially support this distribution for DB2 9. Any problems you encounter using this distribution must be replicated on a supported distribution before IBM Support can help you resolve the issue.
These installation notes are based on a single-partition installation using the 2.6.18.2-34-default kernel.
The installation on OpenSUSE 10.2 completed successfully, with no problems getting the GUI installer working, and no errors during the install.
Basic test results (see Section 21, “Installation and operation test plan” for more details) were successful.
However, I found that after a reboot, the DB2 instance was not being restarted automatically, so clients could not connect to the database. To correct this problem, execute this command as the instance owner:
db2set DB2AUTOSTART=YES
This will ensure that the DB2 instance is initialized and ready to receive incoming connections after a reboot (intentional or otherwise).
Also, to allow DB2 access through the firewall (which is enabled by default), it was necessary to add the port values to the firewall using the YaST2 utility.
You can use the db2 get dbm cfg | grep SVCENAME command to retrieve the DB2 instance service name. By default, this is set as a TCP connection at port 50001. Note that you will need to add another new TCP rule to allow firewall access if you create any additional instances later. If you want to remotely administer the DB2 installation on this system, the UDP and TCP connections at port 523 should also be allowed through the firewall.
To open these ports using YaST, open the YaST tool, and select "Security and Users, then select the "Firewall" icon. In the Allowed Services setup panel, click on the "Advanced" button. In the TCP ports dialog, add 523 50001, and in the UDP ports dialog, add 523. Click "Next" until the setup wizard completes and restarts the firewall. Remote connections will now pass through to the DB2 instance.