Recovery command in 9i

Hi ALL,
what is the correct syntax ....i get 'illegl recovery option until'
when i use
RECOVER DATAFILE 'COMPLETE FILENAME WITH PATH' UNTIL TIME '2006-01-28:16:00:00' ;
wHAT IS THE CORRECT ONE ?
Regards
Sunny

Hi, 
 
It seems that you need to read some documentation, I advise this one : 
Backup and Recovery Concepts 
 
Nicolas.

Similar Messages

Lion Recovery (Command R- reinstall Lion) Says 148 hours after being on for one day and over night

I accidently deleted some file on my computer that wouldn't let me start up my MacBook pro, 13 Inch, so I had to press Command- R at start up (brought me to Lion Recovery) and I choose reinstall lion and I started it yesterday morning and all day and over night. It's barely half way through and it says "148 Hours Left" which is crazy.. Should I just wait? is this normal? what do I do? Pleasee help someone!

It seems Apple is having problems with there servers or you have a Very Slow Internet connection. Best is to let it run as you can't use the computer anyway without the files you deleted.
There are reports of other that can not even get to the Lion download or any downloads for updates and such.

No service password recovery command on cisco 2801 router

HI,
we have a cisco 2801 router in class which has a disabled pasword recovery. We tried almost everything, we cannot get into ROMmon and the break sequence dosent work in any program (hyper terminal, putty, teraterm pro). We dont have any idea how to solve this problem.
Here is the log from hyperterminal:
System Bootstrap, Version 12.3(8r)T9, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2004 by cisco Systems, Inc.
PLD version 0x10
GIO ASIC version 0x127
c2801 processor with 131072 Kbytes of main memory
Main memory is configured to 64 bit mode with parity disabled
Readonly ROMMON initialized
PASSWORD RECOVERY FUNCTIONALITY IS DISABLED
program load complete, entry point: 0x8000f000, size: 0xc100
Initializing ATA monitor library.......
program load complete, entry point: 0x8000f000, size: 0xc100
Initializing ATA monitor library.......
program load complete, entry point: 0x8000f000, size: 0xd49718
Self decompressing the image : #################################################
######## [OK]
--- TRIED BREAK SEQUENCE HERE but nothing happens ---
Smart Init is enabled
smart init is sizing iomem
ID            MEMORY_REQ         TYPE
                0X003AA110 public buffer pools
                0X00211000 public particle pools
0X0013          0X00035000 Card in slot 1
                0X000021B8 Onboard USB
If any of the above Memory Requirements are
"UNKNOWN", you may be using an unsupported
configuration or there is a software problem and
system operation may be compromised.
Allocating additional 7692663 bytes to IO Memory.
PMem allocated: 117440512 bytes; IOMem allocated: 16777216 bytes
              Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
Cisco IOS Software, 2801 Software (C2801-IPBASE-M), Version 12.4(1c), RELEASE SO
FTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Wed 26-Oct-05 08:42 by evmiller
Image text-base: 0x6007ECA0, data-base: 0x61480000
--- TRIED BREAK SEQUENCE HERE but nothing happens too ---
Port Statistics for unclassified packets is not turned on.
Cisco 2801 (revision 6.0) with 114688K/16384K bytes of memory.
Processor board ID FCZ102422KK
2 FastEthernet interfaces
2 Low-speed serial(sync/async) interfaces
DRAM configuration is 64 bits wide with parity disabled.
191K bytes of NVRAM.
62720K bytes of ATA CompactFlash (Read/Write)
Press RETURN to get started!
Thanks for help!

I usually suffer from the same issue, but what works for me everytime is the other method that simulates break sequence. Can't find the documentation for it but this is how it goes:
Set the serial connection as follows in Putty:
Baud rate 1200
1 stop bit
8 data bits
no parity
no flow control
Turn off your router, then turn it back on and immediately press the spacebar for about 10-15 seconds. All you'll see is giberish. After that reset your console connection settings to the usual 9600 baud rate, and you'll find yourself in rommon mode.

Data Recovery for Macbook Air when repair efforts failed

My computer is unable to boot and stays on the gray screen. I've tried to repair my computer with every method up to disk utility but nothing will work, so I want to back up my computer if possible before reinstalling the software. I don't use time machine, so I was wondering if there is a way to do it by external hard drive.
Thank you for any suggestions!

There are several ways to back up a Mac that is unable to fully boot. You need an external hard drive to hold the backup data.
1. Boot into Recovery (command-R at startup) or from a local Time Machine backup volume (option key at startup.) Launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
How to back up and restore your files
2. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
How to use and troubleshoot FireWire target disk mode
3. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

HT4718 Is it possible to back up files onto an external hard drive while in internet recovery mode?

This morning, upon starting up my MacBook, I was greeted with the lovely gray screen. I'm in internet recovery mode and have attempted to repair my disk, but it's too damaged according to the disk utility. So, I'm going to have to reinstall OS X Lion. I'm worried about losing my files and bought a 500gb external hard drive in hopes that I can back up my files while in recovery mode and then erase and reinstall the operating system
Any help would be much appreciated!

