| Author |
Message
|
| kevin_22 |
 Posted: Sat Apr 29, 2006 4:53 am Post subject: |
 |
|
Centurion
Joined: 08 Mar 2005
Posts: 100
|
Hi srinu,
I was having the same problem that you had previously. I did't find the solution for your problem. Please let me know the solution.
At present my problem is....
| Quote: |
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. T
he ODBC return code was '-1'. See the following messages for information obtaine
d from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely t
o be such things as incorrect datasource or table names. Then correct either the
database or message broker configuration.
BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error Text '
[Microsoft][ODBC Driver Manager] Data source name not found and no default drive
r specified'.
The error has the following diagnostic information: SQL State 'I
M002' SQL Native Error Code '0' SQL Error Text '[Microsoft][ODBC
Driver Manager] Data source name not found and no default driver specified'
This message may be accompanied by other messages describing the effect on the m
essage broker itself. Use the reason identified in this message with the accomp
anying messages to determine the cause of the error.
BIP8040E: Unable to connect to the database.
The database cannot be accessed with the userid and password that were specified |
when the broker was created.
Check that the database is running, that an ODBC connection has been created and
that the userid and password pair specified for ODBC connect on the mqsicreate
command are capable of being used to connect to the database using an ODBC conne
ction. Also ensure that the database has a adequate number of database connectio
ns available for use.[/quote]
I started my database.
I had created the data source name.
I am not even able to connect to database from the ODBC data source administration in the administration tools.
Thanks,
Kevin  |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sat Apr 29, 2006 5:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
This is NOT the same problem.
Your problem is with CREATING a broker, the previous problem was with DELETING a broker.
Also, if
| Quote: |
| I am not even able to connect to database from the ODBC data source administration in the administration tools. |
How do you possible expect Broker to do this for you?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kevin_22 |
| Posted: Sat Apr 29, 2006 5:18 am Post subject: |
|
|
Centurion
Joined: 08 Mar 2005
Posts: 100
|
Hi jefflowrey,
I mean that mine and srinu problem is with connecting to the database. Previously i use to have DB2 8.1 now i upgraded to 8.2. After upgrading i am having this problem.
So what can i do to solve this problem.......????Plz. let me know |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Apr 29, 2006 6:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You need to ask your DBA why you can't connect to the database.
Or you need to actually start troubleshooting this problem on your own, one step at a time, and tell us the results - since we can't troubleshoot this for you remotely.
Do you need to know what things to do to troubleshoot a database connection?
Do you need help understanding how to troubleshoot anything?
Do you need to understand how to be a DBA?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kevin_22 |
| Posted: Mon May 01, 2006 3:23 am Post subject: |
|
|
Centurion
Joined: 08 Mar 2005
Posts: 100
|
I think there might be a bug with UDB2 8.2. More over there is a fix pak 10 for it. I did't installed that fix pack. Installing that pick pack may solve the problem. At present i uninstalled UDB2 8.2 and installed 8.1 and its working fine.
Thanks,
Kevin |
|
| Back to top |
|
|
|
|
