Xref: alice comp.databases.oracle.server:56445
Path: alice!news-feed.fnsi.net!netnews.com!europa.netcrusader.net!144.212.100.101!newsfeed.mathworks.com!cam-news-hub1.bbnplanet.com!atl-news-feed1.bbnplanet.com!news.gtei.net!news.ipass.net!not-for-mail
From: "David Sisk" <davesisk@ipass.net>
Newsgroups: comp.databases.oracle.server
References: <7lv5p7$j2p$1@newsread.do.de.uu.net>
Subject: Re: LogMiner and Oracle 8.0
Lines: 56
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <KiUg3.31$w3.111@news.ipass.net>
Date: Wed, 7 Jul 1999 22:55:49 -0400
X-Complaints-To: abuse@ipass.net
X-Trace: news.ipass.net 931402026 209.170.133.235 (Wed, 07 Jul 1999 22:47:06 EDT)
NNTP-Posting-Date: Wed, 07 Jul 1999 22:47:06 EDT
Organization: iPass.Net

Hi Marco:

To my understanding, LogMiner is designed to work with Oracle8.1 and NOT
Oracle8.0.  I *think* that's your problem....

Regards,

--
David C. Sisk
The Unofficial ORACLE on NT site
http://www.ipass.net/~davesisk/oont.htm


Marco Riegel wrote in message <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/