| urgent:dataguard unable to apply logs [message #137956] |
Mon, 19 September 2005 01:41  |
lallmanish
Messages: 28
Registered: September 2005
|
Junior Member |
|
|
hi
i am a dba and i had created an oracle dataguard 10G a month ago.
everything was running properly till there was complete trip at
the production site. i had again restarted the databases-
and saw that:
select max(sequence#) from v$archived_log is the same in both the
production and the standby. there was no archive gaps in the standby and i could see all the archive logs available in the standby.
but as i run
sql> alter sequence#,applied from v$ARCHIVED_LOG WHERE
APPLIED ='NO';
I COULD SEE THERE THAT THERE ARE A LOT OF ARCHIVES SINCE THE DATE AND TIME TRIP OCCURED THAT HAS NOT BEEN APPLIED I TRIED TO MAKE A MEDIA RECOVERY- SO IT SAID THAT DATABASE NOT IN MEDIA
RECOVERY MODE. I AGAIN ISSUED
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEWST_STATE_3=DEFER;-- IN THE PRODUCTION
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;-- IN THE PRODUCTION
THEN ON THE STANDBY I ISSUED THE FOLLOWING STATEMENTS:
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
SQL> RECOVER MANAGED STANDBY DATABASE CANCEL;
media recovery complete.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING
CURRENT LOGFILE DISCONNECT;
SQL> SELECT PROCESS,STATUS FROM V$MANAGED_STANDBY;
PROCESS STATUS
--------- ------------
ARCH CONNECTED
ARCH CLOSING
MRP0 APPLYING LOG
RFS RECEIVING
RFS RECEIVING
RFS WRITING
THE AGAIN I ISSUED SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
WHERE APPLIED='NO';
I COULD SEE THAT TWO OF THE FILES WERE APPLIED.
I AGAIN TRIED TO REPEAT THE ENTIRE PROCESS WITH A MEDIA
RECOVERY BUT NO NOE OF THE ARCHIVES ARE APPLYING.
ALSO AFTER I RECEIVED MRP0--APPLYING LOG
AND FEW MINUTES LATER I COULD SEE THAT THE SAME
STATEMENT :SELECT STATUS,PROCESS FROM V$MANAGED_STANDBY;
IS NOT SHOWING MRP0:
PROCESS STATUS
--------- ------------
ARCH CONNECTED
ARCH CLOSING
RFS RECEIVING
RFS RECEIVING
RFS WRITING
AGAIN I ISSUED ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT- I COULD AGAIN SEE THE MRP0.
TWO MINUTES LATER THE SAME MRP0 GOES OUT OF THE LIST.
I AM WORRIED ABOUT WHAT TO DO.
DATABASE IS RUNNING IN MAXIMUM AVAILABILITY.
PLLZ
HELP ME ON IMMEDIATE BASIS
MANISH
|
|
|
|
|
|
| Re: urgent:dataguard unable to apply logs [message #230352 is a reply to message #230227] |
Wed, 11 April 2007 11:33  |
harshad.gohil
Messages: 157
Registered: April 2007
Location: USA
|
Senior Member |
|
|
Hi,
Have you tried to register your logfiles manually on standby site. If not mount your database on recover standby database mode, get the list of non applied archived log, start with the oldest one and register 3 or 4 archive log manually. After that defer again and restart your standby database.
Syntax to register manually archive logs.
ALTER DATABASE REGISTER LOGFILE '<archive destination with archive file>';
Let me know if you have any concerns.
Regards,
Harsh
|
|
|
|
| Re: urgent:dataguard unable to apply logs [message #231208 is a reply to message #230352] |
Mon, 16 April 2007 00:18 |
raj_t_menon
Messages: 8
Registered: November 2006
Location: Ahmedabad
|
Junior Member |
|
|
Harshad ,
I have followed the steps, that you have suggested-
SQL> select SEQUENCE# , ARCHIVED,APPLIED from v$archived_log;
SEQUENCE# ARC APP
---------- --- ---
83 YES YES
84 YES YES
85 YES YES
86 YES YES
87 YES YES
88 YES NO
89 YES NO
90 YES NO
91 YES NO
92 YES NO
93 YES NO
SEQUENCE# ARC APP
---------- --- ---
94 YES NO
95 YES NO
96 YES NO
97 YES NO
98 YES NO
99 YES NO
100 YES NO
18 rows selected.
Shutdown ..
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 252777712 bytes
Fixed Size 451824 bytes
Variable Size 218103808 bytes
Database Buffers 33554432 bytes
Redo Buffers 667648 bytes
SQL> alter database mount standby database;
Database altered.
SQL> alter database register logfile'/oracle/admin/mudra4/arch/arch_88.arc';
alter database register logfile'/oracle/admin/mudra4/arch/arch_88.arc'
*
ERROR at line 1:
ORA-16089: archive log has already been registered
SQL> alter database register logfile'/oracle/admin/mudra4/arch/arch_89.arc';
alter database register logfile'/oracle/admin/mudra4/arch/arch_89.arc'
*
ERROR at line 1:
ORA-16089: archive log has already been registered
SQL> alter database register logfile'/oracle/admin/mudra4/arch/arch_90.arc';
alter database register logfile'/oracle/admin/mudra4/arch/arch_90.arc'
*
ERROR at line 1:
ORA-16089: archive log has already been registered
===============================================================
This is the value for log_archive_dest_2 So i have selected the
Maximum Performance Mode with
Redo Archival Process-ARCH
Disk Write Option-NOAFFIRM
Standby Database Type-PHYSICAL
and this error is also repeating for me-
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_2 string service=stby4 ARCH NOAFFIRM
===============================================================
/oracle/admin/mudra4/bdump/stby4_qmn0_9932.trc
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
ORACLE_HOME = /oracle/product/9.2.0.4.0
System name: Linux
Node name: earsmcpl
Release: 2.6.5-7.244-bigsmp
Version: #1 SMP Mon Dec 12 18:32:25 UTC 2005
Machine: i686
Instance name: stby4
Redo thread mounted by this instance: 1
Oracle process number: 16
Unix process pid: 9932, image: oracle@earsmcpl (QMN0)
*** SESSION ID:(15.260) 2007-04-13 04:13:11.121
kwqitmmsgs: error 604
error 604 detected in background process
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-00604: error occurred at recursive SQL level 1
ORA-16000: database open for read-only access
|
|
|
|
|
|
|
|
|
|
|
|
| Re: urgent:dataguard unable to apply logs [message #235230 is a reply to message #232189] |
Fri, 04 May 2007 07:21 |
sriram717
Messages: 48
Registered: February 2007
Location: UNITED KINGDOM
|
Member |
|
|
Hi
You are using the realtime apply feature which means that
If ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE is fired to enable
the real-time apply feature , log apply services apply redo data as it is received, without waiting for the current standby redo log file to be archived.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
