| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Creating a new Broker DB issues - SQL STATE 42704 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Tungsten |
 Posted: Fri Sep 15, 2006 9:23 am Post subject: Creating a new Broker DB issues - SQL STATE 42704 |
 |
|
Newbie
Joined: 07 Dec 2005
Posts: 4
|
Folks,
Thanks in advance - this is a first attempt at installing MQ and configuring the broker.
Everything has been going fine - I've executed the commands to create a new DB (using DB2), config manager and have also set up the Queue Manager.
My problem occurs when I attempt to create the broker.. Here are the details of what I have succesfully set up (All names have been replaced):
QManager: QMANAGER
ConfigManager: CONFGMGR
DB2 DB: BROKERDB
I can confirm an ODBC data source has been established.
I am trying to create a new Broker of the name "BROKER01"
When executing the MQSI command:
C:\IBM\TOOLKIT\6.0>mqsicreatebroker BROKER01 -i First.Second -a ******** -q QMGER01 -n BROKERDB
I get the following error:
| Code: |
BIP2371E: Database statement ''CREATE TABLE First.Second.BROKERAAEG (BrokerUUID CHAR (16) FOR BIT DATA NOT NULL , ExecGroupUUID CHAR (16) FOR BIT DATA NOT NULL , ExecGroupLabel BLOB(1073741824) NOT LOGGED NOT NULL , RetryInterval INTEGER, PubSubServer INTEGER, ProcessId INTEGER, ProcessState INTEGER, DynamicState INTEGER, DynamicSync INTEGER, ProcArchitecture INTEGER, MsgId CHAR (24) FOR BIT DATA, CntlGrpMsgId CHAR (24) FOR BIT DATA)'' could not be executed.
A message flow node attempted to execute a database statement. However, the database returned an error when executing the statement ''CREATE TABLE First.Second.BROKERAAEG (BrokerUUID CHAR (16) FOR BIT DATA NOT NULL , ExecGroupUUID CHAR (16) FOR BIT DATA NOT NULL , ExecGroupLabel BLOB(1073741824) NOT LOGGED NOT NULL , RetryInterval INTEGER, PubSubServer INTEGER, ProcessId INTEGER, ProcessState INTEGER, DynamicState 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. 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 ''42704''; Native Error Code '-204'; Error Text ''[IBM][CLI Driver][DB2/NT] SQL0204N "First.Second.BROKERAAEG" is an undefined name. SQLSTATE=42704 ''.
The error has the following diagnostic information: SQL State ''42704'' SQL Native Error Code '-204' SQL Error Text ''[IBM][CLI Driver][DB2/NT] SQL0204N "First.Second.BROKERAAEG" is an undefined name. SQLSTATE=42704 ''
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.
BIP8070E: Exception accessing database table executing SQL statement 'CREATE TABLE First.Second.BROKERAAEG (BrokerUUID CHAR (16) FOR BIT DATA NOT NULL , ExecGroupUUID CHAR (16) FOR BIT DATA NOT NULL , ExecGroupLabel BLOB(1073741824) NOT LOGGED NOT NULL , RetryInterval INTEGER, PubSubServer INTEGER, ProcessId INTEGER, ProcessState INTEGER, DynamicState INTEGER, DynamicSync INTEGER, ProcArchitecture INTEGER, MsgId CHAR (24) FOR BIT DATA, CntlGrpMsgId CHAR (24) FOR BIT DATA)': SQL state '-204'; exception 'ImbException'.
An SQL command has failed.
Ensure that the broker's database is available. Examine the exception and SQL state code to determine and correct the cause of the error. |
You advice to overcome this issue would be much appreciated - I've undertakena little research, but haven't been able to turn up much in the way of overcoming this issue.
Thanks.[/code] |
|
| Back to top |
|
 |
| Tungsten |
| Posted: Tue Sep 19, 2006 6:09 am Post subject: |
|
|
Newbie
Joined: 07 Dec 2005
Posts: 4
|
For those of you, like me, who encounter this problem, I found a solution - the problem was with the service user id (first.second). If you're using a service user id that has full-stop in it, when trying to create the broker table DB2 has issues creating the scemas.
Solution: I create a new user (without the full-stop), and added it the appropriate user groups (mqm, etc). When I ran the comman again to create the broker, all good! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 19, 2006 6:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Wow.
I'd assumed "first.second" was just your way of hiding the user name...
Yeah, databases tend to use "." to separate name qualifiers - schema from table and table from field name - so trying to create a schema name with an embedded "." is going to cause problems.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
