Primary/standby question

All,
I've got a primary and standby 10g (10.2.0.4) on Windows 2003. I think/thought things were fine because when I execute
SELECT SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS WHERE DEST_ID=2 ;
I see the logs have been moved over and applied and I see the recovery mode as 'MANAGED REAL TIME APPLY'
However, looking at the modified date on my DBF files they haven't changed, at least the date. Am I missing something?
Thanks,
Tony

Am I missing something?No, such behaviour is normal on the Windows platform, not only in standby environments, seems to be an internal communication problem between Oracle and Windows. I didn't yet find a published explanation for this,I only can see it.
Werner

Similar Messages

Primary & standby db on same OS plaform but having different OS version

Hi,
I have primary & standby database 10.2.0.4 on AIX 5.3 Operating System platform .
I would like to Upgrade my Operating System(AIX) of standby databse server from 5.3 to 6.0.
Will diffenet Operating System version for primary & standby databases support ?
Thnaks.

so, if my primary db on aix 5.3 & standby db on aix 6.1 plaform, then it will not work
or oracle db will not support for this differnent os versions.
is it right?Yes, along with that I'm asking why you want to choose different versions/releases of OS?
I seen there some issues even if some RPM's are missing. So if the complete version changes then think of it.
Moreover check the certification in support.oracle.com
Recently i checked for Linux 6, it's not yet certified. I'm not sure of unix here. So please do refer http://support.oracle.com
Thanks.

Physical stndby doesn'1 apply redo or primary standby didn't transport redo

I setup physical standby (OEL5.0, DB 11.2), every things seem right. But when i create table on primary DB, it does not appear on standby database. The Physical standby doesn'1 apply redo or primary standby didn't transport redo to standby Datadase
Please consider mine configuration
----Standby :
SQL> select database_role, protection_mode, log_mode from v$database;
DATABASE_ROLE PROTECTION_MODE LOG_MODE
PHYSICAL STANDBY MAXIMUM PERFORMANCE ARCHIVELOG
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
Next log sequence to archive 40
Current log sequence 40
------Primary :
SQL> select database_role, protection_mode, open_mode from v$database;
DATABASE_ROLE PROTECTION_MODE OPEN_MODE
PRIMARY MAXIMUM PERFORMANCE READ WRITE
SQL> create table test_stby (
2 cot_1 number,
3 cot_2 number);
Table created.
SQL> insert into test_stby values (10,11);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
---- Standby :
SQL> SELECT MAX(SEQUENCE#), THREAD# FROM V$ARCHIVED_LOG GROUP BY THREAD#;
no rows selected
SQL> SELECT PROCESS, STATUS,SEQUENCE#,BLOCK#,BLOCKS,DELAY_MINS FROM V$MANAGED_STANDBY;
PROCESS STATUS SEQUENCE# BLOCK# BLOCKS DELAY_MINS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
MRP0 WAIT_FOR_LOG 40 0 0 0
- Standby cancel redo apply, open read only and query for table test_stby, it does not have this table
Please help
Ch

I did solved this problem :)

Dataguard the achivelog not transfort between primary & standby db

Dear all Dataguard gurus
i tried to install oracle 10g dataguard on 2 machines with Centos 4.6 for development
after finish the installation, i 've got some "STRANGE" ..when i do a query at dataguard1
dataguard1 is primary database
dataguard2 is standby database
sys@dataguard1> select sequence#, first_time, next_time from v$archived_log;
SEQUENCE# FIRST_TIM NEXT_TIME
16 24-JUL-09 24-JUL-09
17 24-JUL-09 24-JUL-09
18 24-JUL-09 24-JUL-09
19 24-JUL-09 24-JUL-09
20 24-JUL-09 24-JUL-09
21 24-JUL-09 24-JUL-09
22 24-JUL-09 11-AUG-09
23 11-AUG-09 12-AUG-09
24 12-AUG-09 12-AUG-09
25 12-AUG-09 12-AUG-09
26 12-AUG-09 12-AUG-09
sys@dataguard1>select sequence#,applied
2 from v$archived_log
3 order by sequence#;
SEQUENCE# APP
16 NO
17 NO
18 NO
19 NO
20 NO
21 NO
22 NO
23 NO
24 NO
but if i do the same quey on standby database
sys@dataguard2> select sequence#, first_time, next_time from v$archived_log;
nothing archive...and not applied
what could be the problem????
thanks for u'r attention & help
Edited by: kang dadang on Aug 12, 2009 7:22 PM

