# of threads required between RAC Primary and RAC Standby

Oracle 11.1.0.7
Primary 3 Node RAC
Standby 2 Node RAC
Our primary (3 nodes) has 4 groups on each node, with the thread# relating to the instance number. For example, we have thread 1, 2, 3 each with 4 multiplexed groups.
Our standby was created with RMAN Duplicate and it also has 3 threads, but there are only 2 nodes.
The purpose of this Data Guard implementation is to migrate our development and acceptance environments to another data center with different hardware.
The new site has been running well and we started migrating development, where we did a switchover to the new environment; our standby databases are now our primary databases. We are going to keep the Data Guard implementation for awhile just to be sure all of the developers and applications are good.
I was going to drop the 3rd thread from the new primary (old standby) because there are only 2 nodes. I can take it down to 2 groups and then receive the error:
ORA-01567: dropping log 9 would leave less than 2 log files for instance play3 (thread 3)
ORA-00312: online log 9 thread 3: '+ASM_FRA_DA/dgplay/onlinelog/group_9.28331.811864225'
This group’s status is:
THREAD# GROUP# MEMBER SEQ STATUS
3 5 +ASM_FRA_DA/dgplay/onlinelog/group_5.8108.813676681             0 UNUSED
6 +ASM_FRA_DA/dgplay/onlinelog/group_6.8109.813676687             0 UNUSED
9 +ASM_FRA_DA/dgplay/onlinelog/group_9.28331.811864225            0 UNUSED
22 +ASM_FRA_DA/dgplay/onlinelog/group_22.18321.811184283           0 UNUSED
Plans are to un-Data Guard these environments to decommission the hardware. At that time I’m sure I can remove thread# because it’s not needed.
My question has to do with the logs needed between primary and standby. What I’m seeing is that the greatest number of threads are needed on each side, but not quite sure why if they are UNUSED. Can anyone elaborate on this? I can find no documentation that talks about this.
Sherrie

Hi,
You could do:
ALTER DATABASE DISABLE THREAD 3;
check status of the groups in the thread, if any of them <> UNUSED, then archive them:
ALTER SYSTEM ARCHIVE LOG GROUP x;
Then drop the groups.
My question has to do with the logs needed between primary and standby. What I’m seeing is that the greatest number of threads are needed on each side, but not quite sure why if they are UNUSED. Can anyone elaborate on this? I can find no documentation that talks about this. Actually a RAC standby can work with just 1 instance started, because the MRP process runs only on 1 instance. Opening the standby is another story.
But of course you should have enough standby redo logs on the standby site to receive redo from the primary site.

Similar Messages

Static listener registration 11gr2 RAC Primary and standalone Standby

Hi Guys,
I have to build up a single instance Physical Standby(Dataguard) for a primary RAC (11.2.0.1).The concern or rather confusion we have three SCAN LISTENERS across 2 node cluster,in order for me to have static registration for duplication of database for standby i need to have it put in the listener.ora .
Do i have to create the static listeners for default listener as well as the scan listeners?

My understanding is No.
The Oracle instance would automatically register the local listener to SCAN listeners, so I believe just the default needs this.
This document has Scan listener example and none of them use a _DGMGRL
http://www.oracle.com/technetwork/database/features/availability/maa-wp-11g-rac-standby-133152.pdf
Best Regards
mseberg
This document seems to support my statement :
11.2 Scan and Node TNS Listener Setup Examples [ID 1070607.1]
Edited by: mseberg on Aug 5, 2011 2:02 PM
Also of interest :
11gR2 Grid Infrastructure Single Client Access Name (SCAN) Explained [ID 887522.1]

Data guard synchronization after link down b/w primary and physical standby

Hi All,
I have configured data guard on oracle 11gr2 db. Normally switchover between my primary and physical standby happens smoothly and the Apply lag would be zero. Recently We had to test a scenario when the network link between Primary and Physical standby is completely down and Physical standby is isolated completely for more than half an hour.
When we brought up the link every thing worked smoothly but apply lag started increasing from 0 to around 3 hrs. And then it started reducing to 0. Currently Apply lag and transport lag shows 0.
But is this normal behaviour of oracle data guard that when the link between primary and physical standby is completely down, It requires 3-4 hrs for resynchronization ??? Even when during isolation, there were very few transactions happend on primary database ??
Are there any documents available for this scenario??
Thanks

