System datafile block corruption - no backups and database in NOARCHIVELOG mode

Dear All,
Database version - oracle 11.1 Enterprise
OS - RHELinux 5.8
What are the options of recovering from physical block corruption when there are no backup available to perform block media recovery?
V$DATABASE_BLOCK_CORRUPTION reports two segments corrupted (please see attached image for details).
1 table in system datafile - sys_fba_barrierscn
1 index - (applicaiton index)
What are my options?
I know there is a possibility that the database will not restart after a shutdown due to corruption in system tablespace.
Database is in noarchivelog mode. So online backups are not possible and there aren't any full backups either.
I am thinking of below,
1. Run dbms_repair with fix_block_corruption. - Still database startup might fail?
2. Shutdown the database and take offline full backup with RMAN MAXCorrupt option.
Appreciate your suggestions and advises.
Thanks
Stefan

Thanks Sybrand,
Agree with your first two suggestions .
Also scheduled a expdp job tonight. (Only backup like thing they had was a expdp cron, but until today all the large tables were failing due to small undo_retention).
Yes. Flashback is not used. So hopefully it will not affect the a database restart i guess?
Related to dbms_repair, I was referring to - http://askdba.org/weblog/2010/08/physical-corruption-ora-1578-part-3/.
Where DBMS_REPAIR.FIX_CORRUPT_BLOCKS and DBMS_REPAIR.SKIP_CORRUPT_BLOCKS used.
Which i think will not use any redo.
Thanks
Stefan

Similar Messages

System datafile block corrupted

hi there,
i have got a serious problem, my database is in mount state, but when i try to start it up, it gives error datafile block corrupted file 'd:\path\system01.dbf'. these are backup file from last database, afer which os has been formated and reinstalled.
these are files from oracle 9i R1 and i want to install it intom oracle 9i R2.is it ok or i have to install oracle 9i R1 for making database up?
plz help what should i do???
thanks and regards
VD

ya its true,
its not consistent backup.its not RMAN backup.i just have files >DBF,controlfiles and redo log files.
now i am asked to retrieve data from these files.i have rebuild the database, and mounted it.but it is not getting opened.
if i use 'ALTER DATABASE OPEN RESETLOGS' it takes too much time but dosent open.
thats the issue.
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01190: controlfile or data file 2 is from before the last RESETLOGS
ORA-01110: data file 2: 'D:\ORACLE\ORADATA\ORACLE\UNDOTBS01.DBF'
alert log file entry:-
Mon Nov 17 15:59:49 2008
ORA-1589 signalled during: ALTER DATABASE OPEN..
Mon Nov 17 16:00:06 2008
RESETLOGS after incomplete recovery UNTIL CHANGE 81553193
Resetting resetlogs activation ID 0 (0x0)
Mon Nov 17 16:00:21 2008
Errors in file D:\ORACLE\admin\ORACLE\udump\ORA02204.TRC:
ORA-01110: data file 2: 'D:\ORACLE\ORADATA\ORACLE\UNDOTBS01.DBF'
ORA-01114: IO error writing block to file 2 (block # 1)
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 5) Access is denied.
Mon Nov 17 16:00:22 2008
now tell me what should i do??
thanks and regards
VD

ORA-00257: archiver error. and database is noarchivelog mode

Hi,
I've a Oracle 10.2.0.4 64bit database under Windows. The database has been from the beginning in noarchive log mode. How is it possible it's generating ora-0257 errors?
regards,
Ivan

Helios and oradba,
This is the output of archive list:
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination d:\oradata\DBN\arch
Oldest online log sequence 5249
Current log sequence 5251
On D: there is 10 Gbyte free space. And the error in the alert-log is:
Thu Oct 06 08:30:37 2011
Errors in file d:\oracle\product\10.2.0\admin\dbn\bdump\dbn_j000_3612.trc:
ORA-12012: error on auto execute of job 143
ORA-00257: archiver error. Connect internal only, until freed.
Ivan

RMAN restore when system datafile get corrupt

Hi,
I am new to Backup and recovery, Can anybody suggest.
If my system datafile gets corrupt, do I need to restore and recover complete database or just datafile restore will be suffice.
In case the database is running on archive log mode.
Waiting for reply.
Thanks & Regards,
Deepak

Deepak Pushkarna wrote:
Hi,
I am new to Backup and recovery, Can anybody suggest.
If my system datafile gets corrupt, do I need to restore and recover complete database or just datafile restore will be suffice.
In case the database is running on archive log mode.
Waiting for reply.
Thanks & Regards,
DeepakMount you database
restore tablespace system
recover tablespace system

Urgent- block corruption on standby and recovery thru physical copy file

Hi all,
We have a ORacle 9.2.0.6 DB and we have manula physical standby DB.
We got a block corruption on standby and I got to know thru metalink that we have to copy the data file from primary to standby but
my question is when we copy the datafile from primary to standby, will i be able to do the same because I think the SCN may varies ,as when i down the standby to copy the datafile ,oracle server wrtie a SCN to the control file of standby and when i will open it it will throw an error....
Please suggest me....

we are having n numbers od block corruption so what should be the exact value in
alter database recover automatic standby database allow *1* corruptionpls suggeest me
select * from v$backup_corruption;
RECID     STAMP     SET_STAMP     SET_COUNT     PIECE#     FILE#     BLOCK#     BLOCKS     CORRUPTION_CHANGE#     MARKED_CORRUPT     CORRUPTION_TYPE
1     679059926     679058677     54     1     3     299997     12     1790569359     NO     LOGICAL
2     679059926     679058677     54     1     3     300010     15     1790569374     NO     LOGICAL
3     679059926     679058677     54     1     3     300026     15     1790569389     NO     LOGICAL
4     679059926     679058677     54     1     3     300042     7     1790569404     NO     LOGICAL
5     679059926     679058677     54     1     3     300433     8     1790569404     NO     LOGICAL
6     679059926     679058677     54     1     3     300442     15     1790569419     NO     LOGICAL
7     679059926     679058677     54     1     3     300458     15     1790569434     NO     LOGICAL
8     679059926     679058677     54     1     3     300690     15     1790569450     NO     LOGICAL
9     679059926     679058677     54     1     3     300930     7     1790569465     NO     LOGICAL
10     679059926     679058677     54     1     3     2427217     64     1545959567     NO     LOGICAL
11     679059926     679058677     54     1     3     3078291     126     1790569473     NO     LOGICAL
12     679059926     679058677     54     1     3     3236929     8     1790569465     NO     LOGICAL
13     679059926     679058677     54     1     3     3236941     12     1790464761     NO     LOGICAL
14     679059926     679058677     54     1     3     3236954     15     1790464776     NO     LOGICAL
15     679059926     679058677     54     1     3     3236970     15     1790464792     NO     LOGICAL
16     679059926     679058677     54     1     3     3236986     15     1790464807     NO     LOGICAL
17     679059926     679058677     54     1     3     3237002     7     1790464822     NO     LOGICAL
18     679059926     679058677     54     1     3     3242641     8     1790464822     NO     LOGICAL
19     679059926     679058677     54     1     3     3242650     15     1790464837     NO     LOGICAL
20     679059926     679058677     54     1     3     3242666     15     1790464852     NO     LOGICAL
21     679059926     679058677     54     1     3     3242682     15     1790464867     NO     LOGICAL
22     679059926     679058677     54     1     3     3242771     40     1790464875     NO     LOGICAL
23     679059926     679058677     54     1     3     3242899     126     1790569482     NO     LOGICAL
24     679059926     679058677     54     1     3     3243027     126     1790569491     NO     LOGICAL
25     679059926     679058677     54     1     3     3243155     126     1790569500     NO     LOGICAL
26     679059926     679058677     54     1     3     3243283     126     1790569509     NO     LOGICAL
27     679059926     679058677     54     1     3     3243411     126     1790569518     NO     LOGICAL
28     679059926     679058677     54     1     3     3243539     126     1790569527     NO     LOGICAL
29     679059926     679058677     54     1     3     3243667     126     1790569536     NO     LOGICAL
30     679059926     679058677     54     1     3     3243795     126     1790569545     NO     LOGICAL
31     679059926     679058677     54     1     3     3243923     126     1790569554     NO     LOGICAL
32     679059926     679058677     54     1     3     3244051     126     1790569564     NO     LOGICAL
33     679059926     679058677     54     1     3     3244179     126     1790569573     NO     LOGICAL
34     679059926     679058677     54     1     3     3244307     126     1790569582     NO     LOGICAL
35     679059926     679058677     54     1     3     3244435     126     1790569591     NO     LOGICAL
36     679059926     679058677     54     1     3     3244563     126     1790569600     NO     LOGICAL
37     679059926     679058677     54     1     3     3244691     126     1790569609     NO     LOGICAL
38     679059926     679058677     54     1     3     3244819     126     1790569618     NO     LOGICAL
39     679059926     679058677     54     1     3     3244947     126     1790569627     NO     LOGICAL
40     679059926     679058677     54     1     3     3245075     126     1790569637     NO     LOGICAL
41     679059926     679058677     54     1     3     3245203     126     1790569646     NO     LOGICAL
42     679059926     679058677     54     1     3     3245331     126     1790569655     NO     LOGICAL
43     679059926     679058677     54     1     3     3245459     126     1790569664     NO     LOGICAL
44     679059926     679058677     54     1     3     3245587     126     1790569673     NO     LOGICAL
45     679059926     679058677     54     1     3     3245715     126     1790569683     NO     LOGICAL
46     679059926     679058677     54     1     3     3245843     126     1790569692     NO     LOGICAL
47     679059926     679058677     54     1     3     3245971     126     1790569701     NO     LOGICAL
48     679059926     679058677     54     1     3     3246099     126     1790569710     NO     LOGICAL
49     679059926     679058677     54     1     3     3246227     126     1790569719     NO     LOGICAL
50     679059926     679058677     54     1     3     3246355     126     1790569728     NO     LOGICAL
51     679059926     679058677     54     1     3     3246483     126     1790569737     NO     LOGICAL
52     679059926     679058677     54     1     3     3246611     126     1790569746     NO     LOGICAL
53     679059926     679058677     54     1     3     3246739     126     1790569755     NO     LOGICAL
54     679059926     679058677     54     1     3     3246867     126     1790569764     NO     LOGICAL
55     679059926     679058677     54     1     3     3246995     126     1790569773     NO     LOGICAL
56     679059926     679058677     54     1     3     3247123     126     1790569782     NO     LOGICAL
57     679059926     679058677     54     1     3     3247251     126     1790569791     NO     LOGICAL
58     679059926     679058677     54     1     3     3247379     126     1790569801     NO     LOGICAL
59     679059926     679058677     54     1     3     3247507     126     1790569811     NO     LOGICAL
60     679059926     679058677     54     1     3     3247635     126     1790569820     NO     LOGICAL
61     679059926     679058677     54     1     3     3247763     126     1790569829     NO     LOGICAL
62     679059926     679058677     54     1     3     3247891     126     1790569838     NO     LOGICAL
63     679059926     679058677     54     1     3     3248019     126     1790569847     NO     LOGICAL
64     679059926     679058677     54     1     3     3248147     126     1790569856     NO     LOGICAL
65     679059926     679058677     54     1     3     3248275     126     1790569865     NO     LOGICAL
66     679059926     679058677     54     1     3     3248403     126     1790569874     NO     LOGICAL
67     679059926     679058677     54     1     3     3248531     126     1790569883     NO     LOGICAL
68     679059926     679058677     54     1     3     3248659     126     1790569892     NO     LOGICAL
69     679059926     679058677     54     1     3     3248787     126     1790569901     NO     LOGICAL
70     679059926     679058677     54     1     3     3248915     126     1790569910     NO     LOGICAL
71     679059926     679058677     54     1     3     3249043     126     1790569920     NO     LOGICAL
72     679059926     679058677     54     1     3     3249171     126     1790569929     NO     LOGICAL
73     679059926     679058677     54     1     3     3249299     126     1790569938     NO     LOGICAL
74     679059926     679058677     54     1     3     3249427     126     1790569947     NO     LOGICAL
75     679059926     679058677     54     1     3     3249555     126     1790569956     NO     LOGICAL
76     679059926     679058677     54     1     3     3249683     126     1790569965     NO     LOGICAL
77     679059926     679058677     54     1     3     3249811     126     1790569974     NO     LOGICAL
78     679059926     679058677     54     1     3     3249939     126     1790569984     NO     LOGICAL
79     679059926     679058677     54     1     3     3250067     126     1790569993     NO     LOGICAL
80     679059926     679058677     54     1     3     3250195     126     1790570002     NO     LOGICAL
81     679059926     679058677     54     1     3     3250323     126     1790570011     NO     LOGICAL
82     679059926     679058677     54     1     3     3250451     126     1790570020     NO     LOGICAL
83     679059926     679058677     54     1     3     3250579     126     1790570029     NO     LOGICAL
84     679059926     679058677     54     1     3     3250706     127     1790570039     NO     LOGICAL
85     679059926     679058677     54     1     3     3250837     1020     1790570048     NO     LOGICAL
86     679059926     679058677     54     1     3     3251861     1020     1790570057     NO     LOGICAL
87     679059926     679058677     54     1     3     3252885     1020     1790570067     NO     LOGICAL
88     679059926     679058677     54     1     3     3253909     1020     1790570076     NO     LOGICAL
89     679059926     679058677     54     1     3     3254933     1020     1790570086     NO     LOGICAL
90     679059926     679058677     54     1     3     3255957     1020     1790570095     NO     LOGICAL
91     679059926     679058677     54     1     3     3256981     1020     1790570104     NO     LOGICAL
92     679059926     679058677     54     1     3     3258005     1020     1790570114     NO     LOGICAL
93     679059926     679058677     54     1     3     3259029     1020     1790570123     NO     LOGICAL
94     679059926     679058677     54     1     3     3260053     1020     1790570133     NO     LOGICAL
95     679059926     679058677     54     1     3     3261077     486     1790570142     NO     LOGICAL     NO     LOGICAL
SQL> select * from v$database_block_corruption;
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         3     299997         12         1790569359 LOGICAL
         3     300010         15         1790569374 LOGICAL
         3     300026         15         1790569389 LOGICAL
         3     300042          7         1790569404 LOGICAL
         3     300433          8         1790569404 LOGICAL
         3     300442         15         1790569419 LOGICAL
         3     300458         15         1790569434 LOGICAL
         3     300690         15         1790569450 LOGICAL
         3     300930          7         1790569465 LOGICAL
         3    2427217         64         1545959567 LOGICAL
         3    3078291        126         1790569473 LOGICAL
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         3    3236929          8         1790569465 LOGICAL
         3    3236941         12         1790464761 LOGICAL
         3    3236954         15         1790464776 LOGICAL
         3    3236970         15         1790464792 LOGICAL
         3    3236986         15         1790464807 LOGICAL
         3    3237002          7         1790464822 LOGICAL
         3    3242641          8         1790464822 LOGICAL
         3    3242650         15         1790464837 LOGICAL
         3    3242666         15         1790464852 LOGICAL
         3    3242682         15         1790464867 LOGICAL
         3    3242771         40         1790464875 LOGICAL
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         3    3242899        126         1790569482 LOGICAL
         3    3243027        126         1790569491 LOGICAL
         3    3243155        126         1790569500 LOGICAL
         3    3243283        126         1790569509 LOGICAL
         3    3243411        126         1790569518 LOGICAL
         3    3243539        126         1790569527 LOGICAL
         3    3243667        126         1790569536 LOGICAL
         3    3243795        126         1790569545 LOGICAL
         3    3243923        126         1790569554 LOGICAL
         3    3244051        126         1790569564 LOGICAL
         3    3244179        126         1790569573 LOGICAL
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         3    3244307        126         1790569582 LOGICAL
         3    3244435        126         1790569591 LOGICAL
         3    3244563        126         1790569600 LOGICAL
         3    3244691        126         1790569609 LOGICAL
         3    3244819        126         1790569618 LOGICAL
         3    3244947        126         1790569627 LOGICAL
         3    3245075        126         1790569637 LOGICAL
         3    3245203        126         1790569646 LOGICAL
         3    3245331        126         1790569655 LOGICAL
         3    3245459        126         1790569664 LOGICAL
         3    3245587        126         1790569673 LOGICAL
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         3    3245715        126         1790569683 LOGICAL
         3    3245843        126         1790569692 LOGICAL
         3    3245971        126         1790569701 LOGICAL
         3    3246099        126         1790569710 LOGICAL
         3    3246227        126         1790569719 LOGICAL
         3    3246355        126         1790569728 LOGICAL
         3    3246483        126         1790569737 LOGICAL
         3    3246611        126         1790569746 LOGICAL
         3    3246739        126         1790569755 LOGICAL
         3    3246867        126         1790569764 LOGICAL
         3    3246995        126         1790569773 LOGICAL
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         3    3247123        126         1790569782 LOGICAL
         3    3247251        126         1790569791 LOGICAL
         3    3247379        126         1790569801 LOGICAL
         3    3247507        126         1790569811 LOGICAL
         3    3247635        126         1790569820 LOGICAL
         3    3247763        126         1790569829 LOGICAL
         3    3247891        126         1790569838 LOGICAL
         3    3248019        126         1790569847 LOGICAL
         3    3248147        126         1790569856 LOGICAL
         3    3248275        126         1790569865 LOGICAL
         3    3248403        126         1790569874 LOGICAL
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         3    3248531        126         1790569883 LOGICAL
         3    3248659        126         1790569892 LOGICAL
         3    3248787        126         1790569901 LOGICAL
         3    3248915        126         1790569910 LOGICAL
         3    3249043        126         1790569920 LOGICAL
         3    3249171        126         1790569929 LOGICAL
         3    3249299        126         1790569938 LOGICAL
         3    3249427        126         1790569947 LOGICAL
         3    3249555        126         1790569956 LOGICAL
         3    3249683        126         1790569965 LOGICAL
         3    3249811        126         1790569974 LOGICAL
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         3    3249939        126         1790569984 LOGICAL
         3    3250067        126         1790569993 LOGICAL
         3    3250195        126         1790570002 LOGICAL
         3    3250323        126         1790570011 LOGICAL
         3    3250451        126         1790570020 LOGICAL
         3    3250579        126         1790570029 LOGICAL
         3    3250706        127         1790570039 LOGICAL
         3    3250837       1020         1790570048 LOGICAL
         3    3251861       1020         1790570057 LOGICAL
         3    3252885       1020         1790570067 LOGICAL
         3    3253909       1020         1790570076 LOGICAL
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         3    3254933       1020         1790570086 LOGICAL
         3    3255957       1020         1790570095 LOGICAL
         3    3256981       1020         1790570104 LOGICAL
         3    3258005       1020         1790570114 LOGICAL
         3    3259029       1020         1790570123 LOGICAL
         3    3260053       1020         1790570133 LOGICAL
         3    3261077        486         1790570142 LOGICAL
