Shucks.

Well, grasping at straws:
        have you checked the actlog at that time for errors?
        did you get the meaning of the ORA-19506 and -27006 messages? What
sequential file is it failing on? maybe it's some sort of catalog file
on disk, and the disk is full or permission are wrong.
        Is there an oracle errorlog hiding somewhere with more detail in it?
There is, it's just not in a normal place.  Your Oracle admin probably
knows where it is.




"Jordan, Chris (ELS)" wrote:
>
> 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
>
> -----Original Message-----
> From: Lindsay Morris [mailto:lmorris AT OPENMIC DOT COM]
> Sent: 07 April 2000 16:53
> To: ADSM-L AT vm.marist DOT edu
> Subject: Re: RMAN errors
>
> Are you out of storage space? (q stg)
>
> A common prolem with database agents is that they don't clean up after
> themselves.  If you read the fine manual carefully, it probably makes a
> passing reference to a script you will need to write to clean out old
> database backups, and to a management class you have to create that will
> let that script work.  But neither of these are installed by default, so
> you may have hundreds of old backups clogging up the system.
>
> To check this, type dsmc, then
>         q filespace to see the filespace neames - find the one used by your
> DB
> backups
>         q backup <filepace>
>         q archive <filespace>  (some DB agents use backups, some archives)
>
> If you see thousands of large files with old dates, then I guessed
> right.
>
> "Jordan, Chris (ELS)" wrote:
> >
> > SpamCop - Report spam:
> > http://members.spamcop.net/sc?action=report&id=1058696
> >
> > RMAN backups have been working well for 3 months..... but 3 days ago they
> > just stopped working. Of course, "nothing has changed". ADSM is calling
> the
> > RMAN script with no problems, sees communication from the RMAN node
> > correctly, and records the completion of the RMAN commands correctly with
> no
> > problems.
> >
> > But the client end shows RMAN failure messages like:
> >         RMAN-10035 operation failed
> >         ORA-19506 failed to create sequential file
> >         ORA-27006 sbtremove returned error
> >
> > The last two Oracle describe as backup storage operation failures.
> >
> > Is it a problem at the RMAN end, or at the ADSM end?? ADSM V3.1.2.20
> >
> > We have tried the backup interactively - same problems.
> > We have switched the RMAN backup from allocating an ADSM channel to
> > allocating a disk - and the backups completed successfully.
> > What should we now do to ADSM??
> >
> > Cheers, Chris
>
> --
> Mr. Lindsay Morris
> Gresham Enterprise Storage
> lmorris AT openmic DOT com
> 606-253-8000

--
Mr. Lindsay Morris
Mr. Lindsay Morris
Gresham Enterprise Storage
lmorris AT openmic DOT com
606-253-8000