Flash Recovery - SYSTEM.DBF
Hi!
How can I repair the C:\ORACLEXE\APP\ORACLE\ORADATA\XE\SYSTEM.DBF file?
Drumboy
sqlplus
SQL*Plus: Release 11.2.0.2.0 Beta on K. J˙l. 31 18:43:26 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Enter user-name: /as sysdba
Connected to:
Oracle Database 11g Express Edition Release 11.2.0.2.0 - Beta
SQL> startup;
ORACLE instance started.
Total System Global Area 577511424 bytes
Fixed Size 1385040 bytes
Variable Size 369102256 bytes
Database Buffers 201326592 bytes
Redo Buffers 5697536 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open RESETLOGS;
alter database open RESETLOGS
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'C:\ORACLEXE\APP\ORACLE\ORADATA\XE\SYSTEM.DBF'
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 14038427 generated at 07/31/2012 11:20:36 needed for thread 1
ORA-00289: suggestion :
C:\ORACLEXE\APP\ORACLE\PRODUCT\11.2.0\SERVER\RDBMS\ARC0000000450_0773153579.0001
ORA-00280: change 14038427 for thread 1 is in sequence #450
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
SQL> select l.status, member
*2 from v$logfile inner join v$log l using (group#);*
STATUS MEMBER
UNUSED C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AR
EA\XE\ONLINELOG\O1_MF_1_7KO9RW0Z_.LOG
CURRENT C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AR
EA\XE\ONLINELOG\O1_MF_2_7KO9RWX9_.LOG
950118 wrote:
1. This database has worked without error for 6 months. This morning didn't start.
2. Because there are a lot of recorsd in database
3. [url http://www.drumboy.hu/alert.log] alert.log
Nope, it doesn't make sense. You have told us the outcome of something that you have done because of some error that you had got earlier. This is the last output which you have posted. Questions for you, do you have a valid backup and is your db is in the archivelog mode? Post all the details what you have done so far.
Aman....
Similar Messages
-
Flash Recovery Area On 11.5.10.2
Hello,
We are running 11.5.10.2 on window 2003 server 32-bit,we save backup on flash_recovery area which size is 91 GB,total file system size on window of flash recovery area is 190GB.When i check the space on file system it show me 84 GB free space,I want to ask then where is 27 GB space,because backupset size is 2.70GB autobackup size is 128 MB and datafile size is 79 GB.
Please help me out.
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
2745 B F A DISK 23-SEP-13 1 1 NO TAG20130923T233305
2747 B F A DISK 24-SEP-13 1 1 NO TAG20130924T203609
2749 B F A DISK 26-SEP-13 1 1 NO TAG20130926T194832
2751 B F A DISK 27-SEP-13 1 1 NO TAG20130927T214235
2753 B F A DISK 08-OCT-13 1 1 NO TAG20131008T184055
2754 B 1 A DISK 09-OCT-13 1 1 NO ORA\$OEM_LEVEL_0
2755 B F A DISK 09-OCT-13 1 1 NO TAG20131009T225822
Regards,
MerriHello,
report obsolete show's
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 2745 23-SEP-13
Backup Piece 2745 23-SEP-13 I:\FLASH_RECOVERY\APPPROD\AUTOBACKUP\C-1628308050-20130923-00
Backup Set 2747 24-SEP-13
Backup Piece 2747 24-SEP-13 I:\FLASH_RECOVERY\APPPROD\AUTOBACKUP\C-1628308050-20130924-00
Backup Set 2749 26-SEP-13
Backup Piece 2749 26-SEP-13 I:\FLASH_RECOVERY\APPPROD\AUTOBACKUP\C-1628308050-20130926-00
Archive Log 135874 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98760_578172119.DBF
Backup Set 2751 27-SEP-13
Backup Piece 2751 27-SEP-13 I:\FLASH_RECOVERY\APPPROD\AUTOBACKUP\C-1628308050-20130927-00
Archive Log 135876 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98761_578172119.DBF
Archive Log 135878 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98762_578172119.DBF
Archive Log 135880 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98763_578172119.DBF
Archive Log 135882 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98764_578172119.DBF
Archive Log 135884 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98765_578172119.DBF
Archive Log 135886 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98766_578172119.DBF
Archive Log 135888 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98767_578172119.DBF
Archive Log 135890 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98768_578172119.DBF
Archive Log 135892 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98769_578172119.DBF
Archive Log 135894 03-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98770_578172119.DBF
Archive Log 135896 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98771_578172119.DBF
Archive Log 135898 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98772_578172119.DBF
Archive Log 135900 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98773_578172119.DBF
Archive Log 135902 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98774_578172119.DBF
Archive Log 135904 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98775_578172119.DBF
Archive Log 135906 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98776_578172119.DBF
Archive Log 135908 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98777_578172119.DBF
Archive Log 135910 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98778_578172119.DBF
Archive Log 135912 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98779_578172119.DBF
Archive Log 135914 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98780_578172119.DBF
Archive Log 135916 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98781_578172119.DBF
Archive Log 135918 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98782_578172119.DBF
Archive Log 135920 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98783_578172119.DBF
Archive Log 135922 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98784_578172119.DBF
Archive Log 135924 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98785_578172119.DBF
Archive Log 135926 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98786_578172119.DBF
Archive Log 135928 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98787_578172119.DBF
Archive Log 135930 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98788_578172119.DBF
Archive Log 135932 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98789_578172119.DBF
Archive Log 135934 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98790_578172119.DBF
Archive Log 135936 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98791_578172119.DBF
Archive Log 135938 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98792_578172119.DBF
Archive Log 135940 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98793_578172119.DBF
Archive Log 135942 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98794_578172119.DBF
Archive Log 135944 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98795_578172119.DBF
Archive Log 135946 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98796_578172119.DBF
Archive Log 135948 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98797_578172119.DBF
Archive Log 135950 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98798_578172119.DBF
Archive Log 135952 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98799_578172119.DBF
Archive Log 135954 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98800_578172119.DBF
Archive Log 135956 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98801_578172119.DBF
Archive Log 135958 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98802_578172119.DBF
Archive Log 135960 04-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98803_578172119.DBF
Archive Log 135962 05-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98804_578172119.DBF
Archive Log 135964 05-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98805_578172119.DBF
Archive Log 135966 05-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98806_578172119.DBF
Archive Log 135968 05-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98807_578172119.DBF
Archive Log 135970 05-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98808_578172119.DBF
Archive Log 135972 05-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98809_578172119.DBF
Archive Log 135974 06-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98810_578172119.DBF
Archive Log 135976 06-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98811_578172119.DBF
Archive Log 135978 06-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98812_578172119.DBF
Archive Log 135980 06-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98813_578172119.DBF
Archive Log 135982 06-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98814_578172119.DBF
Archive Log 135984 07-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98815_578172119.DBF
Archive Log 135986 07-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98816_578172119.DBF
Archive Log 135988 07-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98817_578172119.DBF
Archive Log 135990 07-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98818_578172119.DBF
Archive Log 135992 07-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98819_578172119.DBF
Archive Log 135994 07-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98820_578172119.DBF
Archive Log 135996 07-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98821_578172119.DBF
Archive Log 135997 07-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98822_578172119.DBF
Archive Log 136000 07-OCT-13 F:\******\1_98823_578172119.DBF
Archive Log 136002 08-OCT-13 F:\\1_98824_578172119.DBF
Archive Log 136004 08-OCT-13 F:\********\1_98825_578172119.DBF
Archive Log 136006 08-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98826_578172119.DBF
Archive Log 136008 08-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98827_578172119.DBF
Archive Log 136010 08-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98828_578172119.DBF
Archive Log 136012 08-OCT-13 F:\ARCHIVELOGS\APPPROD\1_98829_578172119.DBF
Backup Set 2753 08-OCT-13
Backup Piece 2753 08-OCT-13 I:\FLASH_RECOVERY\APPPROD\AUTOBACKUP\C-1628308050-20131008-00
NAME
SPACE_LIMIT
SPACE_USED
SPACE_RECLAIMABLE
NUMBER_OF_FILES
I:\flash_recovery\
97710505984
83336011776
0
47
Regards,
Merri -
Changing the location of archive log from flash recovery area PLZ HELP!!!
Hi All,
My archive log is being stored in flash memory area which got full and the production server went down.
alert log file details.....
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
*** 2010-04-25 14:22:49.777 62692 kcrr.c
ARCH: Error 19809 Creating archive log file to
'/oracle/product/10.2.0/flash_rec
overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
*** 2010-04-25 14:22:49.777 60970 kcrr.c
kcrrfail: dest:10 err:19809 force:0 blast:1I removed the files and started the database,
Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
I want to change the location of archive log files, can someone please guide me as to hiow to do that
I changed the size of flash recovery area for the time being, but i am afraid it will be full again!!
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE 0 0 0
ONLINELOG 0 0 0
ARCHIVELOG 99.44 0 57
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0
6 rows selected.
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
System altered.
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE 0 0 0
ONLINELOG 0 0 0
ARCHIVELOG 49.72 0 57
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0
6 rows selected.regards,
Edited by: user10243788 on Apr 25, 2010 6:12 AMuser10243788 wrote:
Hi All,
My archive log is being stored in flash memory area which got full and the production server went down.
alert log file details.....
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
*** 2010-04-25 14:22:49.777 62692 kcrr.c
ARCH: Error 19809 Creating archive log file to
'/oracle/product/10.2.0/flash_rec
overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
*** 2010-04-25 14:22:49.777 60970 kcrr.c
kcrrfail: dest:10 err:19809 force:0 blast:1I removed the files and started the database,
Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
I want to change the location of archive log files, can someone please guide me as to hiow to do that
I changed the size of flash recovery area for the time being, but i am afraid it will be full again!!
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE 0 0 0
ONLINELOG 0 0 0
ARCHIVELOG 99.44 0 57
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0
6 rows selected.
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
System altered.
SQL> select * from v$flash_recovery_area_usage;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
CONTROLFILE 0 0 0
ONLINELOG 0 0 0
ARCHIVELOG 49.72 0 57
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0
6 rows selected.regards,
Edited by: user10243788 on Apr 25, 2010 6:12 AMPointing the archive log dest (and/or the FRA) to a new location, or enlarging them, will do no good if you are not performing regular housekeeping on the archivelogs. You will just keep knocking down the same problem over and over.
If you simply delete the archivelogs at the OS level, the database will never know about it and it will continue to think the destination is full, based on records kept in the control file.
For regular housekeeping, you need to be doing something similar to this in rman:
run {
backup archivelog all not backed up 1 times tag='bkup_vlnxora1_arch';
delete noprompt archivelog all backed up 1 times to device type disk;
run {
delete noprompt obsolete;
crosscheck archivelog all;
delete noprompt expired archivelog all; -
Flash recovery area issue. I can not open the database??
Hi all
I am using oracle 11.2.0 .1.0 on windows
when i tried to start the database I got the following error.
ORA-03113: end-of-file on communication channel
I clear out all information in Trace file. I cleared out all operating system level audit trails. then i deleted archivelog files using operating system level delete. still my database is not opening???
I tried to start this using RMAN but got the same error. now i have deleted the files from flash recovery area how can i let oracle system to know that those are deleted and there is enough space. Rman does not execute crosschek commands at mount state of the database?
Need solution.
Regards
MAlikmalikdba wrote:
the last option which ask to delete the files. i already have deleted the files at operating system level. now the issue is how to let the system that the space is free in flash recovery area? rman is not running crosscheck command at mount stage of the target database. What steps should i follow now?
Thanks
malik
Are you saying you are getting an error while trying to crosscheck at mount? Or you simply don't believe it will work?
oracle:orcl$ rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Thu Jul 11 10:52:48 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
RMAN> startup mount;
Oracle instance started
database mounted
Total System Global Area 839282688 bytes
Fixed Size 2231128 bytes
Variable Size 503317672 bytes
Database Buffers 331350016 bytes
Redo Buffers 2383872 bytes
RMAN> crosscheck archivelog all;
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
specification does not match any archived log in the repository
RMAN>
A perfectly normal crosscheck at the mount stage -
Help me,ANYONE!
I was a fool thinking downloading OS X MAVERICKS offline would be easy if I cleared my WHOLE HD, WELL the past 2 days ive been trying to figure it out in disk utilities and in terminal to run os x mavericks installer but nothing will work, it also says OS X cant be installed because a recovery system cant be crested.... plzz... someone help.. idk, ive been pretty **** emotional about this and about to throw laptop out the window..
Macbook pro
Specs are mid 2010 15" screen.This might depend on how you made your installer. If it is a flash pen installer that you made yourself, depending on how you made it, it has consequences on what is installed.
I am assuming that you have made an installer?
If you have and you did it manually, without using the Terminal command then it is a know caveat that a recovery partition is not installed as part of that procedure. The second method to create a bootable installer, using Terminal, will allow and install a recovery partition.
See here (without Terminal): http://www.macworld.com/article/2151706/create-a-bootable-mavericks-install-driv e-for-newer-macs.html
& here (with Terminal): http://www.macworld.com/article/2056561/how-to-make-a-bootable-mavericks-install -drive.html
Alternatively, have you zapped the PRAM and SMC, prior to trying to install?
See here: About NVRAM and PRAM
Some of these might help or even answer your query...
Good luck. -
How to use Flash recovery area only for flashback database feature
I would like to use flash recovery area only for flashback database feature, which means, flash recovery area will store only flashback logs.
I dont want to use that file system for any other files, like archive log files, database backups, control file copies, multiplex redo log, etc
is it possible? I want to use this feature only for flashback database option and hence i dont want to disturb any existing configuration in my database
including backup jobs. Is it required to store archive redo log files also in flash recovery area to use the flashback database feature?
I certainly can't afford to have a copy of entire database in this file system as size of my DB is more than the flash recovery area file system I have.
Thanks
Sarayuuser13312943 wrote:
Aman,
I think i was not clear in my question. Let me try again
My only requirement is to use flashback database feature (or be prepared to use if required). I dont want to create a large file system to use this FRA to store all these files. Out of all the files being stored here copy of data files seems to be consuming more space. I see these files are classified as transient and permanent files. I am okay with permanent files. I fear that this file system may consume more space if i store backup files on disk. I want database backups to go to tapes, not to the FRA disk. Is it possible?
Thanks for your reply
Okay, well in that case you can use RMAN and push the backups to the tape drives. FLB logs would be stored on the FRA.
Aman.... -
"Recovery system can't be created" error when reinstalling Lion from recovery system
I get the infamous OS installation error "Install failed... because a recovery system can't be created" – but in fact, the recovery system already exists, since I'm installing from it, and incidentally, I've previously already used it for an Internet reinstallation. I've tried about a half dozen iterations now.
Here's the exact sequence of events:
Reboot on recovery drive.
Select option to reinstall the OS from the network.
License agreement, etc; then select drive -> install -> sign into Apple store.
"Downloading additional components" message. 1st attempt consistently fails at this stage, need to restart at step 2.
Download for roughly 20 minutes, then automatic reboot -> "Installing Mac OS X".
After about 10 minutes: "Install failed. Mac OS X could not be installed on your computer. Mac OS X can't be installed on the disk ..., because a recovery system can't be created. Visit www.apple.com/support/no-recovery to learn more."
I've pawed through innumerable posts of people who have gotten the same error message, but haven't found one that reproduces my circumstances. I've reviewed the KB articles "OS X: About OS X Recovery" and "OS X Lion: Installer reports This disk cannot be used to start up your computer", with no luck. Based on a suggestion in the second KB article, I've reduced the primary partition size by roughly a GB and retried - no luck.
See this thread if you want to know why I'm reinstalling the OS, even though it's (more or less) functioning and I have Time Machine backups. It would also make me feel a lot better to know that the reinstallation would work in case of real need. Thanks in advance for any help.
-- PhilPhilip Keller wrote:
John,
I think I'm "reinstalling OS X by booting OS X Recovery": I reboot with command-R depressed, or I reboot with Alt depressed and choose the recovery parition, and then I start the installation process from the list of things I can do. Are we talking about the same thing?
Yes, exactly.
I think that OS X Internet Recovery would be necessary only if you were to attempt a Lion installation with a completely empty HD, implying that even a Recovery partition has not been created. Your USB flash drive is the way to cope in that circumstance. If you can install Lion by booting the recovery partition as you described, it seems to me that it is all that is necessary and there is nothing to fix, despite the error message you see.
I'm surprised that Internet Recovery works at all, given that your Mac is not one of those allegedly eligible to use it.
Without a similar 2006 iMac to test, I can only speculate that the "abysmal distribution system" as baltwo describes it just doesn't work well with earlier Macs, and that Apple may not have tested it extensively with them. If I were you I would rely upon that USB installer much more than OS X Recovery or OS X Internet Recovery. I prefer not to rely upon any installation method that can possibly result in "the server is not available at this time" or such nonsense, but that is the direction in which Apple has been going for a long time.
An OS X installation log exists at /var/log/ that you can examine using Console, probably named "install.log". Deciphering it is another challenge. -
How to recreate SYSTEM.DBF if it's broken
My databse is in ARCHIVE mode and i have lost just SYSTEM.DBF. What can I do? I've tried the ALTER DATABASE CREATE DATAFILE but recreation of the SYSTEM.DBF can't be done such way.
Aslo I woild be obligue for helping me in such problem:
I've backed up my DB, but i such way:
-whole Ora81 directory
-whole admin directory
-and all archived redo logs,
(I've used ARCServe to do the backup, and oracle client backed up the DB such way).
Main question is how to recover DB from such backup?
best regards to allI assume you have backed up all your data files too; you don't explicitly say that you did.
When you lose a SYSTEM tablespace data file, your recovery options are dramatically limited. You must recover your latest good back up of the missing data files, mount the database and recover before you can open the database.
Since this is a SYSTEM tablespace data file, you will not be able to open the database in much of any capacity without recovering first. Your efforts to recreate a black datafile are not productive efforts.
If you are responsible for your database and its contents matter then you you must read all you can and practice, practice, practice. Recovery options vary significantly between versions, and you must tune in your studying to your version. The concepts between all versions are remarkably similar, so once you master one version you will be OK on the others in any pinch.
Here's a good place to start reading:
http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/server.920/a96519/toc.htm
Paying money and taking a course is highly recommended for this topic - it isn't an intuitive process that most people can assume they will learn rapidly - if if they learn other technical concepts quickly. Some get, and some don't.
Michael -
How the 865p neo POST F10 Flash Recovery work...
i saw this "F10 Flash Recovery" option for my 865p neo board when the system start POST.
check through the User's Guide and i can't find any info about the "F10 Flash Recovery" thing...?(
how about other 865pe and 875p boards???
are all newer 865/875 boards come with the "F10 Flash Recovery" when POST???
how this thing work???
how come the User's Guide never mention???
anyone got any idea how this thing work???
thank...Quote
did a serch in the neyt and only find this got a bit info about the F10 thing http://si.tatung.com.tw/%E9%A9%85%E5%8B%.../AWD/Readme.txt
1. Make a bootable system floppy disk by typing [FORMAT A:/S] from the DOS prompt.
2. Download the BIOS file from MSI web page.
3. Extract the BIOS file into the bootable floppy.
4. Boot up system with the bootable floppy disk.
5. Run Award (Ex. Awdfl770) or AMI (Ex. amifl822.exe) Flash utility & follow the on-screen
instructions.
6. After flashing the BIOS, reboot system, press [DEL] to go into BIOS setup.
7. Select [Load Setup Default] for or [Load Optimized Defaults] and press Key [Enter] and
press Key [Y].
8. Press Key [F10] than answer [Y] to reboot system again and finish upgrade procedure.
I think this F10 key (above) is (a shortcut key for [save & exit] inside BIOS). -
Clean Install: Recovery system can't be created
I have a late 2007 white Macbook. I installed a 320 GB drive into the optical bay and my O/S drive was a 120 GB OCZ Vertex+
I had previously had a Crucial M4 as the OS drive for months. I used SuperDuper to clone it to the OCZ about a week ago and had no problems.
The system was running fine until a few days ago when it started acting weird, so I tried to reboot. I got the blinking folder with a question mark and couldn't do anything else. I was able to recover some of my data off of the SSD using my brother's MBP and DiskWarrior. I also created a 4 GB Lion bootable USB.
I erased the SSD using disk utility and then tried to run the installation, but I keep getting "Mac OS X can't be installed on the disk XXXX, because a recovery system can't be created."
Any help would be much appreciated.Well, you cannot see the Recovery HD partition and formatting (erasing) the drive does not remove it. Only partitioning the drive will remove it. The error you are getting is the error produced when there is another partition on the drive that cannot be altered or the drive is not prepped correctly or a Recovery HD partition already exists or there is something corrupted on the drive.
I suggest that you boot from your installer flash drive and use Disk Utility to repartition the SSD:
Drive Preparation
1. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. When done quit DU and return to the main menu. Select Reinstall Lion and click on the Continue button. When prompted click on the option to See Other Disks then select the SSD as the target. -
Support debacle: Account recovery system
Who, I wonder, is the genious at Microsoft that thought up the thoroughly useless account recovery system?
I signed out of Skype, then when I tried to log back in I realized I couldn't remember my password (it usually signs me in automatically).
No problem, I thought, they will have an account recovery system in place. So off I went to the support page, input my email address and was promptly sent a link and security code.
Great, I thought.... follow the link and...
"Sorry we cannot find your details"
wtf!
so I try to log into skype using my microsoft account and it finds my skype account and asks me to merge it, but I need my password to do it... d'oh!
I also need to log into skype to get any sort of help, including NOT BEING ABLE TO LOG INTO SKYPE!!!!
so now I have lost my contacts and because I tried to log in a few times unsuccessfully I now have to wait 24hrs before I can try again.
Genious....
PS, this is a newly created account.
Subject/title amended for clarity.Philip Keller wrote:
John,
I think I'm "reinstalling OS X by booting OS X Recovery": I reboot with command-R depressed, or I reboot with Alt depressed and choose the recovery parition, and then I start the installation process from the list of things I can do. Are we talking about the same thing?
Yes, exactly.
I think that OS X Internet Recovery would be necessary only if you were to attempt a Lion installation with a completely empty HD, implying that even a Recovery partition has not been created. Your USB flash drive is the way to cope in that circumstance. If you can install Lion by booting the recovery partition as you described, it seems to me that it is all that is necessary and there is nothing to fix, despite the error message you see.
I'm surprised that Internet Recovery works at all, given that your Mac is not one of those allegedly eligible to use it.
Without a similar 2006 iMac to test, I can only speculate that the "abysmal distribution system" as baltwo describes it just doesn't work well with earlier Macs, and that Apple may not have tested it extensively with them. If I were you I would rely upon that USB installer much more than OS X Recovery or OS X Internet Recovery. I prefer not to rely upon any installation method that can possibly result in "the server is not available at this time" or such nonsense, but that is the direction in which Apple has been going for a long time.
An OS X installation log exists at /var/log/ that you can examine using Console, probably named "install.log". Deciphering it is another challenge. -
Proper layout of datafiles, archivelogs, flash recovery area
Hi all,
Sorry a bit of a newb,
Have a question about how to layout my db files.
My understanding is that control and archivelog files should be multiplexed to a separate disk than the datafiles.
Is this also true for the flash_recovery_area?
Thanks for any help.geeter wrote:
Hi all,
Sorry a bit of a newb,
Have a question about how to layout my db files.
My understanding is that control and archivelog files should be multiplexed to a separate disk than the datafiles.
Is this also true for the flash_recovery_area?
Thanks for any help.Lose your control file or your redo file, and you have a problem. Therefore, in a professional environment, the control file and redo logs need to be protected by multiplexing to different physical drives (not different partitions on same disk). One of those locations can be the same DASD as the database files.
Archivelogs should be bounced from online to nearline to offline storage. These days 'online' is inside flash recovery area. If you are paranoid, you can send archivelogs to multiple destinations (multiplex), although some form of disk protection (RAID 1 ... or 5 - ugh!) should be sufficient.
Flash Recovery Area can be inside ASM or on regular file system. If in ASM, consider using either RAID 1 under ASM and external failgroups, or normal failgroup mode to allow the system to do it's own RAID 1 equivalent. If on regular file system, use standard disk protection (RAID 1 or 5) to do the protection.
Oracle uses the SAME (Stripe and Mirror Everything) philosophy, so separating Fast Recovery Area (new name - used to be Flash Recovery Area in the ancient days of Oracle 10g) from database files is not needed.
Highly recommend you read the first chapter of the Database Concepts Manual and the first chapter of the Database Administrator Guide to get used to the docs, adn then use that as a pringboard (via table of contents) to the sections that answer your question. Start at http://tahiti.oracle.com to get to those docs - they are on the front page of the doc set for your favorite version. -
Changing the location of the Flash Recovery Area
My flash recovery area is currently on the same disk as the database. The recovery area also has all out backups for the past month. What's steps should I take to change location of the flash recovery area? Do I have to do anything besides changing db_recovery_file_dest? Would I have to update the control files, spfile and so on?
Thanks in advance,you can make the change at pfile or spfile level and stop and restart the database. this should work.
-
I had to change my hard drive in my MBP 15". I use Time Machine on a Time Capsule for backup. I am booting up my laptop with a bootable USB key. I have partitioned my new hard drive (bigger than the old one) and named it Macintosh HD (same as the old one). I select the option to restore from Time Machine Backup. I select one of my latest backup....select my destination drive...the restore process starts but stop within minutes with the following message. "An error occurred while adding a recovery system to the destination disk" It then prompts me to restart....
I need your help...what can it be.
ThanksI've encountered this issue when the Time Machine was encrypted with FileVault.
Article: HT4718
Additional Information
Please note that OS X Recovery must be present on the computer's startup volume in order to use FileVault 2. Using RAID partitions or a non-standard Boot Camp partition on the startup disk may prevent OS X from installing a local Recovery system. See "OS X: Some features of Mac OS X are not supported for the disk (volume name)" for more information.
What seems to work, is reinstalling the OSX from the internet, and then using migration assistant to pull the user from the time machine backup external when logged into a temporary administrator user to move the original user back over.
Perhaps if you're stubborn, what would work is the following from the same article:
What to do if the installer warns that no Recovery System can be created
Some disk partition configurations may result in the OS X installer reporting that it could not create a Recovery System. In these situations, even if you are permitted to continue the install, you may want to quit the installation and create an external, bootable OS X hard drive with a Recovery System, first. You can continue your OS X upgrade on your computer's startup drive after creating an external Recovery System.
Your storage device must have at least 13 GB available (after formatting) to install OS X Lion or later and a Recovery partition.
These steps erase and reformat the storage device. This article instructs you on setting up a storage device to use the GUID partition scheme and the Mac OS Extended (Journaled) format, which are required to install OS X and a Recovery partition on your external storage device. You should back up any important files that are on the device to a different drive.
This procedure installs a version of OS X that is compatible with the Mac it was created with. Using this OS X system with a different Mac model may produce unpredictable results.
Your computer's serial number is sent to Apple as part of this process to help authenticate your request to download and install OS X Lion.
All of this information was collected by browsing through the public articles on the Apple Support website. -
Flash recovery area: archivelog file directory modification time
Using Oracle Database 10g Release 10.2.0.3.0 - 64bit (Standard Edition) on Solaris 10, SunOS 5.10 Generic_118833-33, archivelog files in the Flash Recovery Area are still present, after the time that they should have been made redundant and therefore deleted::
bvsmdb01-oracle10g $ date
Thu Jan 24 16:04:46 GMT 2008
bvsmdb01-oracle10g $ ls -lt archivelog
total 20
drwxr-x--- 2 oracle10g oinstall 1024 Jan 24 16:00 2008_01_24
drwxr-x--- 2 oracle10g oinstall 512 Jan 23 23:30 2008_01_19
drwxr-x--- 2 oracle10g oinstall 1536 Jan 23 23:04 2008_01_23
drwxr-x--- 2 oracle10g oinstall 1536 Jan 22 23:30 2008_01_18
drwxr-x--- 2 oracle10g oinstall 1536 Jan 22 22:53 2008_01_22
drwxr-x--- 2 oracle10g oinstall 1024 Jan 21 23:07 2008_01_21
drwxr-x--- 2 oracle10g oinstall 512 Jan 20 22:20 2008_01_20
bvsmdb01-oracle10g $
The archivelog directory for 2008_01_19 has a modification time of Jan 23 23:30 - this is almost 4 days after it was last written to.
The current redundancy setting in RMAN is shown in the output of show all:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/dbs/snapcf_kierli.f'; # default
So, the current retention policy is three days. It is 24/1 today - the archivelog directory from 19/1 should have been deleted by now, but it has not been.
The modification time for the archivelog directory 2008_01_19 has a modification time of Jan 23 23:30 2008.
Why is this? How can this be investigated? Does anyone have any suggestions?
Thanks
Jerry ManderFrom 2 Day DBA:
Even after files in the flash recovery area are obsolete, they are generally not deleted from the flash recovery area until space is needed to store new files. As long as space permits, files recently moved to tape will remain on disk as well, so that they will not have to be retrieved from tape in the event of a recovery.
What is the current space used in the FRA and what is the FRA disk limit ?
Maybe you are looking for
-
Configuration documents for Training and event management &apprisals?
hello xperts can anyone forward me configuration documents for treaining and event management and apprisal? to [email protected]
-
ME21N - error during service PO creation - "Please enter a service"
Hi, PR was created with reference to agreement. When we try to create PO, below error appears. Apparently service code, text are available so this error does not make sense. Have you come across such a situation ? Thanks, Sankar
-
Boot Camp nightmare, in gory detail
I recently had a very difficult time trying to install Windows on my MacBook Pro using Boot Camp. Along the way, I ran into several problems. Some of these problems were documented by other users on this forum, but although I found the questions, I f
-
PDF/A natively created in Mac OS X. Is still impossible?
Hi everybody, I need to generate PDF/A files (http://en.wikipedia.org/wiki/PDF/A) in 10.5/10.6 but I can't figure out how to do it! The best solution I found is to print to PostScript and then convert the files with Adobe Distiller but it is a nasty
-
Our HDB tool just stopped connecting to the Azure virtual machine
Our HDB tool just stopped connecting to the Azure virtual machine while it is working fine on AWS. The error we are getting is: "HDB -system state cannot be determined. Database connection is not available." Any suggestions/comments from the communit