Problems Recovering Sysaux table space with missing archive log

Dear All
We have a 10G r2 database running on RHEL 4.2.
Today when updating certain records in one of the databases. whe have started getting the following error:
error occurred at recursive SQL level 2 ORA-00376: file 3 cannot be read at this time ORA-01110: data file 3: '/u02/oradata/EDM/datafile/o1_mf_sysaux_1wwwhpg5_.dbf'
This appears to have occurred as a result of one ofthe users adding a large amount of data to a table in one of the other tablespaces. Checking the V$datafile view shows this file to have a status of RECOVER. However on trying to do a
recover datafile 3;
I'm told that a change number generated back in April 2006 is required, this being in an archive log we no longer have.
My question is how do I recover the datafile to the point in time shown without causing all the other tablespaces to revert to that date.
It seems the SYSAUX tablespace has been in RECOVER status for some time now with no effect on the operation of the database. As such I'm loathe to return all of the database back to 04/2006 and lose 18 months work. Is it possible to just fix the SYSAUX tablespace? If so what is the process? If I recover the TS to the point in time that the missing archive log occurs and then do a reset logs will that truncate all the other tablespaces.
Many Thanks
Paul

Thanks for the reply
WE have a table named mlm_papertrail which, having added about 2000 rows to it, now causes the error shown whenever someone tries to insert a new row into it. Ihave created a new table and pointed the application to it and the problem no longer occurs.
However the SYSAUX tablespace is marked recover as is the datafile that forms it. I can only assume that adding the rows to the table has in turn caused sysaux to expand until it has hit a part of the disk that is damaged or corrupt.
I've tried recovering both the tablespace and the datafile getting the request for the archivelog back in 04/06. Again I can only assume the sysaux file has been damaged at this point, but till now hasn't caused any problems.
I don't want to roll the whole database back to 04/06 since in the main it works fine. But obviously the SYSAUX tablespace needs recovering.
My question is how do I do that with as little pain as possible :-)
Anyway, thanks for the advice. I'll try what you suggest.
regards
paul

Similar Messages

Problem about space management of archived log files

Dear friends,
I have a problem about space management of archived log files.
my database is Oracle 10g release 1 running in archivelog mode. I use OEM(web based) to config all the backup and recovery settings.
I config "Flash Recovery Area" to do backup and recovery automatically. my daily backup schedule is every night at 2:00am. and my backup setting is "disk settings"--"compressed backup set". the following is the RMAN script:
Daily Script:
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
the retention policy is the second choice, that is "Retain backups that are necessary for a recovery to any time within the specified number of days (point-in-time recovery)". the recovery window is 1 day.
I assign enough space for flash recovery area. my database size is about 2G. I assign 20G as flash recovery area.
now here is the problem, through oracle online manual, it said oracle can manage the flash recovery area automatically, that is, when the space is full, it can delete the obsolete archived log files. but in fact, it never works! whenever the space is full, the database will hang up! besides, the status of archived log files is very strange, for example, it can change "obsolete" stauts from "yes" to "no", and then from "no" to "yes". I really have no idea about this! even though I know oracle usually keep archived files for some longer days than retention policy, but I really don't know why the obsolete status can change automatically. although I can write a schedule job to delete obsolete archived files every day, but I just want to know the reason. my goal is to backup all the files on disk and let oracle automatically manage them.
also, there is another problem about archive mode. I have two oracle 10g databases(release one), the size of db1 is more than 20G, the size of db2 is about 2G. both of them have the same backup and recovery policy, except I assign more flash recovery area for db1. both of them are on archive mode. both of nearly nobody access except for the schedule backup job and sometime I will admin through oem. the strange thing is that the number of archived log files of smaller database, db2, are much bigger than ones of bigger database. also the same situation for the size of the flashback logs for point-in-time recovery. (I enable flashback logging for fast database point-in-time recovery, the flashback retention time is 24 hours.) I found the memory utility of smaller database is higher than bigger database. nearly all the time the smaller database's memory utility keeps more than 99%. while the bigger one's memory utility keeps about 97%. (I enable "Automatic Shared Memory Management" on both databases.) but both database's cup and queue are very low. I'm nearly sure no one hack the databases. so I really have no idea why the same backup and recovery policy will result so different result, especially the smaller one produces more redo logs than bigger one. does there anyone happen to know the reason or how should I do to check the reason?
by the way, I found web based OEM can't reflect the correct database status when the database shutdown abnormally. for example, if the database hang up because of out of flash recovery area, after I assign more flash recovery area space and then restart the database, the OEM usually can't reflect the correct database status. I must restart OEM manually to correctly reflect the current database status. does there anyone know in what situation I should restart OEM to reflect the correct database status?
sorry for the long message, I just want to describe in details to easy diagnosis.
any hint will be greatly appreciated!
Sammy