There are several ways to back up a Mac that is unable to fully boot. You need an external hard drive to hold the backup data.
1. Boot into Recovery (command-R at startup; 10.7 or later), from a local Time Machine backup volume (option key at startup; 10.7.2 or later), or from your installation disc (C key at startup; 10.6.8 or earlier.) Launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
How to back up and restore your files
2. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
How to use and troubleshoot FireWire target disk mode
3. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

Mac OS X Lion (Late 2010) having Recovery screen freeze with spinnig wheel

I have a Mac Air purchased in December 2010 with Snow Leopard. I upgraded the OS to Lion and now running 10.7.4 version. I recently tried to use 'Disk Utility' feature to 'Verify' the disk which asked me to repair through 'Recovery HD' which is done by restarting the computer and pressing Command+R button until Apple logo appears. I did that but after some time Apple logo disappeared and "Do Not Distrub" logo (an O with a diagnol slash in between) appeared with a spinning wheel. This didn't change for more than 40 minutes after which I pressed the 'Power' button for few seconds and shut down the computer.
I tried doing this again but same sign appears with spinning wheel and no 'Disk Utility' window as described in recovery webpage in Apple support website.
Can someone help me figure out the issue??
Thanks.

There are several ways to back up a Mac that is unable to fully boot. You need an external hard drive to hold the backup data.
1. Boot into Recovery (command-R at startup; 10.7 or later), from a local Time Machine backup volume (option key at startup; 10.7.2 or later), or from your installation disc (C key at startup; 10.6.8 or earlier.) Launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
How to back up and restore your files
2. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
How to use and troubleshoot FireWire target disk mode
3. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

Intenet Recovery take initial start up data from somewhere on my iMac, not from Internet

Hello!
Was experimenting with Internet Recovery (Ctrl+R on startup) on my iMac.
After a few reintalls a spinning globe that usually appeared on the initial phase didnt appear anymore. Instead of that the Utilities load right after the initial startup procedure (after apple).
Anyone knows why this happened? Ever before during internet restoration a spinnig globe was shown. No amny more - Utilities start right after the apple on startup. Where are they stored?

The spinning globe only appears if you use internet recovery (command + option + R) and it directly accesses Apple's servers. You can use that if you need to reinstall the original OS version or have a blank drive (after installing a new hard drive for instance). The regular recovery is a hidden partition on your Mac made to do what you need it to do when you boot into it by hitting command + R and it will install the current OS version.

Recovery of thread 1 stuck at Block 113713 of file 643

Hi,
One day ago we had a Hardware problem with our Solaris Machine and 11g(11.1.0.7.0) Database.
Our Server crashed saying..
ORA-00376: file 643 cannot be read at this timeThe above error repeated for another file.
We checked file status and there was some problem(I/O errror when we gave ls command) while accessing the file.
Then we managed to restore that mount point.
and then we started database but the database failed to open saying below error.
RECOVERY OF THREAD 1 STUCK AT BLOCK 113713 OF FILE 643
Thu Jul 21 16:45:41 2011
RECOVERY OF THREAD 1 STUCK AT BLOCK 42896 OF FILE 644We checked V$recover_file, No file mentioned.we checked V$datafile all files status was online and enabled was read/write.Then we manually recover the failed data files by
ALTER DATABASE RECOVER datafile '/data/irsdata/undodbs03.dbf'
ALTER DATABASE RECOVER datafile '/data/irsdata/undodbs04.dbf'It succeeded with media recovery complete and then we were able to open Database.
Even if V$recover_file and V$datafile had not mentioned for above two problematic datafiles, why we had to do media recovery?
Any ideas?
Regards!
Edited by: Nitin Joshi on Jul 22, 2011 10:23 AM

