Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Urgent!: RMAN Problem
Try increasing the shared_pool size in your target database. On of the other option is to try increasing the sort_area_size on the target database. One of the other suggestions is to close the channel after you use i.e release.
It looks like a resource contention issue. So play with increasing those resources that it complains about.
Good luck,
Sam
In article
<F4155D9F9AA4D111B9990020AFBA52D5427BC6_at_class06.ip061.sfi-software.com>,
"Mark G" <markag_at_wonderstats.com> wrote:
> Hi all,
>
> I'm trying to test the backup ability of RMAN. Here is my RMAN session
on
> 8i/EE/NT, tons of memory. My target database is up and open,
archivelog
> mode, on a primary machine. My catalog is on backup machine, same
> machine/Oracle/Instance configuration. I created the RCVCAT on the
backup
> machine. I am able to connect to both the target and the catalog as
seen
> below. It looks like the problem is it cannot allocate the I/O device
> between the catalog database and the target
> database to do the backup.
>
> God status would be achieved in my eyes should anyone with some
experience
> help me through this mess.
>
> =====================================================================
> Recovery Manager: Release 8.1.6.0.0 - Production
>
> RMAN> connect target system/manager_at_pwprod
>
> RMAN-06005: connected to target database: PWDB02 (DBID=3059294144)
>
> RMAN> connect catalog rman/rman_at_pwbu
>
> RMAN-06008: connected to recovery catalog database
>
> RMAN> run {
> 2> allocate channel ch1 type disk;
> 3> backup tablespace system;
> 4> }
>
> RMAN-03022: compiling command: allocate
> RMAN-03023: executing command: allocate
> RMAN-00571:
Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Wed Sep 27 2000 - 16:11:59 CDT