I'd suggest , as others have, that the problem is with the password.
Because the Oracle Client can't use PASSWORD GENERATE, when the password is
due to expire, the MAILPROG option is used to notify you of the expiry and
you may not have set this up.

You can check whether the password is expired by using  q node <nodename>
f=d.
If it is expired, try resetting the node password from the server and
running aobpswd again.

Steve

Steve Harris
AIX/ADSM/Oracle/HACMP/Domino Guy

The Wesley Hospital, Brisbane Australia





"Jordan, Chris (ELS)" <c.jordan AT ELSEVIER.CO DOT UK>@VM.MARIST.EDU> on
08/04/2000 02:22:16

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Fax to:
Subject:  Re: RMAN errors


Thanks, but I don't think that is it.

The system we are backing up has 16,841 MBytes in total, and the Audit
Occupancy shows:
        Normal system: 34,646 MBytes (so hardly two versions).
        RMAN system: 8,280 MBytes.
I am pretty certain that the DBA's implemented the delete old versions
correctly - because we stood over them while they did it.
The Q STGP shows the backup pool never goes over 87% full (total space is
136 GBytes). The databases we are backing up are about 180 MBytes.

Any further ideas I can check?


Cheers, Chris