Yes Hemant.
We all were Puzzled by that scenario.
Posting alert log stack(incomplete) when we try to open database.
MMAN started with pid=28, OS id=1277
Thu Jul 21 16:38:21 2011
DBW0 started with pid=2, OS id=1279
Thu Jul 21 16:38:21 2011
DBW1 started with pid=3, OS id=1281
Thu Jul 21 16:38:21 2011
DBW2 started with pid=32, OS id=1283
Thu Jul 21 16:38:22 2011
DBW3 started with pid=5, OS id=1285
Thu Jul 21 16:38:22 2011
LGWR started with pid=7, OS id=1287
Thu Jul 21 16:38:22 2011
CKPT started with pid=36, OS id=1289
Thu Jul 21 16:38:22 2011
SMON started with pid=40, OS id=1291
Thu Jul 21 16:38:22 2011
RECO started with pid=44, OS id=1293
Thu Jul 21 16:38:22 2011
MMON started with pid=48, OS id=1295
Thu Jul 21 16:38:22 2011
MMNL started with pid=52, OS id=1297
DISM started, OS id=1299
ORACLE_BASE from environment = /data87/ora11g/app/oracle
Thu Jul 21 16:38:27 2011
ALTER DATABASE   MOUNT
Setting recovery target incarnation to 1
Successful mount of redo thread 1, with mount id 2558427203
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Thu Jul 21 16:38:31 2011
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
parallel recovery started with 15 processes
Started redo scan
Completed redo scan
13775 redo blocks read, 631 data blocks need recovery
Started redo application at
Thread 1: logseq 112616, block 157510
Recovery of Online Redo Log: Thread 1 Group 1 Seq 112616 Reading mem 0
Mem# 0: /data1/irsdata/rlog1irs.dbf
Mem# 1: /data3/irsdata/rlog11irs.dbf
Thu Jul 21 16:38:34 2011
RECOVERY OF THREAD 1 STUCK AT BLOCK 113713 OF FILE 643
Thu Jul 21 16:38:34 2011
RECOVERY OF THREAD 1 STUCK AT BLOCK 42896 OF FILE 644
Completed redo application of 1.07MB
Thu Jul 21 16:38:48 2011
Non critical error ORA-48913 caught while writing to trace file "/data87/ora11g/app/diag/rdbms/irs/irs/trace/irs_p000_1307.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [5242880] reached
Writing to the above trace file is disabled for now on...
Thu Jul 21 16:38:48 2011
Non critical error ORA-48913 caught while writing to trace file "/data87/ora11g/app/diag/rdbms/irs/irs/trace/irs_p011_1329.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [5242880] reached
Writing to the above trace file is disabled for now on...
Thu Jul 21 16:39:03 2011
.Then once we gave below command the recovery worked.below is the alert log for the recovery command
ALTER DATABASE   MOUNT
Setting recovery target incarnation to 1
Successful mount of redo thread 1, with mount id 2558426450
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Thu Jul 21 17:20:18 2011
ALTER DATABASE RECOVER datafile '/data/irsdata/undodbs03.dbf'
Media Recovery Start
Fast Parallel Media Recovery NOT enabled
parallel recovery started with 15 processes
Recovery of Online Redo Log: Thread 1 Group 1 Seq 112616 Reading mem 0
Mem# 0: /data1/irsdata/rlog1irs.dbf
Mem# 1: /data3/irsdata/rlog11irs.dbf
Media Recovery Complete (irs)
Completed: ALTER DATABASE RECOVER datafile '/data/irsdata/undodbs03.dbf'
Thu Jul 21 17:21:00 2011
ALTER DATABASE RECOVER datafile '/data/irsdata/undodbs04.dbf'
Media Recovery Start
Fast Parallel Media Recovery NOT enabled
parallel recovery started with 15 processes
Recovery of Online Redo Log: Thread 1 Group 1 Seq 112616 Reading mem 0
Mem# 0: /data1/irsdata/rlog1irs.dbf
Mem# 1: /data3/irsdata/rlog11irs.dbf
Media Recovery Complete (irs)
Completed: ALTER DATABASE RECOVER datafile '/data/irsdata/undodbs04.dbf' it seems it applied all the data from online redolog.Should have been automatic(?) not required to do media recovery?
Regards!
Edited by: Nitin Joshi on Jul 22, 2011 10:46 AM
some typos

I lost all the recovery partition to recovery mac mini from beginning, what do I need to do? please help

I lost all my partitions to recovery my mac mini server, what do I need to do to put them back on? help Thanks

Did your Mac Mini come pre-installed with Mountain Lion? If so, use Internet Recovery (Command+Option+R) keys at restart. You should see a spinning globe. This will boot into Apple's server Recovery HD and let you reinstall ML. So, you will need an Internet connection. Your apps and data will not be touched as this will just install the OS on top of itself.
Backup your system first before doing the above.

Oracle Database Point intime recovery with File System backup.

Hi.. Experts...
We have shutdown the database and have take a file system backup on
09.10.2010 @ 10 AM.
We started the database and all the archive logs generated after that are already
available in archive directory till now.
We discovered there were some deletions took place. Yesterday evening at 4 PM.
Requirement.
We want to recover the database till yesterday 3.30 PM.
Can any one send steps to recover with above backup and available archive logs till 3.30 PM Yesterday.
Regards

Experts.....Nick Loy, Varadharajan M, Mark & Volker.............Thanks U Very Much.
TAIL END MESSAGE OF RECOVERY COMMAND
ORA-00279: change 11331655931 generated at 10/10/2010 11:30:56 needed for
thread 1
ORA-00289: suggestion : /oracle/D10/oraarch/D10arch1_123487_607825009.dbf
ORA-00280: change 11331655931 for thread 1 is in sequence #123487
ORA-00278: log file '/oracle/D10/oraarch/D10arch1_123486_607825009.dbf' no
longer needed for this recovery
Log applied.
Media recovery complete.
SQL>
SQL>
SQL> ALTER DATABASE OPEN RESETLOGS;
Database altered.
SQL>
SYSTEM RECOVERED TO DEMAND & RELEASED
T H A N K S -- T O -- E V E R Y O N E .
RGDS

Old 1760 With password recovery disabled, no way to factory reset

