Re: ORACLE 7.3.2/NT 4.0 problem

Make sure you have Service Pack 1 installed for NT 4.0 Also create multiple 2GB datafilles for the DATA tablespaces. As with any 32-bit OS, 2GB is as large of a datafile it can handle correctly. In other words you can create larger datafiles but the performance will be what you are experiencing now and just wait till you start trying to do full table exports with a TS larger than 2GB. Good Luck.

Matt Arrocha
marrocha_at_bellsouth.net

Ilyse Mazza <imazza_at_udel.edu> wrote in article <329106C7.663A_at_udel.edu>...
> We have just installed Oracle 7.3.2.2.0 on a NT 4.0 Compaq Proliant 5000
> server (384M RAM, 4 P6 processors). All of our older (< 1G) databases
> work fine. However, we created a new instance with @14G of data, of
> which 9G (23 million rows) is in one table.
>
> The instance will start up and run smaller queries on this large
> table(<75000 rows) correctly. Any query against more data than this
> will complete, but the RDBMS will continue to process something instead
> of returning to an idle state. All 4 processors will spike up to 100%
> at various intervals (one processor is always maxed when this happens),
> and the instance will not release the memory it used during the query.
> The trace logs from these SQL queries show that the process is "Waiting
> for SMON to release tx recovery." There are 3 redo logs of 10M each, 5
> rollback segments of 3M each and temp datafiles of 500M total. None of
> these tablespaces come close to being fully used.
>
> In addition, the database becomes unusable at this point. It will not
> accept new connections and can only be shutdown with the ABORT
> parameter. A shutdown immediate or normal produces the same SMON error.
> However it starts right back up again. Please email me if there are any
> ideas, suggestions, etc. Thanks.
>
> Philip Mazza
>
Received on Sun Nov 24 1996 - 00:00:00 CST