| Author |
Message
|
| venu.majji |
 Posted: Tue Jul 06, 2010 2:00 am Post subject: Problem After Upgarding to MQ V7 |
 |
|
Newbie
Joined: 06 Jul 2010
Posts: 4
|
Hi ,
I have recently upgraded MQ from 6.0.2.8 to 7.0.1.0 on Solaris after the installation at the time of creation of default objects it is not able to create some default objects , hence leading in creation of FDC's. And this is happening only if the solaris box is having multiple Queue mangers. If its a single queue manger the problem does not exists .
Please some help me out in this |
|
| Back to top |
|
 |
| ramires |
| Posted: Tue Jul 06, 2010 2:23 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
| You need to give the forum more information: what is the problem, what you do/did to solve it, the fdc's generated, the errors log. |
|
| Back to top |
|
|
| venu.majji |
| Posted: Tue Jul 06, 2010 2:32 am Post subject: |
|
|
Newbie
Joined: 06 Jul 2010
Posts: 4
|
i tried to create the missing mq objects manually but it was failing This is the error i am geting wen i am trying to create the missing objects
DEFINE QLOCAL (SYSTEM.ADMIN.CONFIG.EVENT)
1 : DEFINE QLOCAL (SYSTEM.ADMIN.CONFIG.EVENT)
AMQ8101: WebSphere MQ error (7041) has occurred.
end
2 : end
One MQSC command read.
No commands have a syntax error.
One valid MQSC command could not be processed. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 06, 2010 2:40 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
stop the qmgr
strmqm -c QMGRNAME
strmqm QMGRNAME
This should fix any problems with default objects, or create some FDCs.
In that case you will need to work the FDC's.
Are you sure the file system has all the right permissions / ownership? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Jul 06, 2010 2:57 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Alternatively create the object specifying every parameter (i.e. using the command saved from MS03 or MO71 export).
First create the default objects this way, then the other objects.
You can't create a local queue without SYSTEM.DEFAULT.LOCAL.QUEUE existing unless you do so with all parameters specified (and therefore none defaulted). |
|
| Back to top |
|
|
| venu.majji |
| Posted: Tue Jul 06, 2010 3:04 am Post subject: |
|
|
Newbie
Joined: 06 Jul 2010
Posts: 4
|
The file sstem has all the permissions that are required . The SYSTEM.DEFAULT.LOCAL.QUEUE is already created , there is problem with some system Queues like
SYSTEM!BROKER!DEFAULT!STREAM
SYSTEM!BROKER!CONTROL!QUEUE
SYSTEM!BROKER!ADMIN!STREAM |
|
| Back to top |
|
|
| ramires |
| Posted: Tue Jul 06, 2010 3:37 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
| venu.majji wrote: |
AMQ8101: WebSphere MQ error (7041) has occurred.
|
I saw this error before, when the Q file can't be created. Check qmgr file structure, you may have a directory with the name qmgr is trying to create for the queue you are defining.
Regards |
|
| Back to top |
|
|
| venu.majji |
| Posted: Tue Jul 06, 2010 5:25 am Post subject: |
|
|
Newbie
Joined: 06 Jul 2010
Posts: 4
|
| yes i could find a directory with that name .... But how come the directory get created?? These system broker queues are the features of MQV7 . So hw come they were created before |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jul 06, 2010 6:38 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| But how come the directory get created?? |
Object names that would conflict with filesystem naming rules are transformed. Dots are transformed to !, for example.
_________________
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 |
|
|
| ramires |
| Posted: Tue Jul 06, 2010 6:57 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
| bruce2359 wrote: |
| Object names that would conflict with filesystem naming rules are transformed. Dots are transformed to !, for example. |
I think this isn't always true. For example, if there is a directory called X and inside it there is a file called Q, defining a queue with the name X will fail.
Regards |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jul 06, 2010 7:24 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I think this isn't always true. For example, if there is a directory called X and inside it there is a file called Q, defining a queue with the name X will fail. |
You think? Demonstrate this, and post your results here.
You can name an mq object anything you want using the allowable characters (defined in the WMQ APR and APG manuals.
The qmgr will create the appropriate file in the filesystem - transforming (if necessary) the name you provided into a name that conforms to the filesystem rules for the platform. This transformation process is documented in the manuals, as well.
The process of creating the object includes the qmgr creating the X folder/directory, and the lower-case q file in the filesystem. The q file is the contents of the queue called X.
_________________
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 |
|
|
| ramires |
| Posted: Tue Jul 06, 2010 7:39 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
You can try, but here it goes:
In a dos window:
D:\IBM\WMQ\Qmgrs\QMC04\queues>md ABC
D:\IBM\WMQ\Qmgrs\QMC04\queues>cd ABC
D:\IBM\WMQ\Qmgrs\QMC04\queues\ABC>dir
Volume in drive D is Local Disk
Volume Serial Number is F4EE-23EA
Directory of D:\IBM\WMQ\Qmgrs\QMC04\queues\ABC
07/06/2010 04:31 PM <DIR> .
07/06/2010 04:31 PM <DIR> ..
0 File(s) 0 bytes
D:\IBM\WMQ\Qmgrs\QMC04\queues\ABC>touch Q
D:\IBM\WMQ\Qmgrs\QMC04\queues\ABC>dir
Volume in drive D is Local Disk
Volume Serial Number is F4EE-23EA
Directory of D:\IBM\WMQ\Qmgrs\QMC04\queues\ABC
07/06/2010 04:35 PM <DIR> .
07/06/2010 04:35 PM <DIR> ..
07/06/2010 04:35 PM 0 Q
now start queue manager QMC04
D:\IBM\WMQ\Qmgrs\QMC04\queues\ABC>strmqm QMC04
WebSphere MQ queue manager 'QMC04' starting.
5 log records accessed on queue manager 'QMC04' during the log replay phase.
Log replay for queue manager 'QMC04' complete.
Transaction manager state recovered for queue manager 'QMC04'.
WebSphere MQ queue manager 'QMC04' started.
D:\IBM\WMQ\Qmgrs\QMC04\queues\ABC>echo def qlocal(ABC) | runmqsc QMC04
5724-H72 (C) Copyright IBM Corp. 1994, 2009. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QMC04.
1 : def qlocal(ABC)
AMQ8101: WebSphere MQ error (7041) has occurred.
One MQSC command read.
No commands have a syntax error.
One valid MQSC command could not be processed.
If I remove the file "Q " from directory ABC I can do the define with success. MQ is 7.0.1
Regards |
|
| Back to top |
|
|
| ramires |
| Posted: Tue Jul 06, 2010 8:01 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
In fact, 7041 is object already exists.
C:\mqrc AMQ7041
...
MESSAGE:
Object already exists.
EXPLANATION:
A Define Object operation was performed, but the name selected for the object
is already in use by an object that is unknown to WebSphere MQ. The object name
selected by MQ was <insert one>, in directory <insert two>, of object type
<insert three>.
ACTION:
Remove the conflicting object from the MQ system, then try the operation again.
Regards |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 06, 2010 1:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
In short:
DO NOT MESS with the MQ file system. Let MQ handle it.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
