ADSM-L

need different node name for dfs & api clients to coexist?

1999-02-10 20:31:00
Subject: need different node name for dfs & api clients to coexist?
From: Hilton Tina <HiltonT AT TCE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
Date: Wednesday, February 10, 1999 20:31
>ADSM support finally called and said the only way to make this work is to
>register a separate node for either the dfs or SQL-Backtrack client.  I
>really don't want to do that.  I shouldn't have to pay $200 to IBM for
>another client license since these clients all worked fine in version 2.
>
>Can anyone out there confirm this is true?  The support guy didn't know
that
>it changed from version 2, but he seemed sure that it would not work with
>version 3.
>
>> -----Original Message-----
>> From: Hilton Tina [SMTP:HiltonT AT TCE DOT COM]
>> Sent: Wednesday, February 10, 1999 10:21 AM
>> To:   ADSM-L AT VM.MARIST DOT EDU
>> Subject:      coexistence of b/a client, dfs b/a client, and SQL
Backtrack
>>
>> The client is at version 3.1.20.6, with password access generate.  The
old
>> node is AIX 4.1.5.  The new node is AIX 4.3.1.
>>
>> Previously, I had a node that used the regular backup/archive client, the
>> dfs client, and SQL Backtrack for Oracle.  Under ADSM version 2,
>> everything
>> worked fine.  For the dfs client I executed dsmcdfs, rather than rename
it
>> and use the one common module for both dfs and jfs file systems.  The SQL
>> Backtrack client was removed from this node and ADSM was upgraded to
>> version
>> 3.  I discovered that if I alternated between dsmc and dsmcdfs I would be
>> prompted for the password.  I got around this by renaming dsmcdfs to be
>> dsmc
>> and using the module for both dfs and jfs filesystems.
>>
>> This weekend I moved the dfs backup client to another node.  This node
>> also
>> contains a SQL Backtrack client.  The SQL Backtrack client gets the
>> message:
>>
>> [obsi/adsm 60600] obsi/adsm: ADSM: dsmInit failed: ANS1025E (RC137)
>> Session
>> rejected: Authentication failure
>>
>> The explanation is that the user entered the wrong password.  I had the
>> DBA
>> run SQL-Backtrack interactively and try to enter the password, but it
>> doesn't help.  He just gets the same message.
>>
>> Does anyone know what the problem is?  Why did dsmc and dsmcdfs stop
>> coexisting with version 3?  Should I have the DBA call SQL-Backtrack
>> support?
>>
>> Tina Hilton
>> Thomson Consumer Electronics
>> Systems Software
>> 317-587-4292
>> hiltont AT tce DOT com
<Prev in Thread] Current Thread [Next in Thread>