Did you set the ODCB connection? In the first scenario the problem is regarding the ODBC connection.
I hope this help you. > -----Mensaje original----- > De: Graham Lekota [SMTP:[EMAIL PROTECTED] > Enviado el: Wednesday, February 26, 2003 4:40 PM > Para: [EMAIL PROTECTED] > Asunto: can't create mqsi broker on solaris > > Hi, > > I'm issuing the ff command on Solaris 2.8, WMQ 5.2 and WMQI 2.1 - no CSD. > > FIRST Scenario > > [mqsidev]/opt/mqadmin>mqsicreatebroker LMD1UMQI_BRK -i userid -a paswd -q > LMD1UMQI -n MQSIBRDB -u userid -p passwd > AMQ8110: MQSeries queue manager already exists. > MQSeries queue manager running. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > 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 'IM002'; Native Error Code '0'; Error > Text '[MERANT][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 '[MERANT][ODBC lib] Data source name > not found and no default driver specified' > 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. > [mqsidev]/opt/mqadmin> > > But I can log on to the system with the same userid and passwd. > > SECOND Scenario > > [mqsidev]/opt/mqadmin>db2 start database manager > DB20000I The START DATABASE MANAGER command completed successfully. > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin>db2 connect to MQSIBKDB > > Database Connection Information > > Database server = DB2/SUN 7.2.0 > SQL authorization ID = MQADMIN > Local database alias = MQSIBKDB > > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin>db2 list active databases > > Active Databases > > Database name = MQSIBKDB > Applications connected currently = 1 > Database path = /opt/mqadmin/mqadmin/NODE0000/SQL00002/ > > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin>mqsicreatebroker LMD1UMQI_BRK -i userid -a paswwd -q > LMD1UMQI -n MQSIBKDB > AMQ8110: MQSeries queue manager already exists. > MQSeries queue manager running. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > The setmqaut command completed successfully. > Abort(coredump) > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin>pkginfo | grep mq > application mqjava IBM MQSeries Product Extension MA88 > application mqm MQSeries for Sun Solaris 2 > application mqm-upd02 MQSeries for Sun Solaris 2 - U469913 > application n4cmqsd26 NNSY MQSeries Transport Driver 260 > application wmqi WebSphere MQ Integrator > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin>id > uid=101(mqadmin) gid=102(mqm) > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin>mqsilist > BIP8099I: LMD1UMQI_BRK - LMD1UMQI > BIP8071I: Successful command completion. > [mqsidev]/opt/mqadmin> > [mqsidev]/opt/mqadmin>uname -a > SunOS mqsidev 5.8 Generic_108528-18 sun4u sparc SUNW,Ultra-Enterprise > [mqsidev]/opt/mqadmin> > > > What could be the cause of these problems. > > Regards, > Moepi > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
