| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Migrating mqsisetdbparms from V6.1 to V7 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Mirage |
 Posted: Thu Nov 03, 2011 2:17 pm Post subject: Migrating mqsisetdbparms from V6.1 to V7 |
 |
|
Apprentice
Joined: 30 Nov 2004
Posts: 44
Location: IL
|
Hi,
We are currently working on MB Migration from V6.1.0.7 to MB 7, this is a staged migration and not an in-place migration. So, we've prepared the MB V7 environments in parallel on new servers and provided them for the development teams for deploying and testing the migrated V7 code.
Recently, the development team found out that they do not have the userid/password details for some of the Database DSN's, and asked us for any help in migrating the existing setup from V6 to V7 servers.
so, we started looking at our options to migrate these entries. One option was to see if we can use "mqsimigratecomponents -1" command to migrate the file system and entries to V7 format.
I was thnking maybe if we can backup and restore the V6 broker on one of the Lab servers, where V6 and V7 are installed, and we'll run this command to migrate the entries to V7 format, then use those entries on the V7 server
But, then the key used for encryption/decryption by V6 broker is going to be different from V7. We'll have to move this 'key' info also from V6 to V7, right? I couldn't find where this info is stored in Broker file system.
I wish IBM has just provided a 'list' command for displaying these entries, just like the 'set' command.
Please suggest if you have any ideas.
Thanks. |
|
| Back to top |
|
 |
| mapa |
| Posted: Thu Nov 03, 2011 3:41 pm Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
I'm facing the same problem and wish there was such a command for listing the settings.
However there is none such option or command so you really need to get those user+passwords for your datasources. |
|
| Back to top |
|
|
| Mirage |
| Posted: Thu Nov 03, 2011 4:44 pm Post subject: |
|
|
Apprentice
Joined: 30 Nov 2004
Posts: 44
Location: IL
|
I think we are not the only ones looking for this option, when I searched the site, found couple of threads from 2010 with similar needs. 
They submitted a feature request to IBM also as per the thread, I wonder what happened to the request.
I think it was mqjeff or Peter.
Any IBMers in here, from Hursley(matt?) do you have any suggestions, please
Thanks |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Nov 03, 2011 10:52 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
On a Unix/Linux platform, the DSN password is held in encrypted format in a file. Search for the DSN name and you will see two files in the directory underneath. One is the user and the other is the password.
You could try defining the DSN with a known bad password and then replace the password file with the one from the old broker.
Then you can test it with the mqsicvp command.
THIS IS A POSSIBLE SHORT TERM FIX ONLY
You really need to get the passwords on the DB account reset OR get a new account setup and then create/grant synonyms to allow access to the DB objects from the new account.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
