Oracle Dataguard: data block corruption on SYSAUX
edited Jan 25, 2010 1:54AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 1 commentAnswered
Hello All,
i recently found this under the alert logs on our logical standby db running 10.2.0.4.0 release 2:
**************************************************************************************************** ***
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 3341, \LSTDBY1\STREDO05.LOG
Thu Jan 21 09:53:45 2010
LOGMINER: Begin mining logfile for session 1 thread 2 sequence 3229, \LSTDBY1\STREDO09.LOG
LOGSTDBY Apply process P008 started with pid=67 OS id=3840
LOGSTDBY Apply process P006 started with pid=65 OS id=3620
LOGSTDBY Apply process P005 started with pid=64 OS id=3624
LOGSTDBY Analyzer process P003 started with pid=58 OS id=3632
LOGSTDBY Apply process P007 started with pid=66 OS id=3612
LOGSTDBY Apply process P004 started with pid=63 OS id=3628
Thu Jan 21 09:57:17 2010
Redo Shipping Client Connected as PUBLIC
i recently found this under the alert logs on our logical standby db running 10.2.0.4.0 release 2:
**************************************************************************************************** ***
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 3341, \LSTDBY1\STREDO05.LOG
Thu Jan 21 09:53:45 2010
LOGMINER: Begin mining logfile for session 1 thread 2 sequence 3229, \LSTDBY1\STREDO09.LOG
LOGSTDBY Apply process P008 started with pid=67 OS id=3840
LOGSTDBY Apply process P006 started with pid=65 OS id=3620
LOGSTDBY Apply process P005 started with pid=64 OS id=3624
LOGSTDBY Analyzer process P003 started with pid=58 OS id=3632
LOGSTDBY Apply process P007 started with pid=66 OS id=3612
LOGSTDBY Apply process P004 started with pid=63 OS id=3628
Thu Jan 21 09:57:17 2010
Redo Shipping Client Connected as PUBLIC
0