| Author |
Message
|
| K_A |
 Posted: Tue Apr 10, 2007 2:58 am Post subject: Errorr settings up default configuration |
 |
|
Apprentice
Joined: 10 Nov 2004
Posts: 32
|
Hi,
I have installed WMQ 6, DB2 8.2 and WBIMB 6.0 + the toolkit for WBIMB 6. It all went OK.
The problem is when I am about to set up a default broker, from the Toolkit wizard. It fails in the create database step, according to the following:
mqsicreatedb DEFBKDB6 -i MyUserID -a MyPwd
BIP9816I: Multiple Database types detected, defaulting to 'DB2'.
BIP9809I: Creating DB2 Database 'DEFBKDB6', this may take a while.
BIP9835E: The DB2 batch command failed with the error code SQLSTATE=42705.
BIP9835E: The DB2 batch command failed with the error code SQLSTATE=42705.
The database 'DEFBKDB6' could not be created/deleted. The error code SQLSTATE=42705 was returned from the DB2 batch command. All preceding steps have been rolled back.
Fix the problem indicated by the SQLSTATE code and reissue the command.
Anyone?
Rgds
K_A |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Apr 10, 2007 3:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
SQLSTATE 42705 typically relates to a database not found error. I'd have a look through the DB2 logs, also check that whatever user id is doing the install has all the permissions it needs within DB2.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| K_A |
| Posted: Tue Apr 10, 2007 7:00 am Post subject: |
|
|
Apprentice
Joined: 10 Nov 2004
Posts: 32
|
The things is that the database not-found cannot be the cause, sinc the command actually is to create the db.
I'm not really a DB2 expert. At what DB2-log can I get more details? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 10, 2007 7:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| K_A wrote: |
The things is that the database not-found cannot be the cause, sinc the command actually is to create the db.
|
That's why I said typically. I suspect there's something else in the DB2 setup that it's looking for and not finding.
| K_A wrote: |
I'm not really a DB2 expert. At what DB2-log can I get more details? |
My first reaction in your position would be to grab a DB2 DBA, drag him to your screen, point at your error and shout "Fix it!". It's unlikely to be an MQ issue. 
Failing that, try to create the database from a DB2 command prompt, using the same user id. See if it works like that, and if not record any errors that the process throws up.
Finally, you'll find the DB2 log in the data folder associated with your installation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Mensch |
| Posted: Tue Apr 10, 2007 5:13 pm Post subject: |
|
|
Disciple
Joined: 17 Jul 2005
Posts: 166
|
Hi K_A,
I think it is a user-id problem.
User-ID that you are using to create database is not authorised one.
is it your domain id or local id?
_________________
Thanks and Regards ,
Mensch |
|
| Back to top |
|
|
| K_A |
| Posted: Thu Apr 12, 2007 1:50 am Post subject: |
|
|
Apprentice
Joined: 10 Nov 2004
Posts: 32
|
Hi
I have tried both local "administrator" and the userID, like 'domain\myUserID'. Both these ones have full authority on my machine. Still it fails.
It is very difficult to pu this under the nose of a DBA, since it is the "mqsicreatedb " call that fails. I cannot see exactly which database call itt issues. It's all hidden ...
Can you tell me axactly which user groups does my userID need to be part of?
Is it so that I need to install a fixpack or anything? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 12, 2007 2:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| K_A wrote: |
It is very difficult to pu this under the nose of a DBA, since it is the "mqsicreatedb " call that fails. I cannot see exactly which database call itt issues. It's all hidden ...
|
Maybe I just have a bad attitude but in your position my reasoning would be as follows:
1) I've supplied a valid user id and password
2) This combination is authorised to create databases
3) I've issued a command to create a database from this user id
4) I've received an error code which is clearly DB2 in nature
5) The DB2 DBA needs to fix the DB2 problem which is preventing an authorised user performing an action he's authorised to do.
Sorted. 
Despite the process being "hidden", the outcome required is clear. If the id is authorised properly, it should be able to perform all the steps necessary to create and own the database. Something within DB2 is preventing this.
I'm not aware of any issues surrounding this that are solved by a fix pack. It also sounds too database like to be an MQ problem, and by your own admission you're not a DB2 person. IMHO you're better off seeking local help & resource than thrashing about applying patches.
Though it might help of course. Never can tell.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
