Archive logs are not transferred to STDBY database

Hi,
I have create a STDBY database (I am running the release 9.2.0.7.0).
I see that the archivelogs are not correctly transferred into STDBY server.
From Primary alert log, I see the following error:
ARC1: Evaluating archive log 1 thread 1 sequence 16734
ARC1: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
ARC1: Beginning to archive log 1 thread 1 sequence 16734
Creating archive destination LOG_ARCHIVE_DEST_1: '/backup/archivelogs/log1_16734.arc'
ARC1: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 16734 host STDBY_PROD
ARC1: Completed archiving log 1 thread 1 sequence 16734
Thu Nov 17 14:54:42 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-03114: not connected to ORACLE
Thu Nov 17 14:54:42 2011
ARC0: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
Thu Nov 17 14:54:42 2011
ORACLE Instance PROD - Archival Error. Archiver continuing.
ARCH: Connecting to console port...
Thu Nov 17 14:54:42 2011
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
Thu Nov 17 14:54:42 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-16055: FAL request rejected
ARC0: Begin FAL archive (thread 1 sequence 16483 destination STDBY_PROD)
Creating archive destination LOG_ARCHIVE_DEST_2: 'STDBY_PROD'
Thu Nov 17 15:05:44 2011
LGWR: I/O error 3114 archiving log 2 to 'STDBY_PROD'
Thu Nov 17 15:05:44 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_lgwr_5265.trc:
ORA-03114: not connected to ORACLE
Thu Nov 17 15:10:08 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-03114: not connected to ORACLE
Thu Nov 17 15:10:08 2011
ARC0: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
Thu Nov 17 15:10:08 2011
ORACLE Instance PROD - Archival Error. Archiver continuing.
ARCH: Connecting to console port...
Thu Nov 17 15:10:08 2011
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
Thu Nov 17 15:10:08 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-16055: FAL request rejected
I see that both archiving destinations are VALID:
SQL> select dest_id, dest_name, status from v$archive_dest_status where status != 'INACTIVE';
DEST_ID ---------- DEST_NAME -------------------------------------------------------------------------------- STATUS
1 LOG_ARCHIVE_DEST_1 VALID
2 LOG_ARCHIVE_DEST_2 VALID
SQL>
TNSPING works properly in both directions, e.g. from PROD -> STDBY:
$tnsping STDBY_PROD
TNS Ping Utility for Linux: Version 9.2.0.7.0 - Production on 17-NOV-2011 16:56:40
Copyright (c) 1997 Oracle Corporation. All rights reserved.
Used parameter files:
/mnt/orclEBS/oracle/proddb/9.2.0/network/admin/PROD_ebslive/sqlnet_ifile.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp) (HOST=EBSSTDBY) (PORT=1521)) (CONNECT_DATA=(SID=PROD)))
OK (10 msec)
Please help me to solve this issue.
Thank you.

