A few days ago the physicists turned on what they call the waveform channels. The
channel archive database tracking this information was able to withstand the
additional 2,000,000 rows per hour load for 20 + hours. Then the 257 errors hit. As
we are migrating from a very old ADSM system to TSM with a better SILO, this database
seemed a good choice. The old backup system is still handling a score of databases
without using RMAN. I was also able to procure an additional 18 GB internal disk on
which to place the archived redo logs. I shutdown the channel archive database
(9.0.1.3) changed the destination parameter for archive logs to point to the new
location, then did an alter system switch logfile. I then logged into the RMAN
catalog and registered the database for the first time.
I tried
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)";
backup archivelog all delete input;
release channel c1;
}
But it wanted log sequence 8192 which was backed up and deleted on the old system long
ago.
Any way
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)";
backup archivelog from sequence 9645 delete input;
release channel c1;
}
Backed up that log file. I then ran a backup of all the data files to get even the
read only ones, and then a backup of the read write tablespaces. I didn't include
archive logs in these backups. I have asked the physicists to hold off on their
2,000,000 rows per hour data which they can do for a while. They had some other
waveform data which created slightly over 7,000,000 records per day. I placed the
archive log backup as written above into a different cron job. Currently invoked
hourly, than the one for the database backup invoked daily.
All backups use the recovery catalog. The catalog database is 9.2.0.3. Here's the
gist of the problem
select name from rc_archived_log where db_key = 6411;
(Many previous rows removed)
NAME
--------------------------------------------------------------------------------
/opt/oracle/admin/NLCO/arch/NLCO_9633_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9634_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9635_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9636_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9637_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9638_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9639_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9640_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9641_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9642_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9643_1.ARC
/opt/oracle/admin/NLCO/arch/NLCO_9644_1.ARC
List archived logs from the old location. These were never backed up by RMAN.
List archivelog all;
Again lists only old archive files never backed up by rman
9560 1 9633 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9633_1.ARC
9561 1 9634 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9634_1.ARC
9562 1 9635 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9635_1.ARC
9563 1 9636 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9636_1.ARC
9564 1 9637 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9637_1.ARC
9565 1 9638 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9638_1.ARC
9566 1 9639 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9639_1.ARC
9567 1 9640 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9640_1.ARC
9568 1 9641 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9641_1.ARC
9569 1 9642 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9642_1.ARC
9570 1 9643 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9643_1.ARC
9571 1 9644 A 10-JUN-03 /opt/oracle/admin/NLCO/arch/NLCO_9644_1.ARC
However
List backup of archivelog all;
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Device Type Elapsed Time Completion Time
------- ----------- ------------ ---------------
9612 SBT_TAPE 00:01:37 10-JUN-03
BP Key: 9613 Status: AVAILABLE Tag:
Piece Name: df_496342230_2_1
List of Archived Logs in backup set 9612
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 9645 1570637555 10-JUN-03 1570654513 10-JUN-03
1 9646 1570654513 10-JUN-03 1570683560 10-JUN-03
1 9647 1570683560 10-JUN-03 1570695830 10-JUN-03
1 9648 1570695830 10-JUN-03 1570708498 10-JUN-03
1 9649 1570708498 10-JUN-03 1570713009 10-JUN-03
1 9650 1570713009 10-JUN-03 1570715177 10-JUN-03
BS Key Device Type Elapsed Time Completion Time
------- ----------- ------------ ---------------
9703 SBT_TAPE 00:00:50 10-JUN-03
List of Archived Logs in backup set 9703
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 9651 1570715177 10-JUN-03 1570731894 10-JUN-03
1 9652 1570731894 10-JUN-03 1570738219 10-JUN-03
Backup Set Copy #1 of backup set 9703
Device Type Elapsed Time Completion Time Tag
----------- ------------ --------------- ---
SBT_TAPE 00:00:50 10-JUN-03
List of Backup Pieces for backup set 9703 Copy #1
BP Key Pc# Status Piece Name
------- --- ----------- ----------
9704 1 AVAILABLE df_496343070_4_1
9705 2 AVAILABLE df_496343070_4_2
BS Key Device Type Elapsed Time Completion Time
------- ----------- ------------ ---------------
9715 SBT_TAPE 00:00:31 10-JUN-03
BP Key: 9716 Status: AVAILABLE Tag:
Piece Name: df_496346412_5_1
List of Archived Logs in backup set 9715
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 9653 1570738219 10-JUN-03 1570755025 10-JUN-03
1 9654 1570755025 10-JUN-03 1570784000 10-JUN-03
------------------------------------------------------------------------------------------------------------------------
Selecting from rc_backup_redolog is successful as well
1* select * from rc_backup_redolog where db_key = 6411
SQL> /
DB_KEY DBINC_KEY DB_NAME BRL_KEY RECID STAMP BS_KEY
---------- ---------- -------- ---------- ---------- ---------- ----------
SET_STAMP SET_COUNT B COMPLETIO THREAD# SEQUENCE# RESETLOGS_CHANGE#
---------- ---------- - --------- ---------- ---------- -----------------
RESETLOGS FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME BLOCKS BLOCK_SIZE S
--------- ------------- --------- ------------ --------- ---------- ---------- -
BS_RECID BS_STAMP PIECES
---------- ---------- ----------
6411 6412 NLCO 9717 9 496346443 9715
496346412 5 L 10-JUN-03 1 9653 1
10-MAR-02 1570738219 10-JUN-03 1570755025 10-JUN-03 204800 512 A
4 496346443 1
DB_KEY DBINC_KEY DB_NAME BRL_KEY RECID STAMP BS_KEY
---------- ---------- -------- ---------- ---------- ---------- ----------
SET_STAMP SET_COUNT B COMPLETIO THREAD# SEQUENCE# RESETLOGS_CHANGE#
---------- ---------- - --------- ---------- ---------- -----------------
RESETLOGS FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME BLOCKS BLOCK_SIZE S
--------- ------------- --------- ------------ --------- ---------- ---------- -
BS_RECID BS_STAMP PIECES
---------- ---------- ----------
6411 6412 NLCO 9718 10 496346443 9715
496346412 5 L 10-JUN-03 1 9654 1
10-MAR-02 1570755025 10-JUN-03 1570784000 10-JUN-03 27678 512 A
4 496346443 1
----------------------------------------------------------------------------------------------------------------
========================================================================================================================
That doesn't look good. I've just started a "restore database validate." It may be
my ignorance but not everything seems to jibe. I must have left out a step.
Ian MacGregor
Stanford Linear Accelerator Center
[EMAIL PROTECTED]
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: MacGregor, Ian A.
INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