thank you very much, in fact, my site's oracle never works about managing archive files automatically although I have tried all my best. at last, I made a job running daily to check the archive files and delete them.
thanks again.

Roblem about space management of archived log files

Dear friends,
I have a problem about space management of archived log files.
my database is Oracle 10g release 1 running in archivelog mode. I use OEM(web based) to config all the backup and recovery settings.
I config "Flash Recovery Area" to do backup and recovery automatically. my daily backup schedule is every night at 2:00am. and my backup setting is "disk settings"--"compressed backup set". the following is the RMAN script:
Daily Script:
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
the retention policy is the second choice, that is "Retain backups that are necessary for a recovery to any time within the specified number of days (point-in-time recovery)". the recovery window is 1 day.
I assign enough space for flash recovery area. my database size is about 2G. I assign 20G as flash recovery area.
now here is the problem, through oracle online manual, it said oracle can manage the flash recovery area automatically, that is, when the space is full, it can delete the obsolete archived log files. but in fact, it never works! whenever the space is full, the database will hang up! besides, the status of archived log files is very strange, for example, it can change "obsolete" stauts from "yes" to "no", and then from "no" to "yes". I really have no idea about this! even though I know oracle usually keep archived files for some longer days than retention policy, but I really don't know why the obsolete status can change automatically. although I can write a schedule job to delete obsolete archived files every day, but I just want to know the reason. my goal is to backup all the files on disk and let oracle automatically manage them.
also, there is another problem about archive mode. I have two oracle 10g databases(release one), the size of db1 is more than 20G, the size of db2 is about 2G. both of them have the same backup and recovery policy, except I assign more flash recovery area for db1. both of them are on archive mode. both of nearly nobody access except for the schedule backup job and sometime I will admin through oem. the strange thing is that the number of archived log files of smaller database, db2, are much bigger than ones of bigger database. also the same situation for the size of the flashback logs for point-in-time recovery. (I enable flashback logging for fast database point-in-time recovery, the flashback retention time is 24 hours.) I found the memory utility of smaller database is higher than bigger database. nearly all the time the smaller database's memory utility keeps more than 99%. while the bigger one's memory utility keeps about 97%. (I enable "Automatic Shared Memory Management" on both databases.) but both database's cup and queue are very low. I'm nearly sure no one hack the databases. so I really have no idea why the same backup and recovery policy will result so different result, especially the smaller one produces more redo logs than bigger one. does there anyone happen to know the reason or how should I do to check the reason?
by the way, I found web based OEM can't reflect the correct database status when the database shutdown abnormally. for example, if the database hang up because of out of flash recovery area, after I assign more flash recovery area space and then restart the database, the OEM usually can't reflect the correct database status. I must restart OEM manually to correctly reflect the current database status. does there anyone know in what situation I should restart OEM to reflect the correct database status?
sorry for the long message, I just want to describe in details to easy diagnosis.
any hint will be greatly appreciated!
Sammy

thank you very much, in fact, my site's oracle never works about managing archive files automatically although I have tried all my best. at last, I made a job running daily to check the archive files and delete them.
thanks again.

Missing archived logs in v$archived_log

I want to monitor if system accounts such as system, sys or other DBA accounts
did any DML in my application schema. What are the minimal audit statements?
needed to accomplish this. I know using Oracle Database Vault one can set realm to restrict this but I do
not have Data Vault, just looking to audit this using Oracle’s database auditing.
My organization also has Oracle Audi Vault, but Database Auditing Events have to be set in database
first for collection agent to pass this information to Oracle Audit Vault server.
Thanks a lot.

Duplicate post
Please ignore
Missing archived logs in v$archived_log
Handle:      user632098
Status Level:      Newbie
Registered:      Apr 20, 2008
Total Posts:      115
Total Questions:      29 (28 unresolved)
Edited by: sb92075 on Dec 19, 2009 4:49 PM