thanks for response jerald
everything is same, all pass for sys on primary & standby are the same, password file on both machine are same
here my parameter file[not all parameter included]
[primary db]..on dataguard1 machines [dbname : dgtest]
*.db_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest'
*.db_name='dgtest'
*.DB_UNIQUE_NAME='dgtest'
*.fal_client='dgtest2'
*.fal_server='dgtest'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(dgtest,dgtest2)'
*.log_archive_dest_1='LOCATION=/u02/oradata/archive/dgtest/
valid_for=(all_logfiles,all_roles)
db_unique_name=dgtest'
*.log_archive_dest_2='service=dgtest2 lgwr async
valid_for=(online_logfiles,primary_roles)
db_unique_name=dgtest2'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.log_archive_format='%s_%t_%r.arc'
*.log_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest',
'/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/','/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/'
*.service_names='dgtest'
*.standby_file_management='auto'
[standby] on dataguard1 machines..[dbname : dgtest2]
*.db_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest'
*.db_name='dgtest'
*.DB_UNIQUE_NAME='dgtest2'
*.fal_client='dgtest2'
*.fal_server='dgtest'
*.log_archive_config='DG_CONFIG=(dgtest,dgtest2)'
*.log_archive_dest_1='LOCATION=/u02/oradata/archive/dgtest/
valid_for=(all_logfiles,all_roles)
db_unique_name=dgtest2'
*.log_archive_dest_2='service=dgtest lgwr async
valid_for=(online_logfiles,primary_roles)
db_unique_name=dgtest'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.log_archive_format='%s_%t_%r.arc'
*.log_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest',
'/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/','/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/'
*.remote_login_passwordfile='EXCLUSIVE'
*.service_names='dgtest'
*.standby_file_management='auto'
thanks for all...jerald
Edited by: kang dadang on Aug 12, 2009 11:52 PM

How to Refresh UAT Primary/standby from Production primary/standby

Hi ,
We have the following setup :
Primary/standby - Production
Primary/Standby - UAT
I need to know the process on how to refresh the UAT primary/standby .
I'm thinking on the following lines :
1] If we have the export dump of production , can we go ahead and drop the schemas to be refreshed on both UAT Primary and UAT Standby UAT then perform the schema import on Primary UAT .
2] In case if I have to do a full refresh of UAT , do I need to rebuild the UAT environment from the proudction backups Ie,
(i) Drop both the UAT primary and UAT standby database .
(ii) using the produciton backup built the UAT Primary . Take the UAT primary backup and build the UAT standby .
Appricaite if any one can provide some best practices to refresh UAT from Production.

That setup seems to be rare. We assume that the Standby Database is used for testing and have a feature for that called Snapshot Standby.
But in your scenario, you need to develop your own techniques for "refreshment of the UAT Primary".
An easy way (if your Primary is not too large): Throw away your UAT env each time the "Production Primary" changes and RMAN clone it to "UAT Primary" then.
Then RMAN duplicate "UAT Standby" again. Could be relatively easily scripted.
But again: Why not just create an ordinary Standby on your UAT hardware and use it for testing with Snapshot Standby feature? Much easier to maintain.
Kind regards
Uwe Hesse
http://uhesse.wordpress.com

Switchover_status "FAILED DESTINATION" on both primary-standby databases

Hi,
I setup primary-standby databases and try to test the switchover functionality between them using the following commands:
alter database commit to switchover to primary with session shutdown;
alter database commit to switchover to physical standby with session shutdown;
Currently, both DBs are showing
open_mode= READ WRITE for "select open_mode_from v$database;" and
switchover_status = FAILED DESTINATION for "select switchover_status from v$database"
When both databases get into these states, how can I return them back to primary and standby roles? Could you please provide me a sequence of steps that I can execute to return them back to normal primary-standby states?
Thanks in advance for your suggestion.

