| Author |
Message
|
| LearnMQSI |
 Posted: Fri May 26, 2006 11:25 pm Post subject: MQSI2.1 issue with DB2 Express C v9 - Can't create ConfigMgr |
 |
|
Centurion
Joined: 20 Aug 2002
Posts: 137
|
I have installed DB2 Express C v9 and installed MQSI 2.1 on my computer.
When I try to create the ConfigMgr, it is throwing BIP8075. Based on IBM solution, all my .jar files are correctly setup in my classpath.
MQSI 2.1 was working fine with DB2 7.2.
Wondering if MQSI 2.1 won't support DB2 Express C v9?
Thank you,
_________________
IBM Certified System Administrator - WebSphere MQ 5.3 |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sat May 27, 2006 3:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I don't think MQSI2.1 supports any DB2 greater than v7.
Also, please switch to v6 as soon as possible! v2.1 is not safe for production any more.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| LearnMQSI |
| Posted: Sat May 27, 2006 7:22 am Post subject: |
|
|
Centurion
Joined: 20 Aug 2002
Posts: 137
|
Hi jefflowrey,
Thank you for your respond to my mail. I have a question for you.
Why MQSI 2.1 is NOT safe in Production?
We are running MQSI 2.1 with CSD 11 in production and we don't have any plans to upgrade at least NOT this year.
That reminds me another question. I have installed both MQSI 2.1 and WBIMB 6. I on my PC. I guess V6 Broker need DB2 higher level than DB2 V7 so I have downloaded DB2 Express C V9 and installed it.
Of course I removed DB2 V7.2.
Now my MQSI 2.1 is not recognising my DB2 V7.2 Broker and Configuration Manager Databases which I have backed up them before I removed DB2 V7.2 and installed DB2 Express C V9 and I restored them. I also tried to delete those Databases and created new ones with DB2 Express C v9. I have deleted my ConfigMgr & Broker, uninstalled mqsi 2.1 and re-installed MQSI 2.1, upgraded to CSD 9. Still, I can not create my ConfigMgr, though I can create broker with no issues.
Bottomline, my question is - Is WBIMB V6 (Broker) will work fine with DB2 V7.2 OR required higher DB2 version?
Thank you all of you who have been sharing their thoughts and their experiences.
Thank you,
_________________
IBM Certified System Administrator - WebSphere MQ 5.3
Last edited by LearnMQSI on Sat May 27, 2006 8:00 am; edited 1 time in total |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Sat May 27, 2006 7:29 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| LearnMQSI |
| Posted: Sat May 27, 2006 8:04 am Post subject: |
|
|
Centurion
Joined: 20 Aug 2002
Posts: 137
|
Thank you Michael Dag,
That was quick. I appreciate it. I will look the link you have sent me. Thank you again but I still open to hear more from all MQ/MQSi/WBIMB experts on this topic.
Thank you!!!
_________________
IBM Certified System Administrator - WebSphere MQ 5.3 |
|
| Back to top |
|
|
| wschutz |
| Posted: Sat May 27, 2006 9:01 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| LearnMQSI wrote: |
| Thank you again but I still open to hear more from all MQ/MQSi/WBIMB experts on this topic. |
Okay then: service ends in Sept 2006, after that, if your PRODUCTION mqsi broker stops working, you can't open a problem report with IBM to get it fixed, so you're on your own.
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat May 27, 2006 11:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
In addition to the lack of support, I view 2.1 as unsafe for production because the features that it has are significantly outdated. As a simple example, 2.1 does not support XML Namespaces.
So the odds of a business requirement coming along that is unmeetable in 2.1 are significantly high enough to constitute a risk. The only way to mitigate that risk is to migrate.
You should have migrated to v5 two years ago.
You should be planning to migrate to v6 before the end of the year.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
