Author |
Message
|
4integration |
Posted: Tue Mar 13, 2007 12:38 pm Post subject: Load/Unload problems |
|
|
 Disciple
Joined: 04 Sep 2006 Posts: 197 Location: Gothenburg, Sweden
|
Hello,
I have unloaded three messages with MQMON, one at 96 MB and two <500 kB. The file on disk is 206 MB
I have tried to load that file again and with MQMON I get the following:
MQPUT(MYQUEUE.OUT) failed RC(2010) Data length error.
The maximum message length is set to 104857600 bytes (which are the highest value)
When trying to use qload.exe and the command:
qload.exe -mWBRK6_DEFAULT_QUEUE_MANAGER -oMYQUEUE.OUT -fC:\mymessage.msg
I get:
QLOAD Program by Paul Clarke [ V1.3 Build:Sep 19 2006 ]
Messages Read : 1 Bytes Read : 100371280
Messages Written: 0 Bytes Written: 0
MQPUT(PLSCM.PARMA.OUT) failed RC(2102) Resource problem.
How can I solve this? _________________ Best regards
4 Integration |
|
Back to top |
|
 |
bbburson |
Posted: Tue Mar 13, 2007 1:15 pm Post subject: |
|
|
Partisan
Joined: 06 Jan 2004 Posts: 378 Location: Nowhere near a queue manager
|
Sounds like either your WMQ data or log disk is full. Look at <WMQInstallPath>\qmgrs\... and <WMQInstallPath>\log\... |
|
Back to top |
|
 |
Michael Dag |
Posted: Tue Mar 13, 2007 1:33 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
did you get the message from another qmgr?
you are using the WBRK6_DEFAULT_QUEUE_MANAGER which is default a linear log qmgr with 256 logpage size, 3 primary logs and 2 secondary logs. (=5MB logspace...)
put it back non persistent, that will save a lot of log space _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
4integration |
Posted: Tue Mar 13, 2007 2:05 pm Post subject: |
|
|
 Disciple
Joined: 04 Sep 2006 Posts: 197 Location: Gothenburg, Sweden
|
Yes, I got the messages from another qmgr.
The settings I have changed to is 256 logpage, 200 primary logs and 2 secondary. The queue is persistent.
In the log dir I have:
Code: |
C:\Program Files\IBM\WebSphere MQ\log\WBRK6_DEFAULT_QUEUE_MANAGER>ls -al
total 4
drwx------+ 3 v008789 mkpasswd 0 Oct 4 11:04 .
drwxrwx---+ 4 Administ SYSTEM 0 Oct 4 11:04 ..
d---------+ 2 v008789 mkpasswd 0 Mar 13 21:32 active
----------+ 1 v008789 mkpasswd 3184 Mar 13 20:07 amqhlctl.lfh
C:\Program Files\IBM\WebSphere MQ\log\WBRK6_DEFAULT_QUEUE_MANAGER>ls -al active
total 22550
d---------+ 2 v008789 mkpasswd 0 Mar 13 21:32 .
drwx------+ 3 v008789 mkpasswd 0 Oct 4 11:04 ..
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000000.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 20:05 S0000001.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000002.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000003.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000004.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000005.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000006.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000007.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000008.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000009.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000010.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000011.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 15:40 S0000012.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 21:32 S0000013.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 21:32 S0000014.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 21:32 S0000015.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 21:32 S0000016.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 21:32 S0000017.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 21:32 S0000018.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 21:32 S0000019.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 21:32 S0000020.LOG
----------+ 1 v008789 mkpasswd 1049600 Mar 13 21:32 S0000021.LOG
C:\Program Files\IBM\WebSphere MQ\log\WBRK6_DEFAULT_QUEUE_MANAGER> |
I will try to set it to non-persistent tomorrow _________________ Best regards
4 Integration |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Mar 13, 2007 4:39 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
The queue is not persistent. The queue has a default persistance that applications can choose to set on messages. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
4integration |
Posted: Tue Mar 13, 2007 10:32 pm Post subject: |
|
|
 Disciple
Joined: 04 Sep 2006 Posts: 197 Location: Gothenburg, Sweden
|
Sorry, but I am a bit lost...
How can I put it back on the queue in a non-persistent manner using qload.exe or MQMON? _________________ Best regards
4 Integration |
|
Back to top |
|
 |
Michael Dag |
Posted: Tue Mar 13, 2007 10:40 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
look at QLOAD's help...
or use Q (MA01) instead, also from Paul
Code: |
MQSeries Q Program by Paul Clarke [ V4.5 Build:Sep 15 2006 ]
(c) Copyright IBM Corp. 1995, 2006
Usage: Q <Optional flags as below>
[-a[dnpqRrst] Message attributes
p:Persistent,n:Non-Persisent,q:Persistence as Q,s:Allow Segmentation
d:Datagram,R:Request,r:Reply,t:Report
[-A[i|o]<value> Application Identity|Origin Data |
_________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
4integration |
Posted: Tue Mar 13, 2007 11:26 pm Post subject: |
|
|
 Disciple
Joined: 04 Sep 2006 Posts: 197 Location: Gothenburg, Sweden
|
Thanks for the fast reply..
I have looked into QLOAD's help and can not find the applicable parameter to force non-persistent...
Downloaded Q which seems very flexible and have the parameter for non-persistent but as I said in the first post the unloaded file consists of three messages and when running Q with -f gives (as it says in doc) one message per line which is not correct in this case. The -F parameter loads the whole file as one message, which is not correct either.
Any idea?
Worth to mention again, the dump file is created by MQMON. Is the formats between MQMON and Q compatible? _________________ Best regards
4 Integration |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Mar 14, 2007 2:33 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
4integration wrote: |
Worth to mention again, the dump file is created by MQMON. Is the formats between MQMON and Q compatible? |
If the dump file was created by MO71 have you tried reloading the queue using MO71 but change the direction:(file to queue)? If yes what have you tried? Did you change the commit frequency to each message? (default is 200)...
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
4integration |
Posted: Wed Mar 14, 2007 3:39 am Post subject: |
|
|
 Disciple
Joined: 04 Sep 2006 Posts: 197 Location: Gothenburg, Sweden
|
I have now been able to load the messages...
I used qload.exe as before but switched of the transactions by adding the parameter -t0
Also discovered one thing in my local MQ, the channel had the default 4 MB limit but the queue had 100 MB.
Thanks for your help _________________ Best regards
4 Integration |
|
Back to top |
|
 |
|