Is there anyway to read binary archive log file in a readable format

please advise..
thanks

Logminer is tool provide by Oracle to turn content of archive logs and redo logs into useful information.
Check here for more information
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14215/logminer.htm

Similar Messages

Are there any possible reason RMAN generates some corrupt archive log files

Dear all,
Are there any possible reason RMAN generates some corrupt archive log files?
Best Regards,
Amy

Because I try to perform daily backup at lunch time and found out it takes more than 1 hour had no any progress. Normally we take around 40 minus. The following is the log file:
RMAN> Run
2> {
3> CONFIGURE CONTROLFILE AUTOBACKUP ON;
4> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/db/backup/RMAN/%F.bck';
5> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
6> allocate channel ch1 type disk format '/u03/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
7> backup incremental level 1 cumulative database plus archivelog delete all input;
8> backup current controlfile;
9> backup spfile;
10> release channel ch1;
11> }
12> allocate channel for maintenance type disk;
13> delete noprompt obsolete;
14> delete noprompt archivelog all backed up 2 times to disk;
15>
16>
using target database controlfile instead of recovery catalog
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/db/backup/RMAN/%F.bck';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/db/backup/RMAN/%F.bck';
new RMAN configuration parameters are successfully stored
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
new RMAN configuration parameters are successfully stored
allocated channel: ch1
channel ch1: sid=99 devtype=DISK
Starting backup at 31-MAR-09
current log archived
After that I go to archive log directory "/u02/oracle/uat/uatdb/9.2.0/dbs" and use ls -lt command to see how many archive logs and my screen just hang. After we found out that we cannot use ls -lt command to read arch1_171.dbf
archive log, the rest of archive logs able to use ls -lt command.
We cannot delete this file as well. We shutdown database abort and perform check disk...... and fix the disk error and then open database again. Everything seems back to normal and we can use ls -lt command to read arch1_171.dbf.
The strange problem is we have the same problem in Development and Production..... one ore more archive logs seems to be corrupted under the same directories /u02/oracle/uat/uatdb/9.2.0/dbs.
Does anyone encounter the same problem?
Amy

What will happen when redo log file or archive log file, which is yet to be

What will happen when redo log file or archive log file, which is yet to be read by logminer is corrupted? It seems that the captures process hangs between “Paused for flow control” and “Enqueuing Messages”. How to come out of this condition without recreating the captures process?
Any clue is helpful
Thanks in advance for your help.

Basically you can't skip SCN since it will result in a data integrity issues (say you had skipped some inserts and later there will be some updates to a not replicated data).
Streams maintain their own checkpoint tables with transaction related stuff. So there is no way you can jump over a range of SCN's without recreating capture.
The only thing you can try - temporary give capture process a rule without any objects. But it will need to mine through the redo anyway.

How to delete the data in archived log files

hi
how can i delete the enteries in archived log files. and what is the disadvantage of deleting archived log enteries.

There is no documented way to delete data stored in archived log files: you can only remove the archived log files if needed.

Will RMAN delete archive log files on a Standby server?

Environment:
Oracle 11.2.0.3 EE on Solaris 10.5
I am currently NOT using an RMAN repository (coming soon).
I have a Primary database sending log files to a Standby.
My Retention Policy is set to 'RECOVERY WINDOW OF 8 DAYS'.
Question: Will RMAN delete the archive log files on the Standby server after they become obsolete based on the Retention Policy or do I need to remove them manually via O/S command?
Does the fact that I'm NOT using an RMAN Repository at the moment make a difference?
Couldn't find the answer in the docs.
Thanks very much!!
-gary

Hello again Gary;
Sorry for the delay.
Why is what you suggested better?
No, its not better, but I prefer to manage the archive. This method works, period.
Does that fact (running a backup every 4 hours) make my archivelog deletion policy irrelevant?
No. The policy is important.
Having the Primary set to :
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBYBut set to "NONE" on the Standby.
Means the worst thing that can happen is RMAN will bark when you try to delete something. ( this is a good thing )
How do I prevent the archive backup process from backing up an archive log file before it gets shipped to the standby?
Should be a non-issue, the archive does not move, the REDO is transported and applied. There's SQL to monitor both ( Transport and Apply )
For Data Guard I would consider getting a copy of
"Oracle Data Guard 11g Handbook" - Larry Carpenter (AKA Dr. Paranoid ) ISBN 978-0-07-162111-2
Best Oracle book I've read in 10 years. Covers a ton of ground clearly.
Also Data Guard forum here :
Data Guard
Best Regards
mseberg
Edited by: mseberg on Apr 10, 2012 4:39 PM

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.

Archived Log files

