ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Broker 6 migration and 64bit db2 instance issue

Post new topic  Reply to topic
 Broker 6 migration and 64bit db2 instance issue « View previous topic :: View next topic » 
Author Message
sieijish
PostPosted: Mon Sep 18, 2006 6:40 am    Post subject: Broker 6 migration and 64bit db2 instance issue Reply with quote

Acolyte

Joined: 29 Nov 2004
Posts: 67
Location: London

I am trying to migrate my v.5 broker to broker v.6 & MQ v.6. Since we are using XA transactions with DB2 i have to convert my 32 bit db2 instance to a 64 bit one.

According to the documentation, i have to use db2iupdt command. But it fails with the folloiwng error

./db2iupdt -w 64 db2inst1
DBI1250E Applications are still using instance
db2inst1.

But there is not db2 process running on the server. Here is the output when i run db2iupdt in debug mode. I have pasted the lines from which error is thrown.

Any idea what the probem is?


+663 files=/home/db2inst1/sqllib/adm/db2trc
+664 + /usr/bin/chmod u=rxs,g=rxs,o=x /home/db2inst1/sqllib/adm/db2trc
+665 + [ 0 -ne 0 ]
+666 + trax mkpermission
+667 + [ 0 -eq 0 ]
+668 + /usr/bin/echo ## exit function mkpermission
+669 + /usr/bin/tee -a /tmp/db2iupdt.log.15620
+670 ## exit function mkpermission
+671 + return 0
+672 + [ -f /usr/opt/db2_08_01/security/libchkau ]
+673 + [ -f /home/db2inst1/sqllib/tmp/generate.spf ]
+674 + trax pre_iupdate
+675 + [ 0 -eq 0 ]
+676 + /usr/bin/tee -a /tmp/db2iupdt.log.15620
+677 + /usr/bin/echo ## exit function pre_iupdate
+678 ## exit function pre_iupdate
+679 status=1
+680 + [ -f /usr/opt/db2_08_01/bin/db2gcf ]
+681 + /usr/opt/db2_08_01/bin/db2gcf -i db2inst1 -s -t 10
+682 status=3
+683 + [ 0 -eq 0 ]
+684 + /usr/bin/ps -elf
+685 + /usr/bin/grep db2inst1
+686 200001 A root 15620 25202 0 60 20 168ab 1820 14:43:54 pts/0 0:00 /bin/bsh ./db2iupdt -d db2inst1
+687 200001 A root 45836 15620 0 60 20 35d9b 236 14:44:07 pts/0 0:00 grep db2inst1
+688 + /usr/bin/grep db2inst1
+689 + /usr/bin/ipcs -a
+690 + dmsg db2gcf return code is 3
+691 + [ 0 -eq 0 ]
+692 + /usr/bin/echo ## db2gcf return code is 3
+693 + /usr/bin/tee -a /tmp/db2iupdt.log.15620
+694 ## db2gcf return code is 3
+695 + display_msg /usr/opt/db2_08_01/msg/en_US.iso88591/db2install.cat 250 DBI1250E Applications are still using instance %s.\n db2inst1
+696 + set -x
+697 + unset catname msgid deftmsg msgstr warnmsg infomsg
+698 catname=/usr/opt/db2_08_01/msg/en_US.iso88591/db2install.cat
+699 msgid=250
+700 deftmsg=DBI1250E Applications are still using instance %s.\n
+701 warnmsg=1
+702 infomsg=1
+703 + /usr/bin/echo DBI1250E Applications are still using instance %s.\n
+704 + /usr/bin/grep DBI....W
+705 + [ 1 -eq 0 ]
+706 + /usr/bin/echo DBI1250E Applications are still using instance %s.\n
+707 + /usr/bin/grep DBI....I
+708 + [ 1 -eq 0 ]
+709 + [ 1 -eq 0 ]
+710 + [ 1 -eq 1 -a 1 -eq 1 ]
+711 + /usr/bin/expr 0 + 1
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Sep 18, 2006 6:58 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

So you did a full and complete stop of Broker. Then you did a full, controlled, shutdown of the db2 instance, including disconnectiong all applications and running db2stop.

And you tried to run db2iupdt, and you get an error that an application is using the database?

If so, open a PMR with DB2.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
sieijish
PostPosted: Mon Sep 18, 2006 7:09 am    Post subject: Reply with quote

Acolyte

Joined: 29 Nov 2004
Posts: 67
Location: London

YES. Infact the debug log also shows that no db2 process is running other than the db2iupdt one!..

Code:
+684 + /usr/bin/ps -elf
+685 + /usr/bin/grep db2inst1
+686 200001 A root 15620 25202 0 60 20 168ab 1820 14:43:54 pts/0 0:00 /bin/bsh ./db2iupdt -d db2inst1
+687 200001 A root 45836 15620 0 60 20 35d9b 236 14:44:07 pts/0 0:00 grep db2inst1
+688 + /usr/bin/grep db2inst1
+689 + /usr/bin/ipcs -a
Back to top
View user's profile Send private message
sieijish
PostPosted: Wed Sep 20, 2006 1:09 am    Post subject: Reply with quote

Acolyte

Joined: 29 Nov 2004
Posts: 67
Location: London

Finally I have tracked down the real issue. The error message was wrong. The actual problem was that the command "/usr/opt/db2_08_01/bin/db2gcf -i db2inst1 -s -t 10 " was timing out due to a DNS look up issue. The default timeout specified in this command is 10sec. I have fixed the DNS issue so the name resolution is now fast and db2iupdt is working now.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Broker 6 migration and 64bit db2 instance issue
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.