RE: Archived logs in wrong destination with 2-node RAC
- From: "Harel Safra" <harel.safra@xxxxxxxxx>
- To: <daniel.hubler@xxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 28 Jul 2010 20:41:37 +0300
When you shut down the instance you don't disable the redo thread it's
writing.
One of the other instances will archive redo logs from that thread in some
situations, I have seen it happen when the active instance has wrapped
around all its' redo logs.
For this reason and faster recovery considerations I like to use a central,
shared, location as an archive log destination for all the instances. In our
case it's a NetApp volume in NFS.
Harel Safra
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of daniel.hubler@xxxxxxxxxx
Sent: Wednesday, July 28, 2010 8:23 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Archived logs in wrong destination with 2-node RAC
Oracle 10.2.0.3
AIX 5.3.8.3 + HACMP 5.4.1
2-node RAC
Archived log file systems are defined to the local node only; but failover
via HACMP.
When we shutdown the database instance on node-2,
(not CRS....just the DB),
an archive log file is generated from that instance (node-2),
but shows up in the archive log destination on node-1.
Happens every time.
Does not happen to archived logs that are generated via normal operations,
or even a "alter system switch logfile".
Not a new installation.
Is a test environment where we turned on archive logging not too long ago.
Not certain why that archive log is showing up in the other/incorrect side.
Any ideas?
Other related posts:
