Path: news.easynews.com!easynews!hub1.nntpserver.com!nntp-relay.ihug.net!ihug.co.nz!out.nntp.be!propagator-SanJose!in.nntp.be!news.mindspring.net!not-for-mail From: "nntp.ix.netcom.com" Newsgroups: comp.databases.oracle.server Subject: Log Miner : Performance problem querying archived logs Date: Thu, 29 Nov 2001 22:00:40 -0800 Organization: MindSpring Enterprises Lines: 13 Message-ID: <9u77a6$j0j$1@slb7.atl.mindspring.net> NNTP-Posting-Host: 42.20.13.96 X-Server-Date: 30 Nov 2001 06:00:38 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Xref: easynews comp.databases.oracle.server:126704 X-Received-Date: Fri, 30 Nov 2001 04:11:31 MST (news.easynews.com) I'm seem to be having a performance problem when trying to get information out of the archived redo log files. I have no problem creating the dictionary,or specifying the files, or starting Log Miner. The problem occurs when I query v$logmnr_contents. The query runs forever(it never finished). I'm searching through a days worth of log files(about 2GB). Is it just a matter of doing the disk i/o to read through the files? Anyone have any performance metrics on this? Any suggestions as to instance parameters to look at(shared pool maybe)? Not sure exactly how to tune a query running against a dynamic performance view. Thanks in advance for any help.