| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Search found 5 matches |
| Author |
Message |
 Topic: Question about ODBC Driver for DB2 |
caroljx
Replies: 2
Views: 3299
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 06, 2004 9:50 am Subject: Question about ODBC Driver for DB2 |
MQSI 2.0.2, AIX 5.1+ML3, DB2 7.1.0.40
I have a question about db2 ODBC driver for MQSI. In our .odbc.ini file, I found our current configuration is:
Driver=/db2data/db2inst1/sqllib/lib/db2_36.o
... |
| Topic: Loss message set after upgrade MQSI from 2.0.2 to 2.1 |
caroljx
Replies: 6
Views: 3832
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 06, 2004 9:32 am Subject: Loss message set after upgrade MQSI from 2.0.2 to 2.1 |
Then just redeploy the message sets.
But why do we have to do this step? It is not documented in IBM's instruction. I just feel not comfortable with this redeployment step because I don't know whet ... |
| Topic: Loss message set after upgrade MQSI from 2.0.2 to 2.1 |
caroljx
Replies: 6
Views: 3832
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 06, 2004 9:21 am Subject: Loss message set after upgrade MQSI from 2.0.2 to 2.1 |
| We only upgraded broker on our AIX server. (not configuration manager) |
| Topic: Loss message set after upgrade MQSI from 2.0.2 to 2.1 |
caroljx
Replies: 6
Views: 3832
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 06, 2004 9:09 am Subject: Loss message set after upgrade MQSI from 2.0.2 to 2.1 |
During the migration, we didn't touch message sets. According to IBM's instruction, we did following steps:
1. Deintall MQSI 2.0.2.
2. Install MQSI 2.1
3. Migrate MQSI broker's database by create ... |
| Topic: Loss message set after upgrade MQSI from 2.0.2 to 2.1 |
caroljx
Replies: 6
Views: 3832
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 06, 2004 8:40 am Subject: Loss message set after upgrade MQSI from 2.0.2 to 2.1 |
We are currently running on AIX 5.1+ML3, MQSeries 5.3.0.1, DB2 7.1.0.40.
We upgraded our MQSI from 2.0.2 to 2.1 but when the developers did test after upgrading, their application didn't work. We f ... |
|
|
|
