Critial errors in alert_SID.log not shown at startup

From: <johnvue_at_gte.net>
Date: Mon, 24 Aug 1998 13:05:20 GMT
Message-ID: <6rroeg$l85$1@nnrp1.dejanews.com>

When you startup, mount, and open the database, most errors will visibly show up on the screen. For example, if a data file is missing, you'll get a visible error.

However, one error that does not show up is an invalid member of a redo log group. This of course, is one of the reasons why you're supposed to always check the alert_SID.log after starting up the databases.

Can anyone think of any other "silent" error messages that don't show up at database startup?

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum Received on Mon Aug 24 1998 - 08:05:20 CDT