Editing DB2 installation
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
== Create a new VE == | == Create a new VE == | ||
− | I created a new VE for the Debian distribution using debootstrap | + | I created a new VE for the Debian distribution using debootstrap. |
== Set VE resource limits appropriately == | == Set VE resource limits appropriately == | ||
− | + | DB2 installation can fail and it will not be possible to operate the database if your resource limits are too low. I used these limits for a small database: | |
− | * kmemsize to | + | * kmemsize to 10,000,000 |
− | * privvmpages to | + | * privvmpages to 300,000 |
− | * shmpages to | + | * shmpages to 80,000 |
− | * numproc to | + | * numproc to 150 |
− | * tcpsndbuf to | + | * tcpsndbuf to 700,000 |
− | * tcprcvbuf to | + | * tcprcvbuf to 700,000 |
− | * | + | * diskspace to 6,000,000 |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Install additional packages == | == Install additional packages == | ||
Line 49: | Line 42: | ||
* Run exp/disk1/db2setup | * Run exp/disk1/db2setup | ||
* Follow the prompts: | * Follow the prompts: | ||
− | + | * Setup user 'dasusr1' | |
− | + | * Setup user 'db2inst1' and database instance 'db2inst1' | |
== Post-install actions == | == Post-install actions == | ||
− | This is where it gets yukky. DB2 wants to run a browser inside the | + | This is where it gets yukky. DB2 wants to run a browser inside the VPS. It wants to run Java applets inside the browser. I installed Iceweasel, but the post-install script does not recognise it. I was eventually able to hack the script to recognise and use the browser but it crashed on one of the Java applets. I think you can get by without running the post-install. |
Here's what to do instead: | Here's what to do instead: | ||
Line 69: | Line 62: | ||
If these don't work it means your environment variables are not set properly. IBM set these for me: | If these don't work it means your environment variables are not set properly. IBM set these for me: | ||
− | + | * CLASSPATH=/home/db2inst1/sqllib/java/db2java.zip:/home/db2inst1/sqllib/java/db2jcc.jar:/home/db2inst1/sqllib/java/sqlj.zip:/home/db2inst1/sqllib/function:/home/db2inst1/sqllib/java/db2jcc_license_cu.jar:. | |
− | + | * DB2INSTANCE=db2inst1 | |
− | + | * PATH=/usr/local/bin:/usr/bin:/bin:/usr/games:/home/db2inst1/sqllib/bin:/home/db2inst1/sqllib/adm:/home/db2inst1/sqllib/misc | |
Try creating IBM's sample database: | Try creating IBM's sample database: | ||
Line 115: | Line 108: | ||
;; | ;; | ||
esac | esac | ||
− | + | ||
exit 0 | exit 0 | ||
And I used this command to create the symlink to make it start at VE "boot" time: | And I used this command to create the symlink to make it start at VE "boot" time: | ||
− | + | * update-rc.d db2 start 95 2 . | |
== Testing your installation == | == Testing your installation == | ||
Line 130: | Line 123: | ||
Inside the db2 client, try: | Inside the db2 client, try: | ||
− | + | * connect to sample | |
− | + | * grant all privileges to user fred (?not sure?) | |
− | + | * connect reset | |
− | |||
− | |||
− | |||
− | |||
− | |||
− |