| Author |
Message
|
| troy |
 Posted: Fri Jan 23, 2009 4:31 am Post subject: BIP1230S:The Configuration Manager's repos is not available |
 |
|
Novice
Joined: 07 Jan 2009
Posts: 20
|
Hi,
While deploying the message flow to the broker we are getting the below mentioned error.
BIP1047E: The operation could not be completed by the Configuration Manager.
The utility did not receive an expected message from the Configuration Manager within a reasonable amount of time. The cause is described as: Configuration Manager not running
when user.log is checked then i can see the following error-
]BIP1230S: The Configuration Manager's repository is not available for use
and the warning -
BIP2229E: Warning: abend file directory
Any pointer would be of great help. Please respond as soon as possible if any idea in this regard.
Thanks |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jan 23, 2009 4:38 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
So what did you check?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| troy |
| Posted: Fri Jan 23, 2009 4:42 am Post subject: |
|
|
Novice
Joined: 07 Jan 2009
Posts: 20
|
Thanks for the response.
Actually I am not able find out what is the cause of
BIP1230S: The Configuration Manager's repository is not available for use
and what can be done in this regard. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 23, 2009 4:50 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| troy wrote: |
Actually I am not able find out what is the cause of
BIP1230S: The Configuration Manager's repository is not available for use
and what can be done in this regard. |
I looked in the Info Center (http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/topic/com.ibm.etools.mft.bipmsgs.doc/ay_bip1.htm) and found this:
| Quote: |
BIP1230
The Configuration Manager's repository is not available for use.
Severity
30 : Severe error
Explanation
The Configuration Manager was not able to gain exclusive access to its internal repository. Either another process already has exclusive access to the repository (for example, if another instance of the Configuration Manager is running), or the user ID under which the Configuration Manager was started does not have the required authority to access the repository.
Response
Ensure that the Configuration Manager is not already running, and that no other process is running that may have acquired exclusive access to the repository. Also, ensure that the Configuration Manager's user ID has the required authority to access the database; the user at least needs to be a member of the mqm and mqbrkrs groups, and on Windows the user also needs to be in the Administrators group.
|
Suggested reponse has to be a good place to start; pretty much why IBM suggest it..... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| troy |
| Posted: Fri Jan 23, 2009 5:15 am Post subject: |
|
|
Novice
Joined: 07 Jan 2009
Posts: 20
|
I have checked that the userid is the part of mqm and mqbrkrs group.
But how to check the case given the the response that
"no other process is running that may have acquired exclusive access to the repository" |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 23, 2009 5:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| troy wrote: |
| I have checked that the userid is the part of mqm and mqbrkrs group. |
And an Administrator on Windows.
| troy wrote: |
But how to check the case given the the response that
"no other process is running that may have acquired exclusive access to the repository" |
Normal OS functions.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Jan 23, 2009 5:44 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
You might like to check that the database directory tree that was used to define the configmgr when it was created has not been deleted or its attributes chaned (eg to read only)
You can find that by
1) running mqsiservice on the configmgr
OR
2) on windows searching the registry.
/Steve D
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| JohnSmith |
| Posted: Wed Jun 23, 2010 4:49 am Post subject: |
|
|
Voyager
Joined: 17 Mar 2010
Posts: 86
|
| Quote: |
| The Configuration Manager was not able to gain exclusive access to its internal repository. Either another process already has exclusive access to the repository (for example, if another instance of the Configuration Manager is running) |
We are also facing the same issue, ours is AIX server with MB V 6.1, since last few hours we are getting the same error and we have tried stopping starting the whole MB package(Queue Manager, Message Broker, and Config manager) but still the same problem is visible in "mqsi.log" and config mananger is not responding(despite we are able to "grep" configuration manager process)
smdavies99 wrote:
| Quote: |
You might like to check that the database directory tree that was used to define the configmgr when it was created has not been deleted or its attributes chaned (eg to read only)
You can find that by
1) running mqsiservice on the configmgr |
I did what "smdavies" mentioned above and got the below output, now should I do with the below output?
| Quote: |
mqsiservice CMGR1
BIPv610 en GB
ucnv Console CCSID 819 dft ucnv CCSID 819
ICUW ISO-8859-1 ICUA ISO-8859-1
Install Path = /opt/IBM/mqsi/6.1
Working Path = /var/mqsi
process id = 1552410
ConfigMgr db userId = abcmqm
ConfigMgr db password =
jdbc driver name = com.ibm.db2.jcc.DB2Driver
jdbc connection name = db2
queue manager = BRK_QM
ComponentType = ConfigMgr
Fixpack capability level = (effective level 6.1.0.2) |
Plus there are 2 points that could be addressed :
1. From the error description below how we can check whether the config manager repository is hold by another process, in our AIX environment the repository would be /var/mqsi/components/CMGR1/BERNARD/log
| Quote: |
| The Configuration Manager was not able to gain exclusive access to its internal repository. Either another process already has exclusive access to the repository (for example, if another instance of the Configuration Manager is running) |
2. what else could be the problem beside the problem description given by IBM. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jun 23, 2010 5:15 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
From what you have written, it sound like something has a lock on the file
There might be a lock file lurking around from befroe a possible crash.
Or,
someone has messed up the filw access rights to the configmgr directories.
If this were happening on Linux, then I'd head for the 'lsof' & 'ps' utilities. I'm not sure if there is an equivalent tool for AIX.
Then, I'd shutdown the whole Broker infrastructure and use ps to see if there was some orphaned process lurking around. With all WMQ, Broker etc shutdown, the orpan would be much more visible.
The final things I'd ask for (and probably incur the wrath of your AIX Administrators) is a restart of the LPAR.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 23, 2010 11:01 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I'd also make sure nobody else is trying to access the derby db (configmgr repository) via any SQL tool. This db is for exclusive usage by the configmgr. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
