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

Similar Messages

Archive logs and recovering database with no RMAN

Hello,
I inherited a database with no RMAN backup activated but archive redo logs are activated and generating at every moment.
As there is no rman backup I always thought that those archive redo logs were useless and because of reduced disk space, regularly I delete all of them.
Then I read that archive redo logs can be usefull even if there is no RMAN. Archive redo logs can be used in a recovery situation like this:
set all tablespaces in backup mode
alter tablespace tsp1..tsp100 begin backup;
copy all datafiles
alter tablespace tsp1..tsp100 end backup;
alter database create standby controlfile as 'c:\temp\sbytemp.ctl';
copy of archivelogs from start begin backup time till nowAs I delete my archive logs, I don't have all ones from the first time. My question is:
How many archive redo log files would I need to have? Would I need to have all archive logs that were generated from the first time? Or would be enough to have the last three or four ones?
Thanks
Edited by: user521219 on 21-may-2012 7:50

How many archive redo log files would I need to have?
Would I need to have all archive logs that were generated from the first time?
would be enough to have the last three or four ones?You need all archive redo log from the moment you have started taking full backup.
If you take full backup every night at 1:00 AM, you will need all archive redo logs that have transactions finished at and after 1:00 AM.

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

When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode

Question :
When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode ?
Example:
Create Tablespace
CREATE SMALLFILE TABLESPACE "TEST_DATA"
LOGGING
DATAFILE '+DG_TEST_DATA_01(DATAFILE)' SIZE 10G
AUTOEXTEND ON NEXT 500K MAXSIZE 31000M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
LOGGING: Generate redo logs for creation of tables, indexes and partitions, and for subsequent inserts. Recoverable
Are they not logged and not recoverable if we do not enable LOGGING? What is that ARCHIVELOG mode does?

What is that ARCHIVELOG Mode Does?
Whenever your database is in archive log mode , Oracle will backup the redo log files in the form of Archives so that we can recover the database to the consistent state in case of any failure.
Archive logging is essential for production databases where the loss of a transaction might be fatal.
Why Logging?
Logging is safest method to ensure that all the changes made at the tablespace will be captured and available for recovery in the redo logs.
It is just the level at which we defines:
Force Logging at DB level
Logging at Tablespace Level
Logging at schema Level
Before the existence of FORCE LOGGING, Oracle provided logging and nologging options. These two options have higher precedence at the schema object level than the tablespace level; therefore, it was possible to override the logging settings at the tablespace level with nologging setting at schema object level.

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;
}

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

How to find thead 2 archive log when i recover from 2-node RAC to single

I backup 2-ndoe RAC and restore to single - node
Control file created.
SQL> recover database iuckup controlfile
SQL> recover database using backup controlfIle;
ORA-00279: change 12100176131169 generated at 07/06/2013 16:36:57 needed for
thread 1
ORA-00289: suggestion : /arch/hop1_566085708_1_212692.dat -- Oracle suggest
ORA-00280: change 12100176131169 for thread 1 is in sequence #212692
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
arch/sch1_566085708_1_212692.dat --- I input
ORA-00279: change 12100176131169 generated at needed for thread 2
==> Oracle didn't suggest thread 2 archive log file/
How can I find ?

You have to query V$ARCHIVED_LOG for THREAD# 2 on the source database to find the first archivelog where 12100176131169 is less than the NEXT_CHANGE#
select SEQEUNCE# from V$ARCHIVED_LOG where THREAD#=2 and 12100176131169 between FIRST_CHANGE# and NEXT_CHANGE#
Once you provide the Sequence# and file name for the first Thread 2 file, the RECOVER command will automatically generate the expected file name for the subsequent archivelogs (of both threads).
Hemant K Chitale

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

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

Too many archived logs when trying a backup

