Reg : no rfs background processor in standby

hai all,
os:windows server
oracle :10.2.0.3
i have a problem with my standby database. i found no rfs bacckground processor in standby while siing the query
>>> select process,status,sequence# fro mv$managed_standby;
PROCESS STATUS SEQUENCE#
ARCH CONNECTED 0
ARCH CONNECTED 0
ARCH CONNECTED 0
ARCH CONNECTED 0
ARCH CONNECTED 0
ARCH CONNECTED 0
ARCH CONNECTED 0
ARCH CONNECTED 0
ARCH CONNECTED 0
ARCH CONNECTED 0
MRP0 WAIT_FOR_LOG 5949
i have shutdown the standby instance ,mounted and start the recovery (twice). still having the same issue. .
MORE OVER THERE IS NO ARCHIVE GAP
HELP ME IN THIS ...
REGARDS
GOLD....

my log file...............
Mon Feb 25 07:48:05 2013
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 352321536
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 0
nls_language = ENGLISH
nls_territory = UNITED KINGDOM
sga_target = 1610612736
control_files = E:\ORADATA\WPLQDM\CONTROL01.CTL, I:\ORADATA\WPLQDM\CONTROL02.CTL, J:\ORADATA\WPLQDM\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 1207959552
compatible = 10.2.0.1.0
log_archive_config = DG_CONFIG=(wplqdmp,wplqdms2)
log_archive_dest_2 = SERVICE=wpl_qdm_pro OPTIONAL LGWR ASYNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=wplqdms2
log_archive_max_processes= 10
fal_client = wpl_qdm_stb2
fal_server = wpl_qdm_pro
db_file_multiblock_read_count= 16
db_recovery_file_dest = J:\flash_recovery_area
db_recovery_file_dest_size= 31457280000
standby_file_management = AUTO
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
service_names = WPLQDM
dispatchers = (PROTOCOL=TCP) (SERVICE=wplqdmXDB)
job_queue_processes = 10
audit_file_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\WPLQDM\ADUMP
background_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\WPLQDM\BDUMP
user_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\WPLQDM\UDUMP
core_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\WPLQDM\CDUMP
db_name = wplqdm
db_unique_name = WPLQDMS2
open_cursors = 300
pga_aggregate_target = 1277165568
PMON started with pid=2, OS id=3516
PSP0 started with pid=3, OS id=4064
MMAN started with pid=4, OS id=580
DBW0 started with pid=5, OS id=4184
LGWR started with pid=6, OS id=5032
CKPT started with pid=7, OS id=4076
SMON started with pid=8, OS id=3604
RECO started with pid=9, OS id=344
CJQ0 started with pid=10, OS id=800
MMON started with pid=11, OS id=4200
Mon Feb 25 07:48:05 2013
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=4804
Mon Feb 25 07:48:05 2013
starting up 1 shared server(s) ...
Mon Feb 25 07:48:17 2013
alter database mount standby database
Mon Feb 25 07:48:21 2013
Setting recovery target incarnation to 1
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=4024
ARC1 started with pid=17, OS id=3712
ARC2 started with pid=18, OS id=4376
ARC3 started with pid=19, OS id=2052
ARC4 started with pid=20, OS id=4468
ARC5 started with pid=21, OS id=3556
ARC6 started with pid=22, OS id=3212
ARC7 started with pid=23, OS id=4476
ARC8 started with pid=24, OS id=516
Mon Feb 25 07:48:21 2013
ARC0: Archival started
ARC1: Archival started
Mon Feb 25 07:48:21 2013
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon Feb 25 07:48:21 2013
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Mon Feb 25 07:48:21 2013
ARC1: Becoming the heartbeat ARCH
Mon Feb 25 07:48:21 2013
ARC8: Thread not mounted
Mon Feb 25 07:48:21 2013
Successful mount of redo thread 1, with mount id 171090433
Mon Feb 25 07:48:21 2013
Physical Standby Database mounted.
Completed: alter database mount standby database
Mon Feb 25 07:48:22 2013
ARC7: Thread not mounted
ARC0: Thread not mounted
Mon Feb 25 07:48:24 2013
ARC5: Thread not mounted
Mon Feb 25 07:48:25 2013
ARC2: Thread not mounted
Mon Feb 25 07:48:26 2013
ARC3: Thread not mounted
ARC1: Thread not mounted
Mon Feb 25 07:48:28 2013
ARC6: Thread not mounted
ARC9 started with pid=25, OS id=4384
Mon Feb 25 07:48:30 2013
ARC4: Thread not mounted
Mon Feb 25 07:49:00 2013
alter database recover managed standby database disconnect
MRP0 started with pid=26, OS id=4768
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 3 processes
Mon Feb 25 07:49:07 2013
Errors in file e:\oracle\product\10.2.0\admin\wplqdm\bdump\wplqdm_mrp0_4768.trc:
ORA-00313: Message 313 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1] [J:\ORADATA\WPLQDM\REDO01_3.RDO]
ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1]
ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1] [E:\ORADATA\WPLQDM\REDO01_1.RDO]
ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the fil
Mon Feb 25 07:49:07 2013
Errors in file e:\oracle\product\10.2.0\admin\wplqdm\bdump\wplqdm_mrp0_4768.trc:
ORA-00313: Message 313 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1] [J:\ORADATA\WPLQDM\REDO01_3.RDO]
ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1] [I:]
ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1] [E:\ORADATA\WPLQDM\REDO01_1.RDO]
ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the fil
Clearing online redo logfile 1 E:\ORADATA\WPLQDM\REDO01_1.RDO
Clearing online log 1 of thread 1 sequence number 5937
Mon Feb 25 07:49:07 2013
Errors in file e:\oracle\product\10.2.0\admin\wplqdm\bdump\wplqdm_mrp0_4768.trc:
ORA-00313: Message 313 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1] [J:\ORADATA\WPLQDM\REDO01_3.RDO]
ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1] [I:]
ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1] [E:\ORADATA\WPLQDM\REDO01_1.RDO]
ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the fil
Mon Feb 25 07:49:07 2013
Errors in file e:\oracle\product\10.2.0\admin\wplqdm\bdump\wplqdm_mrp0_4768.trc:
ORA-19527: Message 19527 not found; No message file for product=RDBMS, facility=ORA
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [1] [1] [E:\ORADATA\WPLQDM\REDO01_1.RDO]
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 5949
Mon Feb 25 07:49:07 2013
Completed: alter database recover managed standby database disconnect
Mon Feb 25 08:03:11 2013
db_recovery_file_dest_size of 30000 MB is 7.80% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.

Similar Messages

Set background picture for standby screen on E61

Hi,
is there any way I can change the look of the Standby-screen (different background) without installing a complete new theme?
I tried once with a nice jpg I had found on the internet because I was getting bored with the Nokia-blue-spots-or-something-theme: I loaded it into my gallery and the Options menu displayed a submenu "As Background" which I selected. Whew, there it was, very nice. Was there for two days (equivalent to two restarts as I switch off at night), then it was gone...
Tried once more, was there for another two days, then gone.
Any ideas?
Thanks a lot!
Regards,
Hendikoischnur
IT will paint our future - either green or black
* ecosia, the eco-friendly search engine (powered by Yahoo/Bing/WWF);
* Searching for pics online? Try ecocho.eu or treehoo.com
* For those who don´t want to miss Google: Try znout.de - it´s Google running on green energy
* CO2-free chatting: Try Jabber-server.de (running on 100% waterpower)

Try modifying your Nokia theme (or whichever one is current) so the standby screen is your favourite JPG, then hopefully it won't lose the settings so often...you can do this by going into Tools/Themes, choose the current theme, choose edit, then select wallpaper, point at your pic, save etc etc
good luck.

Reg:ALV list Background Problem

Dear All,
I created a ALV LIST report. While i am running in that program in foreground i am getting timeout error. While running in background i am getting the output in improper way. While i am seeing that report in spool request and pressing the spool output display in maximum width i am getting the output list fields in improper position. What should i have to do for this issue?
Thanks,
Sankar M

When you execute the report in background, u require to provide the width of the output it will be some thing like X_65_255.Try increasing the width.
One more alternative is go to SPAD -> In settings Menu option -> Select Spool System -> go to others tab -> select the check box number of columns for list display format.
Hope this inputs will help you.
Regards,
Shafivullah Mohammad

ORA-16401: archivelog rejected by RFS

Hello, here are the logs and initialisation parameters. It is not applying the logs. Am running XXXXP and the standby and the primary are on the same server.
Please, I need help. Thanks
RFS[1]: Assigned to RFS process 216
RFS[1]: Identified database type as 'physical standby'
Wed May 13 18:39:07 2009
RFS LogMiner: Client disabled from further notification
RFS[1]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST2\STANDBY.LOG'
Wed May 13 18:39:15 2009
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 3-3
DBID 1063720110 branch 686695334
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Wed May 13 18:39:48 2009
RFS[1]: Archived Log: 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TEST2\ARC00003_0686697929.001'
Wed May 13 18:40:33 2009
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Wed May 13 18:40:48 2009
RFS[1]: Archivelog thread 1 sequence 3 cannot be reused
Wed May 13 18:40:48 2009
Errors in file c:\oracle\product\10.2.0\admin\test2\udump\test2_rfs_216.trc:
ORA-16401: archivelog rejected by RFS
test1.__db_cache_size=88080384
test1.__java_pool_size=4194304
test1.__large_pool_size=4194304
test1.__shared_pool_size=62914560
test1.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\test1\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\test1\bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\test1\control01.ctl','C:\oracle\product\10.2.0\oradata\test1\control02.ctl','C:\oracle\product\10.2.0\oradata\test1\control03.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\test1\cdump'
*.db_block_size=8192
*.db_domain='appstech.local'
*.db_create_file_dest='C:\Oracle\product\10.2.0\oradata\test1'
*.db_file_multiblock_read_count=16
*.db_file_name_convert='C:\Oracle\product\10.2.0\oradata\test2\','C:\Oracle\product\10.2.0\oradata\test1\'
*.db_name='test1'
*.db_recovery_file_dest='C:\Oracle\product\10.2.0\flash_recovery_area\TEST1'
*.db_recovery_file_dest_size=2147483648
*.db_unique_name='test1'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=test1XDB)'
*.fal_client='test1'
*.fal_server='test2'
*.job_queue_processes=10
*.local_listener='test1'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(test1,test2)'
*.LOG_ARCHIVE_DEST_1='LOCATION=C:\Oracle\product\10.2.0\flash_recovery_area\TEST1
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=test1'
*.log_archive_dest_2='SERVICE=test2 ARCH MANDATORY
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=test2'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.log_file_name_convert='C:\Oracle\product\10.2.0\flash_recovery_area\TEST2','C:\Oracle\product\10.2.0\flash_recovery_area\TEST1',
'C:\Oracle\product\10.2.0\flash_recovery_area\TEST2\ONLINELOG','C:\Oracle\product\10.2.0\flash_recovery_area\TEST1\ONLINELOG',
'C:\Oracle\product\10.2.0\oradata\test2','C:\Oracle\product\10.2.0\oradata\test1',
'C:\Oracle\product\10.2.0\flash_recovery_area\TEST2\FLASHBACK','C:\Oracle\product\10.2.0\flash_recovery_area\TEST1\FLASHBACK'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.query_rewrite_enabled='true'
*.sga_target=167772160
*.undo_management='AUTO'
*.undo_retention=3600
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\test1\udump'
test2.__db_cache_size=79691776
test2.__java_pool_size=4194304
test2.__large_pool_size=4194304
test2.__shared_pool_size=71303168
test2.__streams_pool_size=0
*.archive_lag_target=1800
*.audit_file_dest='C:\oracle\product\10.2.0\admin\test2\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\test2\bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\Oracle\product\10.2.0\oradata\test2\control01.ctl','C:\Oracle\product\10.2.0\oradata\test2\control02.ctl'
,'C:\Oracle\product\10.2.0\oradata\test2\control03.ctl'
#*.control_files='C:\Oracle\product\10.2.0\oradata\test2\test1_test2.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\test2\cdump'
*.db_block_size=8192
*.db_domain='appstech.local'
*.db_file_multiblock_read_count=16
*.db_file_name_convert='C:\Oracle\product\10.2.0\oradata\test1','C:\Oracle\product\10.2.0\oradata\test2'
*.db_name='test1'
*.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=4147483648
*.dg_broker_start=TRUE
*.dispatchers='(PROTOCOL=TCP) (SERVICE=test1XDB)'
*.db_unique_name='test2'
*.fal_client='test2'
*.fal_server='test1'
*.job_queue_processes=10
*.local_listener='test2'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(TEST1,TEST2)'
*.LOG_ARCHIVE_DEST_1='LOCATION=C:\Oracle\product\10.2.0\flash_recovery_area\TEST2\ARCHIVELOG
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=test2'
*.log_archive_dest_2='SERVICE=test1 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=test1'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.log_file_name_convert='C:\Oracle\product\10.2.0\flash_recovery_area\TEST1\ONLINELOG\','C:\Oracle\product\10.2.0\flash_recovery_area\TEST2\ONLINELOG\'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.query_rewrite_enabled='TRUE'
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\test2\udump'
*.undo_retention=3600
*.db_create_file_dest='C:\Oracle\product\10.2.0\oradata\test2'
*.log_archive_start='TRUE'
*.log_archive_trace=2
*.remote_archive_enable='TRUE'