The OS is Red hat 4.1.2-500.
Oracle version is 11g.
Here is the sequence of steps that lead to this issue:
1. switchover_status on primary = to standby, switchover_status on secondary = not allowed
So on primary, I execute
alter database commit to switchover to physical standby with session shutdown;
and could be shutdown/startup mount ( I don't remember exactly)
2. switchover_status on secondary = to primary
So on secondary, I execute
alter database commit to switchover to primary with session shutdown;
alter database open;
3. Now on secondary, the switchover_status = FAILED DESTINATION
On primary, I execute
alter database commit to switchover to primary with session shutdown;
and could be "alter database open" ( I don't remember exactly)
The switchover_status in step 1) and 2) above should indicates that the data guard is working. At the end of the above steps, I cause both databases to get into switchover_status = "FAILED DESTINATION".
I hope to get one of the DBs back into standby role.
If I execute "alter database commit to switchover to physical standby with session shutdown", I will get
"ORA-16416: No viable Physical Standby switchover targets available"
In this situation, is there any recommendation for rescue?

How tyo know that primary & standby are syncronyzed(SCN)

Dears,,
If i have data guard solution (Primary and physical standby) databases
How to make sure that both primary & standby are syncronyzed(SCN)
Please,help,,

Hi,
Compared across the sequences applied on standby with primary archive logs generation generation
select max(sequence#) from v$archived_log where applied='YES';
- Pavan Kumar N

Yet another standby question...

Hi gurus,
Please help to resolve the quiz. I have completed manual physical standby installation. It is up and running. I then decided to install Grid Control and to use Data Guard for the standby creation. I've successfully installed GC, deployed all agents, I can see my previous standbys, life is good in short. Now, when I am trying to create the second standby for my production database using the Data Guard I stuck on a logical question:
On the step 3 of Data Guard standby creation, there is a note, saying:
The instance name (also referred to as the SID) must be unique on the standby host.
Yeah, fair enough. But i can't understand what should I do next? I have:
db_name YELLOW - primary prod
db_name YELLOW - standby prod 1st
and i need db_name YELLOW - standby 2nd
But I can't create it on the same server where the first standby resides.. What options do I have? Do I need to create the second standby on another server? Do I need to kill 1st standby? Is there any way to avoid this conflict? I am confused. I have no equipment for TWO standby servers... I thought I can install there up to 9 standbys.. But it seems to be a problem.. And definitely, I cannot give my second standby other name than YELLOW as all my applications are strongly tied on db_name...
Friends, please clarify this if you can. I am kinda lost in here..
Thanks as usual,
Maria

well, that's a good question! :)
because I don't have spare server for the standby. the question is not about: 'should I or should not put more than one standbys in one server' , but more about: 'is there any way to put two standbys with the identical db_names in one server'. I know that I probably sound unprofessional, but I just wanna know.. If the answer is 'no way', I will kill the first standby then and recreate the second one using DG with the correct name.
Thanks for writing to me,
M.

Standby question

Hi experts , i have a simple question ..Can we convert a logical standby to physical standby ? Yes or No, if yes how .. if no please let me.. please help

842638 wrote:
Hi experts , i have a simple question ..Can we convert a logical standby to physical standby ? Yes or No, if yes how .. if no please let me.. please helpNo, that is logically impossible: a physical standby is byte-for-byte identical to the primary, but a logical standby may be very different. Even though it will have been instantiated from a physical standby, it will have diverged: different dbname and dbid, the physical and logical structures will have changed, it may have additional objects, it may have objects that are not maintained.

Patch applied primary/standby - when to upgrade standby

I am following metalink document *278641.1*
STEP-6: I have applied patch on both databases.
STEP-7: Started OracleSercivce, Listener.. on standby database.
I have confusion in step 8,9 and 10.. the confusion is when should I upgrade the databases? and which datatabse should be upgraded first? I want to upgrade using DATABASE UPGRADE ASSSISTANT (DBUA).... please help
OPTION-1 should I follow below steps...
STEP-8: startup nomount.
STEP-9: recover managed standby database nodealy disconnect.
and then I upgrade the standby database using DBUA
STEP.10 start primary lisnter, primary instance.
and then I upgrade the primary database using DBUA
OPTION-2 OR should I follow below steps...
STEP-8: startup nomount.
STEP-9: recover managed standby database nodealy disconnect.
STEP.10 start primary lisnter, primary instance.
and then I upgrade both Primary and Standby using DBUA
which one should be upgraded first.?
Can any body explain me... what steps I should follow, and when should I upgrade the database using database upgrade assistant.....its not mentioned clearly in the document... I am stuck in...
waiting for your replies...

it doesn't.... again, my question is same... when should I upgrade the database using DBUA... and which database should be upgraded first?
you want to say... I should follow steps as below..
8. (standby database) startup nomount
9. (standby database) recover managed standby database nodelay disconnect;
10. (primary database) start primary listner, oracle instance
10.1 (primary database) start oracle instance startup command at primary database...right?
10.2 (primary database) upgade using DBUA
10.3 (standby database) upgrade using DBUA
I didnt understand with startup upgrade command.... should I use DBAU to upgrade the database instead ? again my question is which database should be upgraded first with DBAU.

Configure primary & standby with OMS IN dataguard

most respectable viewers,
i have a production database "A"
and a standby database "B" (both of these databases are 9i release2 on server 2003)
Now archives are shipped from primary to standby and after that i manualy recover archives on standby database with "RECOVER STANDBY DATABASE" command.
but i want that the archives which are transferred to standby database recover automatically .
How i can achieve this..............? either running this command on standby database "RECOVER STANDBY DATABASE DISCONNECT FROM SESSION" or anyother way?
i want to watch the performance of both of these database through "ORACLE MANAGEMENT SERVER" graphically. How i can move both of my databases to oracle management server
i think my question is clear. plz reply
REHAN

user10204771 wrote:
i want to watch the performance of both of these database through "ORACLE MANAGEMENT SERVER" graphically. How i can move both of my databases to oracle management server
Data Guard Broker is the solution to manage dataguard graphically;
Check link;
http://www.scribd.com/doc/7479230/oracle-9i-data-guard-broker
Edited by: emre baransel on Mar 30, 2009 4:36 PM

10gr2 standard edition standby question - archive log shipping

Hello,
I have 2 servers with 10gr2 standard edition, one is production(primary) and secondary is standby on windows platform. To keep standby synchronized i use a script to copy archived logs from primary to standby and applying manually (with scripts).
My question is: can i use redo transport service in order to copy archivelogs from primary to standby ?
Thank you in advance.

Hi,
It is a bit of topic.
According to the Licensing Document page 10 DataGuard is not supported for standard edition.
http://download.oracle.com/docs/cd/B28359_01/license.111/b28287.pdfRegards,
Tycho

Oracle 10 upgrade - Primary & standby database

Hi Expert,
I need some information on your project experience. We're currently planning a oracle 10 upgrade. Have a few question:
1. We're planning to upgrade the primary database first and a week later the standby database. Will the archive log which is sent from primary to standby database will still work? Will the recovery still work?
2. Is this the right patch to go 10.2.0.4? I'm currently on 4.7 ext 2
3. Will there be a performance issue known of oracle 10 running on 32-bit machine, since it has the limitation of the memory (3G). Do I need to set AWE option on windows?
Thanks in advance.

Hello Sean,
please let me go more in detail with some of your comments.
> I actually posted my experience with doing a rolling upgrade of a PHYSICAL standby database.
This statement is wrong. You can't do a rolling upgrade with a physical standby database. You have to convert the database to a logical standby database .. and then you can perform a rolling upgrade. But if you have done the conversion, it is not a physical anymore.
This is also described and mentioned in this white paper:
http://www.oracle.com/technology/deploy/availability/pdf/maa_wp_10gr2_rollingupgradebestpractices.pdf
Data Guard SQL Apply (logical standby database) is required in order to perform a database rolling upgrade. You can also do a rolling upgrade when starting with a physical standby by temporarily converting the physical standby to a logical standby. If starting with 11g, see the Rolling Database Upgrades for Physical Standby Databases using Transient Logical Standby 11g paper for details on doing a rolling upgrade when starting with a physical standby. If starting with 10g, see MetaLink note 300479.1.
> It WILL work, and is fairly straight forward.
In this point you are almost correct, because of a standard SAP system is not using the unsupported data types, etc. (afaik)
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/data_support.htm
To be honest if a sap basis admin asks such a question, i would not recommend to perform an unsupported way, because i am in doubt about his dataguard know how.
Regards
Stefan

Ye olde "delete archivelogs in standby" question

11.2.0.2.0
According to note
Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]
oracle should remove archive logs if we have deletion policy set to "delete applied on standby" which I have set on primary and standby. Monitoring the alert log we see
"Deleted Oracle managed file /path/to/an/archive/log"
so we think cool, its removing them automatically. Question is, when does it delete them? Right now my standby is in sync, yet my alert log is only sporadically showing my logs being deleted which were applied hours ago which I can visibly verify.

