Capture stuck at certain sequence redo log which doesn't belong to the database
Capture log (ocap log) indicated :
ocap 2009-05-20 18:35:46.259885 4418 4078537616 Block zero has seqno 223, should be 159
This can happen in environments which have a single ASM instance handling multiple Oracle instances.
The query which is used to map the ASM path of the online redolog uses only the final redolog file name to get the Group and File number which fails to uniquely map the redolog file to ASM's Group/File number if there are multiple instances using the same redolog filenames.
WORKAROUND 1:
Rename the redo logs to an unique name accross all instances.
example: old entry: redo_01.log / new entry: redo_<SID>_01.log
WORKAROUND 2:
Move the redo logs to an OMF managed filesystem
WORKAROUND 3:
Move the redo logs to a non-ASM filesystem
STATUS: Fixed in Version 7.0.1.