Hello those are the latest logs I can see them over to the standby but they are not applied to them. I have set the LGWR on both log_archive_dest_2;
Regards
ompleted: alter database mount standby database
Thu May 14 11:18:15 2009
alter database recover managed standby database disconnect from session
MRP0 started with pid=18, OS id=3940
Managed Standby Recovery not using Real Time Apply
Media Recovery start incarnation depth : 1, target inc# : 4, irscn : 607856
Media Recovery Waiting for thread 1 sequence 3 branch(resetlogs_id) 686695334
Fetching gap sequence in thread 1 branch(resetlogs_id) 686695334, gap seq 3-3
Thu May 14 11:18:21 2009
Completed: alter database recover managed standby database disconnect from session
Thu May 14 11:18:51 2009
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 3-3
DBID 1063720110 branch 686695334
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Thu May 14 11:21:23 2009
Shutting down instance: further logons disabled
Thu May 14 11:21:23 2009
Stopping background process CJQ0
Thu May 14 11:21:24 2009
Stopping background process MMNL
Thu May 14 11:21:25 2009
Stopping background process MMON
Thu May 14 11:32:25 2009
Shutting down archive processes
Thu May 14 11:32:30 2009
ARCH shutting down
ARC2: Archival stopped
Thu May 14 11:32:31 2009
Errors in file c:\oracle\product\10.2.0\admin\test1\bdump\test1_arc1_1912.trc:
ORA-16401: archivelog rejected by RFS
Thu May 14 11:33:31 2009
Errors in file c:\oracle\product\10.2.0\admin\test1\bdump\test1_arc1_1912.trc:
ORA-16401: archivelog rejected by RFS
Thu May 14 11:34:31 2009
Errors in file c:\oracle\product\10.2.0\admin\test1\bdump\test1_arc1_1912.trc:
ORA-16401: archivelog rejected by RFS

Standby database is not completing recovery.

All,
I applied a PSU to 10.2.0.4 (8576156) patch this afternoon on both the primary and standby oracle_home(s). Upon starting up the standby database, I no longer see the “media recovery waiting” message in the alert log when an archive log is sent from the primary.
Not sure if I have an issue with the patch or DG is configured or started.
Perhaps another set of eyes can lead me to an issue I am not seeing.
The standby database was started as follows:
alter database RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION
Example alert log message before:
Sun Sep 13 02:20:39 2009
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Sun Sep 13 02:20:47 2009
Media Recovery Waiting for thread 1 sequence 52 (in transit) <<== NOTE
Sun Sep 13 02:20:47 2009
Recovery of Online Redo Log: Thread 1 Group 4 Seq 52 Reading mem 0
Mem# 0: /oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log
Mem# 1: /oradat2/cwsiqa2/cwsiqa2_sb_redo04_b.log
Example alert log message after:
Primary database is in MAXIMUM PERFORMANCE mode
Tue Sep 15 15:56:27 2009
RFS[3]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Tue Sep 15 15:56:27 2009
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
Tue Sep 15 15:57:05 2009
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[5]: Assigned to RFS process 29772
RFS[5]: Identified database type as 'physical standby'
Tue Sep 15 16:12:56 2009
The same messages are listed in v$datagurd_status
1* select message from v$dataguard_status
SQL> /
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARC9: Becoming the 'no FAL' ARCH
ARC9: Becoming the 'no SRL' ARCH
ARC0: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery starting Real Time Apply
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 28316
RFS[1]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 28318
RFS[2]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 29693
RFS[3]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 29691
RFS[4]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[5]: Assigned to RFS process 29772
RFS[5]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
I also have a “gap” that is not getting resolved.
SQL> select * from v$archive_gap
2 /
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 53 53
SELECT MAX(R.SEQUENCE#) LAST_SEQ_RECD, MAX(L.SEQUENCE#) LAST_SEQ_SENT
2* FROM V$ARCHIVED_LOG R, V$LOG L WHERE R.DEST_ID=2 AND L.ARCHIVED='YES'
SQL> /
LAST_SEQ_RECD LAST_SEQ_SENT
54 58
Any insight would be appreciated.

Problem has been resolved.

Creating Standby Database / Steps might be missing..

I have created standby database..
The archives are copied except one archived log and those copied archived are not applied at Standby database.
Besides this issue, I just checked the alert log file and pasting its contents here.
Do check it and let me know If I m missing any paramter[s].
Dump file c:\oracle\product\10.2.0\admin\rockstd\bdump\alert_rockstd.log
Mon May 12 15:23:42 2008
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 2
CPU : 2 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1194M/2038M, Ph+PgF:1368M/2641M, VA:1940M/2047M
Mon May 12 15:23:42 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 150
sga_target = 167772160
control_files = C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\ROCKSTD.CTL
db_block_size = 8192
compatible = 10.2.0.1.0
log_archive_dest_1 = location=C:\oracle\product\10.2.0\oradata\rockstd\Archive_rock
log_archive_dest_state_1 = ENABLE
log_archive_format = arc_%s_%t_%r.arc
fal_client = ROCKSTD
fal_server = ROCK
db_file_multiblock_read_count= 16
db_recovery_file_dest = C:\oracle\product\10.2.0\flash_recovery_area\rockstd
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=rockXDB)
job_queue_processes = 10
audit_file_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\ADUMP
background_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\BDUMP
user_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\UDUMP
core_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\CDUMP
db_name = rock
db_unique_name = rockstd
open_cursors = 300
pga_aggregate_target = 16777216
PMON started with pid=2, OS id=3656
PSP0 started with pid=3, OS id=504
MMAN started with pid=4, OS id=2544
DBW0 started with pid=5, OS id=3652
LGWR started with pid=6, OS id=552
CKPT started with pid=7, OS id=2688
SMON started with pid=8, OS id=3436
RECO started with pid=9, OS id=3696
CJQ0 started with pid=10, OS id=1636
MMON started with pid=11, OS id=2072
MMNL started with pid=12, OS id=3812
Mon May 12 15:23:43 2008
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Mon May 12 15:24:06 2008
alter database mount standby database
Mon May 12 15:24:11 2008
Setting recovery target incarnation to 14
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=3536
Mon May 12 15:24:11 2008
ARC0: Archival started
ARC1 started with pid=17, OS id=4084
Mon May 12 15:24:12 2008
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon May 12 15:24:12 2008
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC1: Thread not mounted
Mon May 12 15:24:12 2008
Successful mount of redo thread 1, with mount id 3275426006
Mon May 12 15:24:12 2008
Physical Standby Database mounted.
Mon May 12 15:24:13 2008
ARC0: Becoming the heartbeat ARCH
Completed: alter database mount standby database
Mon May 12 15:25:02 2008
Using STANDBY_ARCHIVE_DEST parameter default value as C:\oracle\product\10.2.0\oradata\rockstd\Archive_rock
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 3444
RFS[1]: Identified database type as 'physical standby'
Mon May 12 15:25:02 2008
RFS LogMiner: Client disabled from further notification
Mon May 12 15:25:21 2008
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon May 12 15:26:19 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo04.log' size 50m
Mon May 12 15:26:20 2008
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo04.log' size 50m
Mon May 12 15:26:27 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo05.log' size 50m
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo05.log' size 50m
Mon May 12 15:26:33 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo06.log' size 50m
Mon May 12 15:26:34 2008
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo06.log' size 50m
Mon May 12 15:27:20 2008
alter database recover managed standby database disconnect from session
MRP0 started with pid=19, OS id=596
Managed Standby Recovery not using Real Time Apply
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\UNDOTBS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSAUX01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\TESTING1.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM03.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\ABAMCO_TEST01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
MRP0: Background Media Recovery terminated with error 1110
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_mrp0_596.trc:
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_mrp0_596.trc:
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
Mon May 12 15:27:27 2008
Completed: alter database recover managed standby database disconnect from session
Mon May 12 15:30:18 2008
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 2456
RFS[2]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 15:30:22 2008
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 3124
RFS[3]: Identified database type as 'physical standby'
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 15:53:45 2008
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 15:53:46 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 15:53:58 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:06 2008
RFS[3]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:09 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:14 2008
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 16:00:18 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Regards,
Rakesh Soni.

