Rainer...

The password is munged with the uname so the password file is not portable.
Leave the password file in /etc/security/adsm and be sure to use different
servername stanza names on either system so the file names don't clash.  Set
the password file on one system then swing the ADSM client over and set it on
the other...from then on you should be set.  You probably don't even have to
swing it over if you are leaving the ADSM executables on local disk; just copy
over the dsm.sys file to the other system (save off its dsm.sys) access the
server (dsmc -se=sysAstanza q filesp) at which point it will prompt you for the
password and set the password file /etc/security/adsm/SYSASTANZA on system B.
Replace system B's dsm.sys and you should be set.

Cheers...
Bruce

Rainer Holzinger wrote:

> Hi all,
>
> I'm running an ADSM server 3.1.1.5 under AIX 4.2.1 on SP2 silver node. We
> have SAP R/3 with informix db and using the X/Open interface for backing up
> the informix logs via onbar. The SAP R/3 dbserver and 3 application servers
> are on SP2 silver nodes too.
>
> Now we have setup a HACMP cluster with the SAP R/3 databse server and a
> "big" application server in. The application server will takeover the db
> server if it goes down for whatever circumstances. Last weekwend we tested
> serveral scenarios successfully and it works fine.
>
> But (there's always a but) one problem we were not able to solve. When the
> application server has taken over the SAP R/3 db server and the adsm client
> scheduler is being started (the adsm client at the application sevrver is
> now running with the adsm client name of the SAP R/3 db server ) we're
> receiving msg:
>
>      ANR042W Session x for node node_name (AIX) refused - invalid password
> submitted.
>
> Let me say that we are using passwordaccess generate and that the SAP R/3
> db servers ADSM client password file (which is by default in
> /etc/security/adsm) is located on a "shared disk" which has been taken over
> too.  So it looks like that within the password file there must be
> something more than the node id and an expiration date. There must be
> something in which relates to the physical machine on which it is runnung.
> When the above message has been displayed, we noticed, that the password
> file has been erased too. This means that the SAP R/3 db server will get
> into trouble too, when the R/3 application is going back to the original
> SAP R/3 db server.
>
> Does anyone of you have experiences in taking over an ADSM AIX client to
> another node and how to handle this password problem?
>
> TIA
> Rainer

--
Bruce Elrick, Ph.D.
Bruce Elrick, Ph.D.
mailto:belrick AT home DOT com
http://members.home.net/belrick/