Hemant K Chitale wrote:
Oracle automatically deletes archivelogs only when it needs to clear space in the FRA (db_recovery_file_dest).
Hemant K ChitaleI had thought this so tested.
SQL> SELECT
2 substr(name, 1, 30) name,
3 space_limit/(1073741824) AS Quota_GB,
4 space_used/(1073741824) AS Used_GB,
5 space_reclaimable/(1073741824) AS Reclaimable_GB,
6 number_of_files AS files
7 FROM
8 v$recovery_file_dest ;
NAME                             QUOTA_GB    USED_GB RECLAIMABLE_GB      FILES
/u00/oracle/flash_recovery_are        310 19.7361012     18.1420259         46
-- bring the db_recovery_dest_size to 20gb to so we know we're over 90%. according to that first note I posted, the FRA deems anything over 85% as space pressure
SQL> alter system set db_recovery_file_dest_size=20g scope=both;
System altered.
SQL> SELECT
2   substr(name, 1, 30) name,
3   space_limit/(1073741824) AS Quota_GB,
4   space_used/(1073741824) AS Used_GB,
5   space_reclaimable/(1073741824) AS Reclaimable_GB,
6   number_of_files AS files
7   FROM
8   v$recovery_file_dest ;
NAME                             QUOTA_GB    USED_GB RECLAIMABLE_GB      FILES
/u00/oracle/flash_recovery_are         20 19.7437358     18.1420259         47
SQL> So i waited a good ten minutes but still no extra logs cleared out.
So I switched the logs a couple of times in production as well to see would that help and we did get some deleted then to bring the space used down to 17.5.gb which is just below the 85% mark.
SQL> SELECT
2   substr(name, 1, 30) name,
3   space_limit/(1073741824) AS Quota_GB,
4   space_used/(1073741824) AS Used_GB,
5   space_reclaimable/(1073741824) AS Reclaimable_GB,
6   number_of_files AS files
7   FROM
8   v$recovery_file_dest ;
NAME                             QUOTA_GB    USED_GB RECLAIMABLE_GB      FILES
/u00/oracle/flash_recovery_are         20 17.5075302     15.6462598         47
SQL> quick experiment, dropped to 15gb which is below the 17gb currently used. And yes immediately, I can see the files being deleted.
so what I take from this is that if there is any space available in the 15% free then Oracle waits to be woken up by the receipt of a log from primary, sees that theres less than 15% free and deletes logs to below that limit. however, if the space free is less than the space used then oracle wakes up itself and deletes the logs. Cool.
Thanks hemant.
Edited to fix coding