Hi, after the link is up, if there were some transactions and produced archive logs it's normal to take some time for resync. To check if 3-4 hours is normal or not, you can repeat the scenario and this time check
- how many archivelogs does primary produce in this period.
- after the link is up, does archivelog transfer immediately starts from primary to standby? Is primary able to send these archivelogs parallel?
- Is there anything wrong with the apply process?
check primary & standby alert log files, and run this query on standby to check the transport and apply processes:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
regards

How to bind the Zero line between a primary and secondary Y axis?

All -
We are using combination charts with:
- primary and secondary Y axis (Sales versus Volume).
- Scale: Auto (Y) Axis
- Linear
- Fixed Label Size
In instances where one axis has a negative value and the value ranges are diverse the Zero line will be different for both. This causes some confusion when trying to read. Other that putting in manual (Y) axis with min and max, is there a way to force the chart to keep the same Zero line?
Thanks!

KOENIG Yvan wrote:
It's quite a basic requirement for a spreadsheet program
It's your point of view. It seems that it's not the designers's one
Obviously, true
The number of different features described once as "a basic requirement" is really amazing but a feature asked once is perhaps not one which must be added to a program like Numbers.
Other tools are available for professional numbers crunchers .
I know there are other threads asking about secondary axes, but your point is taken. I'm definitely not a number cruncher, but I am/was a pretty advanced Excel user.
_Go to "Provide Numbers Feedback" in the "Numbers" menu_, describe what you wish.
Then, cross your fingers, and wait _at least_ for iWork'09
Thanks for that, I didn't quite know where to go for the feedback - provided and fingers crossed.
Cheers!

What are the bandwidth requirements between a WCS and a WLC?

We have a customer who has two locations Site A (approx. 30 APs) and Site B (approx. 50 APs). Each site has a WLC. The customer wants to deploy a WCS at Site A that will monitor both WLCs.
What I have been unable to find is how much traffic is going to be generated between the WCS at Site A and the WLC at Site B?
Primarily, I would like to understand how this configuration will impact their point to point WAN link.
Also, are there any known requirements in terms of max. allowable latency between the WCS and WLC?
Any anectdotal evidence would also be appreciated - such as any experiences running this over a T1.
In this particular case, the customer has a 100Mbps wireless point-to-point link as their WAN link, but I do not know the actual throughput capacity and/or if it is half or full duplex.
Thanks,
John

John,
This is very interesting question and I will try to answer with what I know after supporting WCS for a while.
WLC and the WCS communicate over SNMP only. The generated traffic is SNMP (UDP). It's not a lot in terms of bandwidth, should I say quite minimal. Running over a T1 (not congested!) should be completly fine.
There are a few things we can control about snmp as you are over a WAN link: we can increase the SNMP timeout, we can increase the SNMP retries and also, we can reduce the max varbinds per PDU, so the snmp packets sent are smaller and dont get fragmented over your WAN ISP.
As SNMP is UDP, the only things you can control is the timeout and the number of retries because UDP doesnt have the control that TCP offers.
The most intense traffic will be when you first add your controllers in WCS.
I have seen quite a few deployments with WCS over WAN link and tweaking those settings I mentioned made it possible.
You can find those settings in WCS -> Administration -> Settings -> SNMP
HTH

Network bandwidth requirement between MDM server and MDM Clients

The MDM Sizing document for 5.5 states that 'a network connection between MDM Servers and MDM clients should be at least 100 Mbps'. Is this true? This would preclude MDM being offered as a hosted service. I'm interested in MDM Catalogue for SRM, so the catalogue content managers would need the import and data manager clients.

One factor I noticed, in our project...
I would recommend a 4 GB RAM for someone who is working with Import Manager.
As far as the Network connection goes, I am not sure what the requirements are.
We have faced several issues when the end user's laptop are less than 2 GB.
If someone is working with Image Manager, then I would recommend 4GB.
For bulk imports, I would use Import Server.

Time zone difference between primary and physical standby

Dear Team,
We have Primary database server (with EST Time zone) and physical standby (with PST time zone), in case of switch over/fail over to physical standby
what are the major impacts.
Is it mandatory to be in time sync?
Thanks in advance
Aj

