Question regarding removal of physical standby database?

We are running a 2 node rac cluster on linux itanium and we have setup one physical standby server. We did not use the data guard broker to setup the standby database we simply set 2 parameters log_archive_config and log_archive_dest_2.
We now are looking to remove the physical standby server and I see that the 2 parameters are dynamic so I was trying to find out if it is as simple as running the alter system comands to reove the 2 parameters?
I gues my real question is more about the syntax of removing the parameters?
Would this syntax be correct?
alter system set log_archive_config='' scope=both sid='*';
alter system set log_archive_dest_2='' scope=both sid='*';
and does it make a difference which parameter is removed first?
Thanks I appreciate any help.

the standby system is also a 2 node cluster but only one of the nodes has the instance up in a mount state running in recover mode and the other instance is simply shutdown.
Thanks.

Similar Messages

Questions regarding creating a physical standby database in 10gR2

I'm setting up a physical standby database in a test environment using two windows 2003 servers. I was wondering if someone could answer a few questions I'm not too clear on. I've been thru the data guard manual and as much online information as i can find. I may have it working but wanted to post some things I'm not sure I did quite right.
My tnsnames.ora files.
On my primary database server:
# tnsnames.ora Network Configuration File: F:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.
PRIMARY =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = SERVER1)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = PRIMARY.MYDOMAIN.com)
STANDBY =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = SERVER2)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = STANDBY.MYDOMAIN.com)
On my physical standby database server:
# tnsnames.ora Network Configuration File: f:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.
STANDBY =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = SERVER2)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = STANDBY.MYDOMAIN.com)
PRIMARY =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = SERVER1)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = PRIMARY.MYDOMAIN.com)
My Listener.ora files:
On my primary database server:
# listener.ora Network Configuration File: F:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = PRIMARY.MYDOMAIN.com)
(ORACLE_HOME = f:\oracle\product\10.2.0\db_1)
(SID_NAME = primary)
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = server1.mydomain.com)(PORT = 1521))
On my physical standby database server:
# listener.ora Network Configuration File: f:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = standby.mydomain.com)
(ORACLE_HOME = f:\oracle\product\10.2.0\db_1)
(SID_NAME = standby)
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = sever2.mydomain.com)(PORT = 1521))
The next item I'm not sure about is after creating the control file for standby use.
One the primary server I created it using:
alter database create standby controlfile as 'sbcontrol01.ctl';
I copied the primary database pfile I had created earlier to the standby server, renamed it and edited it.
Initially I left the CONTROL_FILES= parameter pointing to the control01.ctl, control02.ctl and control03.ctl that I restored. But I was getting the error ORA-01665: control file is not a standby control file
So I copied the sbcontrol01.ctl to sbcontrol02 and sbcontrol03.ctl and pointed the CONTROL_FILES= parameter at them.
The error went away and the database came up. I still need to test it some more but wanted to see if what i did was correct or a fluke.
Edited by: tjohnson on Mar 23, 2009 2:26 PM

If in the primary I had control files named control01, control02 and control03 would I have been able to create a standby controlfile called control01.ctl or would I have had to name it something else like I did (sbcontrol01.ctl) and rename it to control01.ctl once I got it over to the standby database server?Suppose you have the primary database control file in C:\oracle\primary\control location with names control01.ctl and control02.ctl. Then also you can create a standby controlfile with control01.ctl and control02.ctl , but then the location to be created must be different.You can create it in C:\oracle\primary location and then transfer to the specified location mentioed in the pfile of the standby database and mount the standby database.
But saying this i would suggested to keep the name different from control01.ctl as far as naming conventions are followed.It might confuse someoe whether its a primary database controlfe or a standby database controlfile.Usally primary database controlfile are named control01.ctl , coltrol02.ctl etc and for standby many do prefer keeping standby01.ctl, standby02.ctl.Thats just for for understanding.
HTH
Anand

Physical Standby database Vs. Logical Standby database

I have few questions regarding capability of Logical Standby Database against Physical Standby database.
1. How efficient is Logical Standby database in terms of Physical Standby Database?? How both differ from each other and can I use Logical Standby Database for disaster Recovery?? Can It be use for recovering the failed Primary Instance?? If yes how efficient and reliable it is??
2. What are the known bugs and roadblocks for logical standby database on Oracle 10.2.0.1 on Soalris X86-64?
3.As logical standby database not going to replicate each and every schema of Primary database?? how is the change management effects to the logical standby from primary?? I mean there are some parameters and job that we create on primary how can it be transferred over to the logical standby??

1. How efficient is Logical Standby database in terms
of Physical Standby Database?? How both differ from
each other and can I use Logical Standby Database for
disaster Recovery?? Can It be use for recovering the
failed Primary Instance?? If yes how efficient and
reliable it is??I'm not sure what sort of "efficiency" you're talking about here...
Physical standby is just the old, tried and true application of archived logs to recover a database. Very solid, very old school.
Logical standby, on the other hand, is parsing the redo log, extracting logical change records, and applying them to the standby database. This obviously takes a bit more processing effort, it's newer technology, it doesn't have quite the level of support that physical standby does (i.e. certain data types are excluded), etc. You certainly can use it for failover, but it isn't quite as robust as a physical standby. Of course, this is getting better and better all the time and is definitely a focus of Oracle's development efforts.
On the other hand, logical standby systems can do things other than act as a warm standby. They can be open serving reports, for example. You can create additional structures (i.e. new materialized views) to support reporting. A physical standby is pretty much always going to be in managed recovery mode, so it cannot be queried.
2. What are the known bugs and roadblocks for logical
standby database on Oracle 10.2.0.1 on Soalris
X86-64?a) You'll want to do a Metalink search
b) If you're talking about a high-availability solution, why are you looking at a base release of the database? Why wouldn't you apply the latest patchset?
3.As logical standby database not going to replicate
each and every schema of Primary database?? how is
the change management effects to the logical standby
from primary?? I mean there are some parameters and
job that we create on primary how can it be
transferred over to the logical standby??I'm not sure I understand... Changes made to the primary generate redo. Oracle parses that redo, generates a LCR, and sends that to the standby database where that change record gets applied.
Justin

Need advice regarding physical standby databases in rac environment on orac

need advice regarding physical standby databases in rac environment on oracle 10G r2
I like to have have a Primary ( 10 node RAC cluster ) shipping to a physical standby ( 3 node RAC cluster ) shipping using LGWR .
So I have a lot of questions
1) What will be the performance overhead on the Primay if we are using LGWR SYNC option .
2) Does the overhead depends on the physical distance between primary & physical
3)Do you recommend a seperate private network for shipping logs between primary and standby.
4) I know that DGMGRL supports RAC only from 10g. So are there any know issues are bugs using DGMGRL is RAC environments.
Thanks in advance
-Satish

Generally you should have same CPU architecture and same operating system but it's not mandatory to have the exactly the same CPU model, the same number of CPU, the same RAM size etc.
Actually starting with 11.1 you don't need to have the same hardware setup: it 's even possible to have primary and standby database on different platforms: http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/standby.htm#i72053.

How to create 11.2.0.2 physical standby database from 2 node RAC (11.2.0.2)

Hi,
Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
DB : 11.2.0.2
OS : RHEL5
RMAN duplicate is causing problem with network and we decided to go for manual creation of the same.
Thanks in Advance..

Hi;
Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
DB : 11.2.0.2
OS : RHEL5I had similar issue, what i did
1. Used source oracle_home on standby server
2. Created new asm instance and use same naming
3. I took RMAN full backup on source and move it to target
4. I edit initora file remove RAC setting and restore db(also edited listener file)
Regard
Helios

Configuring a physical standby database in 9i

Hi all,
   SO: Solaris 10 SPARC x64
   DB: 9.2.0.6 x64
   I have a task of creating a physical standby database in a solaris 10 - Oracle 9.2.0.6 env. I am used to do this configuration on the 11.2 version of Oracle, and because of that i have some doubts regarding the possible different configurations necessary to do in a 9i Database.
   1) The main doubt that i have is regarding the RMAN use. I Would like to know if it is possible to restore a normal backup of my primary database into the standby database, and after that, apply the necessary archived logs to sync the standby with the primary? The controlfile that i would use would be the one created by the "BACKUP CURRENT CONTROLFILE FOR STANDBY" RMAN command. The RMAN script woulb be like the one below:
run {
allocate channel ch01 device type disk;
allocate channel ch02 device type disk;
allocate channel ch03 device type disk;
allocate channel ch04 device type disk;
restore controlfile from 'standby_controlfile.ctl';
sql 'alter database mount';
restore database;
recover database;
   2) The directory structure will be the same, so i think it is not necessary to use the SET NEWNAME and the DB_FILE_NAME_CONVERT/LOG_FILE_NAME_CONVERT, is that correct?
   3) Do you have any other considerations regarting the differences between a 9i and a 11g Physical Standby Configuration?
Thanks for your attention and pacience.

Hello;
On question 1 - See this:
http://docs.oracle.com/cd/B10500_01/server.920/a96566/rcmstand.htm
On question 2 - Assuming RMAN work then DB_FILE_NAME_CONVERT/LOG_FILE_NAME_CONVERT would NOT have to be set for the same directory structure.
On question 3 - double check this:
http://docs.oracle.com/cd/B10500_01/server.920/a96653.pdf
Best Regards
mseberg

Data Guard - Steps to install Physical standby database in an RHEL 5.6 x86

HI Team,
I need to install Physical standby database in a OS installed from factory with most basic packages. Please find the info in detail
Standby Server :
Database Version : 10g Release 2
Operating System : Red Hat Enterprise Linux Server release 5.6 (Tikanga) , RHEL 5.6 x86_64
swartis.dc$ free -m
total used free shared buffers cached
Mem: 34158 33847 311 0 558 28367
-/+ buffers/cache: 4921 29237
Swap: 10001 63 9937
- Things i need to validate in the PROD server. Eg : Are the prod db version & standby db version should be the same, Do the OS need to be same ............ETC
- Basic Linux rpm required for standby server & any other pre-requisites required at standby server
- Verify connectivity speed btw servers to decide log file size
- Please give me more detailed steps , where i need to start the steps in installation of Physical standby database.
Thanks in advance.
-- Rakesh
Edited by: Rakesh on Jan 10, 2012 8:23 AM

Hello again;
Sorry for the Delay.
To this question "Do i need to install 10.2.0.2.0 ORACLE_HOME & on top of it apply 10.2.0.3.0 patchset.?"
Yes.
All my Oracle 10 installs started with 10.2.0.1 and then I patched up from there. If I remember correctly 10.2.0.1 may bark on Red Hat 5.
You can work around this by reviewing this file :
/etc/redhat-releaseSave whatever is in there somewhere and replace it with :
redhat-3After the install put back what was there and get rid of the "redhat-3".
I extra RPM's I used were :
rpm -ivh kernel-headers-2.6.18-164.el5.x86_64.rpm
rpm -ivh compat-libstdc++-33* libaio-devel*.x86_64.rpm
rpm -ivh elfutils-libelf-devel*.x86_64.rpm glibc-devel-2* gcc-4*.x86_64.rpm gcc-c++-4*.x86_64.rpm libstdc++-devel-4*.x86_64.rpm glibc-headers*.x86_64.rpm libgomp*.x86_64.rpm
rpm -ivh compat-libstdc++-33* libaio-devel*.x86_64.rpm
rpm -ivh sysstat*I searched my Red Hat Disks before hand and ran the RPM commands as shown. Adjust as needed.
To verify that the required packages have been installed on your system, run the following command :
pm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" binutils \
compat-libstdc++-33 elfutils-libelf elfutils-libelf-devel gcc gcc-c++ glibc \
glibc-common glibc-devel-2.5 libaio libaio-devel libgcc libstdc++ libstdc++-devel \
make sysstatThis document is for Oracle 11, but the OS part should be the same.
http://www.visi.com/~mseberg/installing_oracle_11g_r2_64.html
Currently I have 3 servers running both Oracle 10 and 11 ( In different homes ) using this OS.
I have used Oracle 11 document with Oracle 10 also : ( Better once you are setup and a great standby recovery document )
http://www.visi.com/~mseberg/duprman2.html
Best Regards
mseberg

Downtime for logical or physical standby database

Hi ,
Are there any downtime required to refresh the data from the primary database to logical standby or physical standby database. What are the pros and cons of
using logical and physical standby database approach. which one is advisable to use in production environment.
Regards,
Richard

Hi Richard,
I'd suggest you read the documentation as a starting point, to answer your questions on here would be quite lengthy,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/toc.htm
In a nutshell you dont need downtime to maintain a standby, you can create them from a hot backup of your primary and get them recovering whilst it is open, in terms of which type of standby to use (physical or logical) that depends on your requirements for the use of the standby ... as I said read the doco (chapter 2 has a section on the benefits of each type).
HTH
Paul

Physical standby database fail-over

Hi,
I am working on Oracle 10.2.0.3 on Solaris SPARC 64-bit.
I have a Dataguard configuration with a single Physical standby database that uses real time application. We had a major application upgrade yesterday and before the start of upgrade, we cancelled the media recovery and disabled the log_archive_dest_n so that it doesn't ship the archive logs to standby site. We left the dataguard configuration in this mode incase of a rollback.
Primary:
alter system set log_archive_dest_state_2='DEFER';
alter system switch logfile;
Standby:
alter database recover managed standby database cancel;Due to application upgrade induced problems we had to failover to the physical standby, which was not in sync with primary from yesterday. I used the following method to fail-over since i do not want to apply any redo from yesterday.
Standby:
alter database activate physical standby database;
alter database open;
shutdown immediate;
startupSo, after this step, the database was a stand alone database, which doesn't have any standby databases yet (but it still has log_archive_config parameter set and log_archive_dest_n parameters set but i have 'DEFER' the log_archive_dest_n pointing to the old primary). I have even changed the "archive log deletion policy to NONE"
RMAN> configure archivelog deletion policy to none;After the fail-over was completed, the log sequence started from Sequence 1. We cleared the FRA to make space for the new archive logs and started off a FULL database backup (backup incremental level 0 database plus archivelog delete input). The backup succeded but we got these alerts in the backup log that RMAN cannot delete the archivelogs.
RMAN-08137: WARNING: archive log not deleted as it is still neededMy question here is
1) Even though i have disabled the log_archive_dest_n parameters, why is RMAN not able to delete the archivelogs after backup when there is no standby database for this failed-over database?
2) Are all the old backups marked unusable after a fail-over is performed?
FYI... flashback database was not used in this case as it did not server our purpose.
Any information or documentation links would be greatly appreciated.
Thanks,
Harris.

Thanks for the reply.
The FINISH FORCE works in some cases but if there is an archive gap (though it didn't report in our case), it might not work some times (DOCID: 846087.1). So, we followed the Switch-over & Fail-Over best practices where it mentioned about this "ACTIVE PHYSICAL STANDBY" for a fail-over if you intend not to apply any archivelogs. The process we followed is the Right one.
Anyhow, we got the issue resolved. Below is the resolution path.
1) Even though if you DEFER the LOG_ARCHIVE_DEST_STATE_N parameter's on the primary, there are some situations where the Primary database in a dataguard configuration where it will not delete the archive logs due to some SCN issues. This issue may or may not arise in all fail-over scenarios. If it does, then do the following checks
Follow DOCID: 803635.1, which talks about a PLSQL procedure to check for problematic SCN's in a dataguard configuration even though the physical standby databases are no available (i.e., if the dataguard parameters are set, log_archive_config, log_archive_dest_n='SERVICE=..." still set and even though corresponding LOG_ARCHIVE_DEST_STATE_N parameters are DEFERRED).
If this procedure returns any rows, then the primary database is not able to delete the archivelogs because it is still thinking there is a standby database and trying to save the archive logs because of the SCN conflict.
So, the best thing to do is, remove the DG related parameters from the spfile (log_archive_config, log_archive_dest_n parameters).
After i made these changes, i ran a test backup using "backup archivelog all delete input", the archive logs got deleted after backup without any issues.
Thanks,
Harris.
Edited by: user11971589 on Nov 18, 2010 2:55 PM

