| Author |
Message
|
| Inforz |
 Posted: Wed Apr 27, 2011 10:25 pm Post subject: How can I delete a broker with some errors? |
 |
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
Hi,
I need to delete a broker(MBv6.0) and recreate it(as instructed to me). Its has its DB as oracle. The problem is when I try to delete, it issues an output saying as follows.
"BIP2322E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] Data source name not found and no default driver specified''.
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Data source name not found and no default driver specified''
and
"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."
I have checked for the last two options ie., ensuring the connectivity for the specified id and pwd and secondly the adequate # of connections availability."
The DB connection id(in registry folder) and pwd(using mqsisetdbparms) are correctly set.
Those guys who were at the time of creating the broker are not there.
What would be the best method to delete such a broker.
Thanks, |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Apr 28, 2011 12:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
No, you need to merely delete the 6.0 broker.
6.0 goes out of support in two days.
TWO DAYS.
Otherwise the error is frightfully clear and direct in nature - "Data source name not found".
Using mqsisetdbparms does not allow you to set a userid/password for the broker database. |
|
| Back to top |
|
|
| Inforz |
| Posted: Thu Apr 28, 2011 1:22 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
| mqjeff wrote: |
No, you need to merely delete the 6.0 broker.
Otherwise the error is frightfully clear and direct in nature - "Data source name not found".
Using mqsisetdbparms does not allow you to set a userid/password for the broker database. |
Thanks mqjefff.
I understand "merely delete"ing is just deleting the folder structure. If so, which all folder contents need to be deleted.
I guess some additional steps are also need to be done to completely delete the broker(like any registry entries or something like that..?)
Yeah mqsisetdbparms is not for setting the credentials for DB but just for connecting to the DB(which means use the existing credentials to connect to DB).
Using the same credentials I was able to connect to the DB in the SQLplus and access the tables.
Thanks, |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 28, 2011 1:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
No, I don't mean "delete some folders".
I mean you should delete the broker and then not create it again at v6.0 because v6.0 is going out of support and you should stop using v6.0.
The error you have received has NOTHING to do with the credentials used to log into the database.
You should not delete folders or registry entries or make any further changes to the box until you have READ the error message again and THOUGHT about what the words "data source name" means.
And, again, just stop using Broker v6.0 at all. Use 6.1 or 7. |
|
| Back to top |
|
|
| khudania |
| Posted: Thu Apr 28, 2011 6:59 am Post subject: |
|
|
Apprentice
Joined: 30 Nov 2004
Posts: 43
|
I had similar problem sometime earlier, but I am unable to recollect how I solved that. I am planning to update this thread later with that solution once I recollect.
For now, I strongly feel that the password used when the broker was actually created was different and you need to first update that password to current password. Do this by using
mqsichangebroker with -p option for the this service user [-i, -a]
| Quote: |
| -p dataSourcePassword' the password for the broker's database user ID. |
and then delete it.
_________________
If the doors of perception were cleansed, everything would appear as it is - infinite |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 28, 2011 7:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| khudania wrote: |
For now, I strongly feel that the password used when the broker was actually created was different and you need to first update that password to current password. Do this by using
mqsichangebroker with -p option for the this service user [-i, -a]
| Quote: |
| -p dataSourcePassword' the password for the broker's database user ID. |
and then delete it. |
Do you also strongly feel this will work in the face of the BIP2322E error which clearly states "Data source name not found"? How often does specifying the correct password make a data source suddenly reappear in the broker's scope?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| khudania |
| Posted: Thu Apr 28, 2011 7:14 am Post subject: |
|
|
Apprentice
Joined: 30 Nov 2004
Posts: 43
|
Yes, I understand this sounds wierd but as I said, I had almost identical issue and I have had spent quite some time on this one.
Also, Vitor, please do pay attention to the later error which is masked by Datasource not found error.
| 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." |
[/b]
I fully admit, I have some how forgotten the solution I used to solve this problem. 
_________________
If the doors of perception were cleansed, everything would appear as it is - infinite |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 28, 2011 7:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| khudania wrote: |
| Also, Vitor, please do pay attention to the later error which is masked by Datasource not found error. |
Not masked by - a result of. The broker is reporting that the database is inaccessable, which it is. Because the data source can't be found.
| khudania wrote: |
| I fully admit, I have some how forgotten the solution I used to solve this problem |
Then post it when you've remembered. Try giving your doors of perception another wipe down.
Don't post random nuggets of advice.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| khudania |
| Posted: Thu Apr 28, 2011 7:33 am Post subject: |
|
|
Apprentice
Joined: 30 Nov 2004
Posts: 43
|
| Quote: |
| Not masked by - a result of. The broker is reporting that the database is inaccessable, which it is. Because the data source can't be found. |
Only Inforz can tell whether the Datasource exists or not and he says
| Quote: |
The DB connection id(in registry folder) and pwd(using mqsisetdbparms) are correctly set. |
Which means Datasource does exists...
Now read what he really says... setting the password of broker database using mqsisetdbparms, which is NOT POSSIBLE.
_________________
If the doors of perception were cleansed, everything would appear as it is - infinite |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 28, 2011 7:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| khudania wrote: |
| Quote: |
| Not masked by - a result of. The broker is reporting that the database is inaccessable, which it is. Because the data source can't be found. |
Only Inforz can tell whether the Datasource exists or not and he says
| Quote: |
The DB connection id(in registry folder) and pwd(using mqsisetdbparms) are correctly set. |
Which means Datasource does exists... |
No, it means Inforz ran mqsisetdbparms. It doesn't mean that Informz has configured a DSN in the ODBC or set the right things to make the ODBC available. |
|
| Back to top |
|
|
| khudania |
| Posted: Thu Apr 28, 2011 7:39 am Post subject: |
|
|
Apprentice
Joined: 30 Nov 2004
Posts: 43
|
| mqjeff wrote: |
No, it means Inforz ran mqsisetdbparms. It doesn't mean that Informz has configured a DSN in the ODBC or set the right things to make the ODBC available. |
OK, let us assume, Broker Datasource does exist.
so you are claiming you can change the Broker Datasource password using mqsisetdbparms ?
_________________
If the doors of perception were cleansed, everything would appear as it is - infinite |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 28, 2011 7:50 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| khudania wrote: |
OK, let us assume, Broker Datasource does exist.
|
We can also assume I just won the lottery.
Doesn't mean I can spend the money.
Only the OP can say with authority what does & does not exist on the system in question.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 28, 2011 7:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| khudania wrote: |
| so you are claiming you can change the Broker Datasource password using mqsisetdbparms ? |
No. I already explicitly said you can't change the Broker database password using mqsisetdbparms.
I do not directly comment on whether mqsisetdbparms will function if it can't lookup the DSN it is given. that is left as an exercise. |
|
| Back to top |
|
|
| Inforz |
| Posted: Thu Apr 28, 2011 9:37 pm Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
Experts, sorry I was a bit away from work. I shall make things clear from my side.
I never meant to set a new id or password for the database using mqsisetdbparms. I jus meant that I have used the id and password of the database in the mqsisetdbparms.
FYI, I am using Oracle 10g as broker db and this is linux environment. This is the content from .odbc.ini file related to this topic(truncated the unwanted stanzas).
[ODBC Data Sources]
MQSIBKDB=IBM DB2 ODBC Driver
MYDB=IBM DB2 ODBC Driver
BROKERDB=DataDirect 5.0 Oracle
SYBASEDB=DataDirect 5.0 Sybase Wire Protocol
SQLSERVERDB=DataDirect 5.0 SQL Server Wire Protocol
INFORMIXDB=IBM Informix ODBC Driver
[BROKERDB]
Driver=/opt/ibm/mqsi/6.0/merant/lib/UKor820.so
Description=DataDirect 5.0 Oracle
EnableDescribeParam=1
OptimizePrepare=1
ServerName=TIDEAS
WorkArounds=536870912
ProcedureRetResults=1
I have the BROKERDB as the DSN (set in the mqsisetdbparms (-n)), TIDEAS as the database name.
As I said I am able to access the database and the tables with the credentials that I gave in mqsisetdbparms (-u <uid> and -p <pwd>) using SQL plus
Also the $ODBCINI variable is set correctly pointing to the .odbc.ini file.
I am not sure if I can delete the broker using mqsideletebroker coz I have changed settings and tried a lot but MB6 is stubborn and not even changing a single word in its error  . If possible pls let me know what other settings need to be changed. Else please let me know any alternate set of steps to completely delete the broker successfully(Some manual directory removal or registry changes or something like that).
Also please let me know if any further info is needed. 
Thanks, |
|
| Back to top |
|
|
| khudania |
| Posted: Thu Apr 28, 2011 11:40 pm Post subject: |
|
|
Apprentice
Joined: 30 Nov 2004
Posts: 43
|
| Quote: |
| I have the BROKERDB as the DSN (set in the mqsisetdbparms (-n)), TIDEAS as the database name. |
This is exactly what I tried to tell you since yesterday, BROKER DATASOURCE PASSWORD cannot be changed using mqsisetdbparms . This command is meant for application datasource parameters.
for changing the BROKER DATASOURCE, use
| Quote: |
| mqsichangebroker with -p option for the this service user [-i, -a] |
Just set the password to the current password and then use broker delete command.
I would wait for the reply.
| Quote: |
SYNTAX
>>-mqsichangebroker-- brokername ------------------------------->
>--+---------------------------------------------------+-------->
'- -a --ServicePassword --+-----------------------+-'
'- -i -- ServiceUserID -'
>--+--------------------------+--------------------------------->
'- -p --DataSourcePassword-'
>--+--------------------------------------+--+------+----------->
'- -s --UserNameServerQueueManagerName-' +- -j -+
'- -d -'
>--+------+--+-------------------+------------------------------>
+- -t -+ '- -l --UserLilPath-'
'- -n -'
>--+----------------------------+------------------------------->
'- -g --ConfigurationTimeout-'
>--+---------------------------------+-------------------------->
'- -k --ConfigurationDelayTimeout-'
>--+------------------------+----------------------------------->
'- -P --HTTPListenerPort-'
>--+-------------------------------+---------------------------><
'- -v --statisticsMajorInterval-'
|
_________________
If the doors of perception were cleansed, everything would appear as it is - infinite |
|
| Back to top |
|
|
|
|