Done, I've given the same path in Standby Database [datafiles, controlfiles] as it has been given in the Primary Database.
MoreOver, I m manually switching logfiles at primary database [alter system switch logfile] they are copied and applied sucessfully at standby database. But the archived files that I have copied with cold backup are not applied yet. Infact they are not retrieved executing the below query.
select name, applied from v$archived_log;
How can I apply those archived logs? [archives that copied with cold backup]
Regards.

Standby problem - log numbers out of sequence

Hi everyone! I am on 10.2.0.3.
My physical standby stopped applying logs because all of a sudden the logs went out of sequence. See errors below - after seq 7975 & 7976 seq# 7974 showed up again:
Recovery of Online Redo Log: Thread 1 Group 200 Seq 7974 Reading mem 0
Mem# 0: /db/data3/FSPRD/stby_redo02.log
Mem# 1: /db/data4/FSPRD/stby_redo02_02.log
Thu Dec 18 16:14:58 2008
RFS[23]: Successfully opened standby log 100: '/db/data1/FSPRD/stby_redo01.log'
Thu Dec 18 16:15:01 2008
RFS[25]: Successfully opened standby log 300: '/db/data5/FSPRD/stby_redo03.log'
Thu Dec 18 16:15:01 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[37]: Successfully opened standby log 400: '/db/data7/FSPRD/stby_redo04.log'
Thu Dec 18 16:15:02 2008
RFS[24]: Successfully opened standby log 200: '/db/data3/FSPRD/stby_redo02.log'
Thu Dec 18 16:15:03 2008
Media Recovery Waiting for thread 1 sequence 7975 (in transit)
Thu Dec 18 16:15:03 2008
Recovery of Online Redo Log: Thread 1 Group 100 Seq 7975 Reading mem 0
Mem# 0: /db/data1/FSPRD/stby_redo01.log
Mem# 1: /db/data2/FSPRD/stby_redo01_02.log
Media Recovery Waiting for thread 1 sequence 7976 (in transit)
Thu Dec 18 16:15:07 2008
Recovery of Online Redo Log: Thread 1 Group 200 Seq 7974 Reading mem 0
Mem# 0: /db/data3/FSPRD/stby_redo02.log
Mem# 1: /db/data4/FSPRD/stby_redo02_02.log
MRP0: Background Media Recovery terminated with error 355
Thu Dec 18 16:15:12 2008
Errors in file /db/dbdump/FSPRD/bdump/fsprd_mrp0_11351.trc:
ORA-00355: change numbers out of order
ORA-00353: log corruption near block 2 change 4994299896 time 12/18/2008 16:14:57
ORA-00312: online log 200 thread 1: '/db/data4/FSPRD/stby_redo02_02.log'
ORA-00312: online log 200 thread 1: '/db/data3/FSPRD/stby_redo02.log'
Managed Standby Recovery not using Real Time Apply
Thu Dec 18 16:15:12 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[37]: Successfully opened standby log 100: '/db/data1/FSPRD/stby_redo01.log'
Thu Dec 18 16:15:13 2008
Recovery interrupted!
Thu Dec 18 16:15:13 2008
Errors in file /db/dbdump/FSPRD/bdump/fsprd_mrp0_11351.trc:
ORA-00355: change numbers out of order
ORA-00353: log corruption near block 2 change 4994299896 time 12/18/2008 16:14:57
ORA-00312: online log 200 thread 1: '/db/data4/FSPRD/stby_redo02_02.log'
ORA-00312: online log 200 thread 1: '/db/data3/FSPRD/stby_redo02.log'
Thu Dec 18 16:15:13 2008
MRP0: Background Media Recovery process shutdown (FSPRD)
Thu Dec 18 16:15:19 2008
I of course restarted the managed recovery and everything went fine from this point on - but I could not find the root cause of this problem.
Anybody has any ideas - or experienced this before?
TIA.

I'm afraid you're hitting bug 6039415 ORA-355 can occur during real time apply, the good news: there's a patch available.
HTH
Enrique

RFS[15]: Archivelog thread 1 sequence 3066 cannot be reused

During learning DataGuard on Windows 20003 in Oracle 10g, i run the shutdown abort command on the primary to see if fast-start failover is working, it was completed successfully and standby database became primary.
But on my new standby database which was previously primary, i am getting the following error:
>
RFS[15]: Archivelog thread 1 sequence 3066 cannot be reused
>
Can any body help?