Hello,
I have a understanding problem off the function of the archived log files. My Oracle 9i Database is running in ARCHIVELOG. So if the online log files are full they get backed up to 3 different locations.
However if I view now the v$archive_log view then I see all the archived log files.
So now my questions:
1. At which point does these archived log files get deleted ?
2. If they never get deleted how do I know which archived log file can I delete.
3. If I run a full hot/cold backup can I delete this archive log files?
4. Is there any other way to delete the archived log files then using rman "delete input" option ? Like is there any way to delete the archived log files form the sqplplus prompt ?
I have searched and read some articles in the net about it but it is always just about how to set up the db into archivelog mode but I was not able to find anything answering my questions.
Thank you
Marcus

Out of the box, archived logs are not deleted
automatically. However, you can delete them via
RMAN. RMAN will delete them based on the set
retention policy. You can see which logs and
backups RMAN considers obsolete via the "report
obsolete" command. RMAN keeps track of logs that
are necessary for recovery, and those that can
be safely deleted.
Another option, as you have noted, is to backup
archivelogs using RMAN, with the "delete input"
option.
The best option (IMHO) is to automate deletion
of obsolete archive logs via a script. This
can be done using the "delete noprompt obsolete"
RMAN command.
I'm not aware of any SQLPlus based method to delete
logs. In any case, this would NOT be a good idea, as
RMAN would not be aware of any such deletions.
Hope this helps.
Kailash.

Removing archived log files

Hello all,
Using Oracle 10g R2 ( 10.2.4.0) under UNIX Sun Solaris 10 , I have two rman backup types
1-L0 backup
2-L1 Backup ( Incremental cummulative)
Facts:
-Due to space pressure on archived log destination I'm trying to get less archived files possible under the archived log fs thus at any given time the archived log files destination contains archived log files aged no more than 22hours.
* The backup runs each day at 4PM and there is custom script that remove and compressed archived log files ( out of backup jobs windows) from midnight until 3:45PM
* From the above removal schedule task L0 or L1 backup will always have 24 hours worth of archived log files available during the backup.
-The Backup files Windows retention period is 22 hours meaning that each backup type L0 or L1 removes previous backup files aged more than 22hours.
-Tracking file is enabled
Target:
Knowing that our backup retention windows is 22hours.
Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup.
Would this affect L1 backup? and how?
Thank in advance for your response
Alex

user8979607 wrote:
Hello all,
Using Oracle 10g R2 ( 10.2.4.0) under UNIX Sun Solaris 10 , I have two rman backup types
1-L0 backup
2-L1 Backup ( Incremental cummulative)
Facts:
-Due to space pressure on archived log destination I'm trying to get less archived files possible under the archived log fs thus at any given time the archived log files destination contains archived log files aged no more than 22hours.
* The backup runs each day at 4PM and there is custom script that remove and compressed archived log files ( out of backup jobs windows) from midnight until 3:45PM
* From the above removal schedule task L0 or L1 backup will always have 24 hours worth of archived log files available during the backup.
-The Backup files Windows retention period is 22 hours meaning that each backup type L0 or L1 removes previous backup files aged more than 22hours.
-Tracking file is enabled
Target:
Knowing that our backup retention windows is 22hours.
Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup.
Would this affect L1 backup? and how?
Thank in advance for your response
AlexI'm not sure what you are talking about with Backup files Windows retention period ... 22 hours".
I don't know what you mean by "Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup."
If you are not taking your database backups with rman you are on shaky ground. The principles are simple. To recover your database from a failure, you will need to start with an L0 backup. The rman RESTORE command will then restore individual blocks from any applicable and available L1 backups. You would follow that with a RECOVER command, that would attempt to apply all necessary redo from available archivelogs. If the necessary archivelogs have been deleted, rman will attempt to restore them from a backup. You can use rman to backup AND DELETE archivelog files to keep the archivelog destination cleaned out.
I take an L0 backup once a week, an L1 the other 6 days, and archivelogs twice a day. The only time I've had a problem with the archivelog dest filling up is when some buggy code that has a loop goes into production and starts flooding redo.
Exactly how are you taking your database backups? If you are not using rman, then you are already on shaky ground.

"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

Standby creating archives log files issue!

Hello Everyone,
Working on oracle 10g R2/Windows, I have created a dataguard with one standby database, but there is a strange issue that happen, and I'll need someone to shed the light to me.
By default archived log created from the primary database should be the sent to the stanndby database, but I found that the standby database has plus one archived log file.
From the primary database:
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination C:\local_destination1_orcl
Oldest online log sequence 1021
Next log sequence to archive 1023
Current log sequence 1023
contents of C:\local_destination1_orcl
1_1022_623851185.ARC
from the standby database:
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination C:\local_destination1_orcl
Oldest online log sequence 1022
Next log sequence to archive 0
Current log sequence 1023
contents of C:\local_destination1_orcl
1_1022_623851185.ARC
1_1023_623851185.ARC ---> this is the extra archive file created in the standby database, should someone let me know how to avoid this?
Thanks for your help

SELECT FROM v$version;*
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 64-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
The standby database is a physical standby database (not logical standby)
Thanks against for your contribution, but I'm still not know why standby create and arhive files too?

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.

DB backup and removal of archive log files?