Will CDC look for a missing archive log in an alternate log_archive_dest ?

Will CDC look for a missing archive log in an alternate log_archive_dest ?
If a log is deleted from the primary dest, will CDC look in all the altenate destinations before failing? Or is it unaware of the other destinations?

Duplicate post:
missing archive log in backup and restore

Problems recovering SYSAUX

Dear All
I have a 10g database running on redhat EL 4.2. This morning I tried to run a flashback query on one of the tables only to be told there was a problem with one of the datafiles. Further investigation showed this to be the datafile containing the sysaux tablespace. The status of the file is set as RECOVER. I have tried to recover this with no success. In RMan if I issue the command 'recover tablespace sysaux I get the response.
Starting recover at 19-JUN-06
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=152 devtype=DISK
starting media recovery
archive log thread 1 sequence 424 is already on disk as file /u08/oradata/EDM/archivelog/1_424_580063949.dbf
archive log thread 1 sequence 425 is already on disk as file /u07/oradata/EDM/archivelog/1_425_580063949.dbf
archive log thread 1 sequence 426 is already on disk as file /u07/oradata/EDM/archivelog/1_426_580063949.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/19/2006 14:43:16
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 357 lowscn 7103125 found to restore
RMAN-06025: no backup of log thread 1 seq 356 lowscn 7064717 found to restore
RMAN-06025: no backup of log thread 1 seq 355 lowscn 7064686 found to restore
RMAN-06025: no backup of log thread 1 seq 354 lowscn 7029252 found to restore
RMAN-06025: no backup of log thread 1 seq 353 lowscn 7029220 found to restore
Similarly issuing the command 'alter database recover datafile 3' in sqlplus gives:
alter database recover datafile 3
ERROR at line 1:
ORA-00279: change 6846564 generated at 04/23/2006 18:00:42 needed for thread 1
ORA-00289: suggestion : /u08/oradata/EDM/archivelog/1_345_580063949.dbf
ORA-00280: change 6846564 for thread 1 is in sequence #345
My questions are these.
1) based on the fact that the change nuber in the second response is dated 23/04/06 is this how long the problem has been ongoing?
2) The problem doesn't seem to have had any impact on the daily use of the system. How is this possible? I thought the sysaux file was crucial to the operation of the db.
3) While RMan runs every night we no longer have the archive log files as far back as appril 06. How can I force the recover so that the file can be brought back on line? Will doing this cause any further problems?
Many thanks
Paul
Many thanks

Thanks for the reply
WE have a table named mlm_papertrail which, having added about 2000 rows to it, now causes the error shown whenever someone tries to insert a new row into it. Ihave created a new table and pointed the application to it and the problem no longer occurs.
However the SYSAUX tablespace is marked recover as is the datafile that forms it. I can only assume that adding the rows to the table has in turn caused sysaux to expand until it has hit a part of the disk that is damaged or corrupt.
I've tried recovering both the tablespace and the datafile getting the request for the archivelog back in 04/06. Again I can only assume the sysaux file has been damaged at this point, but till now hasn't caused any problems.
I don't want to roll the whole database back to 04/06 since in the main it works fine. But obviously the SYSAUX tablespace needs recovering.
My question is how do I do that with as little pain as possible :-)
Anyway, thanks for the advice. I'll try what you suggest.
regards
paul

Missing archived logs when recovering database

Scenario is
1-10 archived logs required to recover database.
5 Number log is missing
It means that 6,7,8,9,10 are useless for me
yes/no Please explain it to me
Thanks a Lot

Hi,
Yes all archivelog after the missing sequence of archivelog will be useless for recovery.
in ur case 6,7,8,9,10 are useless for you.
So only incomplete recovery is the solution.
Thanks
Kuljeet Pal Singh

"recover database until cancel" asks for archive log file that do not exist

