Primary/standby and 3rd archive log destination?

Running Oracle EE 10.2.0.4 linux 64 bit. I have a primary and standby configuration using data guard, with appropriate LOG_ARCHIVE_DEST_1, LOG_ARCHIVE_DEST_2 for the primary and standby - all works as expected. I want to multiplex the log files by adding a 3rd archive log destination to a different disk. I'm not clear on whether or not specifying a second 'primary' archive destination will write to both dest_1 and dest_3 or just alternate between the 2? I want to make sure that both DEST_1 and DEST_3 are written to (there can be a lag for DEST_3) -
Is the following all I need or are there additional parameters to LOG_ARCHIVE_DEST_n I'm missing?
LOG_ARCHIVE_DEST_3 = 'valid_for=(ONLINE_LOGFILE,ALL_ROLES)', 'location="/myThirdLoc"'
Thanks -

The database hang because of the redo log file is full. my test database is 16.7G and I gave the recovery filesystem 19 G for the redo log. Apparently it is not enough. After i set up the backup with daily incremental and run for 5 days, the recovery is full and db hang. How do you free up the space or set up the backup so that it can recycle the space? My DB is 10g r2 on RHEL3.

Similar Messages

Standby database Archive log destination confusion

Hi All,
I need your help here..
This is the first time that this situation is arising. We had sync issues in the oracle 10g standby database prior to this archive log destination confusion.So we rebuilt the standby to overcome this sync issue. But ever since then the archive logs in the standby database are moving to two different locations.
The spfile entries are provided below:
*.log_archive_dest_1='LOCATION=/m99/oradata/MARDB/archive/'
*.standby_archive_dest='/m99/oradata/MARDB/standby'
Prior to rebuilding the standby databases the archive logs were moving to /m99/oradata/MARDB/archive/ location which is the correct location. But now the archive logs are moving to both /m99/oradata/MARDB/archive/ and /m99/oradata/MARDB/standby location, with the majority of them moving to /m99/oradata/MARDB/standby location. This is pretty unusual.
The archives in the production are moving to /m99/oradata/MARDB/archive/ location itself.
Could you kindly help me overcome this issue.
Regards,
Dan

Hi Anurag,
Thank you for update.
Prior to rebuilding the standby database the standby_archive_dest was set as it is. No modifications were made to the archive destination locations.
The primary and standby databases are on different servers and dataguard is used to transfer the files.
I wanted to highlight one more point here, The archive locations are similar to the ones i mentioned for the other stndby databases. But the archive logs are moving only to /archive location and not to the /standby location.

Archive log destinations

We have a database with log_archive_dest1 set to /disk1... OPTIONAL and log_archive_dest1 set to db_recovery_file_dest. If log write fails to dest1 which is optional then the database continues to write to the db_recovery_file_dest since location one is optional.
My question is will the opposite be true: If db_recovery_file_dest is full (and the only thing going there is archive logs, will the database still archive to dest1 withoug halting the database until space is made available at the db_recovery_file_dest location?

No. The answer is no (unfortunately).
What is your LOG_ARCHIVE_MIN_SUCCEED_DEST set to?
If you want to prevent the database from stopping when you have this problem of filling up your primary destination, you can have multiple destinations and set your min succeed dest to a higher number than 1. Then, it will use another destination if the primary fills up.
Reference (good article):
=================
http://download-west.oracle.com/docs/cd/A81042_01/DOC/server.816/a76957/miginito.htm
The first destination, the standby destination, and either of the backup destinations are mandatory (minimum succeed destination count is 3).
With these assumptions, issue the following SQL statements to change your old archive log destination parameters to the new ones:
ALTER SYSTEM SET LOG_ARCHIVE_MIN_SUCCEED_DEST = 1;
ALTER SYSTEM SET LOG_ARCHIVE_DUPLEX_DEST = ' ';
ALTER SYSTEM SET LOG_ARCHIVE_DEST = ' ';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1 = 'enable';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2 = 'enable';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_3 = 'enable';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_4 = 'enable';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_1 = 'LOCATION=/oracle/dbs/arclog MANDATORY';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_2 = 'SERVICE=stndby1 MANDATORY';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_3 = 'LOCATION=/backup/dbs/arclog OPTIONAL';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_4 = 'LOCATION=/backup2/dbs/arclog OPTIONAL';
ALTER SYSTEM SET LOG_ARCHIVE_MIN_SUCCEED_DEST = 3;
Edited by: ji li on Oct 16, 2009 10:29 AM

Is RMAN only way to take backup and delete Archive Logs?

On primary db:
===============
OS: Windows 2003 server 32-bit
Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
On Physical standby db:
===============
OS: Windows 2003 server 32-bit
Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
Data Guard just configured. Archive Logs are properly being shipped to standby db. Is RMAN only way to take backup and delete Archive Logs from both primary and standby db? What other command can be used?
Thanks

No, but anything else is way more work. Without using RMAN you would have to find another way to keep track of applied logs.
RMAN make this very simple :
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;Using another method would be like using the handle of your screwdriver as a hammer.
See "RMAN Recipes for Oracle Database 11g" ISBN 978-1-5959-851-1
Best Regards
mseberg

Archived log destination

Hi,
In init.ora file,the archive destination is "oracle_home/database/archive" but all archived logs are placed in "oracle_home/rdbms/". why it is stored in that place, please tell me.
Thanks,
Venkat P.

venkat P. wrote:
Hi,
In init.ora file,the archive destination is "oracle_home/database/archive" but all archived logs are placed in "oracle_home/rdbms/". why it is stored in that place, please tell me.What's Your db version?
Is spfile or pfile is in use?
sqlplus> show parameter spfile;
If spfile is in use and You looked into init.ora, then of course You could observe difference in archive log destinations.
Are several archive_log destinations set and are they enebled?
sqlplus> show parameter log_archive_dest;
sqlplus> show parameter log_archive_dest_state;

Is the only way to import large amount of data and database objects into a primary database is to shutdown the standby, turn off archive log mode, do the import, then rebuild the standby?

I have a primary database that need to import large amount of data and database objects. 1.) Do I shutdown the standby? 2.) Turn off archive log mode? 3.) Perform the import? 4.) Rebuild the standby? or is there a better way or best practice?

