Re: 8i's memory footprint

A few comments

• 96 M to me means your system has insufficient memory. According to Oracle you need 128 M and my experience is it is barely working within 128 M
• If you don't need java, the minimum java_pool_size is 1M
• one of the methods to connect as internal is to create an OS_DBA group on O/S level and grant that O/S group to your (externally authenticated) o/s user.
• There is a separate document in the standard doc set outlining differences between 8.0 and 8i. As usual that doc is online at http://technet.oracle.com

Hth,

Sybrand Bakker, Oracle DBA

Guy Dallaire <gdallair_at_criq.qc.ca> schreef in berichtnieuws 3922b75f.9889897_at_news.criq.qc.ca...
> Hi,
>
> I'm planning to migrate from 7.3.4 to 8.1.6 on solaris in the near
> future. Unfortunately, there is no more printed documentation with
> oracle 8...
>
> To test the new installer and other stuff, I decided to install 8.1.6
> on linux. It never completed, it hung whil creating the test
> database. I had to kill it. I then discovered that the database was
> created and it was HUGE. The SGA was BIGGER than the physical RAM in
> the machine....
>
> Anyway, I shut it down and played with the parameter file. I stumbled
> on a couple of new memory structures and would like to have more
> details about the java_pool_size and java_reserved_size (Or something
> like that) parameters. They were BIG for a 96 Mb machine (At 20 Mb for
> the pool size)
>
> Also, I would like to know if anyone has a good text about what's
> new/changed since 8i in a practical manner. For example, there is no
> more SQL*DBA or svrmgrl with 8i, you have to use sqlplus.
>
> I discovered that you can connect as "internal" from sqlplus to do
> maintenance, but oracle says they will remove "internal" in the
> future, is there a way to connect as sysdba from the command line to
> sql*plus in 8i ? How ?
>
> Thanks
>
>
Received on Wed May 17 2000 - 00:00:00 CDT