In this environment, i have total three databases. One is primary which was previously physical standby database, second is logical standby database and third one which is in problem is the physical standby database.
>
Can you check alert log file & post some more information from trace files
>
ARCH: STARTING ARCH PROCESSES COMPLETE
Tue Oct 18 12:12:39 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
Tue Oct 18 12:12:40 2011
Successful mount of redo thread 1, with mount id 37729331
Tue Oct 18 12:12:40 2011
Allocated 3981204 bytes in shared pool for flashback generation buffer
Starting background process RVWR
RVWR started with pid=46, OS id=3284
Tue Oct 18 12:12:40 2011
Physical Standby Database mounted.
ARCt started with pid=45, OS id=2372
Tue Oct 18 12:12:40 2011
ARC1: Becoming the heartbeat ARCH
Completed: alter database mount
Tue Oct 18 12:12:43 2011
Starting Data Guard Broker (DMON)
INSV started with pid=48, OS id=6044
NSV1 started with pid=47, OS id=5780
RSM0 started with pid=49, OS id=4540
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Tue Oct 18 12:13:04 2011
ALTER SYSTEM SET log_archive_dest_1='location="C:\Oracle\product\10.2.0\flash_recovery_area\standbyFiles\"','valid_for=(STANDBY_LOGFILE,STANDBY_ROLE)' SCOPE=BOTH SID='qadirect';
Tue Oct 18 12:13:04 2011
ALTER SYSTEM SET log_archive_dest_state_1='ENABLE' SCOPE=BOTH SID='qadirect';
Tue Oct 18 12:13:04 2011
ALTER SYSTEM SET standby_archive_dest='C:\Oracle\product\10.2.0\flash_recovery_area\standbyFiles\' SCOPE=BOTH SID='qadirect';
Tue Oct 18 12:13:04 2011
ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='qadirect';
Tue Oct 18 12:13:04 2011
ALTER SYSTEM SET log_archive_format='%t_%s_%r.arc' SCOPE=SPFILE SID='qadirect';
Tue Oct 18 12:13:04 2011
ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';
Tue Oct 18 12:13:04 2011
ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';
Tue Oct 18 12:13:05 2011
ALTER SYSTEM SET log_archive_max_processes=30 SCOPE=BOTH SID='*';
Tue Oct 18 12:13:05 2011
ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';
Tue Oct 18 12:13:05 2011
ALTER SYSTEM SET db_file_name_convert='C:\ORACLE\PRODUCT\10.2.0\ORADATA\QADIRECT\','D:\test\oradata\','D:\QADIRECT_DB_FILES\DATA_FILES\','D:\test\oradata\' SCOPE=SPFILE;
Tue Oct 18 12:13:05 2011
ALTER SYSTEM SET log_file_name_convert='C:\ORACLE\PRODUCT\10.2.0\ORADATA\QADIRECT\','D:\test\oradata\' SCOPE=SPFILE;
Tue Oct 18 12:13:05 2011
ALTER SYSTEM SET fal_server='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SSI-ORACLE)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=test_XPT)(SERVER=dedicated)))' SCOPE=BOTH;
Tue Oct 18 12:13:05 2011
ALTER SYSTEM SET fal_client='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=SSI-ORACLE)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=qadirect_XPT)(INSTANCE_NAME=qadirect)(SERVER=dedicated)))' SCOPE=BOTH;
Tue Oct 18 12:13:05 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE
MRP0 started with pid=50, OS id=5788
Managed Standby Recovery starting Real Time Apply
Clearing online redo logfile 1 C:\ORACLE\PRODUCT\10.2.0\ORADATA\QADIRECT\REDO01.LOG
Clearing online log 1 of thread 1 sequence number 3066
Tue Oct 18 12:13:12 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE
Tue Oct 18 12:13:13 2011
Clearing online redo logfile 1 complete
Clearing online redo logfile 2 C:\ORACLE\PRODUCT\10.2.0\ORADATA\QADIRECT\REDO02.LOG
Clearing online log 2 of thread 1 sequence number 3067
Clearing online redo logfile 2 complete
Clearing online redo logfile 3 C:\ORACLE\PRODUCT\10.2.0\ORADATA\QADIRECT\REDO03.LOG
Clearing online log 3 of thread 1 sequence number 3065
Clearing online redo logfile 3 complete
Media Recovery Waiting for thread 1 sequence 3065
Fetching gap sequence in thread 1, gap sequence 3065-3065
Tue Oct 18 12:13:24 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 6160
RFS[1]: Identified database type as 'physical standby'
Primary database is in MAXIMUM AVAILABILITY mode
Changing standby controlfile to RESYNCHRONIZATION level
Tue Oct 18 12:13:24 2011
RFS LogMiner: Client disabled from further notification
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
RFS[1]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\QADIRECT\LOG1.RDO'
Tue Oct 18 12:13:29 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 6440
RFS[2]: Identified database type as 'physical standby'
Tue Oct 18 12:13:29 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 2868
RFS[3]: Identified database type as 'physical standby'
Tue Oct 18 12:13:30 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 3536
RFS[4]: Identified database type as 'physical standby'
Tue Oct 18 12:13:30 2011
RFS[3]: Archivelog thread 1 sequence 3065 cannot be reused
Tue Oct 18 12:13:30 2011
Errors in file c:\oracle\product\10.2.0\admin\qadirect\udump\qadirect_rfs_2868.trc:
ORA-16401: archivelog rejected by RFS
Tue Oct 18 12:13:30 2011
RFS[2]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\QADIRECT\LOG2.RDO'
Tue Oct 18 12:13:34 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[5]: Assigned to RFS process 2740
RFS[5]: Identified database type as 'physical standby'
RFS[5]: Archivelog thread 1 sequence 3065 cannot be reused
Tue Oct 18 12:13:35 2011
Errors in file c:\oracle\product\10.2.0\admin\qadirect\udump\qadirect_rfs_2740.trc:
ORA-16401: archivelog rejected by RFS
Tue Oct 18 12:13:59 2011
Fetching gap sequence in thread 1, gap sequence 3065-3070
Tue Oct 18 12:14:00 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[6]: Assigned to RFS process 3120
RFS[6]: Identified database type as 'physical standby'
Tue Oct 18 12:14:01 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[7]: Assigned to RFS process 6096
RFS[7]: Identified database type as 'physical standby'
Tue Oct 18 12:14:02 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[8]: Assigned to RFS process 4616
RFS[8]: Identified database type as 'physical standby'
Tue Oct 18 12:14:02 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[9]: Assigned to RFS process 1032
RFS[9]: Identified database type as 'physical standby'
Tue Oct 18 12:14:02 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[10]: Assigned to RFS process 6284
RFS[10]: Identified database type as 'physical standby'
Tue Oct 18 12:14:03 2011
RFS[6]: Archivelog thread 1 sequence 3066 cannot be reused
>
is it RAC or single instance database?
>
It is a single instance database.
>
SQL> SELECT * FROM GV$DATAGUARD_STATUS where message like '% Archivelog thread% cannot be reused%';
>
INST_ID FACILITY SEVERITY DEST_ID MESSAGE_NUM ERROR_CODE CALLOUT TIMESTAMP MESSAGE
1 Remote File Server Error 0 2648 16401 YES 10/19/2011 RFS[6]: Archivelog thread 1 sequence 3065 cannot be reused
1 Remote File Server Error 0 2649 16401 YES 10/19/2011 RFS[11]: Archivelog thread 1 sequence 3066 cannot be reused
1 Remote File Server Error 0 2650 16401 YES 10/19/2011 RFS[10]: Archivelog thread 1 sequence 3065 cannot be reused
1 Remote File Server Error 0 2651 16401 YES 10/19/2011 RFS[9]: Archivelog thread 1 sequence 3066 cannot be reused
1 Remote File Server Error 0 2652 16401 YES 10/19/2011 RFS[12]: Archivelog thread 1 sequence 3065 cannot be reused
1 Remote File Server Error 0 2653 16401 YES 10/19/2011 RFS[13]: Archivelog thread 1 sequence 3066 cannot be reused
1 Remote File Server Error 0 2654 16401 YES 10/19/2011 RFS[14]: Archivelog thread 1 sequence 3065 cannot be reused
1 Remote File Server Error 0 2655 16401 YES 10/19/2011 RFS[26]: Archivelog thread 1 sequence 3066 cannot be reused
1 Remote File Server Error 0 2656 16401 YES 10/19/2011 RFS[16]: Archivelog thread 1 sequence 3065 cannot be reused
1 Remote File Server Error 0 2657 16401 YES 10/19/2011 RFS[17]: Archivelog thread 1 sequence 3066 cannot be reused
1 Remote File Server Error 0 2658 16401 YES 10/19/2011 RFS[18]: Archivelog thread 1 sequence 3065 cannot be reused
>
Is still standby is working? do they have standby redo log file groups?
>
Yes it is still working and contains standby redo log file groups.