A few notes :
Troubleshooting Tips For Dataguard Switchover (9i and 10gR1) [ID 298986.1]
Although it is about Switchover, it does mandate a password file exclusive. If the switchover requires the password file, shouldn't ARCH shipping require it ?
Step By Step Guide To Create Physical Standby Database Using RMAN [ID 469493.1]
also covers 9i with specific mentions of 9i differences from 10g. Passwordfile is not mentioned as different in 9i from 10g.
Data Guard 9i - Net8 Configuration for a 2-node database environment. [ID 175122.1
has log_archive_dest_2='SERVICE=NODE2STDBY.ACME.COM' so it connects to the service
*However* the document "Introduction to Oracle 9i Data Guard Manager" from
Data Guard 9i Introduction to Data Guard Manager GUI [ID 150217.1]
page 59 has this : "The creation process will attempt to create a remote login password file for the standby database to
enable remote connections to the database. (Note: A remote login password file is not necessary for
Data Guard operation; it is only needed to allow remote connections to the database from clients,
such as other Enterprise Manager tools.)"
Similarly the section "3.2.6 Set Initialization Parameters on a Physical Standby Database"
in the 9i DataGuard manual at http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/create_ps.htm#62941
only has
remote_archive_enable=TRUE
(this is an instance parameter)
Similarly the section "5.8.2.1 Primary Database Initialization Parameters"
at http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/log_transport.htm#1067609
explains
The last parameter, REMOTE_ARCHIVE_ENABLE=SEND, allows the primary database to send redo data to the standby database, but prevents the primary database from receiving redo data from another system.
with REMOTE_ARCHIVE_ENABLE=RECEIVE on the Standby
to Receive and archive the incoming redo data from the primary database, but only while the database is running in the standby role
So, I guess that REMOTE_ARCHIVE_ENABLE is the important one. Not REMOTE_LOGIN_PASSWORDFILE.
In 9i : http://download.oracle.com/docs/cd/B10501_01/server.920/a96536/ch1174.htm#1023087
In 10g it is deprecated : http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams176.htm#sthref541 so that LOG_ARCHIVE_CONFIG is used.
(and no longer appears in the 11.2 Reference)
Hemant K Chitale

Similar Messages

Archive logs are not transferring to DR server in DataGuard

Dear Gurus,
We have implemented data guard on 10g and it was working properly till last week.All of a sudden it is stopped working and i am getting the error in primary server alert log as
"ORA-12154: TNS:could not resolve the connect identifier specified
PING[ARCr]: Heartbeat failed to connect to standby 'STANDRR1'"
and the trace file entries are as follows
" Error 12154 received logging on to the standby,Error 12154 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'STANDRR1',Error 12154 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'STANDRR1',ORA-12154: TNS:could not resolve the connect identifier specified".
We have changed nothing on either side of the servers.
Please suggest how to resolve the issue and Thanks in advance.
Thanks & Regards,
venkat

Hi,
The output from standby,
lsnrctl servicesLSNRCTL for HPUX: Version 10.2.0.4.0 - Production on 04-FEB-2012 15:50:20
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=PP1.WORLD))
Services Summary...
Service "RR1" has 1 instance(s).
Instance "RR1", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
The command completed successfully.
The output of tnsping from standby:
tnsping STANDPP1
TNS Ping Utility for HPUX: Version 10.2.0.4.0 - Production on 04-FEB-2012 15:50:
56
Copyright (c) 1997, 2007, Oracle. All rights reserved.
Used parameter files:
/oracle/RR1/102_64/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP
.WORLD) (PROTOCOL = TCP) (HOST = pildrprd) (PORT = 1527))) (CONNECT_DATA = (SID
= RR1) (GLOBAL_NAME = RR1.WORLD)))
OK (10 msec)
The output of tnsping from primary:
tnsping STANDPP1
TNS Ping Utility for HPUX: Version 10.2.0.4.0 - Production on 04-FEB-2012 15:55:
59
Copyright (c) 1997, 2007, Oracle. All rights reserved.
Used parameter files:
/oracle/PP1/102_64/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP
.WORLD) (PROTOCOL = TCP) (HOST = pildrprd) (PORT = 1527))) (CONNECT_DATA = (SID
= RR1) (GLOBAL_NAME = RR1.WORLD)))
OK (30 msec).
Still i am getting the error.Please suggest.

Archived log files not registered in the Database

I have Widows Server 2008 R2
I have Oracle 11g R2
I configured primary and standby database in 2 physical servers , please find below the verification:
I am using DG Broker
Renetly I did failover from primary to standby database
Then I did REINSTATE DATABASE to returen the old primary to standby mode
Then I did Switchover again
I have problem that archive logs not registered and not imeplemented.
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
         16234
I did alter system switch logfile then I ssue the following statment to check and I found same number in primary and stanbyd has not been changed
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
         16234
Any body can help please?
Regards

