| Author |
Message
|
| sathya532k |
 Posted: Fri May 21, 2010 1:19 am Post subject: Migration help on MQ v6.0.2.6 to v7.0.1.1 ( solaris 10 ) |
 |
|
Novice
Joined: 04 Dec 2006
Posts: 15
|
Hi All,
I need help on migrating my qm running on v6.0.2.6 to 7.0.1.1.
Following are steps undergone during migration.
First backedup the MQ FS /var/mqm from 6.0.2.6 and then removed the mq 6.0.2.6 package.
after successfull reomval, installed the mq v7.0.1.1 with fix pack.
Didn't have any exception during the v7 install and qmanager and its objects were succefully populated to new version.
Two we observered the behaviour of qmanager running on Version 7, dont find an issue.
When i frist received an alert script stating the FS is full, we started to debugging the issue.
When check the error directory, its full of FDC's. checkd the probe id. in the ibm support site it says, the FDC is generated due the default objects behaviour and asked us to create a default objects using strmqm -c <qm>
But we failed in that attempt, it shows some a replaced and some are failed.
For the testing purpose i did created a new qm on v7.0.1.1, the newly created QM does not have any problem and didnt throught FDC..
So i request for Help to identify the problem on the migrated QM(6.0.2.6) to QM(7.0.1.1). since i only testing it on a dev env. we didnt have outage.
We planning to migrate all our mq server to v7 from v6
any help is very apprieciated.
[/b] |
|
| Back to top |
|
 |
| wschutz |
| Posted: Fri May 21, 2010 1:33 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
1. Did you open a PMR with IBM ?
2.
| Quote: |
But we failed in that attempt, it shows some a replaced and some are failed.
|
What error did you get?
3. What was the probe ID what said you needed the "-c" on strmqm?
4. Just to be on the safe side, you should also use "saveqmgr" (MS03) before starting the migration (and then on a regular basis thereafter).
-w
_________________
-wayne |
|
| Back to top |
|
|
| sathya532k |
| Posted: Fri May 21, 2010 3:05 am Post subject: Hi |
|
|
Novice
Joined: 04 Dec 2006
Posts: 15
|
i did open a PMR with IBM and they gave me a tech note for the PROBE ID : ZX136011, according to the tech note i issue the command strmqm -c and it failed and i reported back to them. but didnt get a reply and one fine day they asked me to install the fix pack 7.0.1.1 and after that also we are getting the same FDC getting generated.
Note : i have TWO qm running on the same server.
i have the qm backup, before migrating i do the backup at first then do neccessarry upgrades.
so reverted back to 6.0.2.6 and i have one more test server with same scenario for testig the defects..
with respect to the FDC i dont see any bad behaviour, but my FS is getting filled very quickly.
Below is the error
0 created. 39 replaced. 29 failed. |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri May 21, 2010 3:21 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Do you have SYSTEM.BROKER.* queues on that QM? What happens if you disable PUB/SUB on that QM?
_________________
-wayne |
|
| Back to top |
|
|
| sathya532k |
| Posted: Fri May 21, 2010 3:39 am Post subject: |
|
|
Novice
Joined: 04 Dec 2006
Posts: 15
|
| dont have the SYSTEM.BROEKER* QUEUES in my qm. Also i disabled the PSNODE in mq v7...still we are getting the exception |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri May 21, 2010 4:22 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
innaresting .... is the FS full when you run the "strmqm -c"? What happens if you try creating those queues by hand (I assume you have them on the "new" qmgr).
_________________
-wayne |
|
| Back to top |
|
|
| sathya532k |
| Posted: Fri May 21, 2010 4:27 am Post subject: |
|
|
Novice
Joined: 04 Dec 2006
Posts: 15
|
FS is 25% when i run the cmd strmqm -c and and i didnt tried to create one manully. Instead i did compress the system queues from the another qm running version and copied and tried again. at the time it got failed
So do you suggest to create one manually... |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri May 21, 2010 4:32 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
don't know that I will help, but it can't hurt.
_________________
-wayne |
|
| Back to top |
|
|
| sathya532k |
| Posted: Fri May 21, 2010 4:42 am Post subject: |
|
|
Novice
Joined: 04 Dec 2006
Posts: 15
|
| tried and not helpfull... |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri May 21, 2010 8:03 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I have no idea if it will help, but if you are building something new, why not go with the latest version 7.0.1.2? Lots of fixes in 7.0.1.2.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue May 25, 2010 2:12 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
All,
I working with a customer who has an open PMR related to an issue with Java and security exits.
If BOTH client-side and server-side are v7.0.1.0 or higher, then Java/J2EE MQ libraries using a client-side security exut hang (forever) with a queue manager running v7.0.1.0 or higher when the server-side security exit closes the channel for any reason.
Note: Native and .Net at v7.0.1.0 or higher seems to be fine using security exits.
The first eFix was not completely effective. Today I received another eFix that I need to test.
Food for thought.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
