Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> LogMiner and Oracle 8.0

LogMiner and Oracle 8.0

From: Marco Riegel <mr_at_de.uu.net>
Date: 7 Jul 1999 09:14:15 GMT
Message-ID: <7lv5p7$j2p$1@newsread.do.de.uu.net>


Hi,

I am trying to analyze Oracle 8.0 archived redo logs with the LogMiner package of Oracle8i.

The log files are taken from a Sun E450 running Solaris 2.5.1 and Oracle 8.0.5.1.0 . After generating the dictionary on that machine I both transferred the dictionary file and 3 sample archived redo logs to our Oracle 8.1.5 test installation on a Sun E10 running Solaris 2.6. I know this doesn't meet the requirements stated in the documentation (same hardware and os levels) and therefore I necessarily cannot blame Oracle for it.

After selecting 10000 rows from v$logmnr_contents (just 200 rows with sql_redo not null) the statements breaks with:

ORA-00356: inconsistent lengths in change description ORA-00353: log corruption near block 4099 change 140166141 time 07/05/99 17:27:0
1
ORA-00334: archived log: '/users/home/oracle/spool/1_4666.dbf'

This happens to all the sample redo logs I tried. I am quite sure that the redo logs aren't broken.

Does anybody know if there's a switch that changes the behavior to "okay, I know that this log does not seem to be okay but I continue to try to disclose as much statements as I can". Or does it fail because of the different os levels ??

Regards,

Marco

Tools Quality Standards           UUNET Deutschland GmbH
Tel. +49 231 972 1355             Sebrathweg 20
Fax. +49 231 972 1601             44149 Dortmund, Germany
mr@de.uu.net                      URL http://www.uunet.de/

Received on Wed Jul 07 1999 - 04:14:15 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US