The question has to do with backup sets not pieces. A backup set can comprise many
pieces.
Ian MacGregor
Stanford Linear Accelerator Center
[EMAIL PROTECTED]
-Original Message-
Sent: Tuesday, June 17, 2003 9:15 AM
To: Multiple recipients of list ORACLE-L
You have the maxpiecesize set
You have the maxpiecesize set to 2048. It will fill the backup piece and
then start another. Have the datafile sized changed alot from one day to
the next?
Ruth
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Wednesday, June 11, 2003 6:25 PM
I'm
Hmm, puzzling indeed.
For starters, your output log appear truncated. I would have expected a
resync catalog somewhere at the end. You could try resync catalog
manually and try again.
Second, all datafiles should be listed in the output. This listing contains
only 33+2*2 out of 92. Any clues
It appears truncated because it is only the top of the log. I so indicated that by
specifying that only the beginning of the log was being posted. All files do show up
in the complete log. I don't presently have files larger than 2GB. The old backup
system would not handle them. I will
I'm a bit confused by the default for filesperset. I ran the following yesterday
run
{
allocate channel c1 device type sbt format 'df_%t_%s_%p' maxpiecesize=2048M
PARMS=SBT_LIBRARY=/opt/oracle/dbserver/9.0.1/lib/libobk.so,
ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin/tdpo.opt);
How did you join to get BS_KEY and FILE# together?
I don't believe the BS_KEY from a backup database relate directly to a
FILE# from the rc_views.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Thursday, June 12, 2003 10:25 AM
I'm a bit confused
The information matches what was reported while the backup was in progress. Here is
the beginning of the log for
The read write backup.
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile
