Thanks to all. I have changed filesperset parameter to smaller number and it
did work!! ;)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Roark Ludwig
Sent: Tuesday, December 26, 2006 8:57 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] RMAN with TDP for oracle error
TDPO and RMAN have been used at our facility for BOTH hot and cold backups.....
on both UNIX and WINDOWS platforms..
I would be happy to discuss how each is accomplished in a private email..
>From the sketchy information contained in this thread, I would guess that the
>problem is as described by "RICHARD SIMS" It looks like the backup is being
>written to a local disk drive rather then the TSM server...
THE TDPO documents provide a step-by-step scenario..
if you need details, please email me directly.
Roark
William Boyer
<bjdboyer@COMCAST
.NET> To
Sent by: "ADSM: ADSM-L AT VM.MARIST DOT EDU
Dist Stor cc
Manager"
<[email protected] Subject
.EDU> Re: [ADSM-L] RMAN with TDP for
oracle error
12/26/2006 09:44
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[email protected]
.EDU>
But I believe that the database must be configured for transaction archive log
mode before you can do online backups.
Bill Boyer
"Backup my harddrive? How do I put it in reverse?" - ??
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Thomas Rupp
Sent: Tuesday, December 26, 2006 11:11 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: AW: [ADSM-L] RMAN with TDP for oracle error
Hi Ahmed,
We use TDP for Oracle as well. But we do no SHUTDOWN in our RMAN scripts.
Because TDPO is a tool for *online* backups.
I would remove the SHUTDOWN and STARTUP statements from your RMAN scripts and
try again.
Kind regards and greetings from Austria
Thomas
-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag
von Rick Chu
Gesendet: Dienstag, 26. Dezember 2006 16:51
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: [ADSM-L] RMAN with TDP for oracle error
Ahmed Al-Saidi wrote:
> Hi all,
>
> I face a problem this morning with oracle backup using TDP for oracle
>
> RMAN-03009: failure of backup command on ORA_DISK_1 channel at
> 12/26/2006 09:30:26
> ORA-19502: write error on file "df_610190894_54_4", blockno 39297
> (blocksize=8192)
> ORA-27072: skgfdisp: I/O error
> OSD-04008: WriteFile() failure, unable to write to file
> O/S-Error: (OS 112) There is not enough space on the disk.
>
> I didn't find any error in tdpoerror.log
>
>
> Did anyone face same problem???
>
> This is RMAN log file
>
>
> RMAN> run
> 2> {
> 3> allocate channel t1 type 'sbt_tape' parms
> 4> 'ENV=(TDPO_OPTFILE=C:\Program
> Files\Tivoli\TSM\AgentOBA\tdpo.opt)';
> 5>
> 6> shutdown immediate
> 7> startup mount
> 8>
> 9> backup
> 10> filesperset 64
> 11> format 'df_%t_%s_%p'
> 12> (database);
> 13>
> 14> alter database open;
> 15>
> 16> }
> 17>
> 18>
> using target database controlfile instead of recovery catalog
> allocated channel: t1 channel t1: sid=20 devtype=SBT_TAPE channel t1:
> Data Protection for Oracle: version 5.3.3.0
>
> database closed
> database dismounted
> Oracle instance shut down
>
> connected to target database (not started) Oracle instance started
> database mounted
>
> Total System Global Area 1209082940 bytes
>
> Fixed Size 455740 bytes
> Variable Size 1182793728 bytes
> Database Buffers 25165824 bytes
> Redo Buffers 667648 bytes
>
> Starting backup at 26/12/06 09:28:12
> allocated channel: ORA_DISK_1
> channel ORA_DISK_1: sid=11 devtype=DISK channel ORA_DISK_1: starting
> full datafile backupset channel ORA_DISK_1: specifying datafile(s) in
> backupset including current SPFILE in backupset including current
> controlfile in backupset input datafile fno=00008
> name=E:\ORACLE\ORADATA\COPYDB\COPY01.ORA
> input datafile fno=00009 name=E:\ORACLE\ORADATA\COPYDB\COPY02.ORA
> input datafile fno=00010 name=E:\ORACLE\ORADATA\COPYDB\COPY03.ORA
> input datafile fno=00011 name=E:\ORACLE\ORADATA\COPYDB\COPY04.ORA
> input datafile fno=00012 name=E:\ORACLE\ORADATA\COPYDB\COPY17.ORA
> input datafile fno=00013 name=E:\ORACLE\ORADATA\COPYDB\COPY18.ORA
> input datafile fno=00014 name=E:\ORACLE\ORADATA\COPYDB\COPY19.ORA
> input datafile fno=00015 name=E:\ORACLE\ORADATA\COPYDB\COPY05.ORA
> input datafile fno=00016 name=E:\ORACLE\ORADATA\COPYDB\COPY06.ORA
> input datafile fno=00017 name=E:\ORACLE\ORADATA\COPYDB\COPY07.ORA
> input datafile fno=00018 name=E:\ORACLE\ORADATA\COPYDB\COPY08.ORA
> input datafile fno=00019 name=E:\ORACLE\ORADATA\COPYDB\COPY09.ORA
> input datafile fno=00020 name=E:\ORACLE\ORADATA\COPYDB\COPY10.ORA
> input datafile fno=00021 name=E:\ORACLE\ORADATA\COPYDB\COPY11.ORA
> input datafile fno=00022 name=E:\ORACLE\ORADATA\COPYDB\COPY12.ORA
> input datafile fno=00023 name=E:\ORACLE\ORADATA\COPYDB\COPY13.ORA
> input datafile fno=00024 name=E:\ORACLE\ORADATA\COPYDB\COPY14.ORA
> input datafile fno=00025 name=E:\ORACLE\ORADATA\COPYDB\COPY15.ORA
> input datafile fno=00026 name=E:\ORACLE\ORADATA\COPYDB\COPY16.ORA
> input datafile fno=00001 name=E:\ORACLE\ORADATA\COPYDB\SYSTEM01.DBF
> input datafile fno=00002 name=E:\ORACLE\ORADATA\COPYDB\UNDOTBS01.DBF
> input datafile fno=00007 name=E:\ORACLE\ORADATA\COPYDB\XDB01.DBF
> input datafile fno=00004 name=E:\ORACLE\ORADATA\COPYDB\INDX01.DBF
> input datafile fno=00003 name=E:\ORACLE\ORADATA\COPYDB\DRSYS01.DBF
> input datafile fno=00006 name=E:\ORACLE\ORADATA\COPYDB\USERS01.DBF
> input datafile fno=00005 name=E:\ORACLE\ORADATA\COPYDB\TOOLS01.DBF
> channel ORA_DISK_1: starting piece 1 at 26/12/06 09:28:16 channel
> ORA_DISK_1: finished piece 1 at 26/12/06 09:28:51 piece
> handle=C:\ORACLE\ORA92\DATABASE\DF_610190894_54_1 comment=NONE channel
> ORA_DISK_1: starting piece 2 at 26/12/06 09:28:51 channel ORA_DISK_1:
> finished piece 2 at 26/12/06 09:29:26 piece
> handle=C:\ORACLE\ORA92\DATABASE\DF_610190894_54_2 comment=NONE channel
> ORA_DISK_1: starting piece 3 at 26/12/06 09:29:26 channel ORA_DISK_1:
> finished piece 3 at 26/12/06 09:30:01 piece
> handle=C:\ORACLE\ORA92\DATABASE\DF_610190894_54_3 comment=NONE channel
> ORA_DISK_1: starting piece 4 at 26/12/06 09:30:01
> RMAN-00571:
> ===========================================================
> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
> ===============
> RMAN-00571:
> ===========================================================
> RMAN-03009: failure of backup command on ORA_DISK_1 channel at
> 12/26/2006 09:30:26
> ORA-19502: write error on file "df_610190894_54_4", blockno 39297
> (blocksize=8192)
> ORA-27072: skgfdisp: I/O error
> OSD-04008: WriteFile() failure, unable to write to file
> O/S-Error: (OS 112) There is not enough space on the disk.
>
> Recovery Manager complete.
>
>
It's interesting how it seems to allocate the tape channel and after the
shutdown & startup it allocates a disk channel. In my cold backup scripts I
shutdown & "startup mount" outside of the run block.
For example:
connect rcvcat ...
connect catalog ...
shutdown immediate
startup mount
run {
allocate channel t1 type 'SBT_TAPE' parms
'ENV=(tdpo_optfile=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
backup
format 'bk_%s_%c_%t'
(database);
}
alter database open;
Rick C.
|