Help! standby errors

Hi, we got some weird messages from standby alert log on the apply instance of standby. Could someone help me what we need to do to fix this problem. Thank you so much.
Our system is Oracle RAC (2 nodes, 10g, ASM, Windows Servers 2003). Both primary and standby have the same configuration
Fri Feb 06 02:17:28 2009
Recovery of Online Redo Log: Thread 1 Group 12 Seq 547 Reading mem 0
Mem# 0: +DATA/standby/onlinelog/group_12.287.677414141
Mem# 1: +RECOVERY/standby/onlinelog/group_12.5749.677414141
Fri Feb 06 04:59:38 2009
Errors in file c:\oracle\product\10.2.0\admin\standby\bdump\standby2_p005_6116.trc:
ORA-00339: archived log does not contain any redo
ORA-00334: archived log: '+DATA/standby/onlinelog/group_1.306.677414335'
ORA-10567: Redo is inconsistent with data block (file# 8, block# 39122)
ORA-10564: tablespace PAD_INDEX
ORA-01110: data file 8: '+DATA/standby/datafile/pad_index.319.677763323'
ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 50004
Fri Feb 06 04:59:38 2009
Errors in file c:\oracle\product\10.2.0\admin\standby\bdump\standby2_p005_6116.trc:
ORA-00339: archived log does not contain any redo
ORA-00334: archived log: '+DATA/standby/onlinelog/group_9.312.677414345'
Fri Feb 06 04:59:38 2009
Errors in file c:\oracle\product\10.2.0\admin\standby\bdump\standby2_p005_6116.trc:
ORA-00600: internal error code, arguments: [3020], [8], [39122], [33593554], [], [], [], []
Fri Feb 06 04:59:38 2009
Errors in file c:\oracle\product\10.2.0\admin\standby\bdump\standby2_p005_6116.trc:
ORA-00600: internal error code, arguments: [3020], [8], [39122], [33593554], [], [], [], []
Fri Feb 06 04:59:38 2009
Trace dumping is performing id=[cdmp_20090205045938]
Fri Feb 06 04:59:40 2009
MRP0: Background Media Recovery terminated with error 12801
Fri Feb 06 04:59:40 2009
Errors in file c:\oracle\product\10.2.0\admin\standby\bdump\standby2_mrp0_1728.trc:
ORA-12801: error signaled in parallel query server P005, instance standbyDB2:standby2 (2)
ORA-00600: internal error code, arguments: [3020], [8], [39122], [33593554], [], [], [], []
Fri Feb 06 04:59:41 2009
Managed Standby Recovery not using Real Time Apply
Fri Feb 06 04:59:44 2009
Recovery interrupted!
Recovered data files to a consistent state at change 6773432869
Fri Feb 06 04:59:46 2009
Errors in file c:\oracle\product\10.2.0\admin\standby\bdump\standby2_mrp0_1728.trc:
ORA-12801: error signaled in parallel query server P005, instance standbyDB2:standby2 (2)
ORA-00600: internal error code, arguments: [3020], [8], [39122], [33593554], [], [], [], []
Fri Feb 06 08:58:42 2009
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
RFS[30]: Successfully opened standby log 11: '+DATA/standby/onlinelog/group_11.288.677414139'
Fri Feb 06 16:27:51 2009
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
RFS[30]: Successfully opened standby log 12: '+DATA/standby/onlinelog/group_12.287.677414141'

There is a bug published in metalink.
Please read note 30866.1 and 7197445.8

Rfs backgorund process

Hello
Assume Im using maximum protection mode,
arc0 process archives the current redolog and arc1 process pushes the archivelog to standby side.
MRP process applies the archivelog.
What is RFS background process responsible for in this scenerio?

Hi,
Regarding maximum performance protection mode (no standby redologs)
rfs gets the info from arc1 and creates new archivelog in standby database
After that this new archivelog is applied by managed recovery process.
Is this right?Yes if there are no standby redologs that is right. (BTW this is called maximum performance mode -> least data protection)
But still
If this is the case, why oracle simply pushes the copy the archivelog and applies, in this case there is no need for rfs..No from 9i on the RFS is integrated in the oracle software to make the archivelog or standby redologs work.
Regards,
Tycho

Physical Standby Issue-please help

Hi Can anyone please help me here. I get the following error in my alert log in the standby. Whats wrong here ?
Attempt to start background Managed Standby Recovery process (data_db)
MRP0 started with pid=19, OS id=11575532
Fri May 15 09:37:40 2009
MRP0: Background Managed Standby Recovery process started (data_db)
Managed Standby Recovery not using Real Time Apply
MRP0: Background Media Recovery terminated with error 1111
Fri May 15 09:37:46 2009
Errors in file /app/oracle/admin/data_db/bdump/data_db_mrp0_11575532.trc:
ORA-01111: name for data file 91 is unknown - rename to correct file
ORA-01110: data file 91: '/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00091'
ORA-01157: cannot identify/lock data file 91 - see DBWR trace file
ORA-01111: name for data file 91 is unknown - rename to correct file
ORA-01110: data file 91: '/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00091'
Fri May 15 09:37:46 2009
Errors in file /app/oracle/admin/data_db/bdump/data_db_mrp0_11575532.trc:
ORA-01111: name for data file 91 is unknown - rename to correct file
ORA-01110: data file 91: '/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00091'
ORA-01157: cannot identify/lock data file 91 - see DBWR trace file
ORA-01111: name for data file 91 is unknown - rename to correct file
ORA-01110: data file 91: '/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00091'
Fri May 15 09:37:46 2009
MRP0: Background Media Recovery process shutdown (data_db)

I found the cause
RFS[60]: Successfully opened standby log 12: '/data_db/data002/stdbyredo/stdby_1_redo02.log'
Thu May 14 18:33:11 2009
Media Recovery Log /data_db/arch001/637599916_1_47025.dbf
Recovery deleting file #91:'/data_db/data001/streams_tbs_01.dbf' from controlfile.
Recovery dropped tablespace 'STREAMS_TBS'
WARNING: File being created with same name as in Primary
Existing file may be overwritten
File #91 added to control file as 'UNNAMED00091'.
Originally created as:
'/data_db/data001/streams_tbs_01.dbf'
Recovery was unable to create the file as:
'/data_db/data001/streams_tbs_01.dbf'
Errors with log /data_db/arch001/637599916_1_47025.dbf
MRP0: Background Media Recovery terminated with error 1119
Thu May 14 18:33:13 2009
Errors in file /app/oracle/admin/data_db/bdump/data_db_mrp0_11292908.trc:
ORA-01119: error in creating database file '/data_db/data001/streams_tbs_01.dbf'
ORA-27038: created file already exists
Additional information: 1
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail
Thu May 14 18:33:13 2009
Errors in file /app/oracle/admin/data_db/bdump/data_db_mrp0_11292908.trc:
ORA-01119: error in creating database file '/data_db/data001/streams_tbs_01.dbf'
ORA-27038: created file already exists
Additional information: 1
Thu May 14 18:33:13 2009
MRP0: Background Media Recovery process shutdown (data_db)now what to do... :(

Standby and primary

On my Primary database
when I did archive log list, it gives me
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u04/oradata/arch/PROD/
Oldest online log sequence 29627
Next log sequence to archive 29629
Current log sequence 29629
On my standby database, when I did archive log list, it gives me
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u04/oradata/arch/STNBY/
Oldest online log sequence 29627
Next log sequence to archive 0
Current log sequence 29629
But during hotback on primary it pops up with these errors
RMAN-08137: WARNING: archive log not deleted as it is still needed
archive log filename=/u04/oradata/arch/PROD/PROD_0001_749397572_0000028449.arc thread=1 sequence=28449
RMAN-08137: WARNING: archive log not deleted as it is still needed
archive log filename=/u04/oradata/arch/PROD/PROD_0001_749397572_0000028450.arc thread=1 sequence=28450
RMAN-08137: WARNING: archive log not deleted as it is still needed
I am sure Standby is not in sync with primary.
Can someone explain in detail how to resolve this issue.
Any help is greatly appreciated.
Thank you

My alert log in bdump has the following information:
Primary database is in MAXIMUM PERFORMANCE mode
RFS[739]: Successfully opened standby log 4: '/u01/oradata/STNBY/redo_STNBY_04a.log'
Tue Sep 13 11:27:35 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[739]: Successfully opened standby log 4: '/u01/oradata/STNBY/redo_STNBY_04a.log'
Tue Sep 13 11:28:04 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[739]: Successfully opened standby log 4: '/u01/oradata/STNBY/redo_STNBY_04a.log'
Tue Sep 13 11:40:33 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[739]: Successfully opened standby log 4: '/u01/oradata/STNBY/redo_STNBY_04a.log'
Tue Sep 13 12:00:44 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[739]: Successfully opened standby log 4: '/u01/oradata/STNBY/redo_STNBY_04a.log'
Tue Sep 13 12:02:49 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[739]: Successfully opened standby log 4: '/u01/oradata/STNBY/redo_STNBY_04a.log'
Trace file in bdump give me the following information.
*** 2011-09-09 11:58:59.650 61283 kcrr.c
FAL[client, MRP0]: Error 12514 connecting to PROD for fetching gap sequence
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
*** 2011-09-09 11:59:29.662
OCIServerAttach failed -1
.. Detailed OCI error val is 12514 and errmsg is 'ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
*** 2011-09-09 11:59:29.662 61283 kcrr.c
FAL[client, MRP0]: Error 12514 connecting to PROD for fetching gap sequence
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
*** 2011-09-09 11:59:59.674
OCIServerAttach failed -1
.. Detailed OCI error val is 12514 and errmsg is 'ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
*** 2011-09-09 11:59:59.674 61283 kcrr.c
FAL[client, MRP0]: Error 12514 connecting to PROD for fetching gap sequence
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
*** 2011-09-09 12:00:29.687
OCIServerAttach failed -1
.. Detailed OCI error val is 12514 and errmsg is 'ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
*** 2011-09-09 12:00:29.687 61283 kcrr.c
FAL[client, MRP0]: Error 12514 connecting to PROD for fetching gap sequence
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
*** 2011-09-09 12:00:59.697
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
-----------------------------------------------------------

Logical Standby Database Not Getting Sync With Primary Database

Hi All,
I am using a Primary DB and Logical Standby DB configuration in Oracle 10g:-
Version Name:-
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE 10.2.0.5.0 Production
TNS for Solaris: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production
We have build the logical standby last week and till date the Logical DB is not sync. I have checked the init parameters and I wont see any problems with it. Also archive log destinations are also fine enough.
We have a important table named "HPD_HELPDESK" where record count is growing gradually whereas in logical standby it's not growing. There are some 19K record difference in the both the tables.
I have checked the alert log but it is also not giving any error message. Please find the last few lines of the alert log in logical Database:-
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1703_790996778.arc] to LogMiner session id [1]
Tue Aug 28 14:56:52 GMT 2012
RFS[2853]: Successfully opened standby log 5: '/oracle_data/oradata/remedy/stbyredo01.log'
Tue Aug 28 14:56:58 GMT 2012
RFS LogMiner: Client enabled and ready for notification
Tue Aug 28 14:57:00 GMT 2012
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1704_790996778.arc] to LogMiner session id [1]
Tue Aug 28 15:06:40 GMT 2012
RFS[2854]: Successfully opened standby log 5: '/oracle_data/oradata/remedy/stbyredo01.log'
Tue Aug 28 15:06:47 GMT 2012
RFS LogMiner: Client enabled and ready for notification
Tue Aug 28 15:06:49 GMT 2012
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1705_790996778.arc] to LogMiner session id [1]
I am not able to trace the issue that why the records are not growing in logical DB. Please provide your inputs.
Regards,
Arijit