Upgrading with a physical standby database in place

Hi all
I am planning to upgrade my database which is 11.2.0.1 (Windows 32 platform) to 11.2.0.3. It has a primary standby database. I only have 1 server for testing the primary database, so I am looking for some help.
I was reading http://docs.oracle.com/cd/B28359_01/server.111/b28294/upgrades.htm#CHDBJAGG and I confuse about step 4 and 5
+4. Install the new release of the Oracle software into a new Oracle home on the physical standby database system, as described in the Oracle Database Upgrade Guide.+
+5. Mount the physical standby database.+
My question is in step 5, when I mount the physical standby database, does it mounted using new Oracle binary or still using the old version? From my understanding what is step 4 doing is to copying files to new home only. Changing the service to use the new oracle binary is done by dbua. I know this when I test upgrading the primary database.
Regards
Stanley.

Hello;
new Oracle binary or the new Oracle home if you will.
So you install the new software on the standby only, all the upgrade SQL gets done on the Primary and then you ENABLE and startup mount on the new oracle home and the standby gets upgraded from the Primary redo.
Its pretty simple ( My exact plan )
1. Disable log shipping from the Primary
2. Shutdown Standby
3. Install 11.2.0.3 on Standby - Just the software
4. Startup Standby in recovery mode - do NOT run r any SQL at the standby
5. Shutdown Primary
6. Install 11.2.0.3 on Primary
7. Run Upgrade SQL or DBUA at Primary
8. Re-enable log shipping
9. Monitor the redo apply from Primary to Standby - this will also upgrade the Standby data dictionary
Make sure your tnsnames and listener files move to the new Oracle home and edit as needed.
Another oracle note is 278641.1
Best Regards
mseberg
Edited by: mseberg on Jan 29, 2013 8:21 PM

Failover To Physical Standby Database

We have 3 node RAC 11.2.0.3 Primary database data guarded to a 3 node RAC 11.2.0.3 Standby database. There is an activity scheduled to perform some of order extracts in the database which is going to result in a lot of changes. Currently the discussion is on whether what should be the quickest way to go back to a point in time before the extract process starts in case of any issues. The options that we are looking at are:
1) Create a guaranteed restore point on both the Primary and Standby and use this to flashback the database (Quick but we have had issues where in the guaranteed restore point still does not guarantee the availability of the flashback logs) - Tested
2) Use RMAN backup from a day before to restore and recover to point in time before the extract process began (Time consuming) - Tested
3) Use export backup to perform a redirected restore i.e import the data from before the extract process (Time consuming) - Tested
4) Create a guaranteed restore point on both Primary and Standby, stop the Redo Apply/Ship at the time we create the guaranteed restore point and at a point we face some issue and need to go back, simply failover to the physical standby database and then reinstate the new standby database - This has not been tested yet but seems a viable option
With regard to the point 4, note that we are not concerned about data loss as the whole point of stopping the redo apply is to prevent the standby to be caught up with Primary during the run of the extract process. The question is whether the dataguard broker will allow failover of the primary to standby, in a situation described in bullet point 4). Please advice.

HI,
Please check this link:
Physical Standby Database SWITCHOVER &amp; FAILOVER Operations | Talip Hakan Ozturk&#039;s ORACLE BLOG
Thank you

OEM for physical standby database

Hello All,
I am using Oracle 11.2.0.3. My enterprise manager is db console 11.2
I have Oracle Enterprise manager dbcnsole for my RAC primary database and I have created through sqlplus command line a physical standby database.
My questions
Can I use the RAC primary dbconsole to monitor my physical standby database? if yes what the steps?
Is it mandatory to use grid control in that case? if yes, what steps are needed to implement grid control ?
Regards,

