> If you are getting "SQL6036N START or STOP DATABASE MANAGER command is
> already in progress." then you have some kind of problem. If it said
> that the database is already started, that would be OK.
>
> Try and stop the database instance, and restart. If that does not work,
> try a reboot.
I have already tried that: I restarted DB2 and also restarted the whole
computer. I even reinstalled the whole linux but it made no difference.
So It had to be something I did wrong. My DB2 expert told me to execute
db2set DB2NOLIOAIO=false right after installing DB2. That was the
problem. To my surprise I could finally create my database simply by
undoing what I had done. Here are the details:
db2inst1@pjbrlnx:~> db2set
DB2NOLIOAIO=false
DB2COMM=tcpip
DB2AUTOSTART=YES
db2inst1@pjbrlnx:~> db2set DB2NOLIOAIO=true
db2inst1@pjbrlnx:~> db2start
07/02/2006 08:45:10 0 0 SQL1063N DB2START processing was
successful.
SQL1063N DB2START processing was successful.
db2inst1@pjbrlnx:~> db2 create db lnxkaka on /ges
DB20000I The CREATE DATABASE command completed successfully.
db2inst1@pjbrlnx:~>
Thanks anyway for your help
Phil Sherman - 07 Feb 2006 15:28 GMT
DB2NOLIOAIO=false activates asynchronous I/O. It requires a Linux 2.6
kernel that suppots the feature and a specific minimum level libaio module.
I suspect that the support isn't available or properly working on your
system.
Phil Sherman
>>If you are getting "SQL6036N START or STOP DATABASE MANAGER command is
>>already in progress." then you have some kind of problem. If it said
[quoted text clipped - 28 lines]
>
> Thanks anyway for your help
jbaron - 08 Feb 2006 08:17 GMT
Hi, Phil. Now that you say so, it is very likely. I am currently using
SLES8 and DB2 8.2 in an intel PC as a test for my real migration which
will be under SLES9 with DB2 8.2 in an IBM zSeries under z/VM. Probably
this will be solved in SLES9. Let's hope so.
I will take your indications into account.
Thank you very much for your help.
Jose R. Baron
CALCULO S.A.
jbaron@calculo-sa.es