Author |
Message
|
Lex |
Posted: Thu Nov 30, 2006 4:24 am Post subject: Viewing ConfigManager table |
|
|
 Acolyte
Joined: 14 Nov 2006 Posts: 73
|
Hello,
I was wondering if i could see the config manager tables created when i use mqsicreateconfigmanager with the 6.0 software.
I looked in the control center of DB2 (on Windows) and i see no tables... |
|
Back to top |
|
 |
jeevan |
Posted: Thu Nov 30, 2006 4:59 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
AFAIK, Config manaer in version 6 does not use external database. It does everything in cloudescape database. |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Nov 30, 2006 5:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
The v6 ConfigMgr uses "an internal configuration repository".
If it happens, right now, to be Cloudscape/Derby, that's not something you should rely on.
Also, Cloudscape/Derby does not generally allow more than one program to access the database at a time - so you can't read the ConfigMgrs database while the ConfigMgr is running.
And you shouldn't be reading the ConfigMgrs database anyway. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Lex |
Posted: Thu Nov 30, 2006 5:26 am Post subject: |
|
|
 Acolyte
Joined: 14 Nov 2006 Posts: 73
|
Alright, so i can uninstall DB2 from my Windows server right? No use until i specified so? |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Nov 30, 2006 5:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Yes, if you only have the ConfigMgr on that machine, you do not need DB2 anymore. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
JosephGramig |
Posted: Thu Nov 30, 2006 7:28 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
Note that you can also build a broker that uses the Derby database for it as well, but that is only supported for Windows and only for test purposes.
Read the manual on how to do this if you need/want a local broker. _________________ Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
Back to top |
|
 |
wmqiadmin |
Posted: Mon Dec 04, 2006 7:00 am Post subject: |
|
|
 Disciple
Joined: 19 Jun 2005 Posts: 163 Location: epping UK
|
Hi Guys,
While deleting the broker in Broker domain in the Toolkit, toolkit was hanged so I had to kill the toolkit process, now I don’t see the Broker in the Toolkit Domain, but while creating new Broker in the Toolkit it gives error, queue manager already used by another broker.
How can I delete the original broker information from Config manager database (derby inbuilt) and create new broker in the domain? Or there any other way around?
Thanks in advance for your guidance.
wmqiadmin |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Dec 04, 2006 7:21 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Look at the configmgr api exerciser (java) delivered with the broker...
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
mqmatt |
Posted: Tue Dec 05, 2006 6:23 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
|
Back to top |
|
 |
wmqiadmin |
Posted: Tue Dec 05, 2006 7:00 am Post subject: |
|
|
 Disciple
Joined: 19 Jun 2005 Posts: 163 Location: epping UK
|
In CM proxy, I can see the broker with only its UUID and nothing under it, no execution groups nor any other property. I tried deleting Broker from Configmgr proxy this is the error i got,
Quote: |
An attempt was made to view or modify the Broker with UUID 'c57c6274-0a01-0000-0080-92c9371cf19f', but it does not exist in the Configuration Manager's repository.
If you are trying to manipulate an object immediately after submitting a request to create it, it is likely that there was a problem creating the object. An example of this is if you attempt to create a default execution group without first ensuring that the parent broker was created successfully; this error suggests that there was a problem creating the broker.
Check the Configuration Manager's logs to see why the Broker could not be found. If the object has previously been available, the receipt of this error may indicate corruption in the Configuration Manager's repository; if this is the case, you may need to use mqsirestoreconfigmgr to restore the Configuration Manager's repository, or if this is not possible, contact your IBM support center for advice., source=ConfigMgr, timestamp=Tue Dec 05 09:46:51 EST 2006}
(12/5/06 9:46:52 AM) (Log entry) {message=BIP1545E, detail=BIP1545E: Unable to find required broker document in the configuration repository.
When deploying configuration data, the document for broker 'c57c6274-0a01-0000-0080-92c9371cf19f' could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing deploy document is of type 'DeployBrokerAction'.
The broker document 'c57c6274-0a01-0000-0080-92c9371cf19f' is not available. This is an internal error. Contact your IBM support center., source=ConfigMgr, timestamp=Tue Dec 05 09:46:51 EST 2006}
(12/5/06 9:46:52 AM) (Reference property) uuid=c57c6274-0a01-0000-0080-92c9371cf19f
(12/5/06 9:46:52 AM) (Reference property) commsmessage.lastinbatch=true
(12/5/06 9:46:52 AM) (Reference property) configmanagerproxy.osname=Windows 2003
(12/5/06 9:46:52 AM) (Reference property) deployment.identifier=vmconfigmed\wadekar
(12/5/06 9:46:52 AM) (Reference property) deployment.type=deleteallegs
(12/5/06 9:46:52 AM) (Reference property) userid=wadekar
(12/5/06 9:46:52 AM) (Reference property) configmanagerproxy.hostname=vmconfigmed
(12/5/06 9:46:52 AM) (Reference property) commsmessage.configobjecttype=Broker
(12/5/06 9:46:52 AM) (Reference property) commsmessage.operationtype=deploy
(12/5/06 9:46:52 AM) (Reference property) configmanagerproxy.noeventlog=false
(12/5/06 9:46:52 AM) <---- cmp.exerciser.ExerciserAdministeredObjectListener.processActionResponse()
(12/5/06 9:46:54 AM)
(12/5/06 9:46:54 AM) DeployResult.getCompletionCode() = failure
(12/5/06 9:46:54 AM) DeployResult.getLogEntries() : BIP1712W: Broker not found
(12/5/06 9:46:54 AM) DeployResult.getLogEntries() : BIP1545E: Unable to find required broker document in the configuration repository.
(12/5/06 9:46:54 AM) DeployResult.getCompletionCodeForBroker(<Broker/c57c6274-0a01-0000-0080-92c9371cf19f>) = failure
(12/5/06 9:46:54 AM) |
Any advice on this is higly appriciated.
Thanks
wmqiadmin |
|
Back to top |
|
 |
|