| Author |
Message
|
| helping_hand |
 Posted: Thu Aug 25, 2005 11:50 am Post subject: BIP8040E: Unable to connect to the database. |
 |
|
Novice
Joined: 28 Jul 2005
Posts: 14
|
I got this error
plz help me in solving this error
mqsideletebroker BIZBRKD -w
WebSphere MQ queue manager running.
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.
BIP2322E: Database error: SQL State '08001'; Native Error Code '-1013'; Error Text '[IBM][CLI Driver] SQL1013N The database alias name or database name "WBIDB" could not be found. SQLSTATE=42705 '.
The error has the following diagnostic information: SQL State '08001' SQL Native Error Code '-1013' SQL Error Text '[IBM][CLI Driver] SQL1013N The database alias name or database name "WBIDB" could not be found. SQLSTATE=42705 '
This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying 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 connection. Also ensure that the database has a adequate number of database connections available for use.
give me a solution for this error |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Aug 25, 2005 12:12 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Have you tried searching for SQLSTATE=42705
Also: What database? Remote or Local?
What version? |
|
| Back to top |
|
|
| dilse |
| Posted: Thu Aug 25, 2005 1:30 pm Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Make sure the floowing things.
1. Database Manager is started and running.
2. Make sure whether the ODBC drivers & DATABSE Tables are in place and connected.
3. Make sure the password credentails provided has enough permissions to access the database.
Finally check the errors that are in Event viewer's Application log and try to analyze the situation.
If it is a DB2 database, make sure you have valid licenses to use the product.
Post the errors that you find in Application log if you cannot be able to analyze them. Hope this helps.
_________________
DilSe..
Take life as it comes.. |
|
| Back to top |
|
|
| JT |
| Posted: Thu Aug 25, 2005 7:42 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
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 connection. Also ensure that the database has a adequate number of database connections available for use.
give me a solution for this error |
Have you tried the suggested recommendations first ?- 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 connection.
- Ensure that the database has a adequate number of database connections available for use.
|
|
| Back to top |
|
|
| helping_hand |
| Posted: Mon Aug 29, 2005 6:48 am Post subject: |
|
|
Novice
Joined: 28 Jul 2005
Posts: 14
|
thanks everyone for ur suggestions
Problem is solved
solution
I just connected to database
Below r the steps what i did
1. connect to database
2. disconnect database
3. connect to database
4. stop broker (mqsistop BROKER)
5. start broker
6. stop broker
7. delete broker
broker deleted successfully
8. end queue manager
9. dltmqm Queue manager
10. drop tables
11. deleted the database |
|
| Back to top |
|
|
|
|
