And another thing. If in pre 9i days you tried to allocate more than 2gb to the Oracle.exe process, just cause you have 9i and dynamic memory allocation does not mean that os limits have disappeared. Your text file (init.ora) with the incorrect value in it to edit on the other hand, has.
Actually, I have learned a number of lessons from this experience which may have general applicability. 1. Your co-worker having a bad experience (db crashing with bad init.ora parameters for memory) does not mean that you won't hit the same barrier. 2. Spfiles have extra pain and little convenience over pfiles - read you can screw up badly. 3. don't change the same thing on 3 databases at 16:30 Friday. 4. Actually don't make *any* changes at 16:30 Friday. 5. Windows sucks (ok this isn't exactly a lesson really). The Niall practicum (no fee-no certification). On a windows 9i server (not a valuable one OK). Connect / as sysdba Alter system set SGA_MAX_SIZE=2047MB scope=spfile; Alter system checkpoint; Shutdown immediate/abort; Startup What happens next? How do you fix it? Niall -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Niall Litchfield INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
