• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 150
  • Last Modified:


As an oracle dba how can we plan for the database’s future storage requirements ...
Which are the areas..
5 Solutions
slightwv (䄆 Netminder) Commented:
The reality is this is a difficult question to answer on a site like this.

There are people that make a large part of their careers out of nothing but capacity planning.

There are a TON of links out there on capacity planning that are specific to Oracle if you look around.

In a nutshell, you need to understand your database and the applications that use it.  How much storage a specific type of transaction will use and how many of these types of transactions you expect to occur.

Then it is simple math and some blind faith to come up with your plan.

There are also a ton of links out there on figuring out an estimate for a rows size in Oracle.

It is more than just the data in the row.  There is overhead, index storage, etc...
jcob_lAuthor Commented:
Can you invite another expert this is not the expected answer..
Not the general view..
But from the practical expert view give an like

Where in storage ..daily ...weekly wise...

based on real experiance..
slightwv (䄆 Netminder) Commented:
Many Experts monitor this Zone and will likely post later.  Just give it time.

>>Where in storage ..daily ...weekly wise...

I do not understand what you are asking.  Can you explain a little more?
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

if you have oem repository it will maintain a history of tablespace/datafile sizes.

if not, you can always store them yourself periodically.

as slightwv said, it takes some knowledge of your system.

most systems I support grow pretty steadily on a monthly basis.  "steady" has nothing to do with how fast.

some grow steadily at 1 GB a month, some less than that.
some are measured in Kilobytes per month
some grow steadily at 100 GB a month

if I were to monitor them daily I might see lulls and spikes like
 0, 0, 0, 0, 0, 20gb, 0, 0, 0, 0, 0, 30gb, 0, 0, 0, 0, etc

it all depends on usage patterns.  You'll need to make your own analysis.  I'd start with monthly though,  it's frequently enough that you can see a pattern, slow enough that you don't need to be on top it all the time.
slightwv (䄆 Netminder) Commented:
A good starting point for capacity planning is just load up the system with some typical test set and see what happens.

Start with what is used now (in total).

It may be as easy as:
select sum(bytes) from dba_segments;

Load up X number of rows, look at how much space is now used.

Load up the same number of rows again, look at used space.

You can then start seeing that X rows uses Y amount of space.  In a year we 'expect' Z number of rows, therefore we need about Q amount of storage per year.
slightwv (䄆 Netminder) Commented:
Just thought of a few other things I should throw out there that are part of a capacity plan.

You also need to account for the size of things like archived redo logs, on-disk backups, audit logs (if logging to disk), dump files, trace files, etc...

These are database related files that are outside of the size of the actual database.

How you decide to set all this up can have a decent impact on total disk usage for the database as a whole.

For example, my on disk backups use more disk space than my actual database size.

I keep 7 days of archived redo log backups at all times.  I also use a cumulative incremental which rolls the last incremental back into the full.  If you choose a different backup strategy, your backups can consume a LOT more disk than the actual database.

Typically a small item in the big picture but you need to plan for it:
There is also room for the Oracle software itself.  If you plan on running multiple versions on the same server, you need to make sure you have room for the multiple versions.
DavidSenior Oracle Database AdministratorCommented:
What are the business rules you have to provide for?  Every client is different, and there's no working around that fact.

A company that manufactured parts for commercial aircraft, had to record press temperature, pressure, etc. for two dozen presses, running around the clock -- and to keep that data for the FAA for ten years.

A hospital had a few hundred beds, patients' information getting updated frequently, those people checking in and out frequently -- but once a day a dump of all activity was downloaded to a warehouse and used by several dozen bioinformatics teams.

A volunteer group tracks the PII, training, and experience for a few dozen people.

Cell phone companies have to capture "lots" of call transactions in real time for billing.

Insurance providers for the new Obamacare are currently overwhelmed by the volume of demand, and have zero statistics to plan how many customers they'll end up with.

A government agency has fairly stable data, but has to failsafe multi-node RACs on multiple sites.  

DBAs must have the rapport with the system analysts to include their best guesses on how the data changes over time.

Steve WalesSenior Database AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now