CURRENT_TIMESTAMP
04-FEB-10 10.22.20.444692 AM +05:30
( above is same on primary and standby)
SQL> select systimestamp from dual;
SYSTIMESTAMP
03-FEB-10 08.52.46.934125 PM -08:00
(above is 3hr diff from primary and standby)It is 13hrs difference
One is around Indian subcontinent and other should be in US western region ?
Systimestamp is the timestamp of the OS of the server and hence the difference and the sysdate value will be from systimestamp and if the applications uses SYSDATE then there can be an issue...

Backing up primary and physical standby

We have a DG setup with a single instance primary node and a physical standby db. They both use their own FRA's and their own disks. Nothing is shared. Also the datafiles use OMF on both the db's. My questions are
1. Can i register the primary with the rman catalog and still backup the standby?
2. Should i backup the archive logs on primary? If so what rman settings should i use on both for the archive logs?
3. We wanted to back up both the dbs as it will be faster to restore since we wont have to convert filenames (cause of OMF) when we have to resotore backup taken on primary to standby or vice versa.
Any advise related to this scenario is highly appreciated.
Thanks.

Hi All,
you should have same rman format setting and log_archive_format on primary and standby database >to avoide any confusion at the time of restore. if you have different log_archive_format on standby then >primary, you might have to rename your archivelogs from standby to log_archive_format on primary.It is not required to have same log_archive_format for primary and standby database.
The database can be restored and recovered successfully even if the format is different.
Primary database
============
SYS @ oraprim> show parameter log_archive_format
NAME TYPE VALUE
log_archive_format string ARC%S_%R.%T
Standby database
=============
SYS @ orastdby> show parameter log_archive_format
NAME TYPE VALUE
log_archive_format string ARC_STDBY%S_%R.%T
Standby database
=============
C:\> set ORACLE_SID=orastdby
C:\>rman target / catalog recat/recat@recat
RMAN> backup archivelog all delete input;
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=98 recid=15 stamp=631239054
input archive log thread=1 sequence=99 recid=16 stamp=631239055
input archive log thread=1 sequence=100 recid=17 stamp=631239055
input archive log thread=1 sequence=101 recid=19 stamp=631239111
input archive log thread=1 sequence=102 recid=18 stamp=631239110
channel ORA_DISK_1: starting piece 1 at 22-AUG-07
channel ORA_DISK_1: finished piece 1 at 22-AUG-07
piece handle=C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP
tag=TAG20070822T001717 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
channel ORA_DISK_1: deleting archive log(s)
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00098_0630878042.001 recid=15 stamp=631239054
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00099_0630878042.001 recid=16 stamp=631239055
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00100_0630878042.001 recid=17 stamp=631239055
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00101_0630878042.001 recid=19 stamp=631239111
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00102_0630878042.001 recid=18 stamp=631239110
Finished backup at 22-AUG-07
RMAN>
Primary Database
=============
-- deleted users datafile and did complete recovery
C:\>set ORACLE_SID=oraprim
C:\>rman target / catalog recat/recat@recat
RMAN> run{
2> startup mount;
3> restore database;
4> recover database;
5> }
Oracle instance started
database mounted
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=98
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=99
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=100
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=101
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=102
channel ORA_DISK_1: reading from backup piece C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP tag=TAG20070822T001717
channel ORA_DISK_1: restore complete, elapsed time: 00:00:04
archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00098_0630878042.001 thread=1 sequence=98
archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00099_0630878042.001 thread=1 sequence=99
archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00100_0630878042.001 thread=1 sequence=100
media recovery complete, elapsed time: 00:00:07
Finished recover at 22-AUG-07
RMAN>
Regards,
Vaibhav

Diagnosing an ASM space issue for a primary and a standby database instance with external redundancy.

I've received an alert from Enterprise manager saying "Disk Group DATA_SID requires rebalance because at least one disk
is low on space". My colleague who I would go to with this question is unavailable, so this is a learning opportunity
for me. So far google and Oracle documentation have provided lots of information, but nothing that answers my questions.
I've run the following query on both the primary and standby databases ASM instances:
select name, disk_number, sector_size,os_mb, total_mb, free_mb, redundancy from v$asm_disk;
On the primary I get 4810M Free space and 18431M Total Space
on the standby I get 1248M Free space and 18431M Total Space -- this is the one that complained via OEM
When I run the following query in the database instance:
select sum(bytes)/1024/1024 MB from dba_segments;
I get 3736.75M as a result.
My questions are:
1. Will OEM's suggestion to rebalance the disk actually help in this situation since the instance is set up with external redundancy?
2. If I've got 18G of space and only 3.7G of data, why is OEM complaining?
3. How can I reclaim what I presume is allocated but unused space in my problem disk group?
4. How can I determine what extra data the standby has that the primary doesn't since both have the same total space allocation, but different amounts of free space?