Instead of rebuilding the (whole) standby, you take an incremental (from SCN) backup from the Primary and restore it on the Standby. That way, if, for example
a. Only two out of 12 tablespaces are affected by the import, the incremental backup would effectively be only the blocks changed in those two tablespaces (and some other changes in system and undo) {provided that there are no other changes in the other ten tablespaces}
b. if the size of the import is only 15% of the database, the incremental backup to restore to the standby is small
Hemant K Chitale

New standby not applying archive log

I have just created standby database....but its not applying archive log...
when I checked the alerlog file of standby....
ora-19527 physical standby redo log must be renamed

yes, I have created at onlien redo logs at standby database..
what is test and test?
i saw one command like this...
log_file_name_convert= ((''/u01/oradata/prod'', ''/u01/oradata/standby''),(''/u02/oradata/prod'', ''/u02/oradata/standby''))
My Primary DB name is OraclePM
My Standby DB name is OracleDR
I have placed all redo logs in direcrtory (D:\oracle\product\logs\ ) the directory structure for both databases is same... I have created 3 additionals redo logs at standby database...
How can I edit my standby init file...

Dataguard sync and applying archive log

Just did a check on my primary and standby using:
Primary:
SELECT max(sequence#) AS "PRIMARY" FROM v$log_history;
PRIMARY
45527
Standby:
SELECT max(sequence#) AS "STANDBY", applied FROM v$archived_log GROUP BY applied:
STANDBY APP
45476 NO
45528 YES
My question is how do I fix my sync?

SQL> select OPEN_MODE from v$database;
OPEN_MODE
MOUNTED
SQL> recover standby database until cancel;
ORA-01153: an incompatible media recovery is active
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Database altered.
SQL> recover standby database until cancel;
ORA-00279: change 4558008 generated at 08/21/2010 14:02:39 needed for thread 1
ORA-00289: suggestion : /data_gpfs/oracle/archivelogs/1_112_726952005.dbf
ORA-00280: change 4558008 for thread 1 is in sequence #112
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
*/data_gpfs/oracle/archivelogs/2_118_726952005.dbf*
ORA-00325: archived log for thread 1, wrong thread # 2 in header
ORA-00334: archived log: '/data_gpfs/oracle/archivelogs/2_118_726952005.dbf'

How to recover datafile in Oralcle 10g...? No backups and No archive log

All,
I need to recover the datafile 2 which is for undo tablespace and it is in recover state and i need to recover the data files now .
But the bad thing is We dont have backup at all and we dont have archive logs (Archive log disabled in the database)...
In this situation how can i recover the datafile ...?
SQL> select a.file#,a.name,a.status from v$datafile a,v$tablespace b where a.ts#=b.ts#;
FILE# NAME STATUS
1 /export/home/oracle/flexcube/product/10.2.0/db_1/oradata/bwfcc73/system01.dbf SYSTEM
*2 /export/home/oracle/logs/bw/undotbs01.dbf RECOVER*
3 /export/home/oracle/flexcube/product/10.2.0/db_1/oradata/bwfcc73/sysaux01.dbf ONLINE
4 /export/home/oracle/datafiles/bw/bwfcc73.dbf ONLINE
5 /export/home/oracle/datafiles/bw/bwfcc73_01.dbf ONLINE
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 4940
Current log sequence 4942

Hi,
First of all you must Open a ticket with oracle Support and explore the options
You can use this note to fix it:
RECOVERING FROM A LOST DATAFILE IN A UNDO TABLESPACE [ID 1013221.6]
If you is Unable to Drop Undo tablespace Since Undo Segment is in Needs Recovery
You can Upload the following trace file while opening the ticket
SQL>Alter session set tracefile_identifier='corrupt';
SQL>Alter system dump undo header "<new of undo segment in recover status>";
Go to udump
ls -lrt *corrupt*
Upload this trace file
Also upload the alert log fileRegards,
Levi Pereira
Edited by: Levi Pereira on Nov 29, 2011 1:58 PM

Compress and Ship Archive Logs to DR

I am currently working on Oracle 10.2.0.3, Linux 5.5 DR Setup. DR is at a remote location. Automatic Synchronous Archive shipping is enabled. As the DR is at a remote location transferring 500MB archive logs has a load on the bandwitdh. Is there anyway I can compress and send the archivelogs to DR? I am aware of the 11g parameter Compression=enabled, but i guess theres nothing on similiar lines for 10g.
Kindly help!
Regards,
Bhavi Savla.

AliD wrote:
What is "Automatic Synchronous Archive shipping"? Do you mean your standby is in MAXPROTECTION or MAXAVAILABILITY mode? I fail to see how transfering only 500MB of data to anywhere is a problem. Your system should be next to idle!
Compression is an 11g feature and is licensed (advanced compression license). Also if I'm not mistaken, 10.2.0.3 is out of support. You should plan to upgrade it as soon as possible.
Edit - It seems you mean your archivelogs are 500MB each not total of 500MB for the day. In that case to eliminate the peaks in transfer, use LGWR in async mode.
Edited by: AliD on 10/05/2012 23:24It is a problem as we have archives generating very frequently!!!

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.

Full backup and backup archive logs

Hello,
today in the early morning i did backup of my db with :
RMAN> backup as COMPRESSED BACKUPSET DATABASE format '/backup/%d_t%t_s%s_p%p';This command created two files :
[oracle@p1 backup]$ ls -l
total 1132680
-rw-r----- 1 oracle oinstall 1155940352 Sep 14 00:44 TEST_t697508918_s5_p1
-rw-r----- 1 oracle oinstall    2785280 Sep 14 00:44 TEST_t697509873_s6_p1Did i backed up archive logs also with this command ?
If I did not, do i have to i n order to have everything to do complete resterer and recovery ?
Is now to late to backup them?

Can you confirm that this backup will be placed in the FRA, it will backup all datafile, control files, spfile and control files all arhchivle logs and when backup finshes then will delete all archive logs ?+
after running that command yo can confirm it by yourself at RMAN prompt.
RMAN> list backup;
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
200     Full    509.78M    DISK        00:01:03     15-FEB-07
        BP Key: 202   Status: AVAILABLE Compressed: NO Tag: TAG20070215T171219
        Piece Name: /disk2/PROD/backupset/2007_02_15/o1_mf_nnndf_TAG20070215T171219_2xb17nbb_.bkp
List of Datafiles in backup set 200
File LV Type Ckp SCN    Ckp Time Name
1       Full 421946     15-FEB-07 /disk1/oradata/prod/system01.dbf
2       Full 421946     15-FEB-07 /disk1/oradata/prod/sysaux01.dbf
3       Full 421946     15-FEB-07 /disk1/oradata/prod/undotbs01.dbf
4       Full 421946     15-FEB-07 /disk1/oradata/prod/cwmlite01.dbf
5       Full 421946     15-FEB-07 /disk1/oradata/prod/drsys01.dbf
6       Full 421946     15-FEB-07 /disk1/oradata/prod/example01.dbf
7       Full 421946     15-FEB-07 /disk1/oradata/prod/indx01.dbf
8       Full 421946     15-FEB-07 /disk1/oradata/prod/tools01.dbf
9       Full 421946     15-FEB-07 /disk1/oradata/prod/users01.dbf
BS Key Type LV Size       Device Type Elapsed Time Completion Time
201     Full    7.98M      DISK        00:00:03     15-FEB-07
        BP Key: 203   Status: AVAILABLE Compressed: NO Tag: TAG20070215T171219
        Piece Name: /disk2/PROD/backupset/2007_02_15/o1_mf_ncsnf_TAG20070215T171219_2xb19prg_.bkp
SPFILE Included: Modification time: 15-FEB-07
SPFILE db_unique_name: PROD
Control File Included: Ckp SCN: 421968       Ckp time: 15-FEB-07
BS Key Size       Device Type Elapsed Time Completion Time
227     30.50M     SBT_TAPE    00:00:11     15-FEB-07
        BP Key: 230   Status: AVAILABLE Compressed: NO Tag: TAG20070215T171334
        Handle: 0bia4rtv_1_1   Media:
List of Archived Logs in backup set 227
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    5       389156     15-FEB-07 411006     15-FEB-07
1    6       411006     15-FEB-07 412972     15-FEB-07
1    7       412972     15-FEB-07 417086     15-FEB-07
1    8       417086     15-FEB-07 417114     15-FEB-07
1    9       417114     15-FEB-07 417853     15-FEB-07
1    10      417853     15-FEB-07 421698     15-FEB-07
1    11      421698     15-FEB-07 421988     15-FEB-07list backup will show you everything.
Would then this be incremental level 0 backup ?
yes by default i think so.
so with this i must be able to flasback my database at least 3 day in the past if i understood correctly.
But i am little puzled about purging those flasback data ...
Can you point me please to some link or tell how can i purge logs that are not need for that flashback period... ?
please read this link
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/rpfbdb003.htm#sthref513
Khurram

Data guard - logical standby in no archive log

We are creating a logical standby for reporting purpose only. I see no reason why it should be in archivelog mode. Would this hamper our current situation?

the solution is already approved , the only thing i could do is wonder if backup is necessary for the logical.
Its not going to be used for any purpose other than reporting.
From what i understand, no archivemode should not affect it. Is this undertanding true

Best way of deleting archive logs on standby when backup taken on primary

Hello,
I have a 11gr2 dataguard configuration without the broker.
main problem in my particular situation arises from my FRA size on primary much more than on standby (90Gb vs 30Gb) and in some situations I'm constrained with FRA space on standby.... I'm going to align the FRAs but in the mean time....
can anyone confirm that if I have configuration as in subject with maximum performance mode and I'm not using the broker I should consider a sort of "external" way for archive log deletion on the physical standby?
In fact I'm setting on primary
- retention policy = redundancy 1
- archivelog deletion = applied on standby (without using any "backed up...." option)
Considering the standby it seems from docs that:
- retention policy always wins over deletion policy (so no archive eligible for deletion is deleted if retention is not satisfied)
- I can set on standby archivelog deletion = applied on standby (without using any "backed up...." option)
But it is not clear to me the effect of this config in case this is a standby itself and without any other cascade standby databases
The manual says this has to be met:
1) The archived redo log files have been applied to the required standby databases.
---> what does this mean in case the db is a standby.. met or not met as I have no other cascade standby dependant on this one?
2) The logs are not needed by the BACKED UP ... TIMES TO DEVICE TYPE deletion policy. If the BACKED UP policy is not set, then this condition is always met.
---> I should be ok
So the last question for standby is
- what to set retention policy to?
I have not understood if I set it to "NONE", this means no retention at all or retention for ever....
sometimes I read that there is no policy; in other examples that files will be retained forever (because no file considered as obsolete).... or at least so I understood...
I would like to have a sort of policy on standby where the archive logs can be deleted as soon as they are applied during the continuous media recovery phase...
It seems I can't find a self contained set of configurations across the dataguard....
Thanks in advance.
Gianluca

I agree with you.... It is a temporary contingency....
I already stressed the fact that sizes between sites must be quite identical...
we are going towards a production dataguard, migrating from a windows config (without it) to a Linux based config....
but this contingency made me think about these considerations regarding policies and automatic dataguard operations
I also stressed on equal size grow capability for both sites file systems, also for data tablespaces, so that for example in case of high fragmentation we have to avoid a limit situation where
1) a file system full for DR datafiles causes abend of automatic media recovery
2) this generates FRA growth in DR because archive logs are shipped but not applied any more
3) FRA goes 100% in DR and primary cannot ship any more
4) archive logs cannot be automatically deleted on primary because not already shipped
5) FRA full on primary and DB hangs....
Thanks anyway for input

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?

Primary/standby and 3rd archive log destination?

Similar Messages

Maybe you are looking for