Hi
I have an old 1760 router with Password Recovery Functionality Disabled
I don't care about its actual configuration , I need factory reset
I Followed the well documented procedure :
Normal boot
Self decompressing the image : #################################################
################################################################ [OK]
Smart Init is disabled. IOMEM set to: 15
PMem allocated: 57042944 bytes; IOMem allocated: 10065920 bytes
              Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) C1700 Software (C1700-SV8Y7-M), Version 12.3(6d), RELEASE SOFTWARE (fc1
Copyright (c) 1986-2004 by cisco Systems, Inc.
Compiled Fri 15-Oct-04 03:46 by kellythw
Image text-base: 0x80008120, data-base: 0x81440804
Send break at this time , then :
Do you want to reset the router to factory default
configuration and proceed [y/n] ? y
Reset router configuration to factory default.
cisco 1760 (MPC860P) processor (revision 0x500) with 55706K/9830K bytes of memor
y.
Processor board ID FOC07450X9P (3881152211), with hardware revision 0000
MPC860P processor: part number 5, mask 2
Bridging software.
X.25 software, Version 3.0.0.
1 FastEthernet/IEEE 802.3 interface(s)
32K bytes of non-volatile configuration memory.
32768K bytes of processor board System flash (Read/Write)
WARNING:
Executing this command will disable password recovery mechanism.
Do not execute this command without another plan for
password recovery.
Are you sure you want to continue? [yes/no]: y
The router boot up normally anyway , still with original password unrecovered instead a fresh factory default.
Any hint please ?????
Thank you

Federico,
There is something quite strange going on but one thing has caught my attention in particular. This is a part of your transcript:
Send break at this time , then :
Do you want to reset the router to factory default configuration and proceed [y/n] ? y Reset router configuration to factory default.cisco 1760 (MPC860P) processor (revision 0x500) with 55706K/9830K bytes of memory.Processor board ID FOC07450X9P (3881152211), with hardware revision 0000MPC860P processor: part number 5, mask 2Bridging software.X.25 software, Version 3.0.0.1 FastEthernet/IEEE 802.3 interface(s)32K bytes of non-volatile configuration memory.32768K bytes of processor board System flash (Read/Write)WARNING:Executing this command will disable password recovery mechanism.Do not execute this command without another plan forpassword recovery.Are you sure you want to continue? [yes/no]: y
Notice that the first question is whether you want to erase the configuration - you respond with yes, and the router continues booting. The second question displayed clearly shows that the router continues loading the configuration file and in particular processes the no service password-recovery command.
What would happen if you answered with n to this second question, preventing the router from accepting the no password-recovery stored command? Could you reload the router afterwards and try the password recovery procedure again?
Also, if this router has a removable Flash card, would you be able to enter the ROMMON and set the configuration register to 0x2142 if you removed the card and tried booting the router?
Best regards,
Peter

실수로 TABLE을 DELETE 또는 DROP한 경우 복구 방법 (time-based recovery)

제품 : ORACLE SERVER
작성날짜 : 2004-07-29
PURPOSE
사용자의 실수로 중요한 데이타를 delete 하였거나, 테이블을 drop하였을
경우 복구하는 절차를 정리한 자료이다.
Explanation
사용 중인 database 의 archive log mode 여부를 다음과 같이 확인 후
archive log mode인지 아닌지에 따라 복구 방법이 달라진다.
os>svrmgrl
SVRMGR> connect internal;
SVRMGR> archive log list
Database log mode ARCHIVELOG
Automatic archival ENABLED
Archive destination ?/dbs/arch
Oldest online log sequence 2525
Current log sequence 2527
1. Archive mode인 경우 복구 방법
archive log mode로 운영중이면서 full backup및 archive file들이 모두
존재하는 경우 복구가 항상 가능하다.
이때 다시 다음과 같이 두가지의 경우를 구분하여 복구 작업을 수행할 필요가
있으며 아래에 각각의 경우에 대한 절차를 자세히 설명한다.
(1) drop이나 delete한 시점이 얼마 지나지 않았거나, 혹은 필요에 의해
database 전체를 data 손실 이전 시점으로 돌리고자 하는 경우
(2) 손실된 data만을 drop이나 delete이전 상태를 받아내고, 나머지 data는
모두 drop/delete이후 발생한 transaction의 반영분을 유지시키기 위해
현재 시점으로 맞추어햐 하는 경우
1-1 database 전체를 drop이나 delete 이전시점으로 돌리고자 할 때
이러한 경우는 데이타 손실이 발생하기 이전의 datafile들에 대한 backup을
restore한 후 손실 발생 시점 직전까지 time based로 imcomplete recovery를
수행하면 된다.
(1) db를 shutdown시킨 후 현재 상태를 만약의 경우를 대비하여 cold
backup을 받아둔다.
shutdown immediate로 db를 내리고, datafiles, redo log files, control
files 모두 tar등의 명령어를 이용하여 backup을 받아둔다.
이것은 만약의 경우 이전 backup이나 archive file에 문제가 있는 경우,
삭제된 data의 복구가 불가능할 경우 현재 상태로라도 돌리기 위한
것이다.
(2) 데이타를 삭제하기 이전 상태에서 받아둔 datafile full backup을
restore한다.
redo log files과 controlfiles은 현재 것을 그대로 이용하고, 현재
상태의 모든 datafiles을 지우고 데이타가 삭제되기 전에 받아둔
backup datafile을 restore시킨다.
(temp datafile의 경우는 restore시간을 줄이기 위해 restore하지
않아도된다.)
(3) restore한 backup시점 이후의 archive file들을 archive log
destination에 위치시킨다.
full backup 이후의 archive file들을 일부 tape 장비등에 backup을
받아두고 지운 상태라면 그러한 file을을 다시 원래 위치에 restore
하여, full backup받은 시점부터 복구하고자 하는 시점까지의
archive log file들이 모두 log archive destination에 존재하는지
확인한다.
(4) 데이타 삭제 이전 시점까지 time based로 recover를 수행한다.
이때 날짜와 시간 지정은 항상 아래 예와 같은 형식으로 지정한다.
만약 데이타를 삭제한 시간이후로 지정하게 되면 recovery후에도
여전히 data는 지워진 상태로 보여진다.
os>svrmgrl
SVRMGR> connect internal
SVRMGR> startup mount;
SVRMGR> set autorecovery on
SVRMGR> recover database until time '2001-01-30:21:00:00';
SVRMGR> alter database open resetlogs;
(a) 만약 이때, controlfile이 현재것이 존재하지 않아 datafile뿐
아니라, controlfile도 과거것을 사용했다면, recovery command를
다음과 같이 지정하면 된다.
recover database using backup controlfile (아래줄과 이어짐)
until time '2001-01-30:21:00:00';
(b) temp datafile을 restore하지 않은 경우라면 startup mount수행
직후 다음과 같은 문장을 추가하면 된다.
alter databse datafile '/oracle/oradata/temp01.dbf'
offline drop;
/oracle/oradata/temp01.dbf는 temp datafile의 이름을 예로 든
것이다.
(5) 원하는 data가 제대로 조회되는지 확인한다.
1-2. 삭제된 data만을 복구하고 나머지는 현재 상태를 유지하고자 하는 경우
이러한 경우는 데이타가 삭제되기 이전 상태의 backup datafile 중에
SYSTEM, RBS와 삭제된 data가 들어있는 datafile만을 restore시켜 time
based로 recovery하여 db를 open시킨 후 원하는 table만 export를 받아낸다.
그리고 다시 현재 상태의 db에 export받은 내용을 import시키는 것이다.
이때 삭제된 data를 export받기까지의 절차에 대해서 다음과 같이 세가지
경우의 방법을 생각할 수 있다.
(a) 다른 시스템에 backup이나 test용으로 oracle이 설치되어 있는 경우
그 시스템에 backup을 restore하여 해당 table을 export 받는 방법
(b) 같은 시스템에 backup을 restore 하되, db name과 oracle_sid를 다른
이름으로 변경하여 다른 db를 만들어 recovery후 open하여 export받는
방법 <Bulletin:11616 참조>
(c) 현재 db는 cold backup받아 두고, backup을 restore하여 export을
받아내는 방법
여기에서 (a)의 경우는 다른 시스템에 이용하고자 하는 datafile의 oracle
version 이상의 oracle software가 이미 설치되어 있어야 한다.
(b)의 경우는 현재 상태의 cold backup을 받았다가 export받은 후 다시
현재 상태를 restore할 필요는 없애주지만, 대신 SYSTEM, RBS, user
datafile 만큼의 disk space가 추가로 필요하며, 새로운 db를 추가로
구성하는 것이므로 init.ora file 구성 등의 작업이 필요하다.
이것에 관한 자세한 절차는 <Bulletin:11616>을 참조하도록 한다.
이 자료에서는 이중 (c)에 대한 것만을 자세히 설명한다.
(1) 현재의 모든 datafiles과 redo log files, datafiles을 다음과 같이
신중히 cold backup을 받아두도록 한다.
이것은 이후에 삭제한 data를 복구하여 export를 받은 후에 다시 현재
상태의 db로 되돌아오기 위한 것이다.
단 이 때 tar 등을 이용하여 cold backup하는 대신에 disk 상에 cold
backup을 받아 시간을 절약할 수 있다. disk로의 backup이 가능한
이유는 export를 위한 time based recovery를 수행하기 위해 필요한
datafile이 SYSTEM, RBS, 삭제된 data를 포함한 user datafile
정도이기 때문이다.
os>svrmgrl
SVRMGR> connect internal
SVRMGR> shutdown immediate;
SVRMGR> exit
os>cp /oracle/oradata/*.ctl /oracle/backup/*.ctl
os>cp /oracle/oradata/redo*.log /oracle/backup/redo*.log
os>mv /oracle/oradata/system01.dbf /oracle/backup/system01.bak
os>mv /oracle/oradata/rbs01.dbf /oracle/backup/rbs01.bak
os>mv /oracle/oradata/tools01.dbf /oracle/backup/tools01.bak
redo log file이나 controlfile의 경우는 time based recovery시에도
필요하므로 cp를 받아두고, datafile의 경우는 mv를 이용하도록 한다.
위의 예에 제시된 file이름들은 해당 환경에 맞게 변경되어야 하며,
tar를 이용하여 tape에 옮겨도 관계는 없으나, 단 cold backup에
해당하는 모든 datafiles, redo log files, control files를 받아두어야
한다.
(2) 삭제한 data가 존재할 당시에 받아둔 backup에서 SYSTEM datafile, RBS
datafile, 그리고 삭제한 table이 들어있는 datafile만을 restore한다.
redo log files과 controlfiles은 현재 것을 그대로 이용한다.
(3) restore한 backup시점 이후의 archive file들을 archive log
destination에 위치시킨다.
full backup 이후의 archive file들을 일부 tape 장비 등에 backup을
받아두고 지운 상태라면 그러한 file을을 다시 원래 위치에 restore
하여, full backup받은 시점부터 복구하고자 하는 시점까지의
archive log file들이 모두 log archive destination에 존재하는지
확인한다.
(4) restore하지 않을 datafile, 즉 SYSTEM, RBS, 삭제된 data를 포함하
는 user datafile을 제외한 모든 datafile은 모두 offline drop시키
고, 데이타 삭제 이전 시점까지 time based로 recover를 수행한다.
이때 날짜와 시간 지정은 항상 아래 예와 같은 형식으로 지정한다.
만약 데이타를 삭제한 시간이후로 지정하게 되면 recovery후에도
여전히 data는 지워진 상태로 보여진다.
os>svrmgrl
SVRMGR> connect internal
SVRMGR> startup mount;
SVRMGR> alter database datafile '/oracle/oradata/temp01.dbf'
offline drop; (윗줄과 이어짐)
SVRMGR> alter database datafile '/oracle/oradata/userdata05.dbf'
offline drop; (윗줄과 이어짐)
... 이와 같이 resotre하지 않은 datafile을 모두 offline drop시킨다.
SVRMGR> set autorecovery on
SVRMGR> recover database until time '2001-01-30:21:00:00';
SVRMGR> alter database open resetlogs;
만약 이때, controlfile이 현재것이 존재하지 않아 datafile뿐 아니라,
controlfile도 과거것을 사용했다면, recovery command를 다음과 같이
지정하면 된다.
SVRMGR>recover database using backup controlfile until time
'2001-01-30:21:00:00'; (윗줄과 이어짐)
(5) 원하는 data가 제대로 조회되는지 확인한 후 필요한 table을 export한다.
예를 들어 scott user의 dept table을 복구하고자 한것이었다면 다음과
같이 export를 받는다.
os>exp scott/tiger file=dept.dmp tables=dept log=deptlog1
(6) time based로 recovery후 open한 db는 shutdown하여 없애고 (1)번에서
받아둔 현재 상태의 backup을 restore한다.
shutdown은 immediate나 abort 모두 가능하며, shutdown후 restore한
SYSTEM, RBS, user datafile모두 삭제하고, 사용하던 controlfiles,
redo log files도 모두 삭제한다.
그리고 (1)에서 mv나 cp로 (혹은 tar로) 옮겨놓은 모든 datafiles,
controlfiles, redo log files를 원래의 directory와 이름으로
위치시킨다. SYSTEM, RBS, user datafile도 반드시 (1)번 상태의
현재 상태 backup을 restore하여야 한다.
(7) db를 startup시킨 후 (5)에서 받은 export내용을 import시킨다.
os>imp scott/tiger file=dept.dmp tables=dept ignore=y commit=y
log=deptlog2 (윗줄과 이어짐)
(8) 원하는 data가 제대로 조회되는지 확인한다.
2. No archive mode 로 운영할 경우 복구 방법
archive mode 로 운영하지 않았을 경우에는, 삭제한 data를 export 받아
두었거나, 혹은 data가 삭제 전 받아둔 cold backup이 존재하는 경우
복구가 가능하다.
(1) export가 존재하는 경우
다음과 같이 import한다. scott user의 dept가 삭제된 경우를 예로 들었다.
os>imp scott/tiger file=dept.dmp tables=dept ignore=y commit=y log=log1
(2) cold backup이 존재하는 경우
다른 시스템에 사용가능한 oracle engine이 설치되어 있다면, 그곳을
이용하거나, 혹은 현재 database를 backup받아둔후 현재 시스템에
restore하여 export를 받아낼 수 있다.
(1) 현재의 모든 datafiles과 redo log files, datafiles을 다음과 같이
신중히 cold backup을 받아두도록 한다.
이것은 이후에 삭제한 data를 복구하여 export를 받은 후에 다시 현재
상태의 db로 되돌아오기 위한 것이다.
단 이 때 tar 등을 이용하여 cold backup하는 대신에 disk 상에 cold
backup을 받아 시간을 절약할 수 있다. disk로의 backup이 가능한
이유는 export를 위한 time based recovery를 수행하기 위해 필요한
datafile이 SYSTEM, RBS, 삭제된 data를 포함한 user datafile
정도이기 때문이다.
os>svrmgrl
SVRMGR> connect internal
SVRMGR> shutdown immediate;
SVRMGR> exit
os>mv /oracle/oradata/*.ctl /oracle/backup/*.ctl
os>mv /oracle/oradata/redo*.log /oracle/backup/redo*.log
os>mv /oracle/oradata/system01.dbf /oracle/backup/system01.bak
os>mv /oracle/oradata/rbs01.dbf /oracle/backup/rbs01.bak
os>mv /oracle/oradata/tools01.dbf /oracle/backup/tools01.bak
위의 예에 제시된 file이름들은 해당 환경에 맞게 변경되어야 하며,
tar를 이용하여 tape에 옮겨도 관계는 없으나, 단 cold backup에
해당하는 모든 datafiles, redo log files, control files를 받아두어야
한다.
(2) 삭제한 data가 존재할 당시에 받아둔 backup에서 SYSTEM datafile,
RBS datafile, 그리고 삭제한 table이 들어있는 datafile만을
restore한다.
backup당시의 redo log files과 controlfiles도 restore하여야 한다.
(3) restore하지 datafile, 즉 SYSTEM, RBS, 삭제된 data를 포함하는 user
datafile을 제외한 모든 datafile은 모두 offline drop시키고,
database를 open시킨다.
os>svrmgrl
SVRMGR> connect internal
SVRMGR> startup mount;
SVRMGR> alter database datafile '/oracle/oradata/temp01.dbf'
offline drop; (윗줄과 이어짐)
SVRMGR> alter database datafile '/oracle/oradata/userdata05.dbf'
offline drop; (윗줄과 이어짐)
... 이와 같이 resotre하지 않은 datafile을 모두 offline drop시킨다.
SVRMGR> alter database open;
(4) 원하는 data가 제대로 조회되는지 확인한 후 필요한 table을 export
한다.
예를 들어 scott user의 dept table을 복구하고자 한 것이었다면
다음과 같이 export를 받는다.
os>exp scott/tiger file=dept.dmp tables=dept log=deptlog1
(5) exprot받아낸 database는 shutdown하여 없애고 (1)번에서 받아둔
현재 상태의 backup을 restore한다.
shutdown은 immediate나 abort 모두 가능하며, shutdown후 restore한
SYSTEM, RBS, user datafile모두 삭제하고, 사용하던 controlfiles,
redo log files도 모두 삭제한다.
그리고 (1)에서 mv나 tar로 옮겨놓은 모든 datafiles, controlfiles,
redo log files를 원래의 directory와 이름으로 위치시킨다.
(6) db를 startup시킨 후 (4)에서 받은 export내용을 import시킨다.
os>imp scott/tiger file=dept.dmp tables=dept ignore=y commit=y
log=deptlog2 (윗줄과 이어짐)
(7) 원하는 data가 제대로 조회되는지 확인한다.

How to load drivers in Windows 8 Recovery Environment??

Hi everyone,
I'm really stuck here with my HP dv7t-7200 laptop.. I'm running Windows 8 Pro (64-bit) & after a Windows Update reboot, I can't get to the start screen. The spinning balls continue for hours & hours. I know there's a recent restore point that I can
restore to, but I'm having trouble accomplishing this..
My laptop has a RAID array, so I need to load the storage driver in order for the Windows Recovery Environment to be able to see the hard drives. I don't see any options for doing this, can someone please help..? Here's where I'm at step-by-step:
1) Boot from Windows 8 DVD
2) Choose "Repair this computer"
3) Choose "Troubleshoot"
4) Choose "Advanced Options"
5) Choose "System Restore"
Step (5) gives an error message : "To use System Restore, you must specify which Windows installation to restore. Restart this computer, select an operating system, and then select System Restore"
I believe this is occurring b/c
Windows, as booted from DVD, can't see the logical hard drive. If I could figure out how to load the Intel storage driver from USB, I think Window-on-DVD would be able to find the restore point on my hard drive. In Windows 7 Recovery, there's an option to
"Load drivers" during a repair operation. Where is this option in Windows 8?
Here are further troubleshooting steps I tried, based on Internet search results:
A) How do I mount the USB stick (which has the RAID driver for the laptop)? The following link is old, but the steps work. I stopped after step 6.
Internet search : windows command prompt mount usb
http://www.ehow.com/how_8541121_mount-usb-drives-windows-xp.html
B) After navigating to the mounted USB drive & appropriate folder, how do I load the RAID driver for the laptop? The following link suggests to use pnputil.exe, but this program won't run in my Windows 8 DVD recovery environment command prompt.
In any case, is it true that if & when I'm finally able to load the RAID driver, then DISKPART should be able to mount the drive & System Restore should see the Windows installation & offer to repair it?
Internet search: load windows drivers from command prompt
http://superuser.com/questions/531594/windows-how-to-install-driver-from-recovery-command-prompt
Any help appreciated,
Thanks,
Brad

Sergey: WOW & thanks, you are definitely the man! I want you to know that you've solved a problem that three levels of MS tech support haven't been able to work out..
I worked with a level 2 tech agent for several days, 20 minutes at a time. He was going back & forth with level 3 support staff, getting ideas from them & passing on to me. The level 2 guy finally told me it's not possible to load drivers during a Windows
8 system restore & gave up on my support ticket.
The manager then called for customer satisfaction follow-up. He said he had confirmed that Windows 7 DVD had the ability to load drivers for System Restore, but unfortunately this feature was removed for Windows 8. I convinced him that even so, *someone* at
MS must know a way to to load drivers for System Restore. He said he'd take it on as a personal challenge & would find s/o to assist.
Shortly thereafter, I got a call from a guy saying he's in the Research department at MS. He was immediately familiar with my problem. He said that he had previously resolved it by breaking the RAID mirror in the BIOS, which would allow Windows 8 DVD to recognize
one of the drives as an ordinary SATA drive & then load a driver for it. As we started down that path in my BIOS, he became concerned that actually, breaking my RAID mirror might cause data loss. He said he'd get back to me (that was a couple of days ago)..
So the question in my original post is solved, thank you again.
P.S. I still can't get Windows 8 restored, and might after all just have to reinstall everything!
1) I followed your instructions exactly & indeed, System Restore found the Windows 8 installation.
2) I chose the latest restore point & executed the restore. Operation initialized successfully but then failed with a disk read error.
3) I quit the Restore, which caused auto-reboot. I followed your steps again but navigated this time to Repair / Troubleshooting / Advanced Options / Command Prompt
4) I ran DISKPART, then "list volumes" to determine boot drive letter = E: (on my system)
5) I exited diskpart, verified I was on a non-boot drive, & ran "chkdsk E: /X /F"
6) "Corrections to the file system" were made
7) For good measure, I ran "bootrec /FixMbr" & then "bootrec /FixBoot"
8) I exited the command prompt & navigated to System Restore. Same error message.
9) I followed your steps again, but navigated to Automatic Repair.
10) Automatic Repair -> "Windows couldn't load correctly"
Brad

Scn in recovery

Hi
1-)
If I restored a datafile which has higher scn then controlfile and datafiles.
I think The only way to open the db is to recreate a controlfile or copy the old controlfile.
Correct me if I am wrong.
2-)
If I recreate the controlfile how does oracle determine checkpoint scn of the datafiles?
3-)
Even I`ve just recreated a new controlfile and copy a datafile which has high scn then other datafiles.
When I check;
select CHECKPOINT_CHANGE# from v$datafile, all numbers are equal.
What is the reason for that?

Situation 1) would arise when you have backups of datafiles from different points in time and you restore almost all the datafiles from a set prior to the last backup but one datafile from the last backup. (you can't be restoring a datafile from the future ! so you can't have restore a datafile with a higher SCN than the current SCN, ergo, the other datafiles have also been restored from a backup older than this one !)
In this case,
a) if you restore the controlfile, you use the "USING BACKUP CONTROLFILE" clause.
b) if you recreate the controlfile, you use the "USING BACKUP CONTROLFILE" clause.
(ie, the RECOVERY command is the same !)
2) : Oracle reads the datafile headers. It uses this information to determine the lowest SCN in the datafiles and identify which Log Sequence Numbers are required for recovery. Don't think of whether "oracle uses datafile headers to create the controlfile" {although it DOES do so}. Think of "oracle uses the datafile headers to determine SCNs and LSNs for Recovery !".
3) : Checkpoint Change# is as of the last Checkpoint. A Checkpoint could be a system checkpoint ("ALTER SYSTEM CHECKPOINT") or a Checkpoint initiated by a Log Switch or an Incremental Checkpoint (because of FAST_START_MTTR_TARGET) or a Tablespace Checkpoint (ALTER TABLESPACE command) or a Datafile checkpointed (ALTER DATABASE DATAFILE command). (Note : You will not see Incremental Checkpoints in the V$DATAFILE_HEADER)
Here's one example below. Notice one datafile having a different CHECKPOINT_CHANGE# with the ALTER TABLESPACE command.
SQL> select checkpoint_change# from v$datafile_header;
CHECKPOINT_CHANGE#
           1183007
           1183007
           1183007
           1183007
           1183007
           1183007
6 rows selected.
SQL> alter tablespace users begin backup;
Tablespace altered.
SQL> select checkpoint_change# from v$datafile_header;
CHECKPOINT_CHANGE#
           1183007
           1183007
           1183007
           1204726
           1183007
           1183007
6 rows selected.
SQL> alter tablespace users end backup;
Tablespace altered.
SQL> select checkpoint_change# from v$datafile_header;
CHECKPOINT_CHANGE#
           1183007
           1183007
           1183007
           1204726
           1183007
           1183007
6 rows selected.
SQL> Hemant K Chitale
http://hemantoracledba.blogspot.com
Edited by: Hemant K Chitale on May 31, 2009 11:41 PM

Cannot access recovery partition after enabling filevault

I did a clean install of Lion by extracting the disk image to an external Firewire drive, using disk utility to reparition my Macbook Pro's internal drive to a single, blank HFS+ parition, and then installed Lion to that partition from the external firewire drive. It worked flawlessly. At that point, without the firewire drive plugged in, I could boot to Lion, and if I held option while starting the computer, I could also see the recovery parition as an option to boot into.
After that, I used Bootcamp to install Windows, which resized my Lion partition. After that, I enabled FileVault. Everything went resonabley well: The Lion partition is now encrypted, and Windows still works, and the computer is functioning, however when holding option at boot, the only options I see are Lion and Windows. The Recovery boot option is no longer visible. I don't know if it was the act of using Bootcamp, or Filevault (or the combination of both) that caused it to dissapear, but I changed nothing else that I can think of.
I'm resonabley certain the actual recovery partition is still there. The diskutil list command outputs the following:
Lownins-MacBook-Pro:~ Lownin$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *320.1 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:          Apple_CoreStorage                         259.0 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data Windows                 60.2 GB    disk0s4
My question is: How do I re-enable the Apple_Boot Recovery partition as a boot option from the "option key while booting" menu?

OS X Lion: About FileVault 2
OS X Lion: Using FileVault 2 and Lion Recovery
Command-R

Recovery command in 9i

Similar Messages

Maybe you are looking for