Hello,
Oracle Release : Oracle 10.2.0.2.0
Last week we performed, a restore and then an Oracle recovery using the recover database until cancel command. (we didn't use backup control files) .It worked fine and we able to restart the SAP instances. However, I still have questions about Oracle behaviour using this command.
First we restored, an online backup.
We tried to restart the database, but got ORA-01113,ORA-01110 errors :
sr3usr.data1 needed media recovery.
Then we performed the recovery :
According Oracel documentation, "recover database until cancel recovery" proceeds by prompting you with the suggested filenames of archived redo log files.
The probleme is it prompts for archive log file that do not exist.
As you can see below, it asked for SMAarch1_10420_610186861.dbf that has never been created. Therefore, I cancelled manually the recovery, and restarted the database. We never got the message "media recovery complete"
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10417_61018686
Fri Sep 7 14:09:45 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf'
Fri Sep 7 14:09:45 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_61018686
Fri Sep 7 14:10:03 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf'
Fri Sep 7 14:10:03 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_61018686
Fri Sep 7 14:10:13 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf'
Fri Sep 7 14:10:13 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
Errors with log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
ORA-308 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_61018686
Fri Sep 7 14:15:19 2007
ALTER DATABASE RECOVER CANCEL
Fri Sep 7 14:15:20 2007
ORA-1013 signalled during: ALTER DATABASE RECOVER CANCEL ...
Fri Sep 7 14:15:40 2007
Shutting down instance: further logons disabled
When restaring the database we could see that, a recovery of online redo log has been performed automatically, is it the normal behaviour of a recovery using "recover database until cancel" command ?
Started redo application at
Thread 1: logseq 10416, block 482
Fri Sep 7 14:24:55 2007
Recovery of Online Redo Log: Thread 1 Group 4 Seq 10416 Reading mem 0
Mem# 0 errs 0: /oracle/SMA/origlogB/log_g14m1.dbf
Mem# 1 errs 0: /oracle/SMA/mirrlogB/log_g14m2.dbf
Fri Sep 7 14:24:55 2007
Completed redo application
Fri Sep 7 14:24:55 2007
Completed crash recovery at
Thread 1: logseq 10416, block 525, scn 105140074
0 data blocks read, 0 data blocks written, 43 redo blocks read
Thank you very much for your help.
Frod.

Hi,
Let me answer your query.
=======================
Your question: While performing the recovery, is it possible to locate which online redolog is needed, and then to apply the changes in these logs
1.   When you have current controlfile and need complete data (no data loss),
      then do not go for until cancel recovery.
2.   Oracle will apply all the redologs (including current redolog) while recovery
     process is    on.
3. During the recovery you need to have all the redologs which are listed in the    view    V$RECOVERY_LOG and all the unarchived and current redolog. By querying V$RECOVERY_LOG you    can find out about the redologs required.
4. If the required sequence is not there in the archive destination, and if recovery process    asks for that sequence you can query V$LOG to see whether requested sequence is part of the    online redologs. If yes you can mention the path of the online redolog to complete the recovery.
Hope this information helps.
Regards,
Madhukar

Clone database with no archive log mode and downtime with new file structure

We need to clone database with following business requirements :
No downtime at all can be afford
databases are in no archive log mode
data-file locations need to be change to new mount points while cloning for space management factor
Please suggest the best possible methods for same ?

Can you post your version of oracle in 4 digits and OS for better understandig
I dont think you can move the No Archive database to a new location without shutting down.
You just want to move them to the new mount points is it?
1. How big are your datafiles are?
2.How do you backup this DB?
When you move the datafilles then it becomes inconsistent and you need redo logs and probably archive logs to be there to make the file consistent or else it would be prompting for recovery. The chances are your redolog will be overwritten and hence you wont be able to recover.
You need downtime.

Error after Restoring Datafiles in Archivelog but missing archive log files

Hi all,
I have taken backup yesterday monrning in Archive log mode but have lost all the archive log files. Yesterday night i have restored my DB .
I m happy to have my datafile contents till yesterday morning.
But after restoring when i try to open th DB, i m facing the following errors:
SQL>          Startup open;
Oracle instance started but in mounted stagell
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL>         alter database open resetlogs;
Error: ORA-01113: file 1 needs media recovery
          ORA-01110: data file 1: 'E:\oracle\'<SID>\sapdata1\SYSTEM_1\SYSTEM.DATA1'
SQL>         recover database using backup controlfile until cancel;
ORA-00279 : change 26627919 generated at DATE TIMEneeded for thread 1
ORA-00289 : Suggestion E:\ORACLE\<SID>\ORAARCH\<SID>ARCHARC03020_0683715008.001
ORA-00280: change 266277189 for thread 1 is in sequence #3020
ORA - 01112: media recovery not started
SQL>   recover;
ORA-00283: recovery session cancelled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
Alert Log File:
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters with non-default values:
processes                = 80
sessions                 = 96
event                    = 10191 trace name context forever, level 1
sga_max_size             = 633339904
shared_pool_size         = 301989888
shared_pool_reserved_size= 30183260
filesystemio_options     = setall
control_files            = E:\ORACLE\IE6\ORIGLOGA\CNTRL\CNTRLIE6.DBF, E:\ORACLE\IE6\ORIGLOGB\CNTRL\CNTRLIE6.DBF, E:\ORACLE\IE6\SAPDATA1\CNTRL\CNTRLIE6.DBF
control_file_record_keep_time= 30
db_block_size            = 8192
db_cache_size            = 301989888
compatible               = 10.2.0
log_archive_dest         = E:\oracle\IE6\oraarch\IE6arch
log_buffer               = 2854912
log_checkpoint_interval = 0
db_files                 = 254
log_checkpoints_to_alert = TRUE
dml_locks                = 4000
undo_management          = AUTO
undo_tablespace          = PSAPUNDO
undo_retention           = 43200
recyclebin               = off
remote_os_authent        = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes      = 1
background_dump_dest     = E:\ORACLE\IE6\SAPTRACE\BACKGROUND
user_dump_dest           = E:\ORACLE\IE6\SAPTRACE\USERTRACE
core_dump_dest           = E:\ORACLE\IE6\SAPTRACE\BACKGROUND
optimizer_features_enable= 10.2.0.1
sort_area_size           = 2097152
sort_area_retained_size = 0
db_name                  = IE6
open_cursors             = 800
optimpeek_user_binds   = FALSE
pga_aggregate_target     = 402443468
workarea_size_policy     = AUTO
statistics_level         = typical
PMON started with pid=2, OS id=804
PSP0 started with pid=3, OS id=9580
MMAN started with pid=4, OS id=5840
DBW0 started with pid=5, OS id=8136
LGWR started with pid=6, OS id=8712
CKPT started with pid=7, OS id=1620
SMON started with pid=8, OS id=7084
RECO started with pid=9, OS id=9576
CJQ0 started with pid=10, OS id=9156
MMON started with pid=11, OS id=6000
MMNL started with pid=12, OS id=2856
Sat Apr 18 04:01:29 2009
ALTER DATABASE   MOUNT
Sat Apr 18 04:01:33 2009
Setting recovery target incarnation to 1
Sat Apr 18 04:01:33 2009
Successful mount of redo thread 1, with mount id 1124466585
Sat Apr 18 04:01:33 2009
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Sat Apr 18 04:01:34 2009
ALTER DATABASE OPEN
ORA-1589 signalled during: ALTER DATABASE OPEN...
Sat Apr 18 04:02:13 2009
alter database open resetlogs
Sat Apr 18 04:02:13 2009
ORA-1245 signalled during: alter database open resetlogs...
Sat Apr 18 04:11:05 2009
ALTER DATABASE RECOVER DATABASE UNTIL CANCEL
Sat Apr 18 04:11:05 2009
Media Recovery Start
Sat Apr 18 04:11:06 2009
Media Recovery failed with error 1610
ORA-283 signalled during: ALTER DATABASE RECOVER DATABASE UNTIL CANCEL...
Sat Apr 18 04:11:28 2009
ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE
Sat Apr 18 04:11:28 2009
Media Recovery Start
parallel recovery started with 3 processes
ORA-279 signalled during: ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE...
Sat Apr 18 04:17:23 2009
ALTER DATABASE RECOVER database using backup controlfile until cancel
Sat Apr 18 04:17:23 2009
Media Recovery Start
ORA-275 signalled during: ALTER DATABASE RECOVER database using backup controlfile until cancel ...
Any suggestions pls..............
Thanks & Regards,
Subbu

Hello Subbu,
> I have taken backup yesterday monrning in Archive log mode but have lost all the archive log files.
You mean you have taken an online backup and lost all your archive log files after that online backup?
SQL> alter database open resetlogs;
Error: ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'E:\oracle\'<SID>\sapdata1\SYSTEM_1\SYSTEM.DATA1'
SQL> recover database using backup controlfile until cancel;
ORA-00279 : change 26627919 generated at DATE TIMEneeded for thread 1
ORA-00289 : Suggestion E:\ORACLE\<SID>\ORAARCH\<SID>ARCHARC03020_0683715008.001
ORA-00280: change 266277189 for thread 1 is in sequence #3020
To perform a recovery with an online backup you will need all archive log files until the end of the online backup. If you have lost them you are not able to recover (or open) your database in a consistent state.
So the only suggestion we can do is:
You need the archive log files that were created during the online backup to perform an incomplete recovery ... if they are gone you can not restore your database.
Regards
Stefan

Recover database but don't have archive log file

Hi
I use old backup set in tape and restore all datafile completed but I cannot recover that show below errror in RMAN
RMAN> recover database;
Starting recover at 08-SEP-09
using channel ORA_DISK_1
starting media recovery
unable to find archive log
archive log thread=1 sequence=29166
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/08/2009 21:49:36
RMAN-06054: media recovery requesting unknown log: thread 1 seq 29166 lowscn 1648727512
But in backup set and include archive log already that don't have seq 29166 that have last seg is 29165 when I tyr recover in sqlplus that show below error
SQL> recover database using backup controlfile;
ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
1
ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
ORA-00280: change 1648727512 for thread 1 is in sequence #29166
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/oradata/archive/hrprd/1_29166_671345511.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
And I tried to open with reset log that show below error
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: '/oradata/data/hrprd/system01.dbf'
How can I do to open database?
Taohiko.

taohiko wrote:
Hi Werner
I tried and show below error
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
1
ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
ORA-00280: change 1648727512 for thread 1 is in sequence #29166
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/oradata/data/hrprd/system01.dbf'
ORA-01112: media recovery not started
How to do next step?
TaohikoHi Taohiko
Have you made backup of all archived redo log files? If so, why this one was disappeared?
Have you applied all archived redo log files before that required archived redo log file?
Please try to recover the database using the following command:
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE UNTIL SEQUENCE 29166;
RMAN>ALTER DATABASE OPEN RESETLOGS;

Data guard - missed archive log

Hi:
I am on 10.2.0.3, using physical standby. One of my check-up sqls shows missed (not applied) arch log:
SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG
where applied='NO'
THREAD# SEQUENCE# APP
1 16595 NO
It's relatively old one, my max is 18211i and the log application is going fine.
How can I apply this missed one? Do I have to stop managed recovery and do manual recovery for it?
TIA.

GregX,
Please check if this file actually needs to be applied.
You can find out the when the archived log file was created – FIRST_TIME/NEXT_TIME columns in V$ARCHIVED_LOG.
If the archived log file was created before you created the stand-by DB, you do not need ( nor you can) to apply that file.
Please note that the physical standby would stop applying archivelog if you fail to provide the next required archive log file. Since this has not happened (as per your statement) there is a good chance that you archive redo in question is not needed.
Hope that helps,
Edited by: IordanIotzov on Jan 30, 2009 1:34 PM

Can I make some tables of database into archived logging?

Is that possible that making logging part of tables in database ?I mean ,only some changes of tables recorded in archived log file .If do so,the size of logging file may decrease ?

In my oracle database, there are some streams which are used to make the datafile in different machine located in different place.For these streams normal running has to look archived log to kown what has happen in my database and needs to tell other database,
SCN is used to identify the different states of databse.When a stream get a scn, it is what stream get the change which has happen ,such as data insert or update.And applied_scn is used to identify the states streams have told other database .
My question is that,if I do nothing during a long time,the applied_scn stop,and archivelogs increase day after day.If these so large archivelog make the database down ,and I can not delete them .The streams can not work well, What can I do to prevent this thing to happen one day.
I have a solution,I do some changes to local databse.This make applied_snc increase.
Although the archivelog file increase ,I can delete them for the streams has get the informations form them ,But it is not a good idea.
Has a good idea? Help me!
Thank a lot!

Duplicate target database - is failed due to missing archive log

Hi,
"duplicate target database to " is failed due to required archive log is not found on tape.
After mounting the right tape, how to proceed , please suggest
ERROR:-->
RMAN>
connect catalog *******
connect auxiliary /
connect target ******
Run {
set until time '16-NOV-2008 23:50';
allocate auxiliary channel t1 type 'sbt_tape' parms ....
duplicate target database to mydb;
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/30/2008 10:27:00
RMAN-03015: error occurred in stored script Memory Script
ORA-19501: read error on file "orcl_ARCHIVES_BACKUP_0811160110_u0jvq7vt_1
_1", blockno 1 (blocksize=512)
ORA-27190: skgfrd: sbtread2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS1314E (RC14) File data currently unavailable on server
Recovery Manager complete.
Thanks In Advance,

This is basically not a RMAN problem,but a media management issue,which has to be addressed to the TSM staff:
ANS1314E
File data currently unavailable on server
Explanation:
The file data is currently unavailable on the server. A retrieve or restore operation was attempted. Possible causes are:
Data was corrupted at the server
Server found a read error
File is temporarily involved in a reclaim operation at the server
Server requested a tape volume that was marked unavailable.
System action:
Processing stopped.
User response:
Retry the operation. If the problem continues, see your system administrator to determine the problem from the server console or the activity log. Check whether any requests were made for a tape volume that was unavailable. A tape volume may be marked unavailable if prior read errors were encountered or the volume is checked out of the tape library.
Werner

Standby database is not applying redo logs due to missing archive log

We use 9.2.0.7 Oracle Database. My goal is to create a physical standby database.
I have followed all the steps necessary to fulfill this in Oracle Data Guard Concepts and Administration manual. Archived redo logs are transmitted from primary to standby database regularly. But the logs are not applied due to archive log gap.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
MRP0 WAIT_FOR_GAP
RFS RECEIVING
RFS ATTACHED
SQL> select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 503 677
I have tried to find the missing archives on the primary database, but was unable to. They have been deleted (somehow) regularly by the existing backup policy on the primary database. I have looked up the backups, but these archive logs are too old to be in the backup. Backup retention policy is 1 redundant backup of each file. I didn't save older backups as I didn't really need them from up to this point.
I have cross checked (using rman crosscheck) the archive log copies on the primary database and deleted the "obsolete" copies of archive logs. But, v$archived_log view on the primary database only marked those entries as "deleted". Unfortunately, the standby database is still waiting for those logs to "close the gap" and doesn't apply the redo logs at all. I am reluctant to recreate the control file on the primary database as I'm afraid this occurred through the regular database backup operations, due to current backup retention policy and it probably might happen again.
The standby creation procedure was done by using the data files from 3 days ago. The archive logs which are "producing the gap" are older than a month, and are probably unneeded for standby recovery.
What shall I do?
Kind regards and thanks in advance,
Milivoj

On a physical standby database
To determine if there is an archive gap on your physical standby database, query the V$ARCHIVE_GAP view as shown in the following example:
SQL> SELECT * FROM V$ARCHIVE_GAP;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 7 10
The output from the previous example indicates your physical standby database is currently missing log files from sequence 7 to sequence 10 for thread 1.
After you identify the gap, issue the following SQL statement on the primary database to locate the archived redo log files on your primary
database (assuming the local archive destination on the primary database is LOG_ARCHIVE_DEST_1):
SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 2> SEQUENCE# BETWEEN 7 AND 10;
NAME
/primary/thread1_dest/arcr_1_7.arc /primary/thread1_dest/arcr_1_8.arc /primary/thread1_dest/arcr_1_9.arc
Copy these log files to your physical standby database and register them using the ALTER DATABASE REGISTER LOGFILE statement on your physical standby database. For example:
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_7.arc';
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_8.arc';
After you register these log files on the physical standby database, you can restart Redo Apply.
Note:
The V$ARCHIVE_GAP fixed view on a physical standby database only returns the next gap that is currently blocking Redo Apply from continuing. After resolving the gap and starting Redo Apply, query the V$ARCHIVE_GAP fixed view again on the physical standby database to determine the next gap sequence, if there is one. Repeat this process until there are no more gaps.
Restoring the archived logs from the backup set
If the archived logs are not available in the archive destination then at that time we need to restore the required archived logs from the backup step. This task is accomplished in the following way.
To restore range specified archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore'
Restore archivelog from logseq=<xxxxx> until logseq=<xxxxxxx>
To restore all the archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore';
Restore archivelog all;
}

Problems Recovering Sysaux table space with missing archive log

Similar Messages

Maybe you are looking for