MQSeries.net :: View topic

Raman Kathpalia · Posted: Thu Aug 20, 2015 8:17 am Post subject:

My Lab env:

Two CentOS 6.6 VMs(cloned but having separate IP and can ping each other) running on common VMWare hypervisor with x86_64 arch
MQ version is same, MQ v8002 (trial) as well as everything else since VMs are cloned
Trying to create DR env as documented in IBM infocenter: https://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.con.doc/q018580_.htm

VM1 is primary and VM2 is acting as DR in this experiment. All msgs are persistent.

1.) VM1 - >
- create qmgr BOB (crtmqm -lf 4096 -ll -lp 2 -ls 2 BOB), strmqm BOB, create queues (Q1 and Q2), loaded few 1000 msg in both
queues and then endmqm BOB.
- Tar qmgr data and qmgr log dir. scp over to VM2
- started BOB after that.

2.) On VM2 - >
- create qmgr BOB with exact same attributes as qmgr BOB on VM1.
- Never started BOB.
- Deleted qmgr data and log dir. Import qmgr data and log dir from VM1. untar it in it's usual places on VM2.
- Replay copied log extents (strmqm -r BOB)

#qm.ini for BOB are identical on VM1 and VM2.

3.) After that, starting regular update (without stopping BOB on VM1):
- on VM1,
- BOB is running . Cleared and Loaded existing queues Q1 and Q2 further and created 2 more queues (Q3 and Q4) and loaded them as well.
- few more log extents gets created.
- run rcdmqimg -l -m BOB -t all \*
- reset qmgr type(advancelog)
- Copy all logs up to but not including current log file and rsync them to VM2
- run ms62 program on VM1 and zip the unwanted S* log files

On VM2,
- play logs forward as new log extents received. (strmqm -r qmgrname)

4.) Repeat step 3.) (But not the creation of Q3 and Q4 again)
5.) Repeat step 3.) (But not the creation of Q3 and Q4 again)

6.) At this point, On VM2, activate BOB. strmqm BOB. runmqsc BOB to see what's in there:
- I found only queues Q1 and Q2 (with exact same # messages as Q1 and Q2 on BOB at VM1 which is what I expected)
- I do not see queues Q3 and Q4

Is this a known behaviour not to see MQ objects created on DR during update process(in my case Q3 and Q4) or should I be seeing Q3 and Q4 as well since they are in log files transferred from VM1? (On VM1, I saw Q3 and Q4 getting dumped into logs when I ran rcdmqimg against BOB)

On VM2, Upon executing, rcrmqobj -m BOB -t all \* ; I'm still not able to see queues Q3 and Q4
Am I doing something wrong or is it a known behaviour?

Infocenter doesn't mentions anything on this part. or have overlooked maybe?

Now, experimenting further :

7.)
- On VM2, endmqm BOB. dltmqm BOB. crtmqm BOB (exact same attributes as VM1). Delete qmgr dir and log dir.
- On VM1, endmqm BOB, Tar qmgr data and log dir. scp over to VM2.
- On VM2, untar those dir in right places. Run strmqm -r BOB. activate BOB. strmqm BOB. runmqsc BOB and I see all 4 queues
with correct # of msgs.

Huh! Do I have to stop primary qmgr everytime and take a tar dump when I create new objects on primary?