Standby database delay.

Hi All,
When I check the recovery process in my standby database.
select thread#, sequence#, applied, first_time, next_time from v$archived_log;
Few of the output lines is as follows :
THREAD# SEQUENCE# APP FIRST_TIME NEXT_TIME
2 9041 YES Nov 11 2007 17:06:05 Nov 11 2007 18:06:03
1 9070 YES Nov 11 2007 17:06:07 Nov 11 2007 18:06:08
2 9042 YES Nov 11 2007 18:06:03 Nov 11 2007 19:06:03
1 9071 YES Nov 11 2007 18:06:08 Nov 11 2007 19:06:06
2 9043 YES Nov 11 2007 19:06:03 Nov 11 2007 20:06:02
1 9072 YES Nov 11 2007 19:06:06 Nov 11 2007 20:06:07
2 9044 YES Nov 11 2007 20:06:02 Nov 11 2007 21:06:01
1 9073 YES Nov 11 2007 20:06:07 Nov 11 2007 21:06:07
2 9045 YES Nov 11 2007 21:06:01 Nov 11 2007 22:05:54
1 9074 YES Nov 11 2007 21:06:07 Nov 11 2007 22:06:06
2 9046 YES Nov 11 2007 22:05:54 Nov 11 2007 23:05:54
1 9075 YES Nov 11 2007 22:06:06 Nov 11 2007 23:06:04
2 9047 YES Nov 11 2007 23:05:54 Nov 12 2007 00:05:54
1 9076 YES Nov 11 2007 23:06:04 Nov 12 2007 00:06:03
2 9048 YES Nov 12 2007 00:05:54 Nov 12 2007 01:05:53
1 9077 YES Nov 12 2007 00:06:03 Nov 12 2007 01:06:03
2 9049 YES Nov 12 2007 01:05:53 Nov 12 2007 02:05:52
1 9078 YES Nov 12 2007 01:06:03 Nov 12 2007 02:06:04
2 9050 YES Nov 12 2007 02:05:52 Nov 12 2007 03:05:59
1 9079 YES Nov 12 2007 02:06:04 Nov 12 2007 03:06:20
2 9051 YES Nov 12 2007 03:05:59 Nov 12 2007 03:06:30
1 9079 NO Nov 12 2007 02:06:04 Nov 12 2007 03:06:20
1 9080 YES Nov 12 2007 03:06:20 Nov 12 2007 03:06:30
2 9052 YES Nov 12 2007 03:06:30 Nov 12 2007 04:06:26
1 9081 YES Nov 12 2007 03:06:30 Nov 12 2007 04:06:25
1 9082 YES Nov 12 2007 04:06:25 Nov 12 2007 05:06:17
2 9053 YES Nov 12 2007 04:06:26 Nov 12 2007 05:06:16
1 9083 YES Nov 12 2007 05:06:17 Nov 12 2007 05:52:30
2 9054 YES Nov 12 2007 05:06:16 Nov 12 2007 05:52:40
1 9084 YES Nov 12 2007 05:52:30 Nov 12 2007 05:52:37
2 9055 YES Nov 12 2007 05:52:40 Nov 12 2007 05:56:03
2 9056 YES Nov 12 2007 05:56:03 Nov 12 2007 05:56:10
1 9085 YES Nov 12 2007 05:52:37 Nov 12 2007 05:56:13
Question here is how come sequence 9079 of thread 1 is not applied where as the files created after that from the same thread is applied.
Thanks.