95 rows selected.
SQL>

Oracle Datafile block corruption

HI all
i am facing datafile block corruption in following datafile .
i don't have any backup.
how i can recover these blocks
Regards
Vivek Rawat

Hi Vivek,
Please refer below SAP notes to analyze the affected objects which needs to be recovered
365481 - Block corruptions
1559652 - How to deal with block corruptions on Oracle
923919 - Advanced Oracle block checking features
http://www.dba-oracle.com/t_repair_corrupt_blocks.htm
Hope this helps.
Regards,
Deepak Kori

When i try to make a backup of my iphone, it says here that the backup is corrupt, delete backup and then try again. how do i solve this problem? i cant backup my phone for now

when i try to make a backup of my iphone, it says here that the backup is corrupt, delete backup and then try again. how do i solve this problem? i cant backup my phone for now, i have no idea how you delete backup. please if anyone could help

Using iTunes on your computer, open Preferences (under the leftmost item in iTunes menu). Choose "Devices" on top. Find your backup listed there, highlight it, and select "Delete Backup".

How to backup a database in noarchivelog

My database is in NOARCHIVELOG.
I can open rman
which command can i use to backup my database in this mode.
is there anything i need to configure before it backups in this mode.

why you dont need to turn on the archivelog?
CONFIGURE RETENTION POLICY TO REDUNDANCY 1
how many days back you are responsible to revert back the database?Someday It may be asked to you restore the some days before dataabase backup, before that raising the question ,raise the question to mangment personnel how many days back will i be responsible to restore the database,if they give you 7 days then make sure yours disk space can accomodate 7 days backup if not then ask them to arrange space for disk if they give alternate tape cartrdige then tell them that x hours will take to restore the database in disaster recovery scenario cause tape cartridge data restoration takes time.
No archive mode is yours decision then before doing it aware managment personnel that i can only restored the last good backup data,good backup does not mean last backup,last backup may be corrupt ,last good backup is the backup which you can restore then you will be able to restore only till last good backup,with archived enabled you will have chance to recover till before crash but with no archivelog there is only one option recovery till last good backup.
Khurram