How do you know that there's such a gap between the tables?
If your standby db is a physical standby, then it is not open and you can't query your table without cancelling the recovery of the managed standby database.
What does it say if you execute this sql?
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;The ARCH processes should be connected and MRP waiting for a file.
If you query for the archive_gaps, do you get any hits?
select * from gv$archive_gapIf you're not working in a RAC environment you need to query v$archive_gap, instead!
Did you check whether the archives generated from the primary instance are transferred and present in the file system of your standby database?
I believe your standby is not in recovery_mode anymore or has an archive_gap, which is the reason why it doesn't catch up anymore.
Hope it helps a little,
Regards,
Sebastian
PS: I'm working on 11g, so unfortunately I'm not quite sure if the views are exist in 10gR2. It's worth a try though!
Edited by: skahlert on 31.08.2012 13:46

Log applying service is taking more time in phy. Standby

Hi Gurus,
My Database version as follows
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
We have datagaurd setup as well - Huge archive logs are generating in our primary database - Archive logs are shipping to standby with no dealy - But applying the archive logs are taking more in our physical standby database - Can you please help me why it was taking more time to apply archivlogs (sync) in standby ? - What could be possible reasons..?
Note : Size of standby redo logs are same as redo log file of primary database - Also standy by redo one or more than online redo log primary.
I also confirmed from network guy for network issue - He said that network is good.
Please let me know if any other information required? - Since i need to report my higer leve stating this is cause for delay in applying archive logs.
Thanks