Rebuild standby question

Good morning,
I am puzzled by this in rebuilding standby process. I remember see this:
Before run “rman dup for standby …” you do “ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=defer..” in primary db.
After finish RMAN dup and start MRP process you do “ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=enable..” in primary db.
So during this RMAN dup time period (it can take several hours) we don’t ship any archive logs to standby and when RMAN finishes it inevitably has a lot of logs not in standby side. Does this mean that we definitely are going to have log gap after the RMAN dup? Do we need to manually copy those archive logs from primary to standby in order for MRP to apply them? What is the main reason we disable the log ship during rman dup period?
Thanks a lot in advance for sharing your insight!!
Shirley

The main reason to disable shipping during the dup is nothing exists to apply them to. If you are using RMAN to dup a standby you probably will move the RMAN backup and the current logs over before you issue the dup command which is something like this:
RMAN> run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
Once you have the new Standby you can "enable" shipping again. I generally do a log switch on the primary and used the v$ view v$archived_log to check the results. v$archived_log will show logs on both primary and standby, use the DEST_ID to check just one side and order by sequence#.
The alert log on both sides are a great source of information.
Does this answer your question?
Thoiught about this more. You could also try:
duplicate target database for standby from active database;
I have never tested this myself.
Edited by: mseberg on Nov 17, 2010 5:40 AM

Primary/standby question

Similar Messages

Maybe you are looking for