ADSM-L

Re: [ADSM-L] Ang: TSM for DB password expiration

2011-03-25 11:13:58
Subject: Re: [ADSM-L] Ang: TSM for DB password expiration
From: David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 25 Mar 2011 11:13:12 -0400
Are you saying that "password generate" does not work for TSM for DB?

>>> Daniel Sparrman <daniel.sparrman AT EXIST DOT SE> 3/25/2011 9:52 AM >>>
Hi David

Correct me if I'm wrong, but when the nodes password has expired, 
passwordaccess generate will not set a new password for the client. You'll have 
to set a new password for the node, and then use tdpoconf to update the stored 
password on the client machine.

Best Regards

Daniel Sparrman
-----"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> skrev: -----

Till: ADSM-L AT VM.MARIST DOT EDU
Från: David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>
Sänt av: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Datum: 03/25/2011 15:41
Ärende: TSM for DB password expiration

Has anyone had problems with TSM for DB (Oracle), aka TDPO, and password
expiration?

We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to a
TSM server at 6.2.2.0 also on AIX 5.3. We are running with password
generate.  Last night we got two ANR0425W password has expired messages
for node DBFINTEST. I assume I got two messages because the rman command
is using two channels, thus two concurrent TSM sessions.  At that point
the password should have been set to something new and life should go
on.  Instead, subsequent sessions for that node got the "ANS0282E
Password file is not available.", ie password is incorrect, message.

Any thoughts on what might be going wrong?

David Ehresman