Thank you for the reply. That link is very good.
We are an 11.1 version of our database. Linus is OEL 5.6.
So, looking at the portion of the link that refers to 'Add Standby database and Instances to the OCR' - If we use SRVCTL to give the STANDBY the role of ‘physical_standby’ and the start option of ‘mount’, what effect will that have if the STANDBY becomes our PRIMARY?
Would these database settings need to be modified manually with SRVCTL each time?
We understand why the instance is not starting when the node is rebooted, we are looking for a best practice of how this is implemented.
Thank you.

Steps for Data Guard with one primary and 2 standby

Hi,
Database :10.2.0.4, 11.2.0.1
Os: Windows , Unix
A ----------------> Primary database
B ----------------> Standby Database 1
C ----------------> Standby Database 2
I want to configure *2 standby* databases for single primary database.
Lets take, A ,B and C are my machines.My data guard configuration will be like,*archive logs will be moving* from A to B and A to C.
If i do any switchover in between A and B , now B is primary and remaining A and C are standby databases.At this stage also , archive logs should move from B to A and B to C. Also, same should happen from C to A and C to B,If i do switchover in between B and C.If everything is fine , then i will do switchback to main Primary database(A).
How do i have to mention PFILE in all machines ,the parameters like
LOG_ARCHIVE_DEST_1=LOCATION=<PATH> -- LOCAL ARCHIVE PATH
LOG_ARCHIVE_DEST_2=SERVICE=
LOG_ARCHIVE_DEST_3=SERVICE=
FAL_SERVER=
FAL_CLIENT=
STANDBY_FILE_MANAGEMENT=
In my tnsnames.ora , primary,standby1 and standby2 are my service entries and these are same in all of my machines.
Please suggest me , how do i can configure my pfiles in all machines ?.
Thanks,
Sunand

Not yet, but now you have me interested.
Please consider Flashback.
I still have to test but here's my take:
PRIMARY SETTINGS
*.FAL_SERVER=STANDBY
*.FAL_CLIENT=PRIMARY
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=PRIMARY
*.LOG_FILE_NAME_CONVERT='STANDBY','PRIMARY'
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRIMARY'
*.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_3='SERVICE=STANDBY2 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY2'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE
*.LOG_ARCHIVE_DEST_STATE_3=ENABLE
*.LOG_ARCHIVE_MAX_PROCESSES=30
STANDBY 1 SETTINGS
*.FAL_SERVER=PRIMARY
*.FAL_CLIENT=STANDBY
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=STANDBY
*.LOG_FILE_NAME_CONVERT='PRIMARY','STANDBY'
*.log_archive_dest_1=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_2='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
*.log_archive_dest_3='SERVICE=STANDBY2 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY2'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=DEFER
*.LOG_ARCHIVE_DEST_STATE_3=DEFER
*.LOG_ARCHIVE_MAX_PROCESSES=30
STANDBY2 SETTINGS
*.FAL_SERVER=PRIMARY
*.FAL_CLIENT=STANDBY2
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=STANDBY2
*.LOG_FILE_NAME_CONVERT='PRIMARY','STANDBY2'
*.log_archive_dest_1=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY2'
*.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_3='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=DEFER
*.LOG_ARCHIVE_DEST_STATE_3=DEFER
*.LOG_ARCHIVE_MAX_PROCESSES=30
Edited by: mseberg on Nov 29, 2010 9:39 AM
The first test slapped me. Looking at 409013.1 Cascaded Standby Databases
Edited by: mseberg on Nov 29, 2010 12:49 PM

Dataguard 9iR2 using same SID for primary and physical standby issues