Backup and Recovery in different mode

We have a database in noarchivelog mode.
Currently we convert it to archivelog mode before monthly full database RMAN backup.
And after backup,we again back it to noarchivelog mode.
Now my question is that, in case of failure can we recover this database(any how) with that backup?
Please advice and if possible give the recovery steps.
Thanks & Regards
Quazi Abdur Rab

Hi,
It's not good to switch from Archive Log Mode and No Archive Log Mode as your wish.
See, As Khurram had explained you the thing. Point in time recovery before crash is quite not possible but only last the restore point applicable for your DB. Rest of the things can be recovered. Why are the implications you are facing if the DB is in Archive Mode. ?? I Suggest do peform and maintain Archive Log which is good for your DB.
- Pavan Kumar N

Database in noarchivelog mode, truncate command issued

Database in noarchivelog mode, truncate command has been issued how to restore the table?
FACTS:-
1. DB In noarchivelog Mode
2. Cannot enable flash back mode because of 1. above
3. No exports available
4. No backup's Available.
Any thoughts ?

Oracle Support/ Professional Services has a Data Unloader (DUL) and ORA-00600 has DUDE, both of which may be able to extract information from data files that are corrupted, where the control files are lost, etc.
These are not, however, cheap utilities. Unless the data itself is really valuable, it is generally not a viable option.
Justin

