| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| mqsicreatebroker error |
« View previous topic :: View next topic » |
| Author |
Message
|
| jeeth_m |
 Posted: Tue Jul 25, 2006 1:31 am Post subject: mqsicreatebroker error |
 |
|
Voyager
Joined: 21 Jan 2002
Posts: 93
|
Hi,
When i create a broker i am getting the below error.
Any idea how to fix it?
BIP2371E: Database statement ''CREATE TABLE 157216.BROKERAAEG (BrokerUUID CHAR (
16) FOR BIT DATA NOT NULL , ExecGroupUUID CHAR (16) FOR BIT DATA NOT NULL , Exec
GroupLabel BLOB(1073741824) NOT LOGGED NOT NULL , RetryInterval INTEGER, PubSubS
erver INTEGER, ProcessId INTEGER, ProcessState INTEGER, DynamicState INTEGER, Dy
namicSync INTEGER, ProcArchitecture INTEGER, MsgId CHAR (24) FOR BIT DATA, CntlG
rpMsgId CHAR (24) FOR BIT DATA)'' could not be executed.
A message flow node attempted to execute a database statement. However, the data
base returned an error when executing the statement ''CREATE TABLE 157216.BROKER
AAEG (BrokerUUID CHAR (16) FOR BIT DATA NOT NULL , ExecGroupUUID CHAR (16) FOR B
IT DATA NOT NULL , ExecGroupLabel BLOB(1073741824) NOT LOGGED NOT NULL , RetryIn
terval INTEGER, PubSubServer INTEGER, ProcessId INTEGER, ProcessState INTEGER, D
ynamicState INTEGER, DynamicSync INTEGER, ProcArchitecture INTEGER, MsgId CHAR (
24) FOR BIT DATA, CntlGrpMsgId CHAR (24) FOR BIT DATA)''.
If necessary, correct the message flow and redeploy the message broker.
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 obtaine
d from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely t
o be such things as incorrect datasource or table names. Then correct either the
database or message broker configuration.
BIP2322E: Database error: SQL State ''42604''; Native Error Code '-103'; Error T
ext ''[IBM][CLI Driver][DB2/NT] SQL0103N The numeric literal "157216.BROKERAAEG
" is not valid. SQLSTATE=42604 ''.
The error has the following diagnostic information: SQL State ''
42604'' SQL Native Error Code '-103' SQL Error Text ''[IBM][CLI D
river][DB2/NT] SQL0103N The numeric literal "157216.BROKERAAEG" is not valid.
SQLSTATE=42604 ''
This message may be accompanied by other messages describing the effect on the m
essage broker itself. Use the reason identified in this message with the accomp
anying messages to determine the cause of the error.
BIP8070E: Exception accessing database table executing SQL statement 'CREATE TAB
LE 157216.BROKERAAEG (BrokerUUID CHAR (16) FOR BIT DATA NOT NULL , ExecGroupUUID
CHAR (16) FOR BIT DATA NOT NULL , ExecGroupLabel BLOB(1073741824) NOT LOGGED NO
T NULL , RetryInterval INTEGER, PubSubServer INTEGER, ProcessId INTEGER, Process
State INTEGER, DynamicState INTEGER, DynamicSync INTEGER, ProcArchitecture INTEG
ER, MsgId CHAR (24) FOR BIT DATA, CntlGrpMsgId CHAR (24) FOR BIT DATA)': SQL sta
te '-103'; exception 'ImbException'.
An SQL command has failed.
Ensure that the broker's database is available. Examine the exception and SQL s
tate code to determine and correct the cause of the error. |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Tue Jul 25, 2006 1:51 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi jeeth_m,
Can you paste the entire command that you are trying to use...including the userid for the database....
Regards. |
|
| Back to top |
|
|
| jeeth_m |
| Posted: Tue Jul 25, 2006 2:07 am Post subject: |
|
|
Voyager
Joined: 21 Jan 2002
Posts: 93
|
Below is the exact command i am using. I was trying to create a default broker. OS is win xp proffesional
mqsicreatebroker WBRK6_DEFAULT_BROKER -i 157216 -a passwd -q WBRK6_DEFAULT_QUEUE_MANAGER -n DEFBKDB6 |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Tue Jul 25, 2006 2:23 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi jeeth_m,
| jeeth_m wrote: |
| mqsicreatebroker WBRK6_DEFAULT_BROKER -i 157216 -a passwd -q WBRK6_DEFAULT_QUEUE_MANAGER -n DEFBKDB6 |
Is 157216 your userId  tell me that this userId has been forced upon you 
Have you created a System DSN for the database ? You must have as I would have expected a different error than the one you pasted...
What is the userid for the database...? Does this userId have db authority.
Regards. |
|
| Back to top |
|
|
| PieterV |
| Posted: Tue Jul 25, 2006 3:17 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
i would expect to see the -u and -p option in your mqsicreatebroker command.
-u : database userid
-p : database password |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 25, 2006 5:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| PieterV wrote: |
i would expect to see the -u and -p option in your mqsicreatebroker command.
-u : database userid
-p : database password |
This is only needed if the database userid needs to be different than the broker service id.
Granted, usually this is the case, but it is not a problem in any sense if -u and -p are not specified.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Kateel |
| Posted: Wed Jul 26, 2006 11:15 am Post subject: |
|
|
Novice
Joined: 01 May 2006
Posts: 17
|
The error ''''[IBM][CLI D
river][DB2/NT] SQL0103N The numeric literal "157216.BROKERAAEG" is not valid. SQLSTATE=42604 ''
'' sounds like a schema or DSN resolution error.
It appears that database has different userid. In that case,as stated elsewhere in this thread, the mqsicreatebroker command requires -u and -p.
You might as well want to make sure that the DSN specified in your .odbc.ini file matches with the one you are specifying in your createbroker command. |
|
| Back to top |
|
|
| newbee_wmb |
| Posted: Thu Oct 04, 2007 5:48 am Post subject: plz help me for solving this |
|
|
Newbie
Joined: 04 Oct 2007
Posts: 3
|
Hi Jeeth
did you solve this problem?
i am completely new to this MB and i am also getting the exactly same error while trying to create broker using the command
mqsicreatebroker WBRK_BROKER -i 120669 -a password -q WBRK_QM -n WBRKBKDB
i am using DB2 Enterprise server and the system dsn was created properly for ODBC connectivity.
The user id and password using for this db are also correct(infact i am able to create configmanager with the same db2 account details but different DB instance).
can you plz share me with the approach that you followed for solving this problem and help me in this...this is very much urgent for me
Thanks |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 04, 2007 2:46 pm Post subject: Re: plz help me for solving this |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| newbee_wmb wrote: |
The user id and password using for this db are also correct(infact i am able to create configmanager with the same db2 account details but different DB instance).
|
Woe to you my dear friend... From the rest of the posts it appears that you are running WMB V6. The config mgr on V6 does not utilize an external DB and does not access DB2. So your assumption for userid and password passed to DB2 is completely wrong.
Verify userid and passwd for DB2 again...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| newbee_wmb |
| Posted: Thu Oct 04, 2007 9:11 pm Post subject: |
|
|
Newbie
Joined: 04 Oct 2007
Posts: 3
|
Thank you very much for your reply.
I am using WMB5 and DB2 ESE 8.1 with Fixpack3.
so, i hope the external DB2 can be used for config manager and it seems its worked for me also.
But, i am getting problem during the creation of Broker.
FYI , the entire configuration is done on same machine.
The account that ,iam using for creating broker (mq,db2)is same as that of my windows login account, who ia memeber of all MB groups, mqm group and also db2admin group .
The complete exception msg that i am getting is
----------------------------------------------------------
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ 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.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP2371E: Database statement 'CREATE TABLE 120669.BROKERAAEG (BrokerUUID CHAR (1
6) FOR BIT DATA NOT NULL , ExecGroupUUID CHAR (16) FOR BIT DATA NOT NULL , ExecG
roupLabel BLOB(2147483647) NOT LOGGED NOT NULL , RetryInterval INTEGER, PubSubSe
rver INTEGER, ProcessId INTEGER, ProcessState INTEGER, DynamicState INTEGER, Dyn
amicSync INTEGER, MsgId CHAR (24) FOR BIT DATA, CntlGrpMsgId CHAR (24) FOR BIT D
ATA)' could not be executed.
A message flow node attempted to execute a database statement. However, the data
base returned an error when executing the statement 'CREATE TABLE 120669.BROKERA
AEG (BrokerUUID CHAR (16) FOR BIT DATA NOT NULL , ExecGroupUUID CHAR (16) FOR BI
T DATA NOT NULL , ExecGroupLabel BLOB(2147483647) NOT LOGGED NOT NULL , RetryInt
erval INTEGER, PubSubServer INTEGER, ProcessId INTEGER, ProcessState INTEGER, Dy
namicState INTEGER, DynamicSync INTEGER, MsgId CHAR (24) FOR BIT DATA, CntlGrpMs
gId CHAR (24) FOR BIT DATA)'.
If necessary, correct the message flow and redeploy the message broker.
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 obtaine
d from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely t
o be such things as incorrect datasource or table names. Then correct either the
database or message broker configuration.
BIP2322E: Database error: SQL State '42604'; Native Error Code '-103'; Error Tex
t '[IBM][CLI Driver][DB2/NT] SQL0103N The numeric literal "120669.BROKERAAEG" i
s not valid. SQLSTATE=42604
'.
The error has the following diagnostic information: SQL State '4
2604' SQL Native Error Code '-103' SQL Error Text '[IBM][CLI Driv
er][DB2/NT] SQL0103N The numeric literal "120669.BROKERAAEG" is not valid. SQL
STATE=42604
'
This message may be accompanied by other messages describing the effect on the m
essage broker itself. Use the reason identified in this message with the accomp
anying messages to determine the cause of the error.
BIP8070E: Exception accessing database table executing SQL statement 'CREATE TAB
LE 120669.BROKERAAEG (BrokerUUID CHAR (16) FOR BIT DATA NOT NULL , ExecGroupUUID
CHAR (16) FOR BIT DATA NOT NULL , ExecGroupLabel BLOB(2147483647) NOT LOGGED NO
T NULL , RetryInterval INTEGER, PubSubServer INTEGER, ProcessId INTEGER, Process
State INTEGER, DynamicState INTEGER, DynamicSync INTEGER, MsgId CHAR (24) FOR BI
T DATA, CntlGrpMsgId CHAR (24) FOR BIT DATA)': SQL state '-103'; exception 'ImbE
xception'.
An SQL command has failed.
Ensure that the broker's database is available. Examine the exception and SQL s
tate code to determine and correct the cause of the error.
----------------------------------------------------------------------------------
can anyone plz help me in this..its really very needed for me .
Thanks in advance |
|
| Back to top |
|
|
| poorana |
| Posted: Wed Nov 26, 2008 7:36 am Post subject: |
|
|
Newbie
Joined: 26 Nov 2008
Posts: 1
|
Hi newbee_wmb,
Even i got the same error. I created a database with db2admin user gave the following command and it works:-
mqsicreatebroker MBBROKER -i 123456 -a password -q FIRST_CONFIGMGR.queue.manager -n BROKERDSN -u db2admin -p db2admin
Here 123456 is the serviceUserId and password is the servicePassword.
Hope it works for ypou too. |
|
| Back to top |
|
|
| jasonlck |
| Posted: Thu Nov 27, 2008 7:25 pm Post subject: |
|
|
Apprentice
Joined: 06 Oct 2008
Posts: 48
Location: Singapore
|
| Did you guys try "mqsicreatedb -i <UserName> -p <Password> -e DB2" before you run the mqsicreatebroker command? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
