|
-
Oracle Dataguard: data block corruption on SYSAUX
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, D:\LSTDBY1\STREDO05.LOG
Thu Jan 21 09:53:45 2010
LOGMINER: Begin mining logfile for session 1 thread 2 sequence 3229, D:\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
-- Connected User is Valid
RFS[1]: Assigned to RFS process 3108
RFS[1]: Identified database type as 'logical standby'
Thu Jan 21 09:57:17 2010
RFS LogMiner: Client enabled and ready for notification
RFS[1]: Successfully opened standby log 7: 'D:\LSTDBY1\STREDO07.LOG'
Thu Jan 21 09:57:19 2010
RFS LogMiner: Client enabled and ready for notification
Thu Jan 21 09:57:29 2010
RFS LogMiner: Registered logfile [D:\LSTDBY1\STD\1_3354_698506430.ARC] to LogMiner session id [1]
Thu Jan 21 10:06:35 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 2340
RFS[2]: Identified database type as 'logical standby'
Thu Jan 21 10:06:35 2010
RFS LogMiner: Client enabled and ready for notification
RFS[2]: Successfully opened standby log 10: 'D:\LSTDBY1\STREDO10.LOG'
Thu Jan 21 10:06:37 2010
RFS LogMiner: Client enabled and ready for notification
Thu Jan 21 10:06:45 2010
RFS LogMiner: Registered logfile [D:\LSTDBY1\STD\2_3242_698506430.ARC] to LogMiner session id [1]
Thu Jan 21 10:07:19 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 3964
RFS[3]: Identified database type as 'logical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Thu Jan 21 10:07:19 2010
RFS LogMiner: Client enabled and ready for notification
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 7: 'D:\LSTDBY1\STREDO07.LOG'
Thu Jan 21 10:07:42 2010
Hex dump of (file 3, block 78089) in trace file d:\LSTDBY1\bdump\LSTDBY12_p001_3832.trc
Corrupt block relative dba: 0x00c13109 (file 3, block 78089)
Fractured block found during buffer read
Data in bad block:
type: 32 format: 2 rdba: 0x00c13109
last change scn: 0x0000.028f4ec4 seq: 0x3 flg: 0x04
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x02612001
check value in block header: 0x56d2
computed block checksum: 0x4ca7
Reread of rdba: 0x00c13109 (file 3, block 78089) found same corrupted data
Thu Jan 21 10:07:42 2010
krvxerpt: Errors detected in process 61, role builder.
Thu Jan 21 10:07:42 2010
krvxmrs: Leaving by exception: 1578
Thu Jan 21 10:07:42 2010
Errors in file d:\LSTDBY1\bdump\LSTDBY12_p001_3832.trc:
ORA-01578: ORACLE data block corrupted (file # 3, block # 78089)
ORA-01110: data file 3: 'D:\LSTDBY1\SYSAUX01.DBF'
LOGSTDBY status: ORA-01578: ORACLE data block corrupted (file # 3, block # 78089)
ORA-01110: data file 3: 'D:\LSTDBY1\SYSAUX01.DBF'
Thu Jan 21 10:07:43 2010
TLCR process death detected. Shutting down TLCR
logminer process death detected, exiting logical standby
LOGSTDBY Analyzer process P003 pid=58 OS id=3632 stopped
Thu Jan 21 10:07:45 2010
Errors in file d:\LSTDBY1\bdump\LSTDBY12_lsp0_3688.trc:
ORA-12801: error signaled in parallel query server P001, instance RAC6:reports2 (2)
ORA-01578: ORACLE data block corrupted (file # 3, block # 78089)
ORA-01110: data file 3: 'D:\LSTDBY1\SYSAUX01.DBF'
LOGSTDBY Apply process P004 pid=63 OS id=3628 stopped
LOGSTDBY Apply process P005 pid=64 OS id=3624 stopped
LOGSTDBY Apply process P006 pid=65 OS id=3620 stopped
LOGSTDBY Apply process P007 pid=66 OS id=3612 stopped
LOGSTDBY Apply process P008 pid=67 OS id=3840 stopped
Thu Jan 21 10:08:13 2010
Corrupt Block Found
TSN = 2, TSNAME = SYSAUX
RFN = 3, BLK = 78089, RDBA = 12661001
OBJN = 5812, OBJD = 5862, OBJECT = SYS_LOB0000005811C00008$$, SUBOBJECT =
SEGMENT OWNER = SYSTEM, SEGMENT TYPE = Lob Segment
Thu Jan 21 10:08:15 2010
LOGSTDBY status: ORA-16222: automatic Logical Standby retry of last action
LOGSTDBY status: ORA-16111: log mining and apply setting up
Thu Jan 21 10:08:15 2010
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
Thu Jan 21 10:17:24 2010
RFS LogMiner: Client enabled and ready for notification
Thu Jan 21 10:17:25 2010
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 8: 'D:\LSTDBY1\STREDO08.LOG'
Thu Jan 21 10:17:33 2010
RFS LogMiner: Registered logfile [D:\LSTDBY1\STD\1_3356_698506430.ARC] to LogMiner session id [1]
Thu Jan 21 10:27:16 2010
RFS LogMiner: Client enabled and ready for notification
Thu Jan 21 10:27:16 2010
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 7: 'D:\LSTDBY1\STREDO07.LOG'
Thu Jan 21 10:27:31 2010
RFS LogMiner: Registered logfile [D:\LSTDBY1\STD\1_3357_698506430.ARC] to LogMiner session id [1]
Thu Jan 21 10:37:23 2010
RFS LogMiner: Client enabled and ready for notification
Thu Jan 21 10:37:24 2010
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 8: 'D:\LSTDBY1\STREDO08.LOG'
Thu Jan 21 10:37:31 2010
RFS LogMiner: Registered logfile [D:\LSTDBY1\STD\1_3358_698506430.ARC] to LogMiner session id [1]
Thu Jan 21 10:40:58 2010
alter database stop logical standby apply
Thu Jan 21 10:40:58 2010
ALTER DATABASE STOP LOGICAL STANDBY APPLY
Thu Jan 21 10:40:59 2010
LOGSTDBY status: ORA-16128: User initiated stop apply successfully completed
Thu Jan 21 10:40:59 2010
Completed: alter database stop logical standby apply
Thu Jan 21 10:41:32 2010
alter database stop logical standby apply
Thu Jan 21 10:41:32 2010
ALTER DATABASE STOP LOGICAL STANDBY APPLY
Completed: alter database stop logical standby apply
Thu Jan 21 10:47:16 2010
RFS LogMiner: Client enabled and ready for notification
Thu Jan 21 10:47:16 2010
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 7: 'D:\LSTDBY1\STREDO07.LOG'
Thu Jan 21 10:47:34 2010
RFS LogMiner: Registered logfile [D:\LSTDBY1\STD\1_3359_698506430.ARC] to LogMiner session id [1]
Thu Jan 21 10:48:23 2010
alter database start logical standby apply immediate
Thu Jan 21 10:48:23 2010
with optional part
IMMEDIATE
Attempt to start background Logical Standby process
LOGSTDBY Parameter: DISABLE_APPLY_DELAY =
LOGSTDBY Parameter: LOG_AUTO_DELETE = FALSE
LOGSTDBY Parameter: REAL_TIME =
LSP0 started with pid=60, OS id=3668
Thu Jan 21 10:48:24 2010
Completed: alter database start logical standby apply immediate
Thu Jan 21 10:48:24 2010
LOGSTDBY status: ORA-16111: log mining and apply setting up
Thu Jan 21 10:48:24 2010
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
Thu Jan 21 10:49:29 2010
alter database start logical standby apply immediate
Thu Jan 21 10:49:29 2010
ORA-16103 signalled during: alter database start logical standby apply immediate...
Thu Jan 21 10:50:13 2010
alter database start logical standby apply immediate
Thu Jan 21 10:50:13 2010
ORA-16103 signalled during: alter database start logical standby apply immediate...
Thu Jan 21 10:57:16 2010
RFS LogMiner: Client enabled and ready for notification
Thu Jan 21 10:57:16 2010
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 8: 'D:\LSTDBY1\STREDO08.LOG'
Thu Jan 21 10:57:28 2010
RFS LogMiner: Registered logfile [D:\LSTDBY1\STD\1_3360_698506430.ARC] to LogMiner session id [1]
**************************************************************************************************** ***
Unfortunately the Logminer dictionary resides on SYSAUX, as verified by querying V$SYSAUX_OCCUPANTS; the end result is that logical standby apply won't stick.
When i try to perform recovery on the SYSAUX tablespace, i get an ORA-283 error, stating that no recovery is necessary.
Any tips on how to go about this? Would it be possible to just drop SYSAUX, recreate it, then rerun DBMS_LOGSTDBY.BUILD to rebuild the objects/dictionary needed by LogMiner?
tia
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|