Hi,
It is not possible to monitor/administer a Logical or Physical Standby database, i.e Data Guard, using Enterprise Manager Database Control. This is primarily due to the fact that Database Control is designed to monitor 1 database and a Data Guard environment, by definition, includes more than 1 database.
If you attempt to run emca against a standby Database, you will get an error like (i.e. ORA-01219: database not open).
Database Control, can, of course, be used to monitor the current Primary database (with no ability to administer or monitor Data Guard related functionality). In such a case, when failover occurs Database Control must be reconfigured to run on the new Primary database using the commands detailed in Note 278100.1 How To Drop, Create And Recreate DB Control In A 10g Database, section C. Recreate/ReConfig DB Control, Option 2. Recreate the DB Control Configuration Files and Repository.
Enterprise Manager Grid Control or Cloud Control provides the functionality for viewing, monitoring, and administering primary and standby databases in a Data Guard configuration.
Reference: Is it Possible to Configure Database Control for a Logical or Physical Standby Database? (Doc ID 315116.1)
Using EM cloud control 12c is best available option to monitor your standby databases
For install docs refer to
http://docs.oracle.com/cd/E24628_01/install.121/e22624/toc.htm
For Software download link
http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html
Regards,
Rahul

Export on physical standby database ?

Can we take export at physical standby database ?
Its oracle 10.2.0.1.0

GokhanAtil wrote:
oracleRaj wrote:
Renjith Madhavan wrote:
It depends on what mode your standby database is in . If you are in managed recovery mode ... then you cannot take export backup . You will have to be in read only mode so that you can take export backup . But production and standby will not be in sync in that time . You will have to apply the redologs after you are done with the exports in manged recovery mode .
Regards
Renjith MadhavanOkay it means database is in read only mode then we can take export of schema or full database backup ?You need to use "Network export". Data Pump Export cannot run locally on a read-only instance because the job requires write operations on the instance. Please read:
http://www.oracle.com/technetwork/issue-archive/2009/09-jul/datapump11g2009-quickstart-128718.pdf
Best Regards,
Gokhan
If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. ThanksOKay, but traditional export utility will work on standby database ?
Regards,

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

Create ONLINE logfile in physical standby database

We have created a physical standby database with rman duplicate command on a remote server
"duplicate target database for standby dorecover nofilenamecheck"
When I see the standby server...Online logfiles are not created however its relevant entries are there in V$LOG and V$LOGFILE views.
I guess it is the default behaviour of duplicate command in RMAN and we can not specify LOGFILE clause when we create standby database.
Now the problem is we could not drop the online logfile on standby database since it's status is "CURRENT", "ACTIVE".
Since the ONLINE LOGFILE are not actually created , "ALTER DATABASE CLEAR LOGFILE GROUP " command returns with error as it could not find the file in the server.
So How we can drop the current/active online logfile and add new ones in standby db?

I'm assuming you have physical standby. Here are step I did in the past.
1) create a backup control file
2) bring the database back using the "recreate control file" it the trace file BUT you need to remove or comment out the line that has the corrupt or missing redo log file. And don't forget to add the tempfile after you recreate the controlfile
example:
alter database backup controlfile to trace;
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS FORCE LOGGING ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/oracledata/orcl/redo01.log' SIZE 200M,
GROUP 2 '/oracledata/orcl/redo02.log' SIZE 200M,
GROUP 3 '/oracledata/orcl/redo03.log' SIZE 200M,
# GROUP 3 '/oracledata/orcl/redo03.log' SIZE 200M
-- STANDBY LOGFILE
-- GROUP 10 '/oracledata/orcl/redostdby04.log' SIZE 200M,
-- GROUP 11 '/oracledata/orcl/redostdby05.log' SIZE 200M
DATAFILE
'/oracledata/orcl/system01.dbf',
'/oracledata/orcl/undotbs01.dbf',
'/oracledata/orcl/sysaux01.dbf',
'/oracledata/orcl/users01.dbf'
CHARACTER SET WE8ISO8859P1
If you just want to add the standby redo log then using this command.
alter database add standby logfile
'/<your_path>/redostdby01.log' size 200M reuse,

Question regarding removal of physical standby database?

Similar Messages

Maybe you are looking for