| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Silly mqsisetdbparms question. |
« View previous topic :: View next topic » |
| Author |
Message
|
| friedl.otto |
 Posted: Sun Feb 15, 2009 10:19 pm Post subject: Silly mqsisetdbparms question. |
 |
|
Centurion
Joined: 06 Jul 2007
Posts: 116
|
I have trawled the IBM® WebSphere® Message Broker Information
Center's entry on mqsisetdbparms, and some articles (here and here)
on MQSeries.net to try and find out whether one has to delete a DSN,
username and password entry and then create a new entry with the
same DSN and username in order to update an expired password.
The reason I am asking this, is that an Oracle password expired, and I
swiftly stopped the broker to run:
| Code: |
mqsisetdbparms <brokername> -n <DSN name> -u <username> -p <new password> |
However the Oracle account still locked out with incorrect login attempts,
the issue was solved when the Oracle account password was reset to the
original setting. So I am assuming that my command didn't "take".
_________________
Here's an idea - don't destroy semaphores unless you're certain of what you're doing!  -- Vitor |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Feb 15, 2009 10:47 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This command (mqsisetdbparms) covers all data connected DB's. If you need to change the password on the Broker's DB try mqsichangebroker 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| friedl.otto |
| Posted: Sun Feb 15, 2009 11:05 pm Post subject: |
|
|
Centurion
Joined: 06 Jul 2007
Posts: 116
|
Truly scrumptious!
Only ... given this:
| Code: |
Command options:
'brokerName' the name of the broker to change
'-i serviceUserId' the user ID that the broker should run under
'-a servicePassword' the password for the broker user ID
'-p dataSourcePassword' the password for the broker's database user ID
'-s unsQMgrName' the WebSphere MQ queue manager of the User Name Server
'-j' indicates that publish/subscribe access control is to be enabled for this broker
'-d' indicates that publish/subscribe access control is to be disabled for this broker
'-t' indicates that WebSphere MQ fastpath is to be used for this broker (not supported on all platforms)
'-n' indicates that WebSphere MQ fastpath is not to be used for this broker
'-l userLilPath' indicates where user-written 'lil' and 'jar' files are loaded from
'-g configurationTimeout' the maximum time (in seconds) to allow a broker to process a deployed message
'-k configurationDelayTimeout' the maximum time (in seconds) to allow a broker to process a minimum size deployed message
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records
'-P httpListenerPort' the port that the broker's HTTP listener uses
'-c ICU converter path' delimited list (';' in windows, ':' on unix) of paths to search for ICU converters or converter packages.
'-y ldapPrincipal' the LDAP Principal (userId)
'-z ldapCredentials' the LDAP Credentials (password)
'-x userExitPath' the directory from which the broker searches for all user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.
'-e activeUserExits' the active user exits. By default, user exits are inactive. Adding a userExit name to this list changes its default state to active for this broker. The default state can be overridden at the execution group or message flow level using the mqsichangeflowuserexits command. If a user exit name is specified and no library is found to provide that user exit when the Execution Group starts, then a BIP8860 message is written to the system log and the execution group fails to start. The separator character for the list is ':'.
|
I'm guessing the broker 'dataSourceName' will never change! 
_________________
Here's an idea - don't destroy semaphores unless you're certain of what you're doing! -- Vitor |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Feb 15, 2009 11:16 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Two points
1) It can't do any harm to deleted the DSN password/username data before applying the new password.
2) There are some cases where you can actually define the UserNamepassword in the ODBC Connection. you might like to check that this has not been done.
Also
You don't detail what platform your broker is running on. In Windows, you can test the ODBC conection with the ODBC Admin tool(via the config option).
Finally,
Once I was sure that I was using the correct password and if I was still getting the connectivity issues I would run some form of connection tracing to determine where the problem really lies.
Oh, and get your Oracle Password set to NEVER Expire..... I know in some places this is regarded as a NO-NO-Never in a million years but the last thing you want is for a production system to stop dead in its tracks due to password expiry... 
_________________
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
|
|
|
|