Hello, I have been following the Creating Physical Standby Database document from Oracle setting up a physical clone for a 9iR2 database on Solaris 9 environment between two identical workstations. I want to databases to have the same SID for relatively seemless failover however the redo logs are not pushed to the physical clone. when I switch a logfile on the primary and then query v$archive_dest on dest_id=2 I get a status of ERROR and the ERROR is the ORA-12154 TNS service name error.
Here is a summary of my setup:
Primary - SID = PROD1, located on WS001
Clone - SID = PROD1, located on WS002
SPFILE settings on Primary:
*.db_name='PROD1'
*.dg_broker_start=true
*.fal_client='PROD1_node2'
*.fal_server='PROD1_node1'
*.log_archive_dest_2='service=PROD1_node2 optional lgwr async=20480 noaffirm reopen=15 max_failure=10 delay=30 net_timeout=30'
tnsnames.ora on Primary:
PROD1_node2 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = WS002) (PORT = 1521))
(CONNECT_DATA =
(SID = PROD1)
listener.ora on secondary:
PROD1_node2 =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = WS002) (PORT = 1521))
SID_LIST_PROD1_node2 =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME = /export/oracle/oracle_9.2/PROD1)
(SID_NAME = PROD1)
Any input would be appreciated. I can provide whatever else you might need. I thought this was the most pertinent to this problem.
Thanks.
Jim

I have been looking at the sqlnet.ora files for the two databases
for WS001:
Names.Default_Domain = WS001.example.com
Names.Directory_Path = (TNSNAMES, ONAMES,HOSTNAME)
for WS002:
Names.Default_Domain = WS002.example.com
Names.Directory_Path = (TNSNAMES, ONAMES,HOSTNAME)
I cannot connect with sqlplus from WS001 to WS002 on the other machine.

Upgrading the primary and physical standby database

Solaris 9
oracle 9i (9.2.0.8)
upgrade to 10g (10.2.0.3)
Hi,
I would like to know how to upgrade database in dataguard envronment.(primary and remote physical standby database)
Is rolling upgrade possible in this case?
Or any steps or Document is appreciated.
Thanks.
Message was edited by:
user539835

Read this Metalink Note:407040.1

Primary and Physical Standby databases hanging on sqlplus shell command...

I am primarily a java developer that has had the task of oracle dba thrust upon me due to circumstances that are beyond my control. In the QA lab we have two oracle 10 g release 1 instances running. They set up in a dataguard configuration: one is the primary and the other is in a physical standby.
Last week I noticed that the disk space on the primary database was at 100%. After some investigation I discovered that a good deal of the files taking up space on the box were log files and the best solution that I could think of would be to delete all old archive files. So I deleted the old archive files that were at least two weeks old using RMAN.
During this week the database started to shutdown automatically. The QA associate restarted the database twice using the ‘STARTUP’ command from sqlplus. Additionally, the standby database began to have issues: when login in to sqlplus the application would just hang: no ‘SQL” prompt or anything. Finally today the primary database has also begun to hang in a similar manner.
I have looked at many of the trace files and alert logs but haven’t been able to really discern what the real problem is with the database and the proper rectification for the database. Does anyone have a clue into what is going on? If someone could even point me in the right direction it would be greatly appreciated.

Guessing that your flash recovery area is full, archiving is stopped so the instance appears to hang.
Do you see messages like so in the alert log:
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
************************************************************************

ARCHIVELOG deletion on primary and physical standby

Hi,
We have a primary and a physical standby database running Oracle 11.1.0.7.0 software on Red Hat Enterprise Linux x-64 bit OS. I will be using backup software
to only backup the primary database and do not have the backup software for the standby server and database.
We need to backup archived redo log files from primary site and delete the ones which are more than one month old. These archived redo log files will be applied from primary to standby database as and when the log switch occurs.
Can anybody please let me know if the following steps can be used:
Details are:
primary database name - sun (machine name is node1)
standby database name - drsun (machine name is node2)
On node1 as oracle user:
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.sh
#!/bin/sh
ORACLE_SID=sun; export ORACLE_SID
ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1; export ORACLE_HOME
PATH=$ORACLE_HOME/bin; export PATH
$ORACLE_HOME/bin/rman target sys/oracle@sun nocatalog log=/export/home/oracle/rman/log/cleanup_rman_arch_sun.log
@/export/home/oracle/rman/scripts/cleanup_rman_arch_sun.rcv
exit
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.rcv
allocate channel for delete type disk;
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;
release channel;
$ crontab -l
# Delete the archived redo log files at 11:00 PM on the first day of every month
00 23 1 * * /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.sh
On node2 as oracle user:
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.sh
#!/bin/sh
ORACLE_SID=drsun; export ORACLE_SID
ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1; export ORACLE_HOME
PATH=$ORACLE_HOME/bin; export PATH
$ORACLE_HOME/bin/rman target sys/oracle@drsun nocatalog log=/export/home/oracle/rman/log/cleanup_rman_arch_drsun.log
@/export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.rcv
exit
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.rcv
allocate channel for delete type disk;
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;
release channel;
$ crontab -l
# Delete the archived redo log files at 11:00 PM on the first day of every month
00 23 1 * * /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.sh
Regards

