Standby Redolog Creation for Physical standby

I want to migrate my primary database from one server X to standby database which i want to create on other server Y. once Primary and standby will get SYNC , i will do Fail over to make standby as primary and divert current application on standby considering as full functional Primary.
Is it mandatory to create SRL ( Standby redo log)? or I can create physical standby without SRL? If Yes, on which side (primary or standby) i need to create SRL?
Appreciate your help..

Hello,
Now, My standby database has configured. Since i had restore and recover standby database from standby controlfile instead of RMAN Duplicate. I had done following step:
ON standby side:
$rman target /
RMAN> restore standby controlfile from '/app/oracle/standbyctl.ctl'
RMAN> sql 'alter database mount standby database';
RMAN> restore database;
RMAN> list backup of archive log all;
RMAN> RMAN> recover database until sequence 1670;
SQL> alter database recover managed standby database disconnect from session;
• On Primary:
SQL> alter system set log_archive_dest_state_2=ENABLE;
• On Standby:
SQL> select sequence#,applied from v$archived_log order by sequence#;
I am at this stage now. My primary and standby database in synchronization. As per my first thread above, we will have planned outage to move application to standby database and make it full functional primary database. once application will move on new server( standby database). we will not use current primary database anymore.
what are the procedure i need to do on primary side and standby side when migrate application on new server.? rightnow my standby database in MOUNT mode and archive log is shipping from primary to standby. we have no dataguard broker configuration. i need to do it manually using SQL command.

Similar Messages

Test scenario for Physical Standby

Dear Team,
Could you please share the Test scenario for Physical Standby.
1. Read only.
2. Switch Over
3. Fail Over.
Many Thanks in Advance
Arjun.

You didnt mention the version.
Oracle10g Release 2, Data Guard Switchover and Failover best practices
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_SwitchoverFailoverBestPractices.pdfOracle9i, Data Guard Switchover & Failover best practices
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_9iSwitchoveFailoverBestPractices.pdfKhurram

Standby redolog creation

