Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: a sad story for Oracle DBAs

Re: a sad story for Oracle DBAs

From: Zhencan Fan <zhen_at_wam.umd.edu>
Date: 1998/04/04
Message-ID: <6g5lde$kmt@dailyplanet.wam.umd.edu>#1/1

Adrian Shepherd (Adrian.Shepherd_at_BTINTERNET.COM) wrote:
: Not so sad my friend, the SGA size can be justified with many reasons.
: perhaps they have hundreds of SQL*Net connections that have a greater need
: for the memory, perhaps the kind of queries are always full table scans that
: cant use a large SGA, perhaps they know their system and have tuned it as
: such whereas you have no performance stats from this system and are blindly
: insulting the configuration, there are many reasons to have a small SGA as
: mentioned, you never mentioned how big the database was only the amount of
: available disk space...

Maybe I didn't make myself clear in my previous posting, what I do know is this is a system that will only be used by no more than 10 people. I am not sure about the exact size of the database, but the several tables I looked at have about 3 million rows. What I didn't say is that the person responsible for this configuration is so intimidated by Oracle that this person dare not touch anything except for the default setups.

Even if it were the case as you argued, say there were to be hundreds of SQL*Net connections, then you would probably need multi-threaded configuration. Allow me to ask you this: where do you think those request queue and response queues reside?

Wouldn't it be a major joke to use a 18M SGA to support HUNDREDS of SQL*Net connections?

Setting SGA to be 18M for a DEDICATED 896M NT system is just one of the many absurd stories. I still have to see how you justify this setting.

: Shame on you.
 

: I am not arguing against a larger SGA giving better response times, just
: that the machine may need the memory for other reasons...perhaps it was a
: typo in the init.ora, perhaps they used an init.ora from an 8K block size
: machine and used it on a 2K database,

Simply not true. Now you are saying it was probably a typo. Where is the argument about supporting "hundreds of SQL*Net" connections using 18M SGA? Even if (which is not the case) it was migrated from a 8K block system, the SGA size could go no more than 18*4 = 72M (for a 896M system). Let me help you, how about trying this: "perhaps they used an init.ora from an 64K block size and used it on a 2k database."

: Perhaps this company turned you or your friend down for a job...

Very interesting thought, do you always think in this way? This case has nothing with me or my friend personally.

FYI:
I am happily working as an Oracle DBA for an Oracle6 to Oracle7 project. My friend was ACTUALLY offered a position by this company, and is currently evaluating this offer.
And you think I would be interested in working for this company? I was never and will never be interested, that I can assure you.

By the way, are you also working in a consulting company?

An Oracle certified DBA

: Zhencan Fan wrote in message <6g34bo$dbh_at_dailyplanet.wam.umd.edu>...
: >Just heard this REAL story from a friend. It's no joke.
: >
: >One prestigious consulting company is going to deliver an Oracle
: >data warehousing system for a client. Here is the hardware configuration:
: >Windows NT 4.0 running on quad pentium pro 200
: >896 MB RAM
: >About 50 GB Harddrive space
: >
: >Guess how much memory they assigned for SGA: 18MB! Remember this machine
: >is dedicated for this data warehouse. And they complained that Oracle on
: >NT sucks!
: >
: >The fact that the company treats its technical people as second class
: >citizens pretty much predicted this consequence.
: >
: >A sad story for Oracle DBAs or what?
Received on Sat Apr 04 1998 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US