Changing database to noarchivelog mode during impdp

Hi Guys,
I am using Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production on RHEL5.
I am in the middle on the impdp and I want my database to run on noarchivelog as it creates a lot of archivelogs.
Will it be proper if I stop the import:
e.g Import> STOP_JOB=IMMEDIATE
and shutdown the database put the database on noarchivelog mode.
then opne database and
impdp hr/hr@mydb ATTACH=myfulljob Will these work fine?
Or should I execute:
alter system archive log stop;
Please Help !!!!!!!!!!!

Vinod Dhandapani wrote:
Running the database in Noarchivelog mode means you should be ready to lose data incase there is any crash. I would recommend you to change the size of the redologs so that it will not create frequent archivelogs. Which does nothing about the space required for the archivelogs. If you are generating redo at the rate of 1gb/hour, you will consume archivelog dest space at the rate of 1gb/hour. Doesn't matter if those files are 10mb each or 100mb each.
If space is the problem then use a shell script to move the archivelog to another location (Tape)....And hopefully that shell script is invoking rman to do the work, so that in the event of recovery, rman will know that backups were taken and where they are located.
>
Incase you want to convert the database from archivelog to noarchivelog, follow the steps provided in the following link.
http://racadmin.blogspot.com/2011/06/convert-archivelog-mode-to-noarchivelog.html
Thanks