Hello;
Welcome to the forums. ( By physical Standby I assume Data Guard )
The short answer is it should work. I noticed this :
/cleanup_rman_arch_drsun.rcv
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;I see no reason for the "alter system switch logfile". In fact you can do something very simple on the Standby :
$ORACLE_HOME/bin/rman target / catalog <user>/<password>@<catalog> << EOF
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-1';
exit
EOFThis assumes you have doing a backup with RMAN on the Primary ( tested on 11.2.0.2 ) and have this set on the Primary :
CONFIGURE ARCHIVELOG DELETEION POLICY TO APPLIED ON ALL STANDBY;
If you are deleting Archive without using RMAN first then yes something like this ( But I would try to use RMAN and not delete using another method )
echo `date`
echo "Runnung RMAN archive crosscheck"
$ORACLE_HOME/bin/rman <<EOF
connect target /
crosscheck archivelog all;
delete noprompt expired archivelog all;
exit
EOF
echo `date`
Best Regards
mseberg
h2. Another Standby Option
/u01/app/oracle/dba_tool/bin/removestandbyarch.sql
SET echo off
SET feedback off
SET term off
SET pagesize 0
SET linesize 200
SET newpage 0
SET space 0
col name format a120
spool /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
select 'rm '||NAME from v$archived_log
where REGISTRAR='RFS'
and APPLIED='YES'
and DELETED='NO'
and COMPLETION_TIME < (SYSDATE-10);
SPOOL OFFMain shell script
/u01/app/oracle/dba_tool/bin/removestandbyarch.sh
#!/bin/bash
if [ "$1" ]
then DBNAME=$1
else
echo "basename $0 : Syntax error : use . removestandbyarch <DBNAME> "
exit 1
fi
# Set the Environmental variable for input instance ( ORACLE_SID, ORACLE_HOME path etc )
. /u01/app/oracle/dba_tool/env/${DBNAME}.env
$ORACLE_HOME/bin/sqlplus /nolog <<EOF
   connect / as sysdba
-- spool /u01/app/oracle/dba_tool/bin/rm_arch_${ORACLE_SID}.sh
   @/u01/app/oracle/dba_tool/bin/removestandbyarch.sql
   SPOOL OFF
EOF
echo `date`
# Now run the generated script
echo "Setting permissions and running script"
chmod 740 /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
. /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
# Use RMAN to update V$ARCHIVED_LOG.DELETED
echo `date`
echo "Runnung RMAN archive crosscheck"
$ORACLE_HOME/bin/rman <<EOF
connect target /
crosscheck archivelog all;
delete noprompt expired archivelog all;
exit
EOF
echo `date`Edited by: mseberg on Apr 30, 2012 8:40 AM

Data Guard Archive Log Latency Between Primary and Physical Standby

How can I get the time it takes (latency) for the primary instance to get an archive log over to the physical standby instance and get it "archived" and "applied". I have been looking at the V$ARCHIVED_LOG view on each side but the COLUMN "COMPLETION_TIME" always shows a date "MM/DD/YY" and no timestamp. I thought the DATE datatype include data and time. Any ideas on how I can get the latency info I'm looking for?
Thanks
Steve

the COLUMN "COMPLETION_TIME" always shows a date "MM/DD/YY"
and no timestamp. Did you try using TO_CHAR ? e.g.
to_char(completion_time,'dd/mm/yyyy hh24:mi:ss')

# of threads required between RAC Primary and RAC Standby

Similar Messages

Maybe you are looking for