Hi Sybrand Bakker,
Good catch.
The alert entries are as follows:
Mon Nov 12 02:06:42 2007
Media Recovery Log /home/oracle/stdby/arch_1_9078_604578389.arc
Media Recovery Waiting for thread 1 sequence 9079 (in transit)
Mon Nov 12 02:06:47 2007
Recovery of Online Redo Log: Thread 1 Group 7 Seq 9079 Reading mem 0
Mem# 0 errs 0: /home/data/stdby/sb_redo_t01_g07.log
Mon Nov 12 03:06:00 2007
RFS[67]: Successfully opened standby log 16: '/home/data/stdby/sb_redo_t02_g16.log'
Mon Nov 12 03:06:00 2007
ARC1: Evaluating archive thread 2 sequence 9050
Mon Nov 12 03:06:00 2007
ARC1: Beginning to archive thread 2 sequence 9050 (330660529-330699863) (orastdby1)
ARCH: Connecting to console port...
Mon Nov 12 03:06:00 2007
ARC1: Creating local archive destination LOG_ARCHIVE_DEST_3: '/home/oracle/stdby/arch_2_9050_604578389.arc' (thread 2 sequence 9050)
(orastdby1)
ARCH: Connecting to console port...
Mon Nov 12 03:06:08 2007
ARC1: Closing local archive destination LOG_ARCHIVE_DEST_3: '/home/oracle/stdby/arch_2_9050_604578389.arc'
(orastdby1)
ARCH: Connecting to console port...
Committing creation of archivelog '/home/oracle/stdby/arch_2_9050_604578389.arc'
Mon Nov 12 03:06:08 2007
ARC1: Completed archiving thread 2 sequence 9050 (0-0) (orastdby1)
ARCH: Connecting to console port...
Mon Nov 12 03:06:20 2007
RFS[63]: Successfully opened standby log 6: '/home/data/stdby/sb_redo_t01_g06.log'
Mon Nov 12 03:06:30 2007
RFS[67]: Successfully opened standby log 17: '/home/data/stdby/sb_redo_t02_g17.log'
Mon Nov 12 03:06:30 2007
RFS[63]: Successfully opened standby log 8: '/home/data/stdby/sb_redo_t01_g08.log'
Mon Nov 12 03:06:34 2007
ARC1: Evaluating archive thread 1 sequence 9079
Mon Nov 12 03:06:34 2007
ARC1: Beginning to archive thread 1 sequence 9079 (330660759-330699937) (orastdby1)
ARCH: Connecting to console port...
Mon Nov 12 03:06:34 2007
ARC1: Creating local archive destination LOG_ARCHIVE_DEST_3: '/home/oracle/stdby/arch_1_9079_604578389.arc' (thread 1 sequence 9079)
(orastdby1)
ARCH: Connecting to console port...
Thanks.

Similar Messages

Standby database max availability..delay of committed changes at primary

Hi,
I have setup a single instance physical standby database for a 3 node RAC primary database (10.2.0.3 on Solaris 10).
The log_archive_dest_2 is set as "SERVICE=SDSMK LGWR SYNC AFFIRM NET_TIMEOUT=30 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=SDSMK"
at the primary db.
The primary database is running in Maximum availability mode.
The query "select protection_mode from v$database" gives "MAXIMUM AVAILABILITY" on both primary and standby databases.
Now I performed an insert into a table at primary db, COMMITTed the update and issued "ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL" at standby. I could not see the above added row in the table at standby. If I understand correctly, since the standby db is up, the network link is up and all the managed standby processes are up, the change should have been propogated at the standby aswell. Did I miss anything? Also how can I find how long the standby database is lagging interms of committed transactions at primary db?
Thanks,
Sreekanth

on primary:
SQL> insert into sds.test1 values(17);
1 row created.
SQL> commit;
Commit complete.
SQL> SELECT THREAD#, MAX(SEQUENCE#) FROM V$LOG_HISTORY GROUP BY THREAD# order by thread#;
THREAD# MAX(SEQUENCE#)
1 660
2 849
3 619
SQL> select current_Scn from v$database;
CURRENT_SCN
719552723
SQL>
on standby:
SQL> SELECT THREAD#, MAX(SEQUENCE#) FROM V$LOG_HISTORY GROUP BY THREAD# order by thread#;
THREAD# MAX(SEQUENCE#)
1 660
2 849
3 619
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> SELECT THREAD#, MAX(SEQUENCE#) FROM V$LOG_HISTORY GROUP BY THREAD# order by thread#;
THREAD# MAX(SEQUENCE#)
1 660
2 849
3 619
SQL> alter database open;
Database altered.
SQL> the change in test1 table is not seen here.

Error while trying to open physical standby database - (DATA GUARD)

