Database - RAC/Scalability (MOSC)

MOSC Banner

why the archived log of thread 1 was sometimes generated under the archive destination of thread 2 ?

edited Sep 27, 2015 12:21AM in Database - RAC/Scalability (MOSC) 4 commentsAnswered

Our environment is a 2-node RAC, sometimes I find that the information of archiving redolog of thread 1 is recorded in alert.log of thread 2.

For example,following information can be seen from the thread 2's alert.log :

Tue Aug 18 03:28:17 2015

Archived Log entry 343061 added for thread 1 sequence 202057 ID 0x24c8e4e9 dest 1

And the archived log which has sequence #202057 is created under the archive destination of thread 2.

---query on v$archived_log : thread#!=ARCHIVAL_THREAD#

select sequence#,thread#,archival_thread# from v$archived_log where creator='FGRD' and thread#=1

SEQUENCE# THREAD# ARCHIVAL_THREAD#

--------------- -------- --------------------

202057 1 2

Any document or URLs which can explain this behaviour? I have spent much time to search on the web but did not get any valueable findings.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center