Running a physical standby database in noarchivelog mode

Primary Database: 2 node rac cluster, 11.2.0.2 GI and RDBMS
Standby Database: single instance 11.2.0.2
OS: AIX 7.1
Hello,
I'm in the process of implementing a data guard standby system. To make this system simpler to admin, I want to run the standby database in NOARCHIVELOG mode. This standby is used only as a mirror of production (to be copied to a 3rd site for separate user activity) and will never be switched to active mode. Maintaining another set of archive logs seems to be redundant to me and another point of failure, so I want to disable archiving. I wanted to ask if any of the DG experts on the forums have ever had experience with this? Does anyone know if this is recommended? I've searched the Oracle Data guard documentation online... it says that the primary obviously needs to be in archive mode, but I'm not seeing anything specific about the standby. Please let me know if anyone has experience with this.
Thanks

Hello again;
If this is the case, then I have nothing to worry about here. Does that sound right to you?Yes.
For this :
b) monthly, shutdown this system and copy it to a 3rd site to host a separate set of business activityI would consider RMAN Duplicate in which case you may avoid the shutdown.
And for this :
resync the "mirror" with productionAll you have to do if DEFER the primary to the standby, then ENABLE and Data Guard will catch up.
--- Will post a detailed example here in a moment.
Right at the first of the year they wanted to work on our Primary server room ( Power ). What I did was switchover to the Standby but I kept log_archive_dest_state_2 on the new primary set to DEFER. Then I shutdown
all the databases at the Primary site. At the end of work two days later I started the databases at the Primary site in standby mode. Switched log_archive_dest_state_2 to ENABLE. When the databases were back in SYNC
I did another switchover and it was done. I used TAF and none of the users even noticed.
Best Regards
mseberg

ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode

