Log on as root (or gain root access through a terminal if a root logon is not available)
Mount the DVD (if installing from Discovery DVD set), or download the appropriate Linux compressed image (tar.gz file) from the DB2 Express-C download site
Copy the compressed image file to the /tmp directory
Extract the files from the compressed image, either using the Ark GUI tool or using the console command tar zxvf db2exc_91_LNX_x86.tar.gz
Inside the /tmp folder, change to the exp/disk1i directory and run the db2setup command:
./db2setup |
In the DB2 setup Launchpad, choose Install a Product
Choose Install New
Click "Next"
Verify the license and change the radio button to Accept, then choose "Next" to continue the installation
Choose a Typical installation and click "Next"
Verify the install path, or change it to some point on your system with at least 470 MB free, click "Next"
Create a DB2 instance. Click "Next"
Set up the DB2 instance owner account. Again, you can use an existing user, or set up a new one (the default instance owner is 'db2inst1'). Click "Next"
Set up the DB2 fenced user account. Same as before, use an existing user or set up a new one. Click " .:: kemono.im ::. Next"
Click "Finish" to initiate the install
If there are any problems with the installation, it will show up in the installation log (the log is also kept in the /tmp directory as db2setup.log and db2setup.err)
Log in as the DB2 instance owner (db2inst1 by default)
Open a terminal and run 'db2sampl' to create the SAMPLE database
Test terminal based commands:
Test DB2 Control Center:
Create TOOLS database:
db2 'create tools catalog TOOLS create new database TOOLSDB' |
Launch DB2 Task Center:
Launch DB2 Journal: You should be able to see the results of the task you ran in the task center from the Journal. [MDN Docs: Bash]
Test DB2 Configuration Assistant
Start Configuration Assistant from the Control Center, or with .:: code.antopie.org ::. db2ca
You should see the SAMPLE database listed, if not, click View, then Refresh. .:: www3.uwsp.edu ::.
Right click on the SAMPLE database, choose Change Database, then in step 4 of the wizard, register the database as a CLI/ODBC source, and catalog as system data source. Click Finish to commit the changes .:: radical-ton-8dc.notion.site ::.
Right click on the SAMPLE database again, and click on Test Connection. Select all types (Standard (ODBC), CLI, JDBC), then type in a userid and password, and click on Test Connection. Ensure all tests are successful. .:: groups.google.com ::.
Test DB2 trace facility: db2trc on -- check for positive response, then run db2trc off
Test DB2 problem determination facility: db2pd -db sample > sample.txt (examine output for errors)
Test DB2 license: db2licm -l should return:
Product name: "DB2 Express Edition"
License type: "Unwarranted"
Expiry date: "Permanent"
Product identifier: "db2exp"
Version information: "9.1"
Max number of CPUs: "2"
|
Test db2dart:
db2 force applications all db2dart sample |
Test db2look facility: db2look -d sample -e > sample.ddl (should complete successfully)
Test remote connections:
Create connection through command prompt on DB2 remote client system: .:: drivehud.com ::.
db2 catalog tcpip node test remote computername server 50001 db2 catalog db sample at node test |
From remote machine:
db2 connect to sample db2 "select * from dept" |
Reboot server and retest via remote connection (to verify DB2 instance autostart and that any firewall changes stick)