I have troubles using DB2 EEE on linux. I installed the EEE on two linux machine. The operating system is Redhat 7.0. I followed the instruction to create nfs home and successfully mounted from one machine to the other. But when I issued "create database test", I always get the following error message:
05-08-2002 13:32:12 2 0 SQL1063N DB2START processing was successful.
05-08-2002 13:32:14 1 0 SQL1063N DB2START processing was successful.
05-08-2002 13:32:15 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
[db2inst1@speed db2dump]$ db2 "create database test2"
SQL1229N The current transaction has been rolled back because of a system
I'm very appreciate for any suggestions to fix this problems.
You need to start looking at db2diag.log for the cause of this problem. I don't know why you are playing with "nfs" (Is that a typo.?) Everyone if not all knows that NFS is a serious performance killer in a high-volume environment. Maybe you're just experimenting with fault-tolerance and disaster recovery. Get the db2diag.log. To find out where it is on your system read this post: http://dbforums.com/t319674.html
for some pointers.
As described in DB2 EEE quick guide, we can create multiple database partitions on a single machine or more than one machines.
Two days ago, I first create two partition nodes on one machine and issue "create database test" and then partition the test database onto these two nodes. Everything is fine and I successfully partion the test database.
Then I create one node on the other machine and create another test database to see how this work. But as described in DB2 EEE quick guide in order to make it work, I need to create a directory and do the nfs mount so that each partition nodes see this directory. I followed the quick guide instruction and everything is fine before I issued the create database command. I also looked at the db2diag.log and always get the following messages.
I'm appreciate for those who giving me suggestions, I resolved the problem this afternoon. The problem is that I installed the two db2 instances under different directories on the two machines. I resolved the problems by reinstalled the db2 instance under same directory names on two machines.