Hi,
At the time of physical standby DB creation Oracle doc says that...
3.1.3 Configure a Standby Redo Log
Example 3-1 Adding a Standby Redo Log File Group to a Specific Thread
The following statement adds a new standby redo log file group to a standby database and assigns it to THREAD 5:
SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 5
2> ('/oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500M;
Is this logfiles created in the primary DB and the directory structure is in primary DB?
If yes then, how under section 5.1 Introduction to Redo Transport Services figure 5-1shows standby redolog files are showing in standby DB?
So shall I create standby redolog in both DBs? or only in primary DB?
I need your input to clear this confusion please.
regards

Hello,
You SHOULD create your standby redo log files on both your current primary AND your current standby.
You never know, one day the current primary might be the current standby and the current standby your now current primary!
jason
http://jarneil.wordpress.com/2007/11/18/standby-redo-logs/

Creation of logical standby in 9i from physical standby

Hi all,
I want to create logical standby from physical standby in 9i. can anyone send a doc for this

As per the Oracle documents "You create a logical standby database by first creating a physical standby database and then transitioning it to a logical standby database"
Please take a look at the below URL.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm
Regards,
Sabdar Syed.

Cannot Clear Critical Alert for Physical Standby Databases

10.2.0.4.0 Grid Control monitoring 10.2.0.4.0 databases and standby databases with 10.2.0.4.0 agents.
The standby databases are running on Xen guests. The O/S is Red Hat 4 Advanced Server.
I had a failure of Xen guest on Saturday that caused me to have to rebuild the standby servers. EM Grid Control successfully verifies the configurations and the status is normal for both physical standby databases. (A rebuilt logical standby database shows no alerts.)
Grid Control database targets page shows a single critical alert for each physical standby database. The alert is for "number of missing media files is 4". The metric graph shows the count as 0 since before the rebuilds. I cannot clear the alerts from the Critical Alerts page. Grid Control reports "The selected alert(s) cannot be manually cleared. They will clear automatically once the metric is no longer in a critical or warning state.".
Any suggestions?
Thanks,
Ray Westphal

Thanks for the reply Anthony.
The result of the query on both standby databases is '0'. The metric graph also shows the value at '0' since before rebuilds.
And the OMS db and agents have been reset several times since I posted this.
Ray Westphal.

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

Compressing redo data for Physical Standby

Hi All,
I have been checking option of compressing redo data for a Physical Standby database. I did not find many details in the docs. Any one has implemented this kind of compression.
Cheers/Aditya

per Oracle support, redo compression in DG makes sense only if the bandwidth between the primary & standby server is less than 100mbps and is expected to be heavily taxing on CPU.
you may check metalink article ID: 729551.1 where they have given some test stats. Not a whole lot of data, but it might help you make a good judgement.
Cheers.

DB link for physical standby database

Hi All ,
I'm facing the below error on primary while trying to create a db link pointing to the 10g standby database which is in mount stage.
SQL> create database link synct connect to system identified by 123 using 'stdby';
Database link created.
SQL> select max(sequence#) from v$archived_log@synct where applied='YES';
select max(sequence#) from v$archived_log@synct where applied='YES'
ERROR at line 1:
ORA-02068: following severe error from SYNCT
ORA-01033: ORACLE initialization or shutdown in progress
Database version is 10.2 standard edition
My requirement is i need to get max(sequence#) of standby database from primary database using db link.
what i was trying to do is
on primary get max(sequence#) & get max(sequence#) of standby using db link and compare both if the gap differene is more than 10 send a mail.
Any suggestions will be really helpful

976422 wrote:
Hi All ,
I'm facing the below error on primary while trying to create a db link pointing to the 10g standby database which is in mount stage.
SQL> create database link synct connect to system identified by 123 using 'stdby';
Database link created.
SQL> select max(sequence#) from v$archived_log@synct where applied='YES';
select max(sequence#) from v$archived_log@synct where applied='YES'
ERROR at line 1:
ORA-02068: following severe error from SYNCT
ORA-01033: ORACLE initialization or shutdown in progress
Post Standby/DataGuard/ADG all questions further in Oracle Discussion Forums » High Availability » Data Guard
If you try to connect any users other than SYS in standby the error is very much expected. Of course you can connect with other users if you open database in OPEN READ ONLY mode, from 11gRx you can connect with other users even MRP is running if you are using ADG(active Data Guard licensed) .
I like to know, what you want to achieve by creating DB Link on physical standby database? Which is not allowed.
Database version is 10.2 standard edition
My requirement is i need to get max(sequence#) of standby database from primary database using db link.
what i was trying to do is
on primary get max(sequence#) & get max(sequence#) of standby using db link and compare both if the gap differene is more than 10 send a mail.
Any suggestions will be really helpfulNote:- Standard edition, Data Guard not enabled.
To use this you should use Oracle Net Service, you no need of DB Links.
Ex:- sqlplus sys/****@standby as sysdba
Here standby refers to Oracle net service, Where you will have entries in $ORACLE_HOME/network/admin/tnsnames.ora file.
Edited by: CKPT on Dec 12, 2012 2:01 PM

Creating physical standby database from another physical standby database

hi,
We have one production database and one physical standby of the production. Now we have situation where we need to create one database from either production or from standby. As production is loaded we can not do it using active database option. Now we have the only option to copy the database from standby.
As of now we open the standby and copy it using rman duplicate database and again we put it back to standby mode.
Is it possible to create standby database from standby database only?
Oracle version : 11.1.0.7.0
I have seen procedure allowing to do the same in version 11.2.0.3. I have tried searching for the difference but didn't find when this feature was introduced.
Thanks,
Ketul Patel

Hello;
Active duplicate should work when connected to Standby as source Database. However there's a bug 11715084 which is not fixed until version 11.2.0.4.
If patch 11715084 is available for your version it may work, but all the 11.1.0 are gone so I have no way to test.
RMAN ACTIVE DUPLICATE WHEN CONNECTED TO STANDBY AS TARGET [ID 1343515.1]
Understanding ORA-01671 error during controlfile creation / backup [ID 461121.1]
Best Regards
mseberg
Edited by: mseberg on Feb 13, 2013 8:59 AM

Logical file creation for physical inventory

Hi,
How to use MI31/MI34/MI37 t.codes for Physical inventory.
What is mean by logical file.
Regards,
Prabu

Hi
I didnt work on MI34. But SAP help gives below reference: Check with an ABAPer
Short text
Batch input: Enter count with reference to document
Description
This report generates a batch input session (BI session) which, when processed, enters the inventory count results with reference to a physical inventory document.
Before you start the report, make sure that the file entered on the selection screen is stored in the specified directory at operating system level.
The data for the batch input session is imported from an external dataset as a sequential file. The structure of the sequential file is preallocted by the table BISEG. You can display and print this structure via the information system in the data dictionary. Note that the object class Fields is chosen on the request screen of the information system.
Requirements
Entering counting results via a batch input session requires that the corresponding physical inventory document has been created in the system. If you try to enter a counting result for which no physical inventory document exists, an error will occur during the BI session, which will interrupt processing.
Any errors are recorded in the log file for the corresponding BI session.
Before the sequential file is read, you should perform a test run. For this purpose, you have to maintain the corresponding test data in table T159I. For the sequential file data to be read and and for test data in table T159I, please note the following:
The name of the report has to be specified only in table T159I. The name to be specified is RM07II34.
The name of the BI session is optional.
The name of the transaction Enter inventory count to be specified is MI04.
The following data must be entered into the system:
Count date
Fiscal year
Number of physical inventory document
Item in physical inventory document
Quantity of stock counted
Output
The system generates a batch input session which you can process via options System -> Services -> Batch input -> Sessions.
When processing the batch input session for testing purposes, you should set the Display errors only indicator.
When importing the actual productive data, you should always use the Background indicator.
If data expected by the system (required-entry fields) does not exist, an error will occur during the batch input session which will interrupt processing.
An error will also occur during the batch input session if you try to maintain data not expected by the system (fields not ready for input). However, processing will not be interrupted. The system writes a comment in the session log.
Thanks

Cascading physical standby from another physical standby for primary rac

my supplier told me that is possible mount a cascade physical standby from a physical standby for my rac installation.
but according the note "409013.1" seems not:
"Cascading a logical or physical standby database from a physical standby database is supported as long as the primary database is not a RAC database and is not part of a Data Guard Broker configuration - the support status of this configuration is unchanged from previous documentation."
before was possible? do you know why not now?
has anyone mounted? can I allow my provider to mount?
oracle version: 10.2.0.2.0

Is it possible this scenario?YES

Creation of Logical Standby Database Using RMAN ACTIVE DATABASE COMMAND

Hi All,
I am in confusion how to create logical standby database from primary database using rman active database command.
What i did:-
Create primary database on machine 1 on RHEL 5 with Oracle 11gR2
Create standby database on machine 2 on RHEL 5 With Oracle 11gR2 from primary using RMAN active database command
Trying to create logical standby database on machine 3 on RHEL 5 with Oracle 11gR2 using RMAN active database command from primary.
The point which confuse me is to start the logical standby in nomount mode on machine 3 with which pfile like i create the pfile for standby database do i need to create the pfile for logical standby db.
I done the creation of logical standby database by converting physical standby to logical standby database
I am following the below mentioned doc for the same:
Creating a physical and a logical standby database in a DR environment | Chen Guang&#039;s Blog
Kindly guide me how to work over the same or please provide me the steps of the same.
Thanks in advance.

Thanks for your reply
I already started the logical standby database with pfile in nomount mode. And successfully completed the duplication of database. by mentioning the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter.
But i am not able to receive the logs on the above mentioned blog i run the sql command to check the logs but getting "no rows selected"
My primary database pfile is:
pc01prmy.__db_cache_size=83886080
pc01prmy.__java_pool_size=12582912
pc01prmy.__large_pool_size=4194304
pc01prmy.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01prmy.__pga_aggregate_target=79691776
pc01prmy.__sga_target=239075328
pc01prmy.__shared_io_pool_size=0
pc01prmy.__shared_pool_size=134217728
pc01prmy.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01prmy/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01PRMY/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01PRMY/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.fal_client='PC01PRMY'
*.fal_server='PC01SBY'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='SERVICE=pc01sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pc01sby'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='DEFER'
*.log_archive_dest_state_3='DEFER'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
My logical standby pfile is:-
pc01ls.__db_cache_size=92274688
pc01ls.__java_pool_size=12582912
pc01ls.__large_pool_size=4194304
pc01ls.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01ls.__pga_aggregate_target=79691776
pc01ls.__sga_target=239075328
pc01ls.__shared_io_pool_size=0
pc01ls.__shared_pool_size=125829120
pc01ls.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01ls/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01LS/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01LS/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_unique_name='pc01ls'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='LOCATION=/u01/app/oracle/flash_recovery_area/PC01LS/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
Kindly advice over the same

Standby redolog files

Hi
I think standby redolog files are not required if I open the physical standby database in read/write mode by using flashback database techonology. Kindly let me know if I am wrong.

sat1980 wrote:
Hi,
Thanks for coming back on this, sorry for confusing with my question, I will re-frame my question as
"I think standby redolog files are not required on PRODUCTION, if I open the physical standby database in read/write mode by using flashback database techonology", basically I wanted to know that standby redologs on production and standby are required only when switch over are switch back are done.If you would open(using any technology wether flashback or without it) your physical standby database (keeping production also in open mode) that means both these database are now independent and redo logs(archive logs) of any of the database cannot be applied to each other. Hence there would not be any use of standby redo log files.
Standby redo logs are used to get the redo files(data) on the standby database from the primary even if the redo log is not archived on primary. Hence if you want that feature in your standby database it is necessary to have standby redo log files.
Yes standby redo log files are not required for production but oracle recommends it to make smooth switch over.
Regards
Anurag

Issue on physical standby database

Hi
I've a problem on standby database.
I recently added a datafile on primary database, then I scp'ed the data file to physical standby database.On physical standby database I tried performing recovery.
I get following message in my alert log
WARNING! Recovering data file 88 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
how can I fix this now.
We keep physical standby database 2 day behind, and apply logs manually.
Physical standby database is maintained manually.
Could someone help me in getting out of this problem.
Oracle 9.2.0.7
solaris

Versus keeping it in manual mode, you can specify a time "delay" for the application of the logs:
From http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1022811
6.2.2 Specifying a Time Delay for the Application of Archived Redo Log Files
In some cases, you may want to create a time lag between the time when redo data is received from the primary site and when it is applied to the standby database. You can specify a time interval (in minutes) to protect against the application of corrupted or erroneous data to the standby database. When you set a DELAY interval, it does not delay the transport of the redo data to the standby database. Instead, the time lag you specify begins when the redo data is completely archived at the standby destination.
Note:
If you define a delay for a destination that has real-time apply enabled, the delay is ignored.
Specifying a Time Delay
You can set a time delay on primary and standby databases using the DELAY=minutes attribute of the LOG_ARCHIVE_DEST_n initialization parameter to delay applying archived redo log files to the standby database. By default, there is no time delay. If you specify the DELAY attribute without specifying a value, then the default delay interval is 30 minutes.
Canceling a Time Delay
You can cancel a specified delay interval as follows:
For physical standby databases, use the NODELAY keyword of the RECOVER MANAGED STANDBY DATABASE clause:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
For logical standby databases, specify the following SQL statement:
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY;
These commands result in log apply services immediately beginning to apply archived redo log files to the standby database, before the time interval expires. Also, see:
Section 12.8, "Using a Physical Standby Database with a Time Lag"
Oracle Database SQL Reference for the DELAY attribute of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement

How to open a "manual" Physical standby database in read/write mode

Hi,
I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
The standby database is started this way :
startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
alter database mount standby database;
Everything runs perfectly fine, I can do "alter database open read only" and then I can do selects into tables to confirm that everything is up to date.
The thing is, if I shutdown immediate the database, then do just startup :
shutdown immediate;
startup;
The database opens with no error messages, but is still in read-only mode...
I read that the default behavior for a standby database is to open read-only, like I am experiencing, but I would like to know what is the right way to open it correctly in read-write mode (I understand that after that, my standby will not be standby anymore and that I will have to recreate my standby database).
Thanks,
Mat

Hello,
There're features which allows you to open a Standby database in Read/Write mode but for all I know
it needs Entreprise Edition.
In Enterprise Edition you can use Logical Standby database. More over, for Physical standby there's
a way by using flashback database so as to rolling backward the database and avoiding to recreate
the Standby.
In Standard Edition I'm afraid that you'll have to recreate your Standby database.
Best regards,
Jean-Valentin

Standby Redolog Creation for Physical standby

Similar Messages

Maybe you are looking for