Log is not applied, subsequent log applied are "yes"
Hi all,
I am building a new standby.
It is brand new, and I have turned on the managed recovery for the first time after restoring my database.
--> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Why does the first line show "NO" for applied log? (and all the logs after it shows "YES"?)
Is there something wrong, or can I ignore this as it is normal?
SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY sequence#; 2 3
SEQUENCE# FIRST_TIME NEXT_TIME APP
2653893 30-OCT-2012 23:03:21 30-OCT-2012 23:03:25 NO
2653894 30-OCT-2012 23:03:25 30-OCT-2012 23:23:04 YES
2653895 30-OCT-2012 23:23:04 30-OCT-2012 23:23:28 YES
2653896 30-OCT-2012 23:23:28 30-OCT-2012 23:26:32 YES
2653897 30-OCT-2012 23:26:32 30-OCT-2012 23:26:49 YES
2653898 30-OCT-2012 23:26:49 30-OCT-2012 23:31:05 YES
2653899 30-OCT-2012 23:31:05 31-OCT-2012 00:00:41 YES
2653900 31-OCT-2012 00:00:41 31-OCT-2012 00:31:04 YES
2653901 31-OCT-2012 00:31:04 31-OCT-2012 01:01:03 YES
2653902 31-OCT-2012 01:01:03 31-OCT-2012 01:31:17 YES
Edited by: user8875620 on Nov 8, 2012 11:20 PM
user8875620 wrote:
Hi all,
I am building a new standby.
It is brand new, and I have turned on the managed recovery for the first time after restoring my database.
--> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Why does the first line show "NO" for applied log? (and all the logs after it shows "YES"?)
Is there something wrong, or can I ignore this as it is normal?
SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY sequence#; 2 3
SEQUENCE# FIRST_TIME NEXT_TIME APP
2653893 30-OCT-2012 23:03:21 30-OCT-2012 23:03:25 NO
2653894 30-OCT-2012 23:03:25 30-OCT-2012 23:23:04 YES
2653895 30-OCT-2012 23:23:04 30-OCT-2012 23:23:28 YES
2653896 30-OCT-2012 23:23:28 30-OCT-2012 23:26:32 YES
2653897 30-OCT-2012 23:26:32 30-OCT-2012 23:26:49 YES
2653898 30-OCT-2012 23:26:49 30-OCT-2012 23:31:05 YES
2653899 30-OCT-2012 23:31:05 31-OCT-2012 00:00:41 YES
2653900 31-OCT-2012 00:00:41 31-OCT-2012 00:31:04 YES
2653901 31-OCT-2012 00:31:04 31-OCT-2012 01:01:03 YES
2653902 31-OCT-2012 01:01:03 31-OCT-2012 01:31:17 YES
Edited by: user8875620 on Nov 8, 2012 11:20 PMWhat is the version you are using?
Are you using Data Guard broker?
Assuming you are not using Real-time apply.
Basically there are so many bugs with the views specific to Data Guard they are v$archived_gap, v$archived_log depending on the environments.
One of note for this bug.
'APPLIED'-Column not updated if Heartbeat-ARCH hangs [ID 1369630.1]
v$archived_log: applied column is not marked if recovery applied the redo from SRL [ID 1481927.1]
Thanks
Similar Messages
-
I have one problem with Data Guard. My archive log files are not applied.
I have one problem with Data Guard. My archive log files are not applied. However I have received all archive log files to my physical Standby db
I have created a Physical Standby database on Oracle 10gR2 (Windows XP professional). Primary database is on another computer.
In Enterprise Manager on Primary database it looks ok. I get the following message Data Guard status Normal
But as I wrote above the archive log files are not applied
After I created the Physical Standby database, I have also done:
1. I connected to the Physical Standby database instance.
CONNECT SYS/SYS@luda AS SYSDBA
2. I started the Oracle instance at the Physical Standby database without mounting the database.
STARTUP NOMOUNT PFILE=C:\oracle\product\10.2.0\db_1\database\initluda.ora
3. I mounted the Physical Standby database:
ALTER DATABASE MOUNT STANDBY DATABASE
4. I started redo apply on Physical Standby database
alter database recover managed standby database disconnect from session
5. I switched the log files on Physical Standby database
alter system switch logfile
6. I verified the redo data was received and archived on Physical Standby database
select sequence#, first_time, next_time from v$archived_log order by sequence#
SEQUENCE# FIRST_TIME NEXT_TIME
3 2006-06-27 2006-06-27
4 2006-06-27 2006-06-27
5 2006-06-27 2006-06-27
6 2006-06-27 2006-06-27
7 2006-06-27 2006-06-27
8 2006-06-27 2006-06-27
7. I verified the archived redo log files were applied on Physical Standby database
select sequence#,applied from v$archived_log;
SEQUENCE# APP
4 NO
3 NO
5 NO
6 NO
7 NO
8 NO
8. on Physical Standby database
select * from v$archive_gap;
No rows
9. on Physical Standby database
SELECT MESSAGE FROM V$DATAGUARD_STATUS;
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
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
MRP0: Background Media Recovery terminated with error 1110
MRP0: Background Media Recovery process shutdown
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 2148
RFS[1]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 2384
RFS[2]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 3188
RFS[3]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles created
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 3168
RFS[4]: Identified database type as 'physical standby'
RFS[4]: No standby redo logfiles created
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles created
10. on Physical Standby database
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 1 9 13664 2
RFS IDLE 0 0 0 0
10) on Primary database:
select message from v$dataguard_status;
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
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
ARCm: Becoming the 'no FAL' ARCH
ARCm: Becoming the 'no SRL' ARCH
ARCd: Becoming the heartbeat ARCH
Error 1034 received logging on to the standby
Error 1034 received logging on to the standby
LGWR: Error 1034 creating archivelog file 'luda'
LNS: Failed to archive log 3 thread 1 sequence 7 (1034)
FAL[server, ARCh]: Error 1034 creating remote archivelog file 'luda'
11)on primary db
select name,sequence#,applied from v$archived_log;
NAME SEQUENCE# APP
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00003_0594204176.001 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00004_0594204176.001 4 NO
Luda 4 NO
Luda 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00005_0594204176.001 5 NO
Luda 5 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00006_0594204176.001 6 NO
Luda 6 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00007_0594204176.001 7 NO
Luda 7 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00008_0594204176.001 8 NO
Luda 8 NO
12) on standby db
select name,sequence#,applied from v$archived_log;
NAME SEQUENCE# APP
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00004_0594204176.001 4 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00003_0594204176.001 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00005_0594204176.001 5 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00006_0594204176.001 6 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00007_0594204176.001 7 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00008_0594204176.001 8 NO
13) my init.ora files
On standby db
irina.__db_cache_size=79691776
irina.__java_pool_size=4194304
irina.__large_pool_size=4194304
irina.__shared_pool_size=75497472
irina.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\luda\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\luda\bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\luda\luda.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\luda\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='luda','irina'
*.db_name='irina'
*.db_unique_name='luda'
*.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
*.fal_client='luda'
*.fal_server='irina'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(irina,luda)'
*.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/luda/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=luda'
*.log_archive_dest_2='SERVICE=irina LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=irina'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='C:/oracle/product/10.2.0/oradata/irina/','C:/oracle/product/10.2.0/oradata/luda/'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\luda\udump'
On primary db
irina.__db_cache_size=79691776
irina.__java_pool_size=4194304
irina.__large_pool_size=4194304
irina.__shared_pool_size=75497472
irina.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0/admin/irina/adump'
*.background_dump_dest='C:\oracle\product\10.2.0/admin/irina/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\irina\control01.ctl','C:\oracle\product\10.2.0\oradata\irina\control02.ctl','C:\oracle\product\10.2.0\oradata\irina\control03.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0/admin/irina/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='luda','irina'
*.db_name='irina'
*.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
*.fal_client='irina'
*.fal_server='luda'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(irina,luda)'
*.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/irina/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=irina'
*.log_archive_dest_2='SERVICE=luda LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=luda'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='C:/oracle/product/10.2.0/oradata/luda/','C:/oracle/product/10.2.0/oradata/irina/'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0/admin/irina/udump'
Please help me!!!!Hi,
After several tries my redo logs are applied now. I think in my case it had to do with the tnsnames.ora. At this moment I have both database in both tnsnames.ora files using the SID and not the SERVICE_NAME.
Now I want to use DGMGRL. Adding a configuration and a stand-by database is working fine, but when I try to enable the configuration DGMGRL gives no feedback and it looks like it is hanging. The log, although says that it succeeded.
In another session 'show configuration' results in the following, confirming that the enable succeeded.
DGMGRL> show configuration
Configuration
Name: avhtest
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
avhtest - Primary database
avhtestls53 - Physical standby database
Current status for "avhtest":
Warning: ORA-16610: command 'ENABLE CONFIGURATION' in progress
It there anybody that experienced the same problem and/or knows the solution to this?
With kind regards,
Martin Schaap -
Redo log files are not applying to standby database
Hi everyone!!
I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database. I run the following command on the standby database.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
1. How to resolve this issue ?
2.Is it compulsory to have Primary database open ?
3. I have created standby control file by using command
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should I have different database name for both or existing one is correct ?
Can anybody help me to come out from this stuck ?
Thanks & Regards
Tushar LapaniThank you Girish. It solved my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
I did following scenario.
1. Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
Thanks -
Data Guard. My archive log files are not applied.
I have one problem with Data Guard. My archive log files are not applied. However I have received all archive log files to my physical Standby db
I have created a Physical Standby database on Oracle 10gR2 (Windows XP professional). Primary database is on another computer.
In Enterprise Manager on Primary database it looks ok. I get the following message Data Guard status Normal
But as I wrote above the archive log files are not applied
After I created the Physical Standby database, I have also done:
1. I connected to the Physical Standby database instance.
CONNECT SYS/SYS@luda AS SYSDBA
2. I started the Oracle instance at the Physical Standby database without mounting the database.
STARTUP NOMOUNT PFILE=C:\oracle\product\10.2.0\db_1\database\initluda.ora
3. I mounted the Physical Standby database:
ALTER DATABASE MOUNT STANDBY DATABASE
4. I started redo apply on Physical Standby database
alter database recover managed standby database disconnect from session
5. I switched the log files on Physical Standby database
alter system switch logfile
6. I verified the redo data was received and archived on Physical Standby database
select sequence#, first_time, next_time from v$archived_log order by sequence#
SEQUENCE# FIRST_TIME NEXT_TIME
3 2006-06-27 2006-06-27
4 2006-06-27 2006-06-27
5 2006-06-27 2006-06-27
6 2006-06-27 2006-06-27
7 2006-06-27 2006-06-27
8 2006-06-27 2006-06-27
7. I verified the archived redo log files were applied on Physical Standby database
select sequence#,applied from v$archived_log;
SEQUENCE# APP
4 NO
3 NO
5 NO
6 NO
7 NO
8 NO
8. on Physical Standby database
select * from v$archive_gap;
No rows
9. on Physical Standby database
SELECT MESSAGE FROM V$DATAGUARD_STATUS;
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
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
MRP0: Background Media Recovery terminated with error 1110
MRP0: Background Media Recovery process shutdown
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 2148
RFS[1]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 2384
RFS[2]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 3188
RFS[3]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles created
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 3168
RFS[4]: Identified database type as 'physical standby'
RFS[4]: No standby redo logfiles created
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles created
10. on Physical Standby database
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 1 9 13664 2
RFS IDLE 0 0 0 0
10) on Primary database:
select message from v$dataguard_status;
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
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
ARCm: Becoming the 'no FAL' ARCH
ARCm: Becoming the 'no SRL' ARCH
ARCd: Becoming the heartbeat ARCH
Error 1034 received logging on to the standby
Error 1034 received logging on to the standby
LGWR: Error 1034 creating archivelog file 'luda'
LNS: Failed to archive log 3 thread 1 sequence 7 (1034)
FAL[server, ARCh]: Error 1034 creating remote archivelog file 'luda'
11)on primary db
select name,sequence#,applied from v$archived_log;
NAME SEQUENCE# APP
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00003_0594204176.001 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00004_0594204176.001 4 NO
Luda 4 NO
Luda 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00005_0594204176.001 5 NO
Luda 5 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00006_0594204176.001 6 NO
Luda 6 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00007_0594204176.001 7 NO
Luda 7 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00008_0594204176.001 8 NO
Luda 8 NO
12) on standby db
select name,sequence#,applied from v$archived_log;
NAME SEQUENCE# APP
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00004_0594204176.001 4 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00003_0594204176.001 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00005_0594204176.001 5 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00006_0594204176.001 6 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00007_0594204176.001 7 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00008_0594204176.001 8 NO
13) my init.ora files
On standby db
irina.__db_cache_size=79691776
irina.__java_pool_size=4194304
irina.__large_pool_size=4194304
irina.__shared_pool_size=75497472
irina.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\luda\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\luda\bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\luda\luda.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\luda\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='luda','irina'
*.db_name='irina'
*.db_unique_name='luda'
*.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
*.fal_client='luda'
*.fal_server='irina'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(irina,luda)'
*.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/luda/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=luda'
*.log_archive_dest_2='SERVICE=irina LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=irina'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='C:/oracle/product/10.2.0/oradata/irina/','C:/oracle/product/10.2.0/oradata/luda/'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\luda\udump'
On primary db
irina.__db_cache_size=79691776
irina.__java_pool_size=4194304
irina.__large_pool_size=4194304
irina.__shared_pool_size=75497472
irina.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0/admin/irina/adump'
*.background_dump_dest='C:\oracle\product\10.2.0/admin/irina/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\irina\control01.ctl','C:\oracle\product\10.2.0\oradata\irina\control02.ctl','C:\oracle\product\10.2.0\oradata\irina\control03.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0/admin/irina/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='luda','irina'
*.db_name='irina'
*.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
*.fal_client='irina'
*.fal_server='luda'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(irina,luda)'
*.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/irina/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=irina'
*.log_archive_dest_2='SERVICE=luda LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=luda'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='C:/oracle/product/10.2.0/oradata/luda/','C:/oracle/product/10.2.0/oradata/irina/'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0/admin/irina/udump'
Please help me!!!!Hi,
After several tries my redo logs are applied now. I think in my case it had to do with the tnsnames.ora. At this moment I have both database in both tnsnames.ora files using the SID and not the SERVICE_NAME.
Now I want to use DGMGRL. Adding a configuration and a stand-by database is working fine, but when I try to enable the configuration DGMGRL gives no feedback and it looks like it is hanging. The log, although says that it succeeded.
In another session 'show configuration' results in the following, confirming that the enable succeeded.
DGMGRL> show configuration
Configuration
Name: avhtest
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
avhtest - Primary database
avhtestls53 - Physical standby database
Current status for "avhtest":
Warning: ORA-16610: command 'ENABLE CONFIGURATION' in progress
It there anybody that experienced the same problem and/or knows the solution to this?
With kind regards,
Martin Schaap -
Redo log files are not applied in DR of primary
Hi All,
I have a DR database of primary on QA Serevr. The Redo log files are not properly applied in the DR database.
The Oracle version is 11.2.0.1 Some of the files get shipped and applied to DR database automatically but not all.
SQL> select status, error from v$archive_dest where dest_id=2; gives following massage
ERROR ORA-16086: Redo data cannot be written to the standby redo log
Please suggest.
Regards,
ShashiHi,
Sorry for delay in response. Here I am attaching the error captured in standby database.
Please advise
alert_abc.log
RFS[1780]: Identified database type as 'physical standby': Client is LGWR SYNC pid 21855
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
Standby controlfile consistent with primary
RFS[1780]: No standby redo logfiles of file size 94371840 AND block size 512 exist
Clearing online log 16 of thread 0 sequence number 0
Errors in file /oracle/diag/rdbms/abc_location11/abc/trace/abc_rfs_27994.trc:
ORA-00367: checksum error in log file header
ORA-00315: log 16 of thread 0, wrong thread # 1 in header
ORA-00312: online log 16 thread 0: '/oracle/abc/origlogB/log_g116m1.dbf'
Mon Nov 14 00:49:16 2011
Clearing online log 9 of thread 0 sequence number 0
Errors in file /oracle/diag/rdbms/abc_location11/abc/trace/abc_arc0_15653.trc:
/oracle/diag/rdbms/abc_location11/abc/trace/abc_rfs_27994.trc
2011-11-14 00:49:19.385
DDE rules only execution for: ORA 312
START Event Driven Actions Dump -
END Event Driven Actions Dump -
START DDE Actions Dump -
Executing SYNC actions
START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -
DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, 1 csec) -
Executing ASYNC actions
END DDE Actions Dump (total 0 csec) -
ORA-00367: checksum error in log file header
ORA-00315: log 16 of thread 0, wrong thread # 1 in header
ORA-00312: online log 16 thread 0: '/oracle/abc/origlogB/log_g116m1.dbf'
DDE rules only execution for: ORA 312
START Event Driven Actions Dump -
END Event Driven Actions Dump -
START DDE Actions Dump -
Executing SYNC actions
START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -
DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, -641 csec) -
Executing ASYNC actions
END DDE Actions Dump (total 0 csec) -
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 16 thread 0: '/oracle/abc/origlogB/log_g116m1.dbf'
Error 19527 clearing SRL 16
/oracle/diag/rdbms/abc_location11/abc/trace/abc_arc0_15653.trc
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 9 thread 0: '/oracle/abc/origlogA/log_g19m1.dbf'
Error 19527 clearing SRL 9
DDE rules only execution for: ORA 312
START Event Driven Actions Dump -
END Event Driven Actions Dump -
START DDE Actions Dump -
Executing SYNC actions -
Archive logs are being shipped, but are not applied
Hi everyone,
Some strange things are happening when I try to configure an Oracle Data Guard setup. Currently I am at the point where the configuration has been completed, and I just need to sync the standby database to the primary one. I can see in the log files that the archive logs are being shipped, but they are not applied on the standby system.
If I run "recover standby database;" manually in sqlplus I can see that it is trying to apply an archive log which is way too old (ORA-00279: change 9656498443 generated at 04/29/2008 08:45:08 needed for thread 1).
In the alert log I can also see this error: Warning: Recovery target destination is in a sibling branch of the controlfile checkpoint. Recovery will only recover changes to datafiles.
At this point I was thinking that the standby database might be on a different incarnation compared to the primary, but this is not the case, they are both in incarnation 6:
6 6 MVF 4023175798 CURRENT 48493546257 13-06-21
Does anyone have an idea how this could happen, and how I could fix this issue?
Thanks, JM.The restore did not cause any errors to be displayed, so I assumed everything was ok.
That's fair enough.
One thing I think might cause this behaviour is that the backup on the primary database is incremental,
Yes...that may be an issue. Best bet is to re-run your standby creation.....as you are doing.
With version 11gR2 you also have the option of duplicate from active database which negates the need to copy your backupsets over to do the restore: I find it a much simpler process than the rman backup, copy files over, restore and then recover process.
http://www.oracle-base.com/articles/11g/data-guard-setup-11gr2.php
Something worth considering. -
ORA-326/ORA-334 Physical Standby DB - Not applying logs
Hi, all, I have a Dataguard, the primary db is a RAC with three nodes, the standby db is a physical standby. the dataguard are all oracle 10.2.0.3 on solaris 9 sparc system
Now, my standby db did not apply the archivelogs,there are some errors in standby alert log :
Thu Jan 8 15:44:31 2009
Errors in file /oracle/admin/xxxx/bdump/whut_mrp0_12863.trc:
ORA-00326:log begins at change 2984028173, need earlier change 2984013192
ORA-00334:archived log '+DGARCH/whut/3_22648_611942629.dbf'
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Thu Jan 8 15:44:34 2009
Errors in file /export/home/oracle/admin/whut/bdump/whut_mrp0_12863.trc:
ORA-00326:log begins at change 2984028173, need earlier change 2984013192
ORA-00334:archived log '+DGARCH/whut/3_22648_611942629.dbf'
Thu Jan 8 15:44:34 2009
MRP0: Background Media Recovery process shutdown (whut)
and the archivelogs on the standby db like this :
NAME APP DEL
+DGARCH/whut/3_22651_611942629.dbf NO NO
+DGARCH/whut/3_22650_611942629.dbf NO NO
+DGARCH/whut/3_22649_611942629.dbf NO NO
+DGARCH/whut/3_22648_611942629.dbf NO NO
+DGARCH/whut/3_22648_611942629.dbf NO NO
+DGARCH/whut/3_22648_611942629.dbf NO YES
+DGARCH/whut/3_22291_611942629.dbf YES YES
+DGARCH/whut/2_62553_611942629.dbf NO NO
+DGARCH/whut/2_62552_611942629.dbf NO NO
+DGARCH/whut/2_62551_611942629.dbf NO NO
+DGARCH/whut/2_62550_611942629.dbf NO NO
query the first_change# on the standby db like this :
SEQUENCE# FIRST_CHANGE# APP ARC
22646 2983721221 NO YES
22647 2983911304 NO YES
22648 2984028173 NO YES
23813 2984013365 NO YES
23814 2984118027 NO YES
62546 2984027708 NO YES
SEQUENCE# FIRST_CHANGE# APP ARC
62547 2984163823 NO YES
23815 2984132128 NO YES
23816 2984312713 NO YES
62548 2984255538 NO YES
62549 2984312692 NO YES
22649 2984028196 NO YES
23817 2984351070 NO YES
then ,how to fix the dataguard and apply the archivelog on standby db ?
why I can found 2984028173 with 22648,but can not found 2984013192 ??
and why there have three 22648 with different applied status and deleted status on standby db ???
Thanks all.Thank you for your reply.
the trc file like this:
/oracle/admin/xxx/bdump/xxx_mrp0_12863.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /oracle/product/10.2.0/database
System name: SunOS
Node name: stdb
Release: 5.9
Version: Generic_122300-25
Machine: sun4u
Instance name: xxx
Redo thread mounted by this instance: 1
Oracle process number: 27
Unix process pid: 12863, image: oracle@stdb (MRP0)
*** SERVICE NAME:() 2009-01-08 15:44:24.179
*** SESSION ID:(197.3) 2009-01-08 15:44:24.179
ARCH: Connecting to console port...
*** 2009-01-08 15:44:24.180 61287 kcrr.c
MRP0: Background Managed Standby Recovery process started
*** 2009-01-08 15:44:29.191 1103 krsm.c
Managed Recovery: Initialization posted.
*** 2009-01-08 15:44:29.192 61287 kcrr.c
Managed Standby Recovery starting Real Time Apply
Recovery target incarnation = 5, activation ID = 721050634
Influx buffer limit = 152383 (50% x 304766)
Successfully allocated 3 recovery slaves
Using 367 overflow buffers per recovery slave
Start recovery at thread 3 ckpt scn 2984013192 logseq 22648 block 2
*** 2009-01-08 15:44:31.181
Media Recovery add redo thread 3
*** 2009-01-08 15:44:31.181
Media Recovery add redo thread 1
*** 2009-01-08 15:44:31.182
Media Recovery add redo thread 2
*** 2009-01-08 15:44:31.184 1103 krsm.c
Managed Recovery: Active posted.
*** 2009-01-08 15:44:31.838
Media Recovery Log +DGARCH/whut/3_22648_611942629.dbf
*** 2009-01-08 15:44:31.851 61287 kcrr.c
MRP0: Background Media Recovery terminated with error 326
ORA-00326: log begin at 2984028173, need earlier 2984013192
ORA-00334: archivelog: '+DGARCH/whut/3_22648_611942629.dbf'
*** 2009-01-08 15:44:31.851 61287 kcrr.c
Managed Standby Recovery not using Real Time Apply
*** 2009-01-08 15:44:31.851
Media Recovery drop redo thread 3
*** 2009-01-08 15:44:31.851
Media Recovery drop redo thread 1
*** 2009-01-08 15:44:31.851
Media Recovery drop redo thread 2
*** 2009-01-08 15:44:34.269 1103 krsm.c
Managed Recovery: Not Active posted.
ORA-00326: log begin at 2984028173,need earlier 2984013192
ORA-00334: archivelog: '+DGARCH/whut/3_22648_611942629.dbf'
ARCH: Connecting to console port...
*** 2009-01-08 15:44:34.359 61287 kcrr.c
MRP0: Background Media Recovery process shutdown
*** 2009-01-08 15:44:34.359 1103 krsm.c -
Archive log registered,but showing as not applied in standby db + oracle 9i
Hi all,
In my standby database some of the archive log files are not applied.found through the following command
SQL > select sequence#,applied from v$archived_log where applied='NO';
sequence# APP FIRST_TIME
18425 NO 05-FEB-10
but when try to register manually
SQL > alter database register logfile '/disk12/arch/A00123000018425.arc';
ERROR at line 1
ORA-16089:archive log has already been registered.
"recover standby database" also asking for the new archive file. how will i apply that?
any solutions?user11919409 wrote:
I have did that so many times from 05-feb-10 onwards.
even then only one archive gap???
or only one is not applied? if yes may be archive file which exist at standby may be corrupt try to restore it from backup and recover.
also check for some clues at logs at standby and primary.. what actually happen. if archive gap is huge and you have all archvies then you may have to do manual recovery then keep it back to auto recovery mode.
Hope that may help you.
Anil Malkai -
Archive logs not applied on logical database.
I have 10.2.04 oracle logical dataguard on windows:
The logs are trasported smoothly from primary to stanby;
But they are not applied to the logical standby;
There are no GAPS.
This is the message i got from DG broker wehn i ran verify configuration
Initializing
Connected to instance I-AG1101:tito
Starting alert log monitor...
Updating Data Guard link on database homepage...
Data Protection Settings:
Protection mode : Maximum Performance
Redo Transport Mode settings:
hclistg: ASYNC
hclidg: ASYNC
Checking standby redo log files.....OK
Checking Data Guard status
hclistg : Normal
hclidg : Normal
Checking Inconsistent Properties
Checking agent status
hclistg ... OK
hclidg ... WARNING: No credentials available for target. I-SAG1151
Attempting agent ping ... OK
Switching log file 420.Done
Checking applied log on hclidg.......WARNING:
Timed out after 60 seconds waiting for log to be applied.
Processing completed.
This is the results of query: SELECT SEQUENCE#, FIRST_TIME, APPLIED
FROM DBA_LOGSTDBY_LOG
ORDER BY SEQUENCE#;
SEQUENCE#|FIRST_TIME|APPLIED
391|3/31/2010 1:08:27 PM|CURRENT
392|3/31/2010 3:10:19 PM|NO
393|3/31/2010 3:47:05 PM|NO
394|3/31/2010 3:47:13 PM|NO
395|3/31/2010 3:47:40 PM|NO
396|3/31/2010 3:47:46 PM|NO
397|3/31/2010 3:50:14 PM|NO
398|3/31/2010 3:50:20 PM|NO
399|3/31/2010 3:54:01 PM|NO
400|3/31/2010 3:54:36 PM|NO
401|3/31/2010 3:54:43 PM|NO
402|3/31/2010 3:56:24 PM|NO
403|3/31/2010 3:56:30 PM|NO
404|3/31/2010 4:00:46 PM|NO
405|3/31/2010 4:34:03 PM|NO
406|3/31/2010 4:35:31 PM|NO
407|3/31/2010 5:38:57 PM|NO
408|4/1/2010 7:30:25 AM|NO
409|4/1/2010 11:45:23 AM|NO
410|4/1/2010 11:47:06 AM|NO
411|4/1/2010 2:26:25 PM|NO
412|4/1/2010 2:26:43 PM|NO
413|4/1/2010 2:26:44 PM|NO
414|4/1/2010 2:28:13 PM|NO
415|4/1/2010 5:08:12 PM|NO
416|4/1/2010 5:08:19 PM|NO
417|4/1/2010 5:08:52 PM|NO
418|4/2/2010 10:31:19 AM|NO
419|4/2/2010 10:35:06 AM|NO
420|4/2/2010 11:24:27 AM|NO
Please help,,,i am getting this error when i run alter database mount standby database
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 1610612736 bytes
Fixed Size 1299288 bytes
Variable Size 545262760 bytes
Database Buffers 1056964608 bytes
Redo Buffers 7086080 bytes
SQL> alter database mount standby database;
alter database mount standby database
ERROR at line 1:
ORA-01665: control file is not a standby control file
I configured my logical DG using Grid control -
Hi folks,
Tried creating Data guard for the first time. Was able to successfully create a standby and on every log switch on primary database, a switch is seen on standby too..
But the issue is, log's are not getting applied on standby db..
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination F:\app\product\11.2.0\dbhome_1\RDBMS
Oldest online log sequence 33
Next log sequence to archive 0
Current log sequence 38
SQL> SELECT sequence#, first_time, next_time, applied
2 FROM v$archived_log
3 ORDER BY sequence#;
SEQUENCE# FIRST_TIM NEXT_TIME APPLIED
*16 31-MAY-12 31-MAY-12 NO*
*17 31-MAY-12 31-MAY-12 NO*
*19 31-MAY-12 31-MAY-12 NO*
*20 31-MAY-12 31-MAY-12 NO*
*28 31-MAY-12 31-MAY-12 NO*
*29 31-MAY-12 31-MAY-12 NO*
*32 31-MAY-12 31-MAY-12 NO*
*34 31-MAY-12 31-MAY-12 NO*
*36 31-MAY-12 31-MAY-12 NO*
*37 31-MAY-12 31-MAY-12 NO*
*38 31-MAY-12 31-MAY-12 NO*
11 rows selected.
Also the alert log on strandby show's as...
Alert log on standby:
Thu May 31 23:30:43 2012
RFS[18]: Assigned to RFS process 3380
RFS[18]: Identified database type as 'physical standby': Client is ARCH pid 5780
RFS[18]: Selected log 4 for thread 1 sequence 36 dbid 196575176 branch 784736843
Thu May 31 23:30:45 2012
Archived Log entry 9 added for thread 1 sequence 36 ID 0xbb7cbc8 dest 1:
Thu May 31 23:30:45 2012
RFS[19]: Assigned to RFS process 4968
RFS[19]: Identified database type as 'physical standby': Client is LGWR ASYNC pid 5072
Primary database is in MAXIMUM PERFORMANCE mode
RFS[19]: Selected log 4 for thread 1 sequence 37 dbid 196575176 branch 784736843
Thu May 31 23:30:46 2012
RFS[20]: Assigned to RFS process 4996
RFS[20]: Identified database type as 'physical standby': Client is ARCH pid 5192
Thu May 31 23:30:47 2012
Archived Log entry 10 added for thread 1 sequence 37 ID 0xbb7cbc8 dest 1:
RFS[19]: Selected log 4 for thread 1 sequence 38 dbid 196575176 branch 784736843
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001 (162 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4996.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4996.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:30:48 2012
RFS[21]: Assigned to RFS process 4508
RFS[21]: Identified database type as 'physical standby': Client is ARCH pid 5780
Thu May 31 23:30:48 2012
RFS[22]: Assigned to RFS process 1524
RFS[22]: Identified database type as 'physical standby': Client is ARCH pid 5308
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001 (198 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4508.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4508.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001 (17296 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_1524.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_1524.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:30:51 2012
RFS[23]: Assigned to RFS process 460
RFS[23]: Identified database type as 'physical standby': Client is ARCH pid 5192
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001 (65 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_460.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_460.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:30:52 2012
RFS[24]: Assigned to RFS process 3456
RFS[24]: Identified database type as 'physical standby': Client is ARCH pid 5780
Thu May 31 23:30:52 2012
RFS[25]: Assigned to RFS process 1936
RFS[25]: Identified database type as 'physical standby': Client is ARCH pid 5308
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001 (287 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3456.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3456.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001 (10 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_1936.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_1936.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:30:56 2012
RFS[26]: Assigned to RFS process 5084
RFS[26]: Identified database type as 'physical standby': Client is ARCH pid 5192
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001 (193 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_5084.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_5084.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:30:57 2012
RFS[27]: Assigned to RFS process 2404
RFS[27]: Identified database type as 'physical standby': Client is ARCH pid 5780
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001 (8 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_2404.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_2404.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:36:48 2012
RFS[28]: Assigned to RFS process 2988
RFS[28]: Identified database type as 'physical standby': Client is ARCH pid 5192
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001 (162 blocks)
Thu May 31 23:36:49 2012
RFS[29]: Assigned to RFS process 4152
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_2988.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
RFS[29]: Identified database type as 'physical standby': Client is ARCH pid 5308
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_2988.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000010_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:36:49 2012
RFS[30]: Assigned to RFS process 4128
RFS[30]: Identified database type as 'physical standby': Client is ARCH pid 5780
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001 (198 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4128.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4128.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000009_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001 (17296 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4152.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4152.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000008_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:36:51 2012
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_arc2_5596.trc:
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000038_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
ARC2: Error 19504 Creating archive log file to 'F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000038_0784736843.0001'
ARCH: Archival stopped, error occurred. Will continue retrying
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_arc2_5596.trc:
ORA-16038: log 4 sequence# 38 cannot be archived
ORA-19504: failed to create file ""
ORA-00312: online log 4 thread 1: 'F:\APP\ORADATA\STAN\SRL01.LOG'
Thu May 31 23:36:53 2012
RFS[31]: Assigned to RFS process 4340
RFS[31]: Identified database type as 'physical standby': Client is ARCH pid 5192
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001 (65 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4340.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_4340.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000011_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:36:54 2012
RFS[32]: Assigned to RFS process 3080
RFS[32]: Identified database type as 'physical standby': Client is ARCH pid 5780
Thu May 31 23:36:54 2012
RFS[33]: Assigned to RFS process 3296
RFS[33]: Identified database type as 'physical standby': Client is ARCH pid 5308
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001 (287 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3080.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3080.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000012_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001 (10 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3296.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3296.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000013_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:36:55 2012
RFS[34]: Assigned to RFS process 3464
RFS[34]: Identified database type as 'physical standby': Client is ARCH pid 5192
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001 (193 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3464.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_3464.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000014_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:36:57 2012
RFS[35]: Assigned to RFS process 6036
RFS[35]: Identified database type as 'physical standby': Client is ARCH pid 5780
Creating archive destination file : F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001 (8 blocks)
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_6036.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file f:\app\diag\rdbms\stan\stan\trace\stan_rfs_6036.trc:
ORA-00270: error creating archive log F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001
ORA-19504: failed to create file "F:\APP\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000000015_0784736843.0001"
ORA-27056: could not delete file
OSD-04024: Unable to delete file.
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Thu May 31 23:37:09 2012
Archived Log entry 11 added for thread 1 sequence 38 ID 0xbb7cbc8 dest 1:
Archiver process freed from errors. No longer stopped
confirmed that there is enough space and proper permission on the folder's..
someone please suggest what could have gone wrong??
Regards!Hello again;
So I both servers log_archive_dest_1 is not set?
The Oracle example is
Primary
LOG_ARCHIVE_DEST_1= 'LOCATION=/arch1/chicago/VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=chicago'
Standby
LOG_ARCHIVE_DEST_1='LOCATION=/arch1/boston/VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=boston'
If a fast recovery area was configured (with the DB_RECOVERY_FILE_ DEST initialization parameter) and you have not explicitly configured a local archiving destination with the LOCATION attribute, Data Guard automatically
uses the LOG_ARCHIVE_DEST_1 initialization parameter (if it has not already been set) as the default destination for local archiving. Also, see Chapter 15 for complete LOG_ARCHIVE_DEST_n information.
My take is since you are not using FRA this parameter is not defined by default. I would probably set it on both, but frankly I'm not sure this will solve your issue. If it does I would sure like to know about it so i can add it to my notes.
Not related to your issue
Would consider setting standby_file_management to 'Auto' on both.
Would consider setting log_archive_dest_state_2 to 'DEFER' on the Standby.
Best Regards
mseberg
Would -
Logs not applying on Standby Database
I am afraid I am back.
I now have a primary database and a standby database and logs are being shipped but not applied. Done some research and I have got to the point where in my alert log I find the following when I try to start MRP:
Fri Jun 29 15:03:40 2012
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (SAPDS)
Fri Jun 29 15:03:40 2012
MRP0 started with pid=29, OS id=23272
MRP0: Background Managed Standby Recovery process started (SAPDS)
started logmerger process
Fri Jun 29 15:03:45 2012
Managed Standby Recovery not using Real Time Apply
Read of datafile '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf' (fno 2) header failed with ORA-01206
Rereading datafile 2 header failed with ORA-01206
MRP0: Background Media Recovery terminated with error 1110
Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_pr00_23308.trc:
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: file is not part of this database - wrong database id
Recovery Slave PR00 previously exited with exception 1110
Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_mrp0_23272.trc:
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: file is not part of this database - wrong database id
MRP0: Background Media Recovery process shutdown (SAPDS)
Completed: alter database recover managed standby database disconnect from session
My question therefore is how can I get out of this and get my logs to apply on standby?Hello again;
Do you think if I tried to repeat the duplicate?
Yes I think you should do this.
Give me a few minutes and I will review my Word document and provide a step by step overview here as insurance.
I always cleanup the standby before trying another dup
OVERVIEW
Step 1 - Password file fro standby - Copy from primary and rename
Step 2 - Directory Structure on the remote server - Make sure noting is missing
Step 3 - Oracle Net Setup - entry for the CLONE in your TNSNAMES.ORA on both servers
Step 4 - SID_LIST_LISTENER addition ( assumes listener named LISTENER )
Step 5 - Timeouts set in listener.ora and sqlnet.ora Both Servers
Step 6 - Initialization Parameter File for the Auxiliary Instance
Step 7 - Set SID for Auxiliary Instance
Step 8 - Create an SPFILE for the new database by using a pfile with the INIT settings
Step 9 - Shutdown and startup nomount on new Spfile ( Auxiliary Instance )
Step 10 - Start RMAN and run the DUPLICATE Command
SID_LIST_LISTENER Example from mine
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
(PROGRAM = extproc)
(SID_DESC =
(global_dbname = CLONE.hostname)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
(sid_name = CLONE)
Prevent Timeouts
Add these to both servers
To listener.ora
INBOUND_CONNECT_TIMEOUT_ = 120
To sqlnet.ora
SQLNET.INBOUND_CONNECT_TIMEOUT = 120
Then stop and start the listener.
RMAN
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
Connect should return something like this
connected to target database: RECOVER9 (DBID=3806912436)
connected to auxiliary database: CLONE (not mounted)RMAN>duplicate target database for standby from active database NOFILENAMECHECK;
INIT Extras
To avoid ORA-09925 make sure the PFILE has audit_file_dest and core_dump_dest set
Best Regards
mseberg
Edited by: mseberg on Jun 29, 2012 11:12 AM -
Hi,
We have dataguard on Oracle 10g. The logs are shipped from primary to physical stand by but when I look at "Last Applied Log" under EM on the primary db, I see 0. The logs are shipping but not applied to physical stand by.
I restarted the standby to mount stage.
I can tnsping both the database from other servers
***** on primary *****
SELECT name, value FROM gv$parameter WHERE name = 'log_archive_dest_state_1';
NAME
VALUE
log_archive_dest_state_1
enable
SELECT name, value FROM gv$parameter WHERE name = 'log_archive_dest_state_2';
NAME
VALUE
log_archive_dest_state_2
ENABLE
SELECT name, value FROM gv$parameter WHERE name = 'standby_archive_dest';
NAME
VALUE
standby_archive_dest
select status, error from v$archive_dest where dest_id=2;
STATUS ERROR
VALID
select switchover_status from v$database;
SWITCHOVER_STATUS
SESSIONS ACTIVE
select protection_mode, protection_level, database_role from v$database;
PROTECTION_MODE PROTECTION_LEVEL DATABASE_ROLE
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE PRIMARY
SELECT MAX(SEQUENCE#), THREAD# FROM V$ARCHIVED_LOG GROUP BY THREAD#;
MAX(SEQUENCE#) THREAD#
4483 1
SELECT dest_id, valid_type, valid_role, valid_now FROM gv$archive_dest;
DEST_ID VALID_TYPE VALID_ROLE VALID_NOW
1 ONLINE_LOGFILE ALL_ROLES YES
2 ONLINE_LOGFILE PRIMARY_ROLE YES
***** on physical stand by *****
select protection_mode, protection_level, database_role from v$database;
PROTECTION_MODE PROTECTION_LEVEL DATABASE_ROLE
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE PHYSICAL STANDBY
SELECT MAX(SEQUENCE#), THREAD# FROM V$ARCHIVED_LOG GROUP BY THREAD#;
MAX(SEQUENCE#) THREAD#
4483 1
Can anyone advise what can I check and how can I get the logs to apply on the standy by. The stand by is in mount stage. ThanksThe alert log for primary does not show any errors:
LNS: Standby redo logfile selected for thread 1 sequence 4520 for destination LOG_ARCHIVE_DEST_2
This is in the alert log for standby
Primary database is in MAXIMUM PERFORMANCE mode
RFS[11]: Successfully opened standby log 5: '/u02/oradata/prd1/stby_redo_g5_m1.dbf'
On standby I have the MRP process running:
$ ps -ef|grep mrp
oracle 10957 1 0 15:26:48 ? 0:01 ora_mrp0_prd1
SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS WHERE DEST_ID=2 ;
RECOVERY_MODE
MANAGED REAL TIME APPLY
This is from v$dataguard_status
Remote File Server Warning 0 167 0 NO 20-DEC-07
RFS[11]: Successfully opened standby log 5: '/u02/oradata/prd1/stby_redo_g5_m1.dbf'
should I try this as first suggested ?
alter database recover managed standby database parallel 2 using current logfile disconnect; -
Standby not applying the online redo logs
Hi,
The redo apply process does not seem to apply the current logs to the standby database.
The output from the query
Select last_change#, sequence# from v$standby_log;
LAST_CHANGE# GROUP# SEQUENCE#
4 0
10120537 5 8586
6 0
7 0
gives me the current SCN as that of the primary.
But the CURRENT_SCN from v$database on the standby lags from that of the output above.
Select CURRENT_SCN from v$database;
CURRENT_SCN
10119641
The STATUS and PROCESS information from the v$managed_standby show the following:
PROCESS STATUS SEQUENCE#
ARCH CONNECTED 0
ARCH CONNECTED 0
ARCH CONNECTED 0
ARCH CONNECTED 0
RFS IDLE 0
RFS IDLE 0
RFS IDLE 8586
RFS IDLE 0
RFS IDLE 0
RFS IDLE 0
RFS IDLE 0
PROCESS STATUS SEQUENCE#
MRP0 APPLYING_LOG 8586
Any thoughts on why the standby has not applied the recived logs from the primary?
I am currently using version Oracle 11.2.0.2 for Active dataguard setup. I currently have a primary server and one standy server.
ThanksI had sent the output of the queries in the earlier post. Here it is again
The output for the query
select thread#, max(sequence#) from v$archived_log group by thread#; (on primary)
THREAD# MAX(SEQUENCE#)
1 8585
The output for
select thread#, max(sequence#) from v$archived_log where applied = 'YES' group by thread#; (on standby)
THREAD# MAX(SEQUENCE#)
1 8585
Also the query
select LAST_CHANGE#, STATUS from V$STANDBY_LOG;
gives me the current scn generated at the primary.
LAST_CHANGE# STATUS
10149990 ACTIVE
10146538 ACTIVE
10150844 ACTIVE
But the current_scn from v$database is lagging.
select current_scn from v$database;
CURRENT_SCN
10146535
Also the query
select THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# from v$archive_gap;
returns no rows. So there are no archive logs missing on the standby either.
So I beleive that the RFS has recieved the logs from the primary but the logs have not been applied at the standby.
Thanks -
All logs received but not applied | Physical Standby Database
All,
Need your help....
We have physical standby database setup as below
Primary : 2 node RAC
Stdby : Standalone physical standby database.
When I verify the stdby database status, I could see all the logs are received from primary but still not applied many.. Could any one please help me what is the issue and how to resolve it ...?
Primary :
=====
SQL> SELECT THREAD# "Thread",SEQUENCE# "Last Sequence Generated"
FROM V$ARCHIVED_LOG
WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)
ORDER BY 1 2 3 4 ;
Thread Last Sequence Generated
1 8073
1 8073
2 4521
2 4521
stdby:
====
SQL> SELECT ARCH.THREAD# "Thread",
2 ARCH.SEQUENCE# "Last Sequence Received",
3 APPL.SEQUENCE# "Last Sequence Applied",
4 (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
5 FROM
6 (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN
7 (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
8 (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN
(SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
9 10 WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;
Thread Last Sequence Received Last Sequence Applied Difference
1 8073 8055 18
2 4521 4510 11
--Below are tailed messages from standby alert log:
Fri Nov 04 10:45:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 10:50:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 10:50:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 10:50:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 10:55:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 11:00:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 11:00:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 11:00:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 11:05:16 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 11:05:16 2011
Archiver process freed from errors. No longer stoppedPrimary:
=====
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ASM_FRA01
Oldest online log sequence 8073
Next log sequence to archive 8074
Current log sequence 8074
SQL>
Stdby:
=====
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination ?/dbs/arch
Oldest online log sequence 8074
Next log sequence to archive 0
Current log sequence 8074
Enough space is available :
=================
SQL> set lines 180 pages 50000;
SQL> set lines 100
col name format a60
select name
, floor(space_limit / 1024 / 1024) "Size MB"
, ceil(space_used / 1024 / 1024) "Used MB"
from v$recovery_file_dest
order by nameSQL> SQL> 2 3 4 5 ;
NAME Size MB Used MB
+ASM_FRA01 70000 531
Edited by: 889828 on 2011/11/04 2:26 AM -
Standby database is not applying redo logs due to missing archive log
We use 9.2.0.7 Oracle Database. My goal is to create a physical standby database.
I have followed all the steps necessary to fulfill this in Oracle Data Guard Concepts and Administration manual. Archived redo logs are transmitted from primary to standby database regularly. But the logs are not applied due to archive log gap.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
MRP0 WAIT_FOR_GAP
RFS RECEIVING
RFS ATTACHED
SQL> select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 503 677
I have tried to find the missing archives on the primary database, but was unable to. They have been deleted (somehow) regularly by the existing backup policy on the primary database. I have looked up the backups, but these archive logs are too old to be in the backup. Backup retention policy is 1 redundant backup of each file. I didn't save older backups as I didn't really need them from up to this point.
I have cross checked (using rman crosscheck) the archive log copies on the primary database and deleted the "obsolete" copies of archive logs. But, v$archived_log view on the primary database only marked those entries as "deleted". Unfortunately, the standby database is still waiting for those logs to "close the gap" and doesn't apply the redo logs at all. I am reluctant to recreate the control file on the primary database as I'm afraid this occurred through the regular database backup operations, due to current backup retention policy and it probably might happen again.
The standby creation procedure was done by using the data files from 3 days ago. The archive logs which are "producing the gap" are older than a month, and are probably unneeded for standby recovery.
What shall I do?
Kind regards and thanks in advance,
MilivojOn a physical standby database
To determine if there is an archive gap on your physical standby database, query the V$ARCHIVE_GAP view as shown in the following example:
SQL> SELECT * FROM V$ARCHIVE_GAP;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 7 10
The output from the previous example indicates your physical standby database is currently missing log files from sequence 7 to sequence 10 for thread 1.
After you identify the gap, issue the following SQL statement on the primary database to locate the archived redo log files on your primary
database (assuming the local archive destination on the primary database is LOG_ARCHIVE_DEST_1):
SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 2> SEQUENCE# BETWEEN 7 AND 10;
NAME
/primary/thread1_dest/arcr_1_7.arc /primary/thread1_dest/arcr_1_8.arc /primary/thread1_dest/arcr_1_9.arc
Copy these log files to your physical standby database and register them using the ALTER DATABASE REGISTER LOGFILE statement on your physical standby database. For example:
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_7.arc';
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_8.arc';
After you register these log files on the physical standby database, you can restart Redo Apply.
Note:
The V$ARCHIVE_GAP fixed view on a physical standby database only returns the next gap that is currently blocking Redo Apply from continuing. After resolving the gap and starting Redo Apply, query the V$ARCHIVE_GAP fixed view again on the physical standby database to determine the next gap sequence, if there is one. Repeat this process until there are no more gaps.
Restoring the archived logs from the backup set
If the archived logs are not available in the archive destination then at that time we need to restore the required archived logs from the backup step. This task is accomplished in the following way.
To restore range specified archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore'
Restore archivelog from logseq=<xxxxx> until logseq=<xxxxxxx>
To restore all the archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore';
Restore archivelog all;
}
Maybe you are looking for
-
New mac mini audio out through usb
Do any of you know what is the output i would get if i connect my mac mini to my hifi stereo to playback my songs that are 24bit 96khz, can i get that resolution out?
-
Hi, On selection screen i have to display 4 select-options and 2 checkboxes. My requirement is as soon as i enter into selection screen out of 4 select-options it should display only 2 and rest should be hidden and if i check the below checkboxes th
-
Portal integration with Business Objects
Hi, I have a customer who is looking for Oracle portal solution. They have an sso in place using Business Objects and they also have Active Directory for storing user information. They just want to login to Portal through SSO and access their Busines
-
Erro while executing adobe forms in webdynpro
Hi , Please help me in resolving the following issue while running the adobe form in webdynpro for java on sneakpreview java.lang.exception:incorect content type found "text/html" thanks
-
Hi All, I created "user1" by copying "user2". Now "user2" is loging and doing all its job bt when i login with "user1" i get follwoing error - com.sap.lcr.api.cimclient.LcrException: com.sap.lcr.api.cimclient.CIMClientException: HTTP response code: 4