Hello all,
I'm having a bit of trouble running a backup script on an Oracle instance (10g1, on Solaris).
As a normal DBA practice, I guess the backup should be scheduled and run from the very beginning of using a DB. Sometimes, from various reasons, this does not happen. In this case, before running the first (full) backup of the DB, there might be tens or hundreds of archived logs waiting to be backed up, and the flash recovery area might just not be able to handle all of them (at least that's how I see it, I might be wrong, I'm still fighting my way through Oracle's Backup and Recovery issues). In that case, a backup script containing the following RMAN sequence:
run{
allocate channel ch1 type disk;
backup
incremental
level = 0
database;
release channel ch1;
fails with the error message ORA-19804 (cannot reclaim disk space from the DB_RECOVERY_FILE_DEST_SIZE limit).
After this, the archived logs that were backed up are marked as obsolete, and I can delete them from RMAN with "delete obsolete". The script I'm using for backup runs fine afterwards. Before attempting a backup, however, no logs are reported as obsolete.
The retention policy is the default "redundancy 1" and the archivelog deletion policy is none.
How could I prevent the backup script from crashing? If I'm changing the archivelog deletion policy, will I be able to restore the DB properly from my backup set? (as earlier logs will be deleted before making a backup)
Thank you for any suggestions, your help is very much appreciated,
Adrian

I am having an impression that you are not using scheduled backups and let client decided when to take backup. Well this is not good, in this case you won't be able to get rid of this error bcz you never know when the next or even first backup is going to occur and without that you can't even think of deleting your logs. If you are not using tape drives then your archivelogs and backups both will sit in recovery area and you should have enough available space to hold both of them. I would say to schedule your backups and use DELETE INPUT clause of RMAN backup to delete the archivelogs after backing them up. And also delete the obsolete backups according to your recovery window. This is the proper way to manage recovery area space. You really need to tune the recovery area space by testing the amount of redo generation, backup size, retention policy etc etc and then come up with a figure of recovery area size which is suitable for your env to hold all of the required files for required time (recover window).
Daljit Singh

Manually apply archived log to standby database.

Hi all,
I am working on oracle 10g EE(10.2.0.4).I am having a very difficult database switchover case in my hand.
1.> There are two database .one primary(prim) and another standby(standby).
2.> Initially both of them was configured as oracle data guard, where prim was primary and standby was standby using rman .(RMAN>duplicate target database for
standby dorecover).
3.>But the rate of generation of archivelog is very high( 20 archivelog per hour with 200mb each).
4.> So automatic shipping of archivelog has been disabled from primary.(log_archive_dest_state_2=defer and nullifying the value of log_archive_dest_2).
5> Now after a period of time archived logs are shipped to dr site manually and applied manually.(alter database recover automatic standby database;)
6.> Now there is a hardware problem occured at primary..it will take 72 hours to come up.
How can i use standby database as primary for that 72 hour.As archive log apply is manually done and parameters are being changed,can i switch over these two?
Is it possible to switchover and switch back these two database with such a configuration?

How can i use standby database as primary for that 72 hour.As archive log apply is manually done and parameters are being changed,can i switch over these two?
Is it possible to switchover and switch back these two database with such a configuration?
As of now you can perform failover your standby to primary database. you should have flashaback enabled, so you have to create a restore point.
Then it can be opened in read & write mode, So once you finished again you can go back to that point.
http://docs.oracle.com/cd/B19306_01/server.102/b14239/manage_ps.htm#i1017111
The above case applicable if you ready to loose, But it doesnt make sense. But in your case this doesnt work. Because once you start use of Standby as primary, there would be live/production data, which you need very much.
So there is lot of work to do.
You have to rebuild standby database and then switchover back to same location. So its a little trip work.
Have you enabled Dataguard Broker ?
Edited by: CKPT on Mar 13, 2012 1:43 PM

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

Error returns when "Recover database"?

Hi all experts,
I am doing recover the database and get the following errors, I don't know what I have done wrong?
recover database;
Starting recover at 05-MAR-08
using channel ORA_DISK_1
starting media recovery
unable to find archive log
archive log thread=1 sequence=9
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/05/2008 17:19:37
RMAN-06054: media recovery requesting unknown log: thread 1 scn 1254920
Any ideas,
Fan

I have done what you said and get the followings:
ORA-00279: change 1254920 generated at 03/05/2008 14:11:26 needed for thread 1
ORA-00289: suggestion : /home/oracle/OraHome1/dbs/arch/1_9.dbf
ORA-00280: change 1254920 for thread 1 is in sequence #9
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/home/oracle/OraHome1/dbs/arch/1_9.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
It seems to be SCN 1254920 for thread 1 is in sequence #9 and the 1_9.dbf not found. I didn't delete any files in redo log arch directory. What if this possible happen?
I am really tired. Any ideas?
Fan

Transfering archive logs in standby database

hi,
i am trying to create a standby database for a a test scenario using oracle 10g R2 and windows xp
Primary DB = primary
standby DB=stby
iam able to ping databases from each other using tnsping , but iam not able to transfer archive logs from primary to standby
pfile for primary is
primary.__db_cache_size=67108864
primary.__java_pool_size=4194304
primary.__large_pool_size=4194304
primary.__shared_pool_size=88080384
primary.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0/admin/primary/adump'
*.background_dump_dest='C:\oracle\product\10.2.0/admin/primary/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\primary\control01.ctl','C:\oracle\product\10.2.0\oradata\primary\control02.ctl','C:\oracle\product\10.2.0\oradata\primary\control03.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0/admin/primary/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='primary'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=primaryXDB)'
*.job_queue_processes=10
*.log_archive_dest_2='SERVICE=stby'
*.log_archive_dest_state_2=ENABLE
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0/admin/primary/udump'
log_archive_dest_1='LOCATION=C:\oracle\product\10.2.0\db_1\database\archive'
log_archive_dest_state_1=ENABLE
LOG_ARCHIVE_CONFIG='DG_CONFIG=(primary,stby)'
pfile from standby
primary.__db_cache_size=75497472
primary.__java_pool_size=4194304
primary.__large_pool_size=4194304
primary.__shared_pool_size=79691776
primary.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\stby.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='primary'
db_unique_name='stby'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=primaryXDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\udump'
standby_archive_dest='C:\oracle\product\10.2.0\stbyarch'
db_file_name_convert='C:\oracle\product\10.2.0\oradata\primary','C:\oracle\product\10.2.0\oradata'
log_file_name_convert='C:\oracle\product\10.2.0\oradata\primary','C:\oracle\product\10.2.0\oradata'
standby_file_management=AUTO

You do not point to the standby database from your primary, in order to get the archivelogs transfered. You need to set at least the parameter LOG_ARCHIVE_DEST_2 like this:
SQL>alter system set LOG_ARCHIVE_DEST_2='SERVICE=stdby VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stdby';stdby has to be resolved by the tnsnames.ora on the primary server. Have a look here:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i67520
That explains all you need to do to create a physical standby briefly.
Kind regards
Uwe
http://uhesse.wordpress.com

Missing archived logs when recovering database

Similar Messages

Maybe you are looking for