| Author |
Message
|
| Harshalw |
 Posted: Tue Aug 05, 2008 6:16 am Post subject: urgent - deleted the default broker database |
 |
|
Voyager
Joined: 23 Jul 2008
Posts: 77
|
I somehow deleted default broker database - DEFBKD61 entry from ODBC window (Control panel->adm tool->Datasource(odbc)) . Now ehen i am trying to connect to my remote db2 database - its giving me exception - Text:CHARACTER:[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
pls letme know what needs to be done in this case. shall i install WMB again? |
|
| Back to top |
|
 |
| Harshalw |
| Posted: Tue Aug 05, 2008 6:30 am Post subject: |
|
|
Voyager
Joined: 23 Jul 2008
Posts: 77
|
when i try to connect from db2 cmd prompt - it gives following error
db2 => connect to DEFBKD61
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "127.0.0.1". Communication function detecting
the error: "connect". Protocol specific error code(s): "10061", "*", "*".
SQLSTATE=08001
db2 => |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Tue Aug 05, 2008 6:39 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
|
| Back to top |
|
|
| Harshalw |
| Posted: Tue Aug 05, 2008 7:04 am Post subject: |
|
|
Voyager
Joined: 23 Jul 2008
Posts: 77
|
| where will i get TCP/IP services file on windows? |
|
| Back to top |
|
|
| Harshalw |
| Posted: Tue Aug 05, 2008 7:14 am Post subject: |
|
|
Voyager
Joined: 23 Jul 2008
Posts: 77
|
| like how do i find out which port should i use ? |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Tue Aug 05, 2008 11:15 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
|
| Back to top |
|
|
| Harshalw |
| Posted: Wed Aug 06, 2008 1:17 am Post subject: |
|
|
Voyager
Joined: 23 Jul 2008
Posts: 77
|
I check for the port and found it as 1572. have updated same in odbc db connect. still it is not working.
Also i tried to delete the default broker
it is giving me following error -
C:\Program Files\IBM\MQSI\6.1>mqsideletebroker WBRK61_DEFAULT_BROKER
WebSphere MQ queue manager running.
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 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 '-30081'; Error
Text ''[IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCK
ETS". Location where the error was detected: "127.0.0.1". Communication functi
on detecting the error: "connect". Protocol specific error code(s): "10061", "*
", "*". SQLSTATE=08001 ''.
The error has the following diagnostic information: SQL State ''
08001'' SQL Native Error Code '-30081' SQL Error Text ''[IBM][CLI
Driver] SQL30081N A communication error has been detected. Communication prot
ocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location w
here the error was detected: "127.0.0.1". Communication function detecting the
error: "connect". Protocol specific error code(s): "10061", "*", "*". SQLSTATE
=08001 ''
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 specified user Id and password pair.
- Check that the database is running.
- On Windows, check that an ODBC connection has been created.
- On systems that use $ODBCINI, check that the file pointed to by $ODBCINI has
been correctly updated.
- Use mqsichangebroker brokername -a xxx to set the password to the correct va
lue and try again.
Use mqsichangeconfigmgr configmgr -a xxx to set the password to the correct val
ue and try again.
- Check that the database has an adequate number of database connections available for use. |
|
| Back to top |
|
|
| Harshalw |
| Posted: Wed Aug 06, 2008 1:49 am Post subject: |
|
|
Voyager
Joined: 23 Jul 2008
Posts: 77
|
Also get GET DATABASE MANAGER CONFIGURATION is not giving me service name.
what can be the service name?
db2 => get dbm cfg
Database Manager Configuration
Node type = Client
Database manager configuration release level = 0x0a00
Federated Database System Support (FEDERATED) = NO
Transaction processor monitor name (TP_MON_NAME) =
Default charge-back account (DFT_ACCOUNT_STR) =
Java Development Kit installation path (JDK_PATH) = D:\SQLLIB\java\jd
Diagnostic error capture level (DIAGLEVEL) = 3
Notify Level (NOTIFYLEVEL) = 3
Diagnostic data directory path (DIAGPATH) =
SYSADM group name (SYSADM_GROUP) =
SYSCTRL group name (SYSCTRL_GROUP) =
SYSMAINT group name (SYSMAINT_GROUP) =
SQL10007N Message "8525" could not be retrieved. Reason code: "4".
SQL10007N Message "8566" could not be retrieved. Reason code: "4".
SQL10007N Message "8565" could not be retrieved. Reason code: "4".
SQL10007N Message "8567" could not be retrieved. Reason code: "4".
SQL10007N Message "8568" could not be retrieved. Reason code: "4".
SQL10007N Message "8562" could not be retrieved. Reason code: "4".
SQL10007N Message "8564" could not be retrieved. Reason code: "4".
SQL10007N Message "8569" could not be retrieved. Reason code: "4".
SQL10007N Message "8563" could not be retrieved. Reason code: "4".
Database manager authentication (AUTHENTICATION) = SERVER
Cataloging allowed without authority (CATALOG_NOAUTH) = YES
Bypass federated authentication (FED_NOAUTH) = NO
Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 512
Directory cache support (DIR_CACHE) = YES
Max requester I/O block size (bytes) (RQRIOBLK) = 32767
DOS requester I/O block size (bytes) (DOS_RQRIOBLK) = 4096
Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 10
Transaction manager database name (TM_DATABASE) = 1ST_CONN
NetBIOS Workstation name (NNAME) =
Discovery mode (DISCOVER) = SEARCH |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Wed Aug 06, 2008 8:40 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
Run this "get dbm cfg" and search the services file on db2 server machine to get to know the right port what db2 is listening(and authentication setting also).
Then on client
"catalog tcpip node xxnode remote xxx.xxx.xxx.xxx server port xxxxx " and
"catalog database YYYY at node xxnode"
and be careful that you have the same settings on db2-server and client authentication property.
Then you should be able to connect with db2 clp from client to your database and be able define odbc dsn.
Marko |
|
| Back to top |
|
|
|
|