No we don't have delay option in log_archive_dest
here is alert log
edia Recovery Waiting for thread 1 sequence 42017 (in transit)
Thu Sep 19 09:00:09 2013
Recovery of Online Redo Log: Thread 1 Group 6 Seq 42017 Reading mem 0
Mem# 0: /xyz/u002/oradata/xyz/stb_redo/redo0601.log
Mem# 1: /xyz/u200/oradata/xyz/stb_redo/redo0601.log
Thu Sep 19 09:00:49 2013
RFS[1]: Successfully opened standby log 5: '/xyz/u002/oradata/xyz/stb_redo/redo0501.log'
Thu Sep 19 09:00:54 2013
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 7: '/xyz/u002/oradata/xyz/stb_redo/redo0701.log'
Thu Sep 19 09:00:58 2013
Media Recovery Waiting for thread 1 sequence 42018 (in transit)
Thu Sep 19 09:00:58 2013
Recovery of Online Redo Log: Thread 1 Group 5 Seq 42018 Reading mem 0
Mem# 0: /xyz/u002/oradata/xyz/stb_redo/redo0501.log
Mem# 1: /xyz/u200/oradata/xyz/stb_redo/redo0501.log
Media Recovery Waiting for thread 1 sequence 42019 (in transit)
Thu Sep 19 09:01:08 2013
Recovery of Online Redo Log: Thread 1 Group 7 Seq 42019 Reading mem 0
Mem# 0: /xyz/u002/oradata/xyz/stb_redo/redo0701.log
Mem# 1: /xyz/u200/oradata/xyz/stb_redo/redo0701.log
Thu Sep 19 09:01:08 2013
RFS[1]: Successfully opened standby log 5: '/xyz/u002/oradata/xyz/stb_redo/redo0501.log'
Thu Sep 19 09:01:22 2013
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 6: '/xyz/u002/oradata/xyz/stb_redo/redo0601.log'
Thu Sep 19 09:01:26 2013
RFS[1]: Successfully opened standby log 5: '/xyz/u002/oradata/xyz/stb_redo/redo0501.log'
Thu Sep 19 09:01:26 2013
Media Recovery Log /xyz/u002/oradata/xyz/arch/ARCH1_42020_821334023.LOG
Media Recovery Waiting for thread 1 sequence 42021 (in transit)
Thu Sep 19 09:01:30 2013
Recovery of Online Redo Log: Thread 1 Group 5 Seq 42021 Reading mem 0
Mem# 0: /xyz/u002/oradata/xyz/stb_redo/redo0501.log
Mem# 1: /xyz/u200/oradata/xyz/stb_redo/redo0501.log
Thu Sep 19 09:01:51 2013
Media Recovery Waiting for thread 1 sequence 42022 (in transit)
Thu Sep 19 09:01:51 2013
Recovery of Online Redo Log: Thread 1 Group 6 Seq 42022 Reading mem 0
Mem# 0: /xyz/u002/oradata/xyz/stb_redo/redo0601.log
Mem# 1: /xyz/u200/oradata/xyz/stb_redo/redo0601.log
Thu Sep 19 09:01:57 2013
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 5: '/xyz/u002/oradata/xyz/stb_redo/redo0501.log'
Thu Sep 19 09:02:01 2013
Media Recovery Waiting for thread 1 sequence 42023 (in transit)
Thu Sep 19 09:02:01 2013
Recovery of Online Redo Log: Thread 1 Group 5 Seq 42023 Reading mem 0
Mem# 0: /xyz/u002/oradata/xyz/stb_redo/redo0501.log
Mem# 1: /xyz/u200/oradata/xyz/stb_redo/redo0501.log

Logical standby | archive log deleted | how to remove gap ???

hi gurus...
i have problem on logical standby
by mistake standby log coming to logical standby has been deleted , now how to fill up the gap ???
ON STANDBY
SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# APPLIED
228 674847 674872 YES
229 674872 674973 CURRENT
230 674973 674997 NO
231 674997 675023 NO
232 675023 675048 NO
233 675048 675109 NO
234 675109 675135 NO
235 675135 675160 NO
236 675160 675183 NO
237 675183 675208 NO
238 675208 675232 NO
239 675232 675257 NO
240 675257 675282 NO
241 675282 675382 NO
242 675382 675383 NO
243 675383 675650 NO
244 675650 675652 NO
245 675652 675670 NO
246 675670 675688 NO
247 675688 675791 NO
248 675791 678524 NO
archive log are shipping to standby location also and getting registered
ALERT LOG OF STANDBY
Fri May 7 12:25:36 2010
Primary database is in MAXIMUM PERFORMANCE mode
RFS[21]: Successfully opened standby log 5: '/u01/app/oracle/oradata/BEST/redo05.log'
Fri May 7 12:25:37 2010
RFS LogMiner: Registered logfile [u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_248_1_715617824.dbf] to LogMiner session id [1]
but i dont have standby log after 229 sequence ...
ON PRIMARY
SYS@TEST AS SYSDBA> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u01/app/oracle/flash_recovery_area/TEST/standlogOldest online log sequence 247
Next log sequence to archive 249
Current log sequence 249
what to do next to apply sequences and bring both in sync.
please help me ,,,,
Edited by: user12281508 on May 7, 2010 9:45 AM

thanks for response.
no its pure logical standby
i have tried to ftp the archive logs of primary to standby and applied manually
SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf';
alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf'
ERROR at line 1:
ORA-01289: cannot add duplicate logfile
SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf';
alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf'
ERROR at line 1:
ORA-01289: cannot add duplicate logfile
any other way ????

Reg : no rfs background processor in standby

Similar Messages

Maybe you are looking for