Hi Everyone,
I have problems in opening the database of the physical standby in read- write mode/ read only mode. I have a primary server which is running on 2 node RAC and the standby on a seperate single server being used as DR. I recently got this server and my aim was to isolate the standby server from primary server and perform few test. As it has never been tested even once.
Primary Database spec: (2 Node Rac on ASM)
Oracle Version : 10.2.0.3.0
O/s : HP-UX B.11.23
Standby Database spec: (Single Node)
Oracle Version : 10.2.0.3.0
O/s: HP-UX db01 B.11.23
Error:
alter database recover managed standby database cancel;
Database altered.
SQL> alter database open
2 ;
alter database open
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+DATA/dprod/datafile/system01.dbf'
Parameters :
log_archive_dest_2 string SERVICE=PROD1 LGWR ASYNC VALID
FOR=(ONLINELOGFILES,PRIMARY_
ROLE) DB_UNIQUE_NAME=PROD
remote_archive_enable string true
fal_client string DPROD
fal_server string PROD1, PROD2
Steps tried so far:
Changed log_archive_dest_2 = DEFER on both the primary nodes
Standby :
startup nomount
alter database mount standby database;
alter database recover managed standby database disconnect;
alter database recover managed standby database cancel;
alter database open/readonly (tried both)
Same error.
On Primary:
SQL> select max(sequence#) from v$log_history;
MAX(SEQUENCE#)
55702
on Standby:
MAX(SEQUENCE#)
33289
Primary Database:
SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
55700 13-JUN-11 13-JUN-11
55700 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
55702 13-JUN-11 13-JUN-11
60824 rows selected.
Standby Database:
SEQUENCE# FIRST_TIME NEXT_TIME
55698 13-JUN-11 13-JUN-11
55699 13-JUN-11 13-JUN-11
55700 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
15206 rows selected.
Additional Information :
There is a delay of 20 minutes before the logs get applied. which has been intentional set by team.
Any help will be highly appreciated. Thanks in advance
Sadiq

Hi,
Primary Database:
select status,checkpoint_count from v$datafile_header;
STATUS CHECKPOINT_COUNT
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
STATUS CHECKPOINT_COUNT
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 59736
ONLINE 59736
ONLINE 59736
ONLINE 59736
ONLINE 59736
STATUS CHECKPOINT_COUNT
ONLINE 57717
ONLINE 57717
57 rows selected.
Standby Database;
select status,checkpoint_count from v$datafile_header;
STATUS CHECKPOINT_COUNT
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
STATUS CHECKPOINT_COUNT
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 32742
ONLINE 32742
ONLINE 32742
ONLINE 32742
ONLINE 32742
STATUS CHECKPOINT_COUNT
ONLINE 30723
ONLINE 30723
57 rows selected.
Archieve log list :
Primary database:
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 49110
Next log sequence to archive 49111
Current log sequence 49111
Standby Database:
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 49110
Next log sequence to archive 0
Current log sequence 49111
I tried log switch multiple times in primary database i saw that its getting highlighted in standby database.

Restored standby database from primary; now no logs are shipped

Hi
We recently had a major network/SAN issue and had to restore our standby database from a backup of the primary. To do this, we restored the database to the standby, created a standby controlfile on the primary, copied this across to the control file locations and started in standby recover and applied the logs manually/registered to get it back up to speed.
However, no new logs are being shipped across from the primary.
Have we missed a step somewhere?
One thing we've noticed is that there is no RFS process running on the standby:
SQL> SELECT PROCESS, CLIENT_PROCESS, SEQUENCE#, STATUS FROM V$MANAGED_STANDBY;
PROCESS CLIENT_P SEQUENCE# STATUS
ARCH ARCH 0 CONNECTED
ARCH ARCH 0 CONNECTED
MRP0 N/A 100057 WAIT_FOR_LOG
How do we start this? Or will it only show if the arc1 process on the primary is sending files?
The arc1 process is showing at OS level on the primary but I'm wondering if its faulty somehow?
There are NO errors in the alert logs in the primary or the standby. There's not even the normal FAL gap sequence type error - in the standby it's just saying 'waiting for log' and a number from ages ago. It's like the primary isn't even talking to the standby. The listener is up and running ok though...
What else can we check/do?
If we manually copy across files and do an 'alter database register' then they are applied to the standby without issue; there's just no automatic log shipping going on...
Thanks
Ross

Hi all
Many thanks for all the responses.
The database is 10.2.0.2.0, on AIX 6.
I believe the password files are ok; we've had issues previously and this is always flagged in the alert log on the primary - not the case here.
Not set to DEFER on primary; log_archive_dest_2 is set to service="STBY_PHP" optional delay=720 reopen=30 and log_archive_dest_state_2 is set to ENABLE.
I ran those troubleshooting scripts, info from standby:
SQL> @troubleshoot
NAME DISPLAY_VALUE
db_file_name_convert
db_name PHP
db_unique_name PHP
dg_broker_config_file1 /oracle/PHP/102_64/dbs/dr1PHP.dat
dg_broker_config_file2 /oracle/PHP/102_64/dbs/dr2PHP.dat
dg_broker_start FALSE
fal_client STBY_PHP
fal_server PHP
local_listener
log_archive_config
log_archive_dest_2 service=STBY_PHP optional delay=30 reopen=30
log_archive_dest_state_2 DEFER
log_archive_max_processes 2
log_file_name_convert
remote_login_passwordfile EXCLUSIVE
standby_archive_dest /oracle/PHP/oraarch/PHParch
standby_file_management AUTO
NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE
PHP PHP MAXIMUM PERFORM PHYSICAL S MOUNTED
ANCE TANDBY
THREAD# MAX(SEQUENCE#)
1 100149
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
MRP0 WAIT_FOR_LOG 1 100150
NAME VALUE UNIT TIME_COMPUTED
apply finish time day(2) to second(1) interval
apply lag day(2) to second(0) interval
estimated startup time 8 second
standby has been open N
transport lag day(2) to second(0) interval
NAME Size MB Used MB
0 0
On the primary, the script has froze!! How long should it take? Got as far as this:
SQL> @troubleshoot
NAME DISPLAY_VALUE
db_file_name_convert
db_name PHP
db_unique_name PHP
dg_broker_config_file1 /oracle/PHP/102_64/dbs/dr1PHP.dat
dg_broker_config_file2 /oracle/PHP/102_64/dbs/dr2PHP.dat
dg_broker_start FALSE
fal_client STBY_R1P
fal_server R1P
local_listener
log_archive_config
log_archive_dest_2 service="STBY_PHP" optional delay=720 reopen=30
log_archive_dest_state_2 ENABLE
log_archive_max_processes 2
log_file_name_convert
remote_login_passwordfile EXCLUSIVE
standby_archive_dest /oracle/PHP/oraarch/PHParch
standby_file_management AUTO
NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE SWITCHOVER_STATUS
PHP PHP MAXIMUM PERFORMANCE PRIMARY READ WRITE SESSIONS ACTIVE
THREAD# MAX(SEQUENCE#)
1 100206
NOW - before you say it - :) - yes, I'm aware that fal_client as STBY_R1P and fal_server as R1P are incorrect - should be PHP - but it looks like it's always been this way! Well, as least for the last 4 years where it's worked fine, as I found an old SP file and it still has R1P set in there...?!?
Any ideas?
Ross

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

Impact of force_logging on standby database in 10g?

Hi there,
We have a 10.2.0.5 database from which we want to setup a standby database...
We took a hot backup of the primary and send it to the standby server but at that time we realized that force logging is not enabled at the Primary before we took the hot backup!
Can you please suggest what are our options at this stage without losing any data and without a need to redo the hot backup again since it is a huge database?
- If we turn the force_logging on now(on Primary) and then set up the standby using the backup taken prior to force_logging ON - would it cause any issues?
Any help would be greatly appreciated.
Thanks.

No it won't because the hot backup is a copy period. So do it ASAP and the Archive will handle the rest.
So your hot backup is the Standby copy ( exact copy ). Just make sure forced logging is on and the archive with keep the data in sync.
If you delay then you are up the creek without a paddle as NOLOGGING actions are bound to occur and then the Standby data will not match the Primary.
If you have doubts your best option is to roll the standby forward using RMAN Incremental Backups :
http://www.oracle-ckpt.com/?s=incremental&op.x=31&op.y=11
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

Oracle Dataguard Question on Physical Standby Database with a Time Lag

I have a Standby database (PROD_LAG) that has a delay of 24hrs. How do I check to see what Archive have applied, what is current, and what is left to do.
There is a script but its for a Logical Standby database...
Thanks you in advance...

hi,
ok a little bit more explanation.
The GUI does work but seems to report incorrect data.
I have carried out a switchover so the primary database is now 'offsite_emrep' and the standby database is 'office_emrep'
The GUI how ever still reports that office_emrep is the primary database.
I cannot add the offsite_emrep database as the host is unknown. I am however running the GUI from the Host.
I have the following from the agent status
[oracle@griddg bin]$ ./emctl status agent
#Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.3.0
OMS Version : 10.2.0.3.0
Protocol Version : 10.2.0.2.0
Agent Home : /u01/app/oracle/product/10.2.0/agent10g
Agent binaries : /u01/app/oracle/product/10.2.0/agent10g
Agent Process ID : 19797
Parent Process ID : 19780
Agent URL : https://griddg.domain.net:3872/emd/main/
Repository URL : https://griddg.domain.net:1159/em/upload
Started at : 2007-10-01 12:35:02
Started by user : oracle
Last Reload : 2007-10-01 12:35:02
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 116
Size of XML files pending upload(MB) : 27.67
Available disk space on upload filesystem : 83.08%
Last attempted heartbeat to OMS : 2007-10-01 12:38:08
Last successful heartbeat to OMS : unknown
Agent is Running and Ready
any help is appreciated.
rgds
alan

How to apply Oracle patch when physical standby database in place

Dear All,
I want to apply Oracle patchset 8 on 10.2.0.5 when physical standby database in place. What are the steps for Primary site and for standby site.
Thanks in advance
Kamran Laeeq

Hi Kamran,
You will not upgrade or patch the standby database by importing offline redologs. On the contrary, there is a procedure to do this. Please note that you will not transitiate the role from standby to primary or startup the database. You will just startup the database by executing "startup mount" and "startup upgrade", during the upgrade. It means that you will not change database role standby to primary and you will be able to continue to the log shipment after the respective upgrade.
But, it is very important that you should stop the log shipment and apply all the offline redologs, before the upgrade. Technically, you can import offline redologs after the upgrade, by changing "compatibility" parameter in oracle, but regarding to my experiences it may cause some problems after you transitiate the role from standby to primary.
In short;
In order to stop log shipment, at the primary site;
alter system set log_archive_dest_state_2=defer;
In order to import all the offline redologs without a delay, at the standby site;
alter database recover managed standby database cancel;
alter database recover managed standby database nodelay disconnect from session;
I hope that I clarified the issue,
Best regards,
Orkun Gedik

Standby database doubts

Hi All,
I have some doubts in Oracle Standby database configuration and log transfer and redo apply.
I have read the below document.
Oracle® Data Guard Concepts and Administration
Now my doubts are *(in Physical standby database with Maximum performance mode)*
1. When configuring the standby database we are creating standby redologs in primary database,Is this standby redologs are used only when the role transition happens or for anyother purpose?
2.The archivelogs are shipped from primary to standby and the archivelogs are applied to the standby database by doing the normal media recovery.Now, how and when the data is written in the standby database redologfiles,so that when we enable the real time apply it uses the standby database redologfile to apply the data without delay?
3.(if the second point is true)In the standby database will it generate the Archivelogfiles from the redo applied, apart from the primary archivelogs which are transfered?
Please Advice..
TIA,

1. When configuring the standby database we are creating standby redologs in primary database,Is this standby redologs are used only when the role transition happens or for anyother purpose?It is not for role transition.
A standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases.
You can recover more data than only applying archive logs in case of failure.
SRLs' are a must for real time apply.
2.The archivelogs are shipped from primary to standby and the archivelogs are applied to the standby database by doing the normal media recovery.Now, how and when the data is written in the standby database redologfiles,so that when we enable the real time apply it uses the standby database redologfile to apply the data without delay?The data is directly written from production to SRL of standby database using lgwr process(with the help of RFS), that is why it real time. Not waiting for a log switch. See the [diagram.|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1021537]
3.(if the second point is true)In the standby database will it generate the Archivelogfiles from the redo applied, apart from the primary archivelogs which are transfered?No. Only standby redo log will generate archived logs.
Regards,
S.K.

Best way to synchronize DR standby database

Hi,
My setup consists of 3 database installations in three data centers on aix 6.1 and oracle 11g release 2 Enterprise editions.
The first data center will host the primary database, while the second data center will act as a hot standby site, hosting the physical standby database in a data guard configuration. This second data center is just a few hundred meters from the primary site and is connected with dark fiber.
The 3rd site is a DR site located about 300KM from the first two centers, and with a WAN link of speeds around 2Mbps. This third site should act as a disaster recovery site in case there's a natural calamity that destroys the first two sites.
We purchased full license for the first two sites for oracle. However, for the 3rd site, we're only allowed to open the database for up to 10 days in a year. My question is how can we always bring this 3rd database into sync with the first two. Can we use full backups to recover the database periodically, like every month? Or is there another option of using archivelogs, considering that the database can only be open up to a maximum of 10 days in a year?
Both the primary and the DR sites have Tivoli server installed complete with the tape libraries and we're suppose to take backups even on the DR site.
Regards,
dula

I think your potential solutions depend in part on the meaning of 'open' and what kind of database set up you have at the third site. If the third site is a Standby Datbase and open means in use for any purpose other than recovery mode then you should be able to start it and apply the logs so the the database is ready should the need arise.
If open means the database is started and active then all you can really do is install Oracle at the third site and leave it off. In this case what I would do is use the rman duplicate command to build the initial database, start it, test it, and shut it down. Then you transfer your primary database rman backup to the site every day along with copies of the archived redo logs. In the event of a primary/secondary site failure you just need to run an rman restore of the newest backup set then recovery using the copied archive redo logs and you are up and running.
There will be the time delay equal to the time to run restore and recovery but you can set up the remote diaster site, test it, and be pretty sure it will work without using up your 10 day limit.
An alternate license arrangement might be to run RAC at the two local data centers and have a Stand by database at the remote site.
HTH -- Mark D Powell --

When is anything written to standby redo logs on standby database?

I am on Oracle 10.2.0.4 on HP UNIX. I have read Oracle 10.2 concepts guide on technet.oracle.com, have read may article on metalink and internet, yet I am unable to verify when anything is written to standby redo logs on stand by database.
I have a simple database reconfiguration: a primary database and one standby database.
I created primary database and set up log_archive_dest_2 to use LGWR SYNC AFFIRM
I have created standby redo logs on primary.
alter database add standby logfile GROUP
I create standby control file on primary.
I copied all the primary information to create standby database. I have put standby database in managed recovery.
I did archive log switches, I created a table and inserted information in table.
I never saw standby redo logs updated on standby database by looking at timestamp of standby redo log files.
I then setup database in maximum availability mode by running following on primary:
Alter database set standby database to maximize availability
When I do insert into my tables, I do see standby redo log files on primary database being updated, but I have never seen standby redo logs on standby database updated. Why?
I am still at loss when actually standby redo logs are updated on standby database.
When I read Oracle 9i database documentation on data guard, it says that you do not need standby redo logs on primary instead you need them on standby. Only reason, you need them on primary is from primary changes role to standby database, so standby redo logs on standby database should be updated instead of standby redo logs on primary.

What is the PROTECTION_MODE ,PROTECTION_LEVEL values of your database.
As per metalink:--
Create standby redo log files, if necessary:
Standby redo logs are necessary for the higher protection levels such as
Guaranteed, Instant, and Rapid. In these protection modes LGWR from the
Primary host writes transactions directly to the standby redo logs.
This enables no data loss solutions and reduces the amount of data loss
in the event of failure. Standby redo logs are not necessary if you are using
the delayed protection mode.
If you configure standby redo on the standby then you should also configure
standby redo logs on the primary database. Even though the standby redo logs
are not used when the database is running in the primary role, configuring
the standby redo logs on the primary database is recommended in preparation
for an eventual switchover operation.
Standby redo logs must be archived before the data can be applied to the
standby database. The standby archival operation occurs automatically, even if
the standby database is not in ARCHIVELOG mode. However, the archiver process
must be started on the standby database. Note that the use of the archiver
process (ARCn) is a requirement for selection of a standby redo log.
METALINK ID:- Doc ID: Note:219344.1
Edited by: Anand... on Sep 15, 2008 2:15 AM

Using LOGMNR on Standby Database

We are running Solaris 8 9i Release 1 Patchset 3
databases. I have a primary database and
a delayed mode Data Guard standby in Managed Recovery mode.
What I want to do is use the Standby to mine the Primary's Logs via LOGMNR, however I don't want to initialize the Standby. From what I recall, you can run LOGMNR against a Mounted Database rather than an OPEN READ WRITE database. Here are my questions:
1. Can LOGMNR be run on a Standby Database opened in READ ONLY mode?
2. Can LOGMNR be run on a Mounted Standby?
3. Can I analyze the Primary Logs currently being Transferred and subsequently applied to the Standby?
Obviously, I could test these one-by-one, but I thought I'd start here first. Any help would be appreciated.
Best Regards,
James Colestock
OCP Oracle DBA
Portland State University

No this to my knowlewdge is not true.
The DBID is created upon creation of the database. If you duplicate your database quick and dirty, you would probably simply copy the control file to a different server, assure that all mounting points and pathes are the same than on production and perform a restore and recovery based on the production backup sets and archive logs. This then would result in a complelety identical database, including the DBID.
If you need to change the DBID because you did a manual duplication as indicated above and want to register the new database with a recovery catalog, this then would force you to utilize the dbnewid tool to overwrite the DBID.
If you duplicate your database using the RMAN duplicat command, RMAN will assing a new DBID, so this then is the clean way. Using the RMAN frees you from any headache related to the DBID.
Best regards,
Jürgen

Need help on Physical standby database

Currently our physical standby database is running in manual mode and logs are applied by me manually delay of 2 days.
And also when I add a data file in the primary database ,I've to manually add the file again on the standby .
This process is becoming too laborious, now I want to automate this process,
Now my question is
For automating this process ,do I need to bounce the database ?
I want to have 2 days gap for archive log apply process? How should I do that.
And what all parameters I need to change.
Please advice....
Verison Oracle 9.2.0.7
OS-solaris 10

Duplicate thread
[duplicate thread | http://forums.oracle.com/forums/thread.jspa?threadID=699262&tstart=0 ]

[Standby Database] Advantage and Disadvantage of using stanby redolog

Hi fellow DBA. I'd like to ask the disadvantage and advantage of using standby redo logs. I hope you could help me out. Thanks

Advantages
1. if your Standby needs to run on Maximum Availability or Protection modes you have to use the Standby redo logs
2. Redo data writen on the primary will be written to standby at the same time. therefore if you primary fails you have a fall back option without or minimum data lost.
(LGWR with Sync option on Maximum Protection will have Zero Data lost.)
3. It uses LGWR than ARCH process on the standby.
4. If you are using Cascaded Destinations (cascade Standby Databases - One standby sends the Redo to another Standby ) Then you have to use Standby redo logs.
5. Standby redo logs can create even after the standby database creation.
Disadvantages
1. Your Primary Has to Write data into two different Redo logs. Hence there will be a delay on the transaction response time.
(But with Maximum Availability and LGWR with aSync option will not wait the transactions to be commited on standby database) .
Refer the note 219344.1 Usage, Benefits and Limitations of Standby Redo Logs (SRL)
Hope you will have a fair idea about this

Standby database delay.

Similar Messages

Maybe you are looking for