Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: RMAN - Can't release channel error

Re: RMAN - Can't release channel error

From: Jay Strauss <jstrauss_at_compuserve.com>
Date: Tue, 17 Oct 2000 10:19:24 -0500
Message-ID: <ryPG5.49288$Km6.3040026@news-west.usenetserver.com>

My script is straight out of the manual

In the body of the this email is the entire script and the output when I run it

Thanks
Jay

--

Jay Strauss
jstrauss_at_bazillion.com
(h) 773.935.5326
(c) 312.617.0264

"Van Messner" <vmessner_at_bestweb.net> wrote in message
news:qsKG5.6939$mC.497890_at_monger.newsread.com...

> Here's a typical disk script:
>
> replace script backup_one_tspc_level0_dbrman {
> execute script alloc_one_disk_dbrman;
> backup
> incremental level 0
> tag backup_ts_hist1_level0
> filesperset 10
> format 'backup_one_tspc_level0_dbrman_t%t_s%s_p%p_c%c'
> tablespace hist1;
> execute script release_one_disk_dbrman;
> execute script archive_cur_redo_log_dbrman;
> }
> # Alloc_One_Disk_DbRMAN
> #
> # Allocates one disk drive available for backup.
> # The setlimit commands below enforce the following restrictions:
> # - no single backup piece is greater than 2G
> # setlimit kbytes 2097152)
> # - a channel can only have a maximum of 32 files open at any
> # one time (setlimit maxopenfiles)
> # - no more than 200 buffers are allowed to be read per file
> # per second (readrate 200). The size of each buffer is
> # determined by the init.ora parameter sequential_io_bufsize.
> # This is done to limit the effect the backup file scan is
> # having on online users / batch jobs.
> #
> replace script alloc_one_disk_dbrman {
> allocate channel d1 type disk;
> setlimit channel d1 kbytes 2097150 maxopenfiles 32 readrate 200;
> }
> # Release_One_Disk_DbRMAN
> #
> # Releases one disk drive which was used for backup.
> #
> replace script release_one_disk_dbrman {
> release channel d1;
> }
> # Archive_Cur_Redo_Log_DbRMAN
> #
> # Archives the current redolog (for Oracle Parallel Server,
> # does this for all opened instances)
> # Oracle recommends the current log is archvived immediately
> # after performing any open (i.e. hot) backups.
> #
> replace script archive_cur_redo_log_dbrman {
> sql 'alter system archive log current';
> }
>
> Does yours have a release channel statement?
>
> Van
>
> "Jay Strauss" <jstrauss_at_bazillion.com> wrote in message
> news:39EB0949.336EDEF0_at_bazillion.com...
> > Anyone got an idea why this is happening?
> > I've RTFM, and this is supposed to be a baby step. I'll I'm trying to
> > do is a full backup 8.1.6 database using RMAN 8.1.6.
> > Nothing gets written to the backup. I'm not using any storage
> > management software, I'm trying to write to a regular file system.
> >
> > Thanks
> > Jay
> >
> > Below is my output:
> >
> >
> > [oracle_at_localhost admin]$ rman
> >
> > Recovery Manager: Release 8.1.6.1.0 - Production
> >
> > RMAN> connect target
> >
> > RMAN-06005: connected to target database: ORCL (DBID=938272352)
> >
> > RMAN> connect catalog rman/rman_at_rman
> >
> > RMAN-06008: connected to recovery catalog database
> >
> > RMAN> @/u01/app/oracle/admin/fullback.rcv
> >
> > RMAN> # Full backup script
> > 2>
> > 3> run {
> > 4> allocate channel d1 type disk;
> > 5> backup
> > 6> incremental level 0
> > 7> tag fullback
> > 8> filesperset 50
> > 9> format '/u03/oradata/backup/%d/%d__t%t_s%s_p%p'
> > 10> (database);
> > 11> }
> > RMAN-03022: compiling command: allocate
> > RMAN-03023: executing command: allocate
> > RMAN-08030: allocated channel: d1
> > RMAN-08500: channel d1: sid=19 devtype=DISK
> >
> > RMAN-03022: compiling command: backup
> > RMAN-03023: executing command: backup
> > RMAN-08008: channel d1: starting incremental level 0 datafile backupset
> > RMAN-08502: set_count=4 set_stamp=411116017 creation_time=16-OCT-00
> > RMAN-08010: channel d1: specifying datafile(s) in backupset
> > RMAN-08522: input datafile fno=00001 name=/u02/oradata/ORCL/system01.dbf
> >
> > RMAN-08011: including current controlfile in backupset
> > RMAN-08522: input datafile fno=00003 name=/u02/oradata/ORCL/rbs01.dbf
> > RMAN-08522: input datafile fno=00008 name=/u02/oradata/ORCL/rmancat.dbf
> > RMAN-08522: input datafile fno=00004 name=/u02/oradata/ORCL/temp01.dbf
> > RMAN-08522: input datafile fno=00005 name=/u02/oradata/ORCL/users01.dbf
> > RMAN-08522: input datafile fno=00006 name=/u02/oradata/ORCL/indx01.dbf
> > RMAN-08522: input datafile fno=00007 name=/u02/oradata/ORCL/drsys01.dbf
> > RMAN-08522: input datafile fno=00002 name=/u02/oradata/ORCL/tools01.dbf
> > RMAN-03026: error recovery releasing channel resources
> > RMAN-00571: ===========================================================
> > RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
> > RMAN-00571: ===========================================================
> > RMAN-07005: error during channel cleanup
> > RMAN-07004: unhandled exception during command execution on channel d1
> > RMAN-10032: unhandled exception during execution of job step 1:
> > RMAN-10031: ORA-65535 occurred during call to
> > DBMS_BACKUP_RESTORE.DEVICESTATUS
> > RMAN-03006: non-retryable error occurred during execution of command:
> > backup
> > RMAN-07004: unhandled exception during command execution on channel d1
> > RMAN-10032: unhandled exception during execution of job step 1:
> > RMAN-10031: ORA-65535 occurred during call to
> > DBMS_BACKUP_RESTORE.BACKUPPIECECRATE
> >
> > RMAN> **end-of-file**
> >
> >
> >
> >
> >
>
>
Received on Tue Oct 17 2000 - 10:19:24 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US