| Author |
Message
|
| bkRaju |
 Posted: Sat Oct 03, 2009 5:00 am Post subject: AMQ5615: Default objects cannot be created |
 |
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
Hi All,
I am getting below error when I am trying to start Queue managger
strmqm QM1
WebSphere MQ queue manager 'QM1' starting.
AMQ5615: Default objects cannot be created: CompCode = 2 Reason = 2059.
AMQ5615: Default objects cannot be created: CompCode = 2 Reason = 2059
Could you please let me know what could be the issue and resolution. |
|
| Back to top |
|
 |
| harish_td |
| Posted: Sat Oct 03, 2009 5:51 am Post subject: |
|
|
Master
Joined: 13 Feb 2006
Posts: 236
|
What does the helpful AMQERR0*.LOG files state?
Are there any FDC's generated when you execute strmqm?
Is the file system that you initially created your queue manager still present or accessible by the user id that you are using to execute strmqm.
Have you ever been able to start this queue manager in the past?
If the default system objects are corrupted then you can use the below command to re-create the default objects.
But my guess is that your problem is not so superficial. |
|
| Back to top |
|
|
| bkRaju |
| Posted: Sat Oct 03, 2009 6:13 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
the log file AMQERR0*.LOG are not getting updated.
yes, fdcs are getting generated when I issue strmqm.
yes. the files are accesbile for user id mqm
yes, I was able to start these queue managers in my past.
I have already tried using strmqm -c QM1 but throwing same error.
Snippet of FDC :
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday October 03 07:04:12 MST 2009 |
| Host Name :- Myserver |
| PIDS :- 5724H7201 |
| LVLS :- 6.0.2.3 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XY019008 |
| Application Name :- MQM |
| Component :- xufOpenIniEdit |
| SCCS Info :- lib/cs/unix/amqxufrx.c, 1.55.1.1 |
| Line Number :- 1617 |
| Build Date :- Jan 23 2008 |
| CMVC level :- p600-203-080123 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000007 (mqm) |
| Program Name :- amqzxma0_nd |
| Addressing mode :- 64-bit |
| Process :- 197480 |
| Thread :- 1 |
| QueueManager :- QM1 |
| ConnId(2) QM :- 2 |
| Last HQC :- 2.0.0-604160 |
| Last HSHMEMB :- 2.0.0-711832 |
| Major Errorcode :- xecU_E_INI_FILE_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6162 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6162: An error has occurred reading an INI file. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
Please suggest |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Oct 03, 2009 6:15 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Probe Description :- AMQ6162: An error has occurred reading an INI file.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Oct 03, 2009 6:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bkRaju wrote: |
| Please suggest |
Well this:
| bkRaju wrote: |
| Probe Description :- AMQ6162: An error has occurred reading an INI file. |
|
looks like a clue to me.
My suggestions:
-The ini file permissions are wrong
-The ini file has been edited (perhaps to change the log parameters) and it's been done badly.
Could be something else of course.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bkRaju |
| Posted: Sat Oct 03, 2009 6:19 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
From AMQERROR.Log
AMQ6184: An internal WebSphere MQ error has occurred on queue manager QM1.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 200692.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 807 --------------------------------------------------------
from this information any idea? |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Oct 03, 2009 6:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bkRaju wrote: |
| from this information any idea? |
Yes - that's telling you an FDC file has been generated. 
I stand by my previous comments.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bkRaju |
| Posted: Sat Oct 03, 2009 6:23 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
| Same issue is happening to all Queue managers on my server. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Oct 03, 2009 6:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bkRaju wrote: |
| Same issue is happening to all Queue managers on my server. |
Really? It's like there's only one ini file for all the queue managers.........
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bkRaju |
| Posted: Sat Oct 03, 2009 6:35 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
amqhlctl.lfh--->I could see this file is zeroed.
is this causing the issue? and when it will be modified? and what it's importance? |
|
| Back to top |
|
|
| bkRaju |
| Posted: Sat Oct 03, 2009 6:38 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
| no, Different ini files for different queue managers |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Oct 03, 2009 6:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Do not touch that file.
Look at mqs.ini.
Make sure, for example, that you're running commands as a member of the mqm group. |
|
| Back to top |
|
|
| bkRaju |
| Posted: Sat Oct 03, 2009 7:04 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
id
uid=7(mqm) gid=12(mqm) groups=201(mqbrkrs)
What I have to check in mqs.ini file? |
|
| Back to top |
|
|
| bkRaju |
| Posted: Sat Oct 03, 2009 7:11 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Oct 03, 2009 7:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bkRaju wrote: |
| Do you need any inputs? |
No, but you clearly do.
Try creating a new manager, then compare & contrast the files.
If the create doesn't work, that will be another clue to your problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
