OH!!! BOY!!!! Are you in trouble now!!! You went and played with it and BROKE
IT !!!!!!!!
Some ingenious person or system task took it upon itself to go in and change
the password on your UID. OR, some sneaky DBA went in and took away your access
authority. You need to see if what you THINK is the UID and PASSWORD actually
works on the DB and then work backwards. (ie. settings on the OS for that UID,
Broker (MQSICHANGEBROKER). I am assuming your Broker was running before this
happened.
Just remember if it is accessing the Broker DB, you can change the PWD but not
the UID. Cannot figure out why but it is what it is. So try to stay with the
same UID. If you issue an 'mqsiservice <brokername>' it will tell you lots of
interesting stuff that you may need.
bobbee
Date: Wed, 1 Aug 2007 16:21:11 +0200From: [EMAIL PROTECTED]: WMB V60 and DB8.2
- ODBC error - Please helpTo: [email protected]
mqsilist -a BROKERDEV
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 ''IM003''; Native Error Code '0'; Error
Text ''[DataDirect][ODBC lib] Specified driver could not be loaded''.
The error has the following diagnostic information: SQL State
''IM003'' SQL Native Error Code '0' SQL Error Text
''[DataDirect][ODBC lib] Specified driver could not be loaded''
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.
Nedbank Limited Reg No 1951/000009/06. The following link displays the names of
the Nedbank Board of Directors and Company Secretary.
This email is confidential and is intended for the addressee only. The
following link will take you to Nedbank's legal notice.
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in the
Listserv General Users Guide available at http://www.lsoft.com
_________________________________________________________________
Don't get caught with egg on your face. Play Chicktionary!
http://club.live.com/chicktionary.aspx?icid=chick_wlmailtextlink
To unsubscribe, write to [EMAIL PROTECTED] and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
