torturedmind
Programmer
Hi to all Oracle gurus.
In our Oracle 10R2 DB, we unintentionally added a datafile in a tablespace where it's not suppose to be in. So we placed the concerned tablespace to offline then we restore/recover the needed datafiles and left the "rogue" datafile as is because we intend to drop it. Problem is DROPping a datafile in a locally managed tablespace is not possible (I've read it somewhere) unless it's online. We tried putting it in online mode but RMAN failed to do so. Message says "unable to perform media recovery because of missing log" (please see RMAN messages below). And we can't make the tablespace online because one datafile still needs to be recovered. Is there any way we can place the tablespace online? Thanks in advanced.
kilroy![[knight] [knight] [knight]](/data/assets/smilies/knight.gif)
philippines
"Once a king, always a king. But being a knight is more than enough."
In our Oracle 10R2 DB, we unintentionally added a datafile in a tablespace where it's not suppose to be in. So we placed the concerned tablespace to offline then we restore/recover the needed datafiles and left the "rogue" datafile as is because we intend to drop it. Problem is DROPping a datafile in a locally managed tablespace is not possible (I've read it somewhere) unless it's online. We tried putting it in online mode but RMAN failed to do so. Message says "unable to perform media recovery because of missing log" (please see RMAN messages below). And we can't make the tablespace online because one datafile still needs to be recovered. Is there any way we can place the tablespace online? Thanks in advanced.
Code:
Recovery Manager: Release 10.2.0.3.0 - Production on Sat Dec 4 08:41:29 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN>
connected to target database: THERP (DBID=3602721984)
using target database control file instead of recovery catalog
RMAN>
echo set on
RMAN> run {
2> recover datafile 18;
3> sql 'alter database datafile 18 online';
4> }
Starting recover at 04-DEC-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=500 instance=therp2 devtype=DISK
starting media recovery
archive log thread 1 sequence 11838 is already on disk as file /thp3/1_11838_632497279.dbf
archive log thread 1 sequence 11839 is already on disk as file /thp3/1_11839_632497279.dbf
archive log thread 1 sequence 11840 is already on disk as file /thp3/1_11840_632497279.dbf
archive log thread 1 sequence 11841 is already on disk as file /thp3/1_11841_632497279.dbf
archive log thread 1 sequence 11842 is already on disk as file /thp3/1_11842_632497279.dbf
archive log thread 1 sequence 11843 is already on disk as file /thp3/1_11843_632497279.dbf
archive log thread 1 sequence 11844 is already on disk as file /thp3/1_11844_632497279.dbf
archive log thread 1 sequence 11845 is already on disk as file /thp3/1_11845_632497279.dbf
archive log thread 1 sequence 11846 is already on disk as file /thp3/1_11846_632497279.dbf
archive log thread 1 sequence 11847 is already on disk as file /thp3/1_11847_632497279.dbf
archive log thread 1 sequence 11848 is already on disk as file /thp3/1_11848_632497279.dbf
archive log thread 1 sequence 11849 is already on disk as file /thp3/1_11849_632497279.dbf
archive log thread 1 sequence 11850 is already on disk as file /thp3/1_11850_632497279.dbf
archive log thread 1 sequence 11851 is already on disk as file /thp3/1_11851_632497279.dbf
archive log thread 1 sequence 11852 is already on disk as file /thp3/1_11852_632497279.dbf
archive log thread 1 sequence 11853 is already on disk as file /thp3/1_11853_632497279.dbf
archive log thread 1 sequence 11854 is already on disk as file /thp3/1_11854_632497279.dbf
archive log thread 1 sequence 11855 is already on disk as file /thp3/1_11855_632497279.dbf
archive log thread 1 sequence 11856 is already on disk as file /thp3/1_11856_632497279.dbf
archive log thread 1 sequence 11857 is already on disk as file /thp3/1_11857_632497279.dbf
archive log thread 1 sequence 11858 is already on disk as file /thp3/1_11858_632497279.dbf
archive log thread 1 sequence 11859 is already on disk as file /thp3/1_11859_632497279.dbf
archive log thread 1 sequence 11860 is already on disk as file /thp3/1_11860_632497279.dbf
archive log thread 1 sequence 11861 is already on disk as file /thp3/1_11861_632497279.dbf
archive log thread 1 sequence 11862 is already on disk as file /thp3/1_11862_632497279.dbf
archive log thread 1 sequence 11863 is already on disk as file /thp3/1_11863_632497279.dbf
archive log thread 1 sequence 11864 is already on disk as file /thp3/1_11864_632497279.dbf
archive log thread 1 sequence 11865 is already on disk as file /thp3/1_11865_632497279.dbf
archive log thread 1 sequence 11866 is already on disk as file /thp3/1_11866_632497279.dbf
archive log thread 1 sequence 11867 is already on disk as file /thp3/1_11867_632497279.dbf
archive log thread 1 sequence 11868 is already on disk as file /thp3/1_11868_632497279.dbf
archive log thread 1 sequence 11869 is already on disk as file /thp3/1_11869_632497279.dbf
archive log thread 1 sequence 11870 is already on disk as file /thp3/1_11870_632497279.dbf
archive log thread 1 sequence 11871 is already on disk as file /thp3/1_11871_632497279.dbf
archive log thread 1 sequence 11872 is already on disk as file /thp3/1_11872_632497279.dbf
archive log thread 1 sequence 11873 is already on disk as file /thp3/1_11873_632497279.dbf
archive log thread 1 sequence 11874 is already on disk as file /thp3/1_11874_632497279.dbf
archive log thread 1 sequence 11875 is already on disk as file /thp3/1_11875_632497279.dbf
archive log thread 1 sequence 11876 is already on disk as file /thp3/1_11876_632497279.dbf
archive log thread 1 sequence 11877 is already on disk as file /thp3/1_11877_632497279.dbf
archive log thread 1 sequence 11878 is already on disk as file /thp3/1_11878_632497279.dbf
archive log thread 1 sequence 11879 is already on disk as file /thp3/1_11879_632497279.dbf
archive log thread 1 sequence 11880 is already on disk as file /thp3/1_11880_632497279.dbf
archive log thread 1 sequence 11881 is already on disk as file /thp3/1_11881_632497279.dbf
archive log thread 1 sequence 11882 is already on disk as file /thp3/1_11882_632497279.dbf
archive log thread 1 sequence 11883 is already on disk as file /thp3/1_11883_632497279.dbf
archive log thread 1 sequence 11884 is already on disk as file /thp3/1_11884_632497279.dbf
archive log thread 1 sequence 11885 is already on disk as file /thp3/1_11885_632497279.dbf
archive log thread 1 sequence 11886 is already on disk as file /thp3/1_11886_632497279.dbf
archive log thread 1 sequence 11887 is already on disk as file /thp3/1_11887_632497279.dbf
archive log thread 1 sequence 11888 is already on disk as file /thp3/1_11888_632497279.dbf
archive log thread 1 sequence 11889 is already on disk as file /thp3/1_11889_632497279.dbf
archive log thread 1 sequence 11890 is already on disk as file /thp3/1_11890_632497279.dbf
archive log thread 1 sequence 11891 is already on disk as file /thp3/1_11891_632497279.dbf
archive log thread 1 sequence 11892 is already on disk as file /thp3/1_11892_632497279.dbf
archive log thread 1 sequence 11893 is already on disk as file /thp3/1_11893_632497279.dbf
archive log thread 1 sequence 11894 is already on disk as file /thp3/1_11894_632497279.dbf
archive log thread 2 sequence 10694 is already on disk as file /thp3/2_10694_632497279.dbf
archive log thread 2 sequence 10695 is already on disk as file /thp3/2_10695_632497279.dbf
archive log thread 2 sequence 10696 is already on disk as file /thp3/2_10696_632497279.dbf
archive log thread 2 sequence 10697 is already on disk as file /thp3/2_10697_632497279.dbf
archive log thread 2 sequence 10698 is already on disk as file /thp3/2_10698_632497279.dbf
archive log thread 2 sequence 10699 is already on disk as file /thp3/2_10699_632497279.dbf
archive log thread 2 sequence 10700 is already on disk as file /thp3/2_10700_632497279.dbf
archive log thread 2 sequence 10701 is already on disk as file /thp3/2_10701_632497279.dbf
archive log thread 2 sequence 10702 is already on disk as file /thp3/2_10702_632497279.dbf
archive log thread 2 sequence 10703 is already on disk as file /thp3/2_10703_632497279.dbf
archive log thread 2 sequence 10704 is already on disk as file /thp3/2_10704_632497279.dbf
archive log thread 2 sequence 10705 is already on disk as file /thp3/2_10705_632497279.dbf
archive log thread 2 sequence 10706 is already on disk as file /thp3/2_10706_632497279.dbf
archive log thread 2 sequence 10707 is already on disk as file /thp3/2_10707_632497279.dbf
archive log thread 2 sequence 10708 is already on disk as file /thp3/2_10708_632497279.dbf
archive log thread 2 sequence 10709 is already on disk as file /thp3/2_10709_632497279.dbf
archive log thread 2 sequence 10710 is already on disk as file /thp3/2_10710_632497279.dbf
archive log thread 2 sequence 10711 is already on disk as file /thp3/2_10711_632497279.dbf
archive log thread 2 sequence 10712 is already on disk as file /thp3/2_10712_632497279.dbf
archive log thread 2 sequence 10713 is already on disk as file /thp3/2_10713_632497279.dbf
archive log thread 2 sequence 10714 is already on disk as file /thp3/2_10714_632497279.dbf
archive log thread 2 sequence 10715 is already on disk as file /thp3/2_10715_632497279.dbf
archive log thread 2 sequence 10716 is already on disk as file /thp3/2_10716_632497279.dbf
archive log thread 2 sequence 10717 is already on disk as file /thp3/2_10717_632497279.dbf
archive log thread 2 sequence 10718 is already on disk as file /thp3/2_10718_632497279.dbf
archive log thread 2 sequence 10719 is already on disk as file /thp3/2_10719_632497279.dbf
archive log thread 2 sequence 10720 is already on disk as file /thp3/2_10720_632497279.dbf
archive log thread 2 sequence 10721 is already on disk as file /thp3/2_10721_632497279.dbf
archive log thread 2 sequence 10722 is already on disk as file /thp3/2_10722_632497279.dbf
archive log thread 2 sequence 10723 is already on disk as file /thp3/2_10723_632497279.dbf
archive log thread 2 sequence 10724 is already on disk as file /thp3/2_10724_632497279.dbf
archive log thread 2 sequence 10725 is already on disk as file /thp3/2_10725_632497279.dbf
archive log thread 2 sequence 10726 is already on disk as file /thp3/2_10726_632497279.dbf
archive log thread 2 sequence 10727 is already on disk as file /thp3/2_10727_632497279.dbf
archive log thread 2 sequence 10728 is already on disk as file /thp3/2_10728_632497279.dbf
archive log thread 2 sequence 10729 is already on disk as file /thp3/2_10729_632497279.dbf
archive log thread 2 sequence 10730 is already on disk as file /thp3/2_10730_632497279.dbf
archive log thread 2 sequence 10731 is already on disk as file /thp3/2_10731_632497279.dbf
archive log thread 2 sequence 10732 is already on disk as file /thp3/2_10732_632497279.dbf
archive log thread 2 sequence 10733 is already on disk as file /thp3/2_10733_632497279.dbf
archive log thread 2 sequence 10734 is already on disk as file /thp3/2_10734_632497279.dbf
archive log thread 2 sequence 10735 is already on disk as file /thp3/2_10735_632497279.dbf
archive log thread 2 sequence 10736 is already on disk as file /thp3/2_10736_632497279.dbf
archive log thread 2 sequence 10737 is already on disk as file /thp3/2_10737_632497279.dbf
archive log thread 2 sequence 10738 is already on disk as file /thp3/2_10738_632497279.dbf
archive log thread 2 sequence 10739 is already on disk as file /thp3/2_10739_632497279.dbf
archive log thread 2 sequence 10740 is already on disk as file /thp3/2_10740_632497279.dbf
archive log thread 2 sequence 10741 is already on disk as file /thp3/2_10741_632497279.dbf
archive log thread 2 sequence 10742 is already on disk as file /thp3/2_10742_632497279.dbf
archive log thread 2 sequence 10743 is already on disk as file /thp3/2_10743_632497279.dbf
archive log thread 2 sequence 10744 is already on disk as file /thp3/2_10744_632497279.dbf
archive log thread 2 sequence 10745 is already on disk as file /thp3/2_10745_632497279.dbf
archive log thread 2 sequence 10746 is already on disk as file /thp3/2_10746_632497279.dbf
archive log thread 2 sequence 10747 is already on disk as file /thp3/2_10747_632497279.dbf
archive log thread 2 sequence 10748 is already on disk as file /thp3/2_10748_632497279.dbf
archive log thread 2 sequence 10749 is already on disk as file /thp3/2_10749_632497279.dbf
archive log thread 2 sequence 10750 is already on disk as file /thp3/2_10750_632497279.dbf
archive log thread 2 sequence 10751 is already on disk as file /thp3/2_10751_632497279.dbf
archive log thread 2 sequence 10752 is already on disk as file /thp3/2_10752_632497279.dbf
archive log thread 2 sequence 10753 is already on disk as file /thp3/2_10753_632497279.dbf
archive log thread 2 sequence 10754 is already on disk as file /thp3/2_10754_632497279.dbf
archive log thread 2 sequence 10755 is already on disk as file /thp3/2_10755_632497279.dbf
archive log thread 2 sequence 10756 is already on disk as file /thp3/2_10756_632497279.dbf
archive log thread 2 sequence 10757 is already on disk as file /thp3/2_10757_632497279.dbf
archive log thread 2 sequence 10758 is already on disk as file /thp3/2_10758_632497279.dbf
archive log thread 2 sequence 10759 is already on disk as file /thp3/2_10759_632497279.dbf
archive log thread 2 sequence 10760 is already on disk as file /thp3/2_10760_632497279.dbf
archive log thread 2 sequence 10761 is already on disk as file /thp3/2_10761_632497279.dbf
archive log thread 2 sequence 10762 is already on disk as file /thp3/2_10762_632497279.dbf
archive log thread 2 sequence 10763 is already on disk as file /thp3/2_10763_632497279.dbf
archive log thread 2 sequence 10764 is already on disk as file /thp3/2_10764_632497279.dbf
archive log thread 2 sequence 10765 is already on disk as file /thp3/2_10765_632497279.dbf
archive log thread 2 sequence 10766 is already on disk as file /thp3/2_10766_632497279.dbf
archive log thread 2 sequence 10767 is already on disk as file /thp3/2_10767_632497279.dbf
archive log thread 2 sequence 10768 is already on disk as file /thp3/2_10768_632497279.dbf
archive log thread 2 sequence 10769 is already on disk as file /thp3/2_10769_632497279.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
[COLOR=red][b]RMAN-03002: failure of recover command at 12/04/2010 08:41:34
RMAN-06053: unable to perform media recovery because of missing log[/b][/color]
RMAN-06025: no backup of log thread 2 seq 10076 lowscn 293695795 found to restore
RMAN-06025: no backup of log thread 2 seq 10075 lowscn 293655736 found to restore
RMAN-06025: no backup of log thread 2 seq 10074 lowscn 293616001 found to restore
RMAN-06025: no backup of log thread 2 seq 10073 lowscn 293576326 found to restore
RMAN-06025: no backup of log thread 2 seq 10072 lowscn 293536806 found to restore
RMAN-06025: no backup of log thread 2 seq 10071 lowscn 293497689 found to restore
RMAN-06025: no backup of log thread 2 seq 10070 lowscn 293463871 found to restore
RMAN-06025: no backup of log thread 2 seq 10069 lowscn 293461208 found to restore
RMAN-06025: no backup of log thread 2 seq 10068 lowscn 293457563 found to restore
RMAN-06025: no backup of log thread 2 seq 10067 lowscn 293454143 found to restore
RMAN-06025: no backup of log thread 2 seq 10066 lowscn 293450627 found to restore
RMAN-06025: no backup of log thread 2 seq 10065 lowscn 293447221 found to restore
RMAN-06025: no backup of log thread 2 seq 10064 lowscn 293443758 found to restore
RMAN-06025: no backup of log thread 2 seq 10063 lowscn 293440572 found to restore
RMAN-06025: no backup of log thread 2 seq 10062 lowscn 293416606 found to restore
RMAN-06025: no backup of log thread 2 seq 10061 lowscn 293375341 found to restore
RMAN-06025: no backup of log thread 2 seq 10060 lowscn 293335636 found to restore
RMAN-06025: no backup of log thread 2 seq 10059 lowscn 293295434 found to restore
RMAN-06025: no backup of log thread 2 seq 10058 lowscn 293254048 found to restore
RMAN-06025: no backup of log thread 2 seq 10057 lowscn 293213324 found to restore
RMAN-06025: no backup of log thread 2 seq 10056 lowscn 293171832 found to restore
RMAN-06025: no backup of log thread 2 seq 10055 lowscn 293171811 found to restore
RMAN-06025: no backup of log thread 2 seq 10054 lowscn 293171779 found to restore
RMAN-06025: no backup of log thread 2 seq 10053 lowscn 293170472 found to restore
RMAN-06025: no backup of log thread 2 seq 10052 lowscn 293146716 found to restore
RMAN-06025: no backup of log thread 2 seq 10051 lowscn 293106160 found to restore
RMAN-06025: no backup of log thread 2 seq 10050 lowscn 293063732 found to restore
RMAN-06025: no backup of log thread 2 seq 10049 lowscn 293023711 found to restore
RMAN-06025: no backup of log thread 2 seq 10048 lowscn 292982725 found to restore
RMAN-06025: no backup of log thread 2 seq 10047 lowscn 292942210 found to restore
RMAN-06025: no backup of log thread 2 seq 10046 lowscn 292900802 found to restore
RMAN-06025: no backup of log thread 2 seq 10045 lowscn 292860728 found to restore
RMAN-06025: no backup of log thread 2 seq 10044 lowscn 292860698 found to restore
RMAN-06025: no backup of log thread 2 seq 10043 lowscn 292860668 found to restore
RMAN-06025: no backup of log thread 2 seq 10042 lowscn 292860589 found to restore
RMAN-06025: no backup of log thread 2 seq 10041 lowscn 292847803 found to restore
RMAN-06025: no backup of log thread 2 seq 10040 lowscn 292806606 found to restore
RMAN-06025: no backup of log thread 2 seq 10039 lowscn 292765114 found to restore
RMAN-06025: no backup of log thread 2 seq 10038 lowscn 292723484 found to restore
RMAN-06025: no backup of log thread 2 seq 10037 lowscn 292682675 found to restore
RMAN-06025: no backup of log thread 2 seq 10036 lowscn 292642579 found to restore
RMAN-06025: no backup of log thread 2 seq 10035 lowscn 292601511 found to restore
RMAN-06025: no backup of log thread 2 seq 10034 lowscn 292559475 found to restore
RMAN-06025: no backup of log thread 2 seq 10033 lowscn 292519123 found to restore
RMAN-06025: no backup of log thread 2 seq 10032 lowscn 292478156 found to restore
RMAN-06025: no backup of log thread 2 seq 10031 lowscn 292438352 found to restore
RMAN-06025: no backup of log thread 2 seq 10030 lowscn 292397741 found to restore
RMAN-06025: no backup of log thread 2 seq 10029 lowscn 292357650 found to restore
RMAN-06025: no backup of log thread 2 seq 10028 lowscn 292317647 found to restore
RMAN-06025: no backup of log thread 2 seq 10027 lowscn 292276199 found to restore
RMAN-06025: no backup of log thread 2 seq 10026 lowscn 292235928 found to restore
RMAN-06025: no backup of log thread 2 seq 10025 lowscn 292195374 found to restore
RMAN-06025: no backup of log thread 2 seq 10024 lowscn 292155816 found to restore
RMAN-06025: no backup of log thread 2 seq 10023 lowscn 292116968 found to restore
RMAN-06025: no backup of log thread 2 seq 10022 lowscn 292077062 found to restore
RMAN-06025: no backup of log thread 2 seq 10021 lowscn 292036336 found to restore
?????????????????????????????????????????????????????????????
RMAN> exit;
Recovery Manager complete.
kilroy
![[knight] [knight] [knight]](/data/assets/smilies/knight.gif)
philippines
"Once a king, always a king. But being a knight is more than enough."