Quantcast
Channel: SCN : Popular Discussions - SAP on Oracle
Viewing all articles
Browse latest Browse all 810

select max(sequence#) from v$archived_log where applied='YES' showd differn

$
0
0

Background :

We have Primary Server is in one town & We have Disaster Recovery Server in another town connected over 2MB MPLS.

Recently we have done "DB Reprganizations, during that time archive logs were created in huge as we aware, and due to archive directory space constraint, We backedup files and deleted immediately from primary.

 

Now Reorganizations completed - and manually we restoring archive files in DISASTER RECOVERY SITE and trying to recover Standby Database as below in DR Site:

 

-


1) lsnrctl start

2) sqlplus "/ as sysdba"

3) startup nomount;

4) alter database mount standby database;

5) recover standby database;

-


as soon as i issed command 5, Recovery started with Option "AUTO" as belo

 

-


ORA-00279: change 12324727338 generated at 11/21/2010 14:37:29 needed for

thread 1

ORA-00289: suggestion : /oracle/P10/oraarch/P10arch1_886187_638666197.dbf

ORA-00280: change 12324727338 for thread 1 is in sequence #886187

ORA-00278: log file '/oracle/P10/oraarch/P10arch1_886186_638666197.dbf' no

longer needed for this recovery

 

 

ORA-00279: change 12324728068 generated at 11/21/2010 14:37:38 needed for

thread 1

ORA-00289: suggestion : /oracle/P10/oraarch/P10arch1_886188_638666197.dbf

ORA-00280: change 12324728068 for thread 1 is in sequence #886188

ORA-00278: log file '/oracle/P10/oraarch/P10arch1_886187_638666197.dbf' no

longer needed for this recovery

 

 

ORA-00279: change 12324728652 generated at 11/21/2010 14:37:48 needed for

thread 1

ORA-00289: suggestion : /oracle/P10/oraarch/P10arch1_886189_638666197.dbf

ORA-00280: change 12324728652 for thread 1 is in sequence #886189

ORA-00278: log file '/oracle/P10/oraarch/P10arch1_886188_638666197.dbf' no

longer needed for this recovery

 

 

ORA-00279: change 12324728953 generated at 11/21/2010 14:37:57 needed for

thread 1

ORA-00289: suggestion : /oracle/P10/oraarch/P10arch1_886190_638666197.dbf

ORA-00280: change 12324728953 for thread 1 is in sequence #886190

ORA-00278: log file '/oracle/P10/oraarch/P10arch1_886189_638666197.dbf' no

longer needed for this recovery

 

 

ORA-00308: cannot open archived log

'/oracle/P10/oraarch/P10arch1_886190_638666197.dbf'

ORA-27037: unable to obtain file status

IBM AIX RISC System/6000 Error: 2: No such file or directory

Additional information: 3

 

 

SQL>

-


 

if you see above screen shot

the db is recovered still archive log sequense Number : 886189 (P10arch1_886189_638666197.dbf').

 

So understanding DB is recovered till 886189.

But when i issue command at SQL prmpt as below

 

SQL> select max(sequence#) from v$archived_log where applied='YES';

 

MAX(SEQUENCE#)

-


        885116

 

SQL>

-


 

I am failing understand , even thought it is recoverd till 886189 , Why it is showing still 885116.

This observation we did for 1 day, when we try to recover with command it is recovering,

But applied shows the same.

 

-


 

We request to post their view / comments - Why this applied Sequence Number is differ than applied ?Rgds

PR

 

 

###########################################################################

GENERAL INFORMATION - BEGINING

###########################################################################

 

====================================================

To bring standby database into managed recovery mode

====================================================

1) Telnet to DRSERVER as root

2) lsnrctl start

3) sqlplus "/ as sysdba"   as ora<sid>

4) startup nomount;

5) alter database mount standby database;

6) recover managed standby database disconnect;

7) exit

 

 

====================================================

TO RECOVER MANUALLY

====================================================

1) Telnet to DRSERVER as root

2) lsnrctl start

3) sqlplus "/ as sysdba"    as "ora<sid>

4) startup nomount;

5) alter database mount standby database;

6) recover standby database;

7) recover managed standby database disconnect; 

          (after recovery completed & to put into MRM Mode)

8) exit

====================================================

 

 

====================================================

TO CHECK APPLIED ARCHIVE LOGS

====================================================

SQL> select max(sequence#) from v$archived_log where applied='YES';

 

###########################################################################

GENERAL INFORMATION - END

 


Viewing all articles
Browse latest Browse all 810

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>