Hi All,
Need help from the gurus.
Currently we are in state unable to do anything.
Was using a database and all of a sudden it crashed. Tried to mount the database, open it, it failed. Also tried the recover and alter database open, even that failed. Errors are as follows.
Errors in file e:\oracle\product\10.2.0 \admin\devrevdb\bdump\devrevdb_p000_2620.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-00449: background process 'DBW0' unexpectedly terminated with error 1242
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
In my spfile, the administrator has set only two control files and there is no mirroring and hence do not have another control file that will help me boot the db.
Please let me know how I should go about it. I am only a timebeing person trying to carryout a db activity. Any help would be of great help.

Hemant,
thanks for the reply.
I tried the way you suggested and it threw an error.
ORA-01145: offline immediate disallowed unless media recovery enabled
I searched and found that an additional tag of drop needs to be added to the command which you suggested.
ALTER DATABASE DATAFILE '<filename>' OFFLINE DROP.
i don't know what will the drop command have an effect ?
i have copied the data file to another location. Since i don't know much, i just want to be sure of what im doing.
if the above command is successfull, will it drop the datafile or the tablespace and i can no more use it. How can i use the copied datafile.
Thanks,
Sachin
I

How to recover database SYSTEM datafile get corrupt ?

Database is in ARCHIVELOG mode, and the datafile belonging to SYSTEM tablespace gets corrupted. Up to what point can I recover the database ?
A. Until last commit.
B. Until the time you perform recovery.
C. Until the time the datafile got corrupted.
D. You cannot recover the SYSTEM tablespace and you must be re-create the database.
and 1 more doubt :
If redologfiles are not multiplexed and redolog blocks get corrupt in group 2, and archiving stops. All redolog files are filled and database activity is halted.
DBWR has written everything to disk. What command can be used to proceed further ?
A. recover logfile block group 2;
B. alter database drop logfile group 2;
C. alter database clear logfile group 2;
D. alter database recover logfile group 2;
E. alter database clear unarchived lofile group 2;
Edited by: user642367 on Sep 18, 2008 8:45 PM

1. A. Since the DB is in archivelog mode, so you can always restore and recover the whole DB including system tablespace datafile till last SCN generated provided the redo record is available in archive/online logfiles.
2. E. Since only redolog is corrupted so archiver won't proceed and hence a db hang is obvious, So, in order to proceed further you need to clear online (un archived log file) and then db will work as usual. Care should be taken that you must take a full backkup of DB(cold backup wherever feasible) as soon as possible after issuing this command. As now you don't have redo info in archivelog files to recover the db in case of a crash.
Please go through Oracle 10g DB Administrators guide (available on OTN) for more details.
Thanks

Backup and database export fails

Now that I've got the database up and running, I'd like to export and/or backup the database. After relaying (I've got a German version of Oracle, so I have to guess what the original terminology might be) the job, it is listed as 'unsucccessful' in the job history. The error code is "VNI-2015 Fehler in der Berechtigungspr|fung" (meaning 'error in authorization check'). The preferred ID-data should be the correct ones.
Helpless again,
Claus.

Greg,
You need to push planning application into maintenance mode or stop planning server -- to stop users logging/entering data through forms
If you have single planning app or all apps can go down during nightly process then just stop planning server by calling stopplanning.cmd( not sure about file name)
after you nightly process is done call startplanning.cmd
If you have multiple applications and only a subset of them needs to be under maintenance mode
then you need to change few values in your application Relational repository ( its not recommended by Oracle)
LOGIN_LEVEL='0' - For all Users
LOGIN_LEVEL='2' - For Administrators
you need to change Login_level value to '2' to move app into maintenance mode..
this link will give you a better idea http://www.orahyplabs.com/2011/02/place-planning-under-maintenance-mode.html
just add above mentioned steps based on your requirement
KK

System datafile block corruption - no backups and database in NOARCHIVELOG mode

Similar Messages

Maybe you are looking for