Thanks for reply
What I mean after I do alter system switch log file, I can see the archived log files is generated in the physical Disk but when
select MAX(SEQUENCE#) FROM V$ARCHIVED_LOG;
the sequence number not changed it should increase by 1 when ever I do switch logfile.
however I did as you asked please find the result below:
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> SELECT DB_NAME,HOSTNAME,LOG_ARCHIVED,LOG_APPLIED_02,LOG_APPLIED_03,APPLIED_TIME,LOG_ARCHIVED - LOG_APPLIED_02 LOG_GAP_02,
2 LOG_ARCHIVED - LOG_APPLIED_03 LOG_GAP_03
3 FROM (SELECT NAME DB_NAME FROM V$DATABASE),
4 (SELECT UPPER(SUBSTR(HOST_NAME, 1, (DECODE(INSTR(HOST_NAME, '.'),0, LENGTH(HOST_NAME),(INSTR(HOST_NAME, '.') - 1))))) HOSTNAME FROM V$INSTANCE),
5 (SELECT MAX(SEQUENCE#) LOG_ARCHIVED FROM V$ARCHIVED_LOG WHERE DEST_ID = 1 AND ARCHIVED = 'YES'),
6 (SELECT MAX(SEQUENCE#) LOG_APPLIED_02 FROM V$ARCHIVED_LOG WHERE DEST_ID = 2 AND APPLIED = 'YES'),
7 (SELECT MAX(SEQUENCE#) LOG_APPLIED_03 FROM V$ARCHIVED_LOG WHERE DEST_ID = 3 AND APPLIED = 'YES'),
8 (SELECT TO_CHAR(MAX(COMPLETION_TIME), 'DD-MON/HH24:MI') APPLIED_TIME FROM V$ARCHIVED_LOG WHERE DEST_ID = 2 AND APPLIED = 'YES');
DB_NAME HOSTNAME           LOG_ARCHIVED   LOG_APPLIED_02    LOG_APPLIED_03     APPLIED_TIME     LOG_GAP_02      LOG_GAP_03
EPPROD CORSKMBBOR01     16252                  16253                        (null)                      15-JAN/12:04                  -1                   (       null)

Generate archive logs are not in sequence number?

On last friday... the latest archive log number was ARC00024.ARC. Tomorrow when I come backup, the archive logs ARC00001.ARC and ARC00002.ARC were being generated by oracle itself. I wondering the archive log sequence should be in sequence. What is happening?
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination C:\oracle\ora92\RDBMS
Oldest online log sequence 1
Next log sequence to archive 3
Current log sequence 3
SQL>
FAN
Edited by: user623471 on Jun 7, 2009 7:35 PM

khurram,
Its our production instance and havent issued resetlogs option but when listing the arvchives it shows in different sequence number...
and also while copying the archives by RMAN it doesnt copy in sequence
-rw-r----- 1 xxx dba 69363859 May 28 19:16 2_10373.arc.gz
-rw-r----- 1 xxx dba 43446622 May 28 19:16 1_10553.arc.gz
-rw-r----- 1 xxx dba 52587365 May 28 19:16 1_10578.arc.gz
-rw-r----- 1 xxx dba 45251820 May 28 19:16 1_10543.arc.gz
-rw-r----- 1 xxx dba 60890256 May 28 19:17 1_10579.arc.gz
-rw-r----- 1 xxx dba 46659008 May 28 19:17 1_10548.arc.gz
-rw-r----- 1 xxx dba 116899466 May 28 19:17 2_10353.arc.gz
-rw-r----- 1 xxx dba 77769517 May 28 19:17 1_10531.arc.gz
-rw-r----- 1 xxx dba 66401923 May 28 19:18 1_10530.arc.gz
-rw-r----- 1 xxx dba 45972697 May 28 19:18 1_10605.arc.gz
-rw-r----- 1 xxx dba 55082543 May 28 19:18 1_10600.arc.gz
-rw-r----- 1 xxxq dba 42682207 May 28 19:19 1_10547.arc.gz
thanks,
baskar.l

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 Lapani

Thank 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

Logs are not getting applied in the standby database

Hello,
I have created a physical standby database and in it the logs are not getting applied..
following is an extract of the standby alert log
Wed Sep 05 07:53:59 2012
Media Recovery Log /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
Error opening /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
Attempting refetch
Media Recovery Waiting for thread 1 sequence 37638
Fetching gap sequence in thread 1, gap sequence 37638-37643
Wed Sep 05 07:53:59 2012
RFS[46]: Assigned to RFS process 3081
RFS[46]: Allowing overwrite of partial archivelog for thread 1 sequence 37638
RFS[46]: Opened log for thread 1 sequence *37638* dbid 1723205832 branch 765704228
Wed Sep 05 07:55:34 2012
RFS[42]: Possible network disconnect with primary database
However, the archived files are getting copied to the standby server.
I tried registering and recovering the logs but it also failed..
Follows some of the information,
Primary
Oralce 11R2 EE
SQL> select max(sequence#) from v$log where archived='YES';
MAX(SEQUENCE#)
37668
SQL> select DEST_NAME, RECOVERY_MODE,DESTINATION,ARCHIVED_SEQ#,APPLIED_SEQ#, SYNCHRONIZATION_STATUS,SYNCHRONIZED,GAP_STATUS from v$archive_dest_status where DEST_NAME = 'LOG_ARCHIVE_DEST_3';
DEST_NAME RECOVERY_MODE DESTINATION ARCHIVED_SEQ# APPLIED_SEQ# SYNCHRONIZATION_STATUS SYNCHRONIZED GAP_STATUS
LOG_ARCHIVE_DEST_3 MANAGED REAL TIME APPLY ABC 37356 0 CHECK CONFIGURATION NO RESOLVABLE GAP
Standby
Oralce 11R2 EE
SQL> select max(sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
37637
SQL> select * from v$archive_gap;
no rows selected
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
READ ONLY WITH APPLY PHYSICAL STANDBY
Please help me to troubleshoot this and get the standby in sync..
Thanks a lot..

the results are as follows..
SQL> select process, status, group#, thread#, sequence# from v$managed_standby order by process, group#, thread#, sequence#;
PROCESS STATUS GROUP# THREAD# SEQUENCE#
ARCH CLOSING 1 1 37644
ARCH CLOSING 1 1 37659
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
MRP0 WAIT_FOR_GAP N/A 1 37638
RFS IDLE N/A 0 0
RFS IDLE N/A 0 0
RFS IDLE N/A 0 0
RFS RECEIVING N/A 1 37638
RFS RECEIVING N/A 1 37639
RFS RECEIVING N/A 1 37640
RFS RECEIVING N/A 1 37641
RFS RECEIVING N/A 1 37642
RFS RECEIVING N/A 1 37655
RFS RECEIVING N/A 1 37673
RFS RECEIVING N/A 1 37675
42 rows selected.
SQL>
SQL> select name,value, time_computed from v$dataguard_stats;
NAME VALUE TIME_COMPUTED
transport lag +00 02:44:33 09/05/2012 09:25:58
apply lag +00 03:14:30 09/05/2012 09:25:58
apply finish time +00 00:01:09.974 09/05/2012 09:25:58
estimated startup time 12 09/05/2012 09:25:58
SQL> select timestamp , facility, dest_id, message_num, error_code, message from v$dataguard_status order by timestamp
TIMESTAMP FACILITY DEST_ID MESSAGE_NUM ERROR_CODE MESSAGE
05-SEP-12 Remote File Server 0 60 0 RFS[13]: Assigned to RFS process 2792
05-SEP-12 Remote File Server 0 59 0 RFS[12]: Assigned to RFS process 2790
05-SEP-12 Log Apply Services 0 61 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 62 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 63 0 Managed Standby Recovery Canceled
05-SEP-12 Log Apply Services 0 64 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 65 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 66 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 67 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 68 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 69 0 RFS[5]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 70 0 RFS[6]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 71 0 RFS[14]: Assigned to RFS process 2829
05-SEP-12 Remote File Server 0 72 0 RFS[15]: Assigned to RFS process 2831
05-SEP-12 Network Services 0 73 0 RFS[9]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 74 0 RFS[16]: Assigned to RFS process 2833
05-SEP-12 Network Services 0 75 0 RFS[1]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 76 0 RFS[17]: Assigned to RFS process 2837
05-SEP-12 Network Services 0 77 0 RFS[3]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 78 0 RFS[2]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 79 0 RFS[7]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 80 0 RFS[18]: Assigned to RFS process 2848
05-SEP-12 Network Services 0 81 0 RFS[16]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 82 0 RFS[19]: Assigned to RFS process 2886
05-SEP-12 Network Services 0 83 0 RFS[19]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 84 0 RFS[20]: Assigned to RFS process 2894
05-SEP-12 Log Apply Services 0 85 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 86 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 87 0 Managed Standby Recovery Canceled
05-SEP-12 Remote File Server 0 89 0 RFS[22]: Assigned to RFS process 2900
05-SEP-12 Remote File Server 0 88 0 RFS[21]: Assigned to RFS process 2898
05-SEP-12 Remote File Server 0 90 0 RFS[23]: Assigned to RFS process 2902
05-SEP-12 Remote File Server 0 91 0 Primary database is in MAXIMUM PERFORMANCE mode
05-SEP-12 Remote File Server 0 92 0 RFS[24]: Assigned to RFS process 2904
05-SEP-12 Remote File Server 0 93 0 RFS[25]: Assigned to RFS process 2906
05-SEP-12 Log Apply Services 0 94 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 95 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 96 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 97 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Log Transport Services 0 98 0 ARCa: Beginning to archive thread 1 sequence 37644 (7911979302-7912040568)
05-SEP-12 Log Transport Services 0 99 0 ARCa: Completed archiving thread 1 sequence 37644 (0-0)
05-SEP-12 Network Services 0 100 0 RFS[8]: Possible network disconnect with primary database
05-SEP-12 Log Apply Services 0 101 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 102 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 103 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 104 0 Managed Standby Recovery Canceled
05-SEP-12 Network Services 0 105 0 RFS[20]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 106 0 RFS[26]: Assigned to RFS process 2930
05-SEP-12 Network Services 0 107 0 RFS[24]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 108 0 RFS[27]: Assigned to RFS process 2938
05-SEP-12 Network Services 0 109 0 RFS[14]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 110 0 RFS[28]: Assigned to RFS process 2942
05-SEP-12 Network Services 0 111 0 RFS[15]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 112 0 RFS[29]: Assigned to RFS process 2986
05-SEP-12 Network Services 0 113 0 RFS[17]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 114 0 RFS[30]: Assigned to RFS process 2988
05-SEP-12 Log Apply Services 0 115 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 116 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 117 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 118 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 119 0 RFS[18]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 120 0 RFS[31]: Assigned to RFS process 3003
05-SEP-12 Network Services 0 121 0 RFS[26]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 122 0 RFS[32]: Assigned to RFS process 3005
05-SEP-12 Network Services 0 123 0 RFS[27]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 124 0 RFS[33]: Assigned to RFS process 3009
05-SEP-12 Remote File Server 0 125 0 RFS[34]: Assigned to RFS process 3012
05-SEP-12 Log Apply Services 0 127 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 126 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 128 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 129 0 Managed Standby Recovery Canceled
05-SEP-12 Network Services 0 130 0 RFS[32]: Possible network disconnect with primary database
05-SEP-12 Log Apply Services 0 131 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 132 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 133 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 134 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 135 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 136 0 RFS[33]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 137 0 RFS[35]: Assigned to RFS process 3033
05-SEP-12 Log Apply Services 0 138 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 139 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 140 0 Managed Standby Recovery Canceled
05-SEP-12 Remote File Server 0 141 0 RFS[36]: Assigned to RFS process 3047
05-SEP-12 Log Apply Services 0 142 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 143 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 144 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 145 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 146 0 RFS[35]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 147 0 RFS[37]: Assigned to RFS process 3061
05-SEP-12 Network Services 0 148 0 RFS[36]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 149 0 RFS[38]: Assigned to RFS process 3063
05-SEP-12 Remote File Server 0 150 0 RFS[39]: Assigned to RFS process 3065
05-SEP-12 Network Services 0 151 0 RFS[25]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 152 0 RFS[21]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 153 0 Archivelog record exists, but no file is found
05-SEP-12 Remote File Server 0 154 0 RFS[40]: Assigned to RFS process 3067
05-SEP-12 Network Services 0 155 0 RFS[37]: Possible network disconnect with primary database

What order are Archive logs restored in when RMAN recover database issued

Ok, you have a run block that has restored your level-0 RMAN backup.
Your base datafiles are down on disc.
You are about to start recovery to point in time, lets say until this morning at 07:00am.
run { set until time "TO_DATE('2010/06/08_07:00:00','YYYY/MM/DD_HH24:MI:SS')";
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
recover database;
So the above runs, it analyses the earlies SCN required for recovery, checks for incremental backups (none here), works out the archivelog range
required and starts to restore the archive logs. All as expected and works.
My question: Is there a particular order that RMAN will restore the archive logs and is the restore / recover process implemented as per the run block.
i.e Will all required archive logs based on the run block be restored and then the database recovered forward. Or is there something in RMAN that says restore these archive logs, ok now roll forwards, restore some more.
When we were doing this the order of the archive logs coming back seemed to be random but obviously constrained by the run block. Is this an area we need to tune to get recoveries faster for situations where incrementals are not available?
Any inputs on experience welcome. I am now drilling into the documentation for any references there.
Thanks

Hi there, thanks for the response I checked this and here are the numbers / time stamps on an example:
This is from interpreting the list backup of archivelog commands.
Backupset = 122672
==============
Archive log sequence 120688 low time: 25th May 15:53:07 next time: 25th May 15:57:54
Piece1 pieceNumber=123368 9th June 04:10:38 <-- catalogued by us.
Piece2 pieceNumber=122673 25th May 16:05:18 <-- Original backup on production.
Backupset = 122677
==============
Archive log sequence 120683 low time: 25th May 15:27:50 Next time 25th May 15:32:24 <-- lower sequence number restored after above.
Piece1 PieceNumber=123372 9th June 04:11:34 <-- Catalogued by us.
Piece2 PieceNumber=122678 25th May 16:08:45 <-- Orignial backup on Production.
So the above would show that if catalogue command you could influence the Piece numbering. Therefore the restore order if like you say piece number is the key. I will need to review production as to why they were backed up in different order completed on production. Would think they would use the backupset numbering and then piece within the set / availability.
Question: You mention archive logs are restored and applied and deleted in batches if the volume of archivelogs is large enough to be spread over multiple backup sets. What determines the batches in terms of size / number?
Thanks for inputs. Answers some questions.

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.

Export and Import are not supported on 10g databases for users logged

Hi
I having the below written error, when i want to export or import my database. I having Standalone system using windows xp.
Role Error - Export and Import are not supported on 10g databases for users logged in with the SYSDBA role. Logout and login using a different role before trying again.

Actually i ma new to EM...
When I want to Import any thing He is asking abt the HOST CREDENTIALS
I can't undrstatnd wht he is asking????
Host Credentials
* Username
* Password
          Save as Preferred Credential
It Genrate the below error
Error - ERROR: Wrong password for user

EMERGENCY: List of files in Recovery Area not managed by the database

Hi,
this is an emergency request....
I have this data guard set up. And i accidently dropped online redo logs, standby logs and the archive log except the current online redolog.
i actually ran to cleanup the whole directory which included the controlfile and the datafiles (was on the wrong location on ASM)
but the controlfile and the datafiles did not get deleted. i can still see them on the ASM.
and now when i am trying to restore the archive logs, but i keep getting error as shown below...
WARNING: A file of type ARCHIVED LOG may exist in
db_recovery_file_dest that is not known to the database.
Use the RMAN command CATALOG RECOVERY AREA to re-catalog
any such files. This is most likely the result of a crash
during file creation.
so when i did the below i was getting error as:
RMAN> CATALOG RECOVERY AREA;
using target database control file instead of recovery catalog
searching for all files in the recovery area
no files found to be unknown to the database
List of files in Recovery Area not managed by the database
==========================================================
File Name: +DATA/afcpdg/controlfile/controlfile01.ctl
RMAN-07526: Reason: File is not an Oracle Managed File
File Name: +DATA/afcpdg/onlinelog/group_1.304.718194815
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
number of files not managed by recovery area is 82, totaling 168.10GB
But i do see those data files that RMAN is complaining as shown above in the ASM.
I HOPE I DID NOT MESS UP THE CONTROLFILE and the DATFILES
CAN SOMEONE HELP ME FIX THIS MISTAKE THAT I DID.
Right now the data guard is running fine, the logs are getting shipped from primary and the getting applied at the DG.
And i am able to see all the redo logs got deleted.
But not sure how the deleted redo logs got created in the ASM (i did not create them manually)
Thanks.
Philip.
Edited by: user8898644 on May 5, 2010 8:52 AM
Edited by: user8898644 on May 5, 2010 9:16 AM
Edited by: user8898644 on May 5, 2010 11:43 AM

Yes this happened on the standby database.
I had to restore the archive logs because i deleted all the archive logs which got shipped from the primary.
I did re-create the standby logs. But when i checked back the redo logs that i deleted came back again.
I have no idea how they can back again. is it a feature of ASM where a mirrored copy of the files are stored on ASM and they re-create them when accidently dropped.
Can you help me understand how the redologs got created again automatically.
Right now the data guard is running fine but i do see the error
WARNING: A file of type ARCHIVED LOG may exist in
db_recovery_file_dest that is not known to the database.
Use the RMAN command CATALOG RECOVERY AREA to re-catalog
any such files. This is most likely the result of a crash
during file creation.
and when i do the following
RMAN> catalog recovery area;
i do see errors as below...
List of files in Recovery Area not managed by the database
==========================================================
File Name: +DATA/afcpdg/controlfile/controlfile01.ctl
RMAN-07526: Reason: File is not an Oracle Managed File
File Name: +DATA/afcpdg/onlinelog/group_1.304.718194815
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
File Name: +DATA/afcpdg/onlinelog/group_2.372.718194833
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
File Name: +DATA/afcpdg/datafile/system.596.715610261
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
File Name: +DATA/afcpdg/datafile/undotbs1.571.715603525
number of files not managed by recovery area is 82, totaling 168.10GB
we do have the db_create_file_dest and db_recovery_file_dest pointing to the same location as +DATA
How do i fix the above error?
Thanks in advance.

Archive logs are missing in hot backup

Hi All,
We are using the following commands to take hot backup of our database. Hot backup is fired by "backup" user on Linux system.
=======================
rman target / nocatalog <<EOF
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$backup_dir/$date/%F';
run {
allocate channel oem_backup_disk1 type disk format '$backup_dir/$date/%U';
#--Switch archive logs for all threads
sql 'alter system archive log current';
backup as COMPRESSED BACKUPSET database include current controlfile;
#--Switch archive logs for all threads
sql 'alter system archive log current';
#--Backup Archive logs and delete what we've backedup
backup as COMPRESSED BACKUPSET archivelog all not backed up delete all input;
release channel oem_backup_disk1;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
exit
EOF
=======================
Due to which after command (used 2 times) "sql 'alter system archive log current';" I see the following lines in alert log 2 times. Because of this all the online logs are not getting archived (Missing 2 logs per day), the backup taken is unusable when restoring. I am worried about this. I there any to avoid this situation.
=======================
Errors in file /u01/oracle/admin/rac/udump/rac1_ora_3546.trc:
ORA-19504: failed to create file "+DATA/rac/1_32309_632680691.dbf"
ORA-17502: ksfdcre:4 Failed to create file +DATA/rac/1_32309_632680691.dbf
ORA-15055: unable to connect to ASM instance
ORA-01031: insufficient privileges
=======================
Regards,
Kunal.

All thanks you for help, pleas find additional information. I goth the following error as log sequence was missing. Everyday during hotbackup, there are 2 missing archive logs, which makes our backup inconsistent and useless.
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32531_632680691.dbf thread=1 sequence=32531
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28768_632680691.dbf thread=2 sequence=28768
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28769_632680691.dbf thread=2 sequence=28769
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28770_632680691.dbf thread=2 sequence=28770
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32532_632680691.dbf thread=1 sequence=32532
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28771_632680691.dbf thread=2 sequence=28771
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28772
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28773
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/13/2012 04:22:56
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
ORA-00310: archived log contains sequence 28772; sequence 28773 required
ORA-00334: archived log: '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
Let me try the susggestions provided above.

How to determine which archive logs are needed in flashback.

Hi,
Let's assume I have archive logs 1,2,3,4, then a "backup database plus archivelogs" in RMAN, and then archive logs 5+6. If I want to flashback my database to a point immediately after the backup, how do I determine which archive logs are needed?
I would assume I'd only need archive logs 5 and/or 6 since I did a full backup plus archivelogs and the database would have been checkpointed at that time. I'd also assume archive logs 1,2,3,4 would be obsolete as they would have been flushed to the datafiles in the checkpoint.
Are my assumptions correct? If not what queries can I run to determine what files are needed for a flashback using the latest checkpointed datafiles?
Thanks.

Thanks for the explanation, let me be more specific with my problem.
I am trying to do a flashback on a failed primary database, the only reason why I want to do a flashback is because dataguard uses the flashback command to try and synchronize the failed database. Specifically dataguard is trying to run:
FLASHBACK DATABASE TO SCN 865984
But it fails, if I run it manually then I get:
SQL> FLASHBACK DATABASE TO SCN 865984;
FLASHBACK DATABASE TO SCN 865984
ERROR at line 1:
ORA-38754: FLASHBACK DATABASE not started; required redo log is not available
ORA-38761: redo log sequence 5 in thread 1, incarnation 3 could not be accessed
Looking at the last checkpoint I see:
CHECKPOINT_CHANGE#
865857
Also looking at the archive logs:
RECID STAMP THREAD# SEQUENCE# FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# RESETLOGS_CHANGE# RESETLOGS
25 766838550 1 1 863888 10-NOV-11 863892 863888 10-NOV-11
26 766838867 1 2 863892 10-NOV-11 864133 863888 10-NOV-11
27 766839225 1 3 864133 10-NOV-11 864289 863888 10-NOV-11
28 766839340 1 4 864289 10-NOV-11 864336 863888 10-NOV-11
29 766840698 1 5 864336 10-NOV-11 865640 863888 10-NOV-11
30 766841128 1 6 865640 10-NOV-11 865833 863888 10-NOV-11
31 766841168 1 7 865833 10-NOV-11 865857 863888 10-NOV-11
How can I determine what archive logs are needed by a flashback command? I deleted any archive logs with a SCN less than the checkpoint #, I can restore them from backup but I am trying to figure out how to query what is required for a flashback. Maybe this coincides with the point that flashbacks have nothing to do with the backups of datafiles or the checkpoints?

How can I turn off archive logs are being generated by system? (ugrent)

Dear all,
How can I turn off archive logs are being generated by system?
Best Regards,
Amy

Sorry not to you @kamran its to OP.accidently it reply button pressed for you
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size                   787988 bytes
Variable Size             145750508 bytes
Database Buffers           25165824 bytes
Redo Buffers                 262144 bytes
Database mounted.
SQL> alter database noarchivelog
2 /
Database altered.
SQL> Khurram

ORA-00339: archived log does not contain any redo

Hi All,
recently we faced 'ORA-00339: archived log does not contain any redo' issue at standby side,
after searching on Google and from Metalink (note 30866.1 and 7197445.8 ) I find out that this is the known issue for 10g and below versions, our's is 11.2.0.3,
Error in Alert Log :
Errors in file /oracle/ora_home/diag/diag/rdbms/dwprd/DWPRD/trace/DWPRD_pr0a_48412.trc:
ORA-00339: archived log does not contain any redo
ORA-00334: archived log: '/redolog2/redo/redolog3a.log'
Errors in file /oracle/ora_home/diag/diag/rdbms/dwprd/DWPRD/trace/DWPRD_pr0a_48412.trc (incident=190009):
ORA-00600: internal error code, arguments: [kdBlkCheckError], [1], [56702], [6114], [], [], [], [], [], [], [], []
Incident details in: /oracle/ora_home/diag/diag/rdbms/dwprd/DWPRD/incident/incdir_190009/DWPRD_pr0a_48412_i190009.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Slave exiting with ORA-10562 exception
Errors in file /oracle/ora_home/diag/diag/rdbms/dwprd/DWPRD/trace/DWPRD_pr0a_48412.trc:
ORA-10562: Error occurred while applying redo to data block (file# 1, block# 56702)
ORA-10564: tablespace SYSTEM
ORA-01110: data file 1: '/oradata1/database/DATAFILES/system01.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 2
ORA-00600: internal error code, arguments: [kdBlkCheckError], [1], [56702], [6114], [], [], [], [], [], [], [], []
Mon Apr 15 11:34:12 2013
Dumping diagnostic data in directory=[cdmp_20130415113412], requested by (instance=1, osid=48412 (PR0A)), summary=[incident=190009].
Thanks

Hi,
"The archived log is not the correct log.
It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log."
"Restore the correct log file."
Can you say, what is last changes on your database, On log files?
Did you copies your '/redolog2/redo/redolog3a.log' log file from other ?
Regards
Mahir M. Quluzade

Need to copy archive log file "arch1_601.dbf" when restore database?

Hi all,
I have the following case:
1) Full hot backup today (Feb-12-2009) in directory /u03/db/backup
2) But ongoing archive log are generated in directory /u02/oracle/uat/uatdb/9.2.0/dbs
3) I need to restore database becuase some data files are missing.
4) Use today ful backup to restore
5) Am I need to copy all archive log files in /u02/oracle/uat/uatdb/9.2.0/dbs to /u03/db/backup because "/u03/db/backup/RMAN" is restore directory?
FAN

Here is backup scripts:
Run
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u02/db/backup/RMAN/%F.bck';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
allocate channel ch1 type disk format '/u02/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup incremental level 1 cumulative database plus archivelog delete all input;
backup current controlfile;
backup spfile;
release channel ch1;
allocate channel for maintenance type disk;
delete noprompt obsolete;
delete noprompt archivelog all backed up 2 times to disk;

Archive logs are not transferred to STDBY database

Similar Messages

Maybe you are looking for