| Author |
Message
|
| mgm |
 Posted: Tue Dec 18, 2007 1:00 pm Post subject: mqsicreatebroker or mqsideletebroker produce IOT/Abort trap |
 |
|
Apprentice
Joined: 14 Dec 2007
Posts: 48
Location: anywhere
|
Hi All,
I have MB 6.1 installed on Aix 5.3
I am getting following error when trying to create/delete broker
mqsicreatebroker .............
AMQ8110: MQSeries queue manager already exists.
MQSeries queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
IOT/Abort trap(coredump)
mqsideletebroker test
Websphere MQ queue manager runing.
IOT/Abort trap(coredump)
Any help is highly appreciated |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Tue Dec 18, 2007 8:22 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
 us to u..
provide some more error info.. may be read the core n see if something can be figured out....
_________________
Cheers |
|
| Back to top |
|
|
| AndreasMartens |
| Posted: Wed Dec 19, 2007 8:10 am Post subject: |
|
|
Acolyte
Joined: 30 Jan 2006
Posts: 65
Location: Hursley, UK
|
Further to AkankshA's reply, the following pieces of information are helpful:
1. `mqsiservice -v` output (this checks some basic functionality and setup)
2. your odbc.ini (pointed to by $ODBCINI)
3. Software levels of both your AIX config and database config.
If the above information isn't sufficient then the next step is trace  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 19, 2007 8:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Heap/Core dumps should always be followed by PMRs...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rknox |
| Posted: Wed Dec 19, 2007 10:53 am Post subject: |
|
|
Apprentice
Joined: 28 Aug 2007
Posts: 34
|
| mgm, it appears that you and I have similar issues. I had a C++ problem and you also had the same issue. I am also getting the core dump problem when trying to do the mqsimigratecomponents command. I currently have a PMR open with IBM. You have to be sure to read the install doc to make sure your LIBPATH variables are set correctly and the ODBCINI variable is set as the doc states. I have read the doc thoroughly and IBM has confirmed I have everything set correctly, but I am still getting the core dump. |
|
| Back to top |
|
|
| mgm |
| Posted: Thu Dec 20, 2007 4:36 am Post subject: |
|
|
Apprentice
Joined: 14 Dec 2007
Posts: 48
Location: anywhere
|
Thanks for all who replied.
My enviroment is
AIX 5.3 maintenance level 6
DB 2 FP 15 . 64 bit DB2 instance
MB 6.1
I have also checked the documentation and I found nothing relevant.
I added to the user profile the follwing lines as I use only 64 instance.
export ODBCINI=/var/mqm/odbc/odbc64.ini
export LIBPATH=/home/db2inst1/sqllib/lib64:$LIBPATH
Not sure if anything else is required.
Special thanks for rknox, and I hope I got a resolution to your issue and mine as well so I can follw you as I did lat time.  |
|
| Back to top |
|
|
| mgm |
| Posted: Sun Dec 23, 2007 4:48 am Post subject: Any help |
|
|
Apprentice
Joined: 14 Dec 2007
Posts: 48
Location: anywhere
|
| any help or feedback on my reported issue ? |
|
| Back to top |
|
|
| samar14 |
| Posted: Tue Dec 25, 2007 11:08 am Post subject: |
|
|
Novice
Joined: 30 Nov 2007
Posts: 17
|
Edit the odbc64.ini file to remove the comment from [ODBC] stanza
[ODBC]
Trace=0 # To turn on ODBC trace set = 1
change the above to -
[ODBC]
Trace=0
(Notice that the comment "# To turn on ODBC trace set = 1" has been removed).
This should solve the problem. |
|
| Back to top |
|
|
| mgm |
| Posted: Tue Dec 25, 2007 12:10 pm Post subject: |
|
|
Apprentice
Joined: 14 Dec 2007
Posts: 48
Location: anywhere
|
| It didn't work after the change as well |
|
| Back to top |
|
|
| mgm |
| Posted: Fri Dec 28, 2007 3:00 pm Post subject: The problem has been fixed. |
|
|
Apprentice
Joined: 14 Dec 2007
Posts: 48
Location: anywhere
|
The problem has been fixed.
If you are interested, I analyzed all steps and reviewed all input/output files and finally it was due line feed mismatch between Unix and Windows platforms.Very simple ,isn't it ?  |
|
| Back to top |
|
|
| samar14 |
| Posted: Mon Dec 31, 2007 10:51 pm Post subject: |
|
|
Novice
Joined: 30 Nov 2007
Posts: 17
|
Thanks , and its really strange to see the linefeed being the root cause.
Btw, can you explain a bit more on what did you do to correct the problem. Have you also removed the comment from the line
Trace=0 # To turn on ODBC trace set = 1
?
I did face the same coredump issue and problem was resolved by
just removing the above comment. Hence more curious to know you solution in detail. |
|
| Back to top |
|
|
| mgm |
| Posted: Tue Jan 01, 2008 4:24 am Post subject: |
|
|
Apprentice
Joined: 14 Dec 2007
Posts: 48
Location: anywhere
|
Actually I have edited the odbc.ini once using wordpad on Windows. I assumed my ftp tool should take care of that.
I opend the odbc.ini on the AIX machine and it was normal using the graphical editor but when I opend it using vi command I saw ^M at each line end. I used the vi editor to clear that and it worked fine.
I have removed also removed the comment from the line
Trace=0 # To turn on ODBC trace set = 1.
Last edited by mgm on Tue Jan 01, 2008 12:18 pm; edited 1 time in total |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 01, 2008 11:57 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mgm wrote: |
Actually I have edited the odbc.ini once using wordpad on Windows. I assumed my ftp tool should take care of that.
I opend the odbc.ini on the AIX machine and it was normal using the graphical editor but when I opend it using vi command I saw ^M at each line end. I used the vi editor to clear that and it worked fine.
I have removed the also removed the comment from the line
Trace=0 # To turn on ODBC trace set = 1. |
Bet you did your ftp in binary instead of text mode...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mgm |
| Posted: Tue Jan 01, 2008 12:07 pm Post subject: |
|
|
Apprentice
Joined: 14 Dec 2007
Posts: 48
Location: anywhere
|
| The ftp client send option was set to Auto and the sent file is .ini which is supposed to be sent as ASCII. but for some reason it didn't |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 01, 2008 12:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mgm wrote: |
| The ftp client send option was set to Auto and the sent file is .ini which is supposed to be sent as ASCII. but for some reason it didn't |
.ini is not a recognized text file (by default) for ftp. .txt might have been. You would have needed to specify the transfer mode instead of letting the program choose. I believe the default if the extension is not recognized or in the recognized list is binary...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