I have an application that uses Oracle 10gR2 on Linux RedHat EL 4.5. The DB is fairly simple, so backing up daily or weekly by using expdp (Datapump) is fine for our needs. We have an install that uses Data Guard, which in archivelog mode is filling up the disks fast.
What is the best way to clean up archive log files in a Data Guard configuration? I have seen posts that indicate RMAN is tough to work with and has problems with recovery, so I would rather avoid it.
I would like script something on a daily or weekly basis.
Thanks,

RMAN not easy? Lets see how hard it is:
rman target /
RMAN> backup database;Surely that isn't too challenging.
Now if you want to do it properly you are talking about setting up a repository ... much more complex:
-- on the repository database server
CREATE USER repos
IDENTIFIED BY oracl1
DEFAULT TABLESPACE users
TEMPORARY TABLESPACE temp
QUOTA UNLIMITED on users;
GRANT create session, recovery_catalog_owner TO repos;
-- on the target server (your production db)
rman target / catalog repos/oracle1@<tnsnames_entry_for_your repository>
RMAN> create catalog;
RMAN> register database;
RMAN> backup database;If this is too much perhaps you should look into MS Access. <g>
All of this is documented at the top of the RMAN page in Morgan's Library at www.psoug.org so you can cut-and-paste your way through it if you want.
How is an export not a backup you ask?
The Oracle docs can be found at http://tahiti.oracle.com. You should consider reading them some time.
As I said before ... an export can NOT be used to recover ... ever. That says it all.
Your resistance to change. Your resistance to doing things properly. Your resistance to reading the docs. You'd better watch out. There are people who would like to have your job ... a lot of them.

Archive log file size is varying in RAC 10g database.

---- Environment oracle 10g rac 9 node cluster database, with 3 log groups for each node with 500 mb size for each redo log file.
Question is why would be the archive log file size is varying, i know when ever there is log file switch the redo log will be archived, So as our redo log file size is of 500 MB
isn't the archive log file size should be the same as 500 MB?
Instead we are seeing the archive log file is varying from 20 MB to 500 MB this means the redo log file is not using the entire 500 MB space? What would be causing this to happen? how can we resolve this?
Some init parameter values.(just for information)
fast_start_mttr_target ----- 400
log_checkpoint_timeout ----- 0
log_checkpoint_interval ----- 0
fast_start_io_target ----- 0

There was a similar discussion a few days back,
log file switch before it filled up
The guy later claimed it's because their log_buffer size. It's remain a mystery to me still.

How to Recover database from old backup and full archive log file

Hi Oracle expert!
I met problem when restore my oracle database.
In my case:
- My database version: 10.2.0.2
- I have a database full backup (01-Nov)
- I have all Archived log file from (01-Nov -> 05-Nov)
- My database drop in 05-Nov with disk error (no datafile, no redo..).
- I have no any RMAN backup from (01-Nov -> 05-Nov)
How can i restore my database to 05-Nov?
Thanks

user10280724 wrote:
Hi Chinar.
When i used RMAN flow as your step, but i met the problem!
- After recover database i select sequence#, applied from v$archived_log;
--> it apply newest archived log that i had.
- but when I select Data from table created between 01-Nov to 05-Nov, it not found!
Not the same way the step:
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL?
It apply newest the same archived log i had table created between 01-Nov to 05-Nov.
How can i do with RMAN to recover my table?That is not possible,if your all available archive logs applied using rman or through sqlplus(recover database using backup controlfile until cancel) and one of these logs contain your table then there are not any problems.So there are not any difference between recovery using rman and user managed(using sqlplus),but there main matter is applying all archive logs.So first check through rman list copy of archivelog all or list backup of archivelog all and identify there in rman repository is any information or not about these logs.

Manual delete archived log files

Because we don't have RMAN in our development server, I need to use manual operation to delete all archived logs. Is my procedure correct and safe?
SHUTDOWN IMMEDIATE
STARTUP MOUNT
ALTER DATABASE NOARCHIVELOG;
EXITRun OS command to manually delete archived log files:
rm /oradata/arch/*
Login to sqlplus
SHUTDOWN IMMEDIATE
STARTUP MOUNT
ALTER DATABASE ARCHIVELOG;
STARTUP OPENThanks!

linuxos wrote:
Oh I suppose RMAN need to be configured somthing before use. I tried it, and find no pre-requisite is required. Thanks!
If the archives are deleted manually in open mode, how can Oracle match the archived logs' retention policy? Does Oracle store the archived logs in data dictionary?While you can delete archivelogs manually any time you want, you should let rman manage them with appropriate rman commands, preferably in a script that you schedule for regular execution.
Some of your questions lead me to question if you understand that archivelogs are not actively open by the database, and they technically are not part of the database. They are simply a series of "offline" copies of the online redo logs. They are written to once, when an online redo is being archived, then they just sit there until needed for a recovery.

Is there anyway to read binary archive log file in a readable format

Similar Messages

Maybe you are looking for