From: Mark D Powell Subject: Re: Redo-Log Archiv Problem Date: 2000/07/07 Message-ID: <223d4e04.30f2d9de@usw-ex0104-032.remarq.com>#1/1 References: <3965BCFD.7696861E@brocom.de> <8k4hbs$1p6lr$1@ID-6887.news.cis.dfn.de> Bytes: 625 X-Originating-Host: 199.228.142.8 X-Complaints-To: wrenabuse@remarq.com X-Trace: WReNphoon3 962974382 10.0.2.32 (Fri, 07 Jul 2000 05:53:02 PDT) Organization: http://www.remarq.com: The World's Usenet/Discussions Start Here NNTP-Posting-Date: Fri, 07 Jul 2000 05:53:02 PDT Newsgroups: comp.databases.oracle.server X-Wren-Trace: eObD6+rztP61q/P86Oj34OPw+u/D56Ljrenm6K+jpv+nsvS/pvenuqS/ Increasing the size and count of redo logs is probably the answer, but the other possibility is that you have an IO problem on your archive log destination directory that will still need resolving. Adding another disk or stripping may be necessary. But if you only have 3 redo logs a 4th is the place to start. If your problem persists you should probably post your redo log size and information on the redo and archive log disk arrangement. ----------------------------------------------------------- Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free! http://www.keen.com