Oracle Database Sizing

Sizing an Oracle database is part of its installation. Even before installing Oracle you should consult your DBA to estimate how big your data is going to be and size the database accordingly.

[spacer]

Size your database server’s disk based on anticipated traffic. Oracle's archive logs can grow rapidly. (In one test these archive logs grew to 12 GB in two weeks). If the file system fills up with the archives, Oracle stops, and may need to be restarted to clear an archive error.

Installation of Oware-based products produces files like the following:

load_{product_name}_sizing.sql

For example: load_redcell_sizing.sql. The sql extension for this file has no significance (you cannot run this file in a SQL tool).

Here is an excerpt from the sizing file generated for Oware service classes:

REM ################################################################

REM #

REM # Script Name : load_oware_svc_sizing.sql

REM # Creation Date: Fri Jul 05 16:17:29 PDT 2002

REM #

REM # Columns:

REM # sql Prompt, Classname, tablename, Tablesize, Blob size (0/1024)

REM ################################################################

This is a comma-delimited file. The comma-separated columns are as follows:

Column #

Definition

1

n/a

2

class name

3

tablename

4

Tablesize (non-blob fields)

5

Blob size (0 if table does not contain a blob 1024 otherwise)

To use this sizing file, do the following:

1. Import this file into a spreadsheet, choosing comma-delimited formatting.

2. Once imported, you can see the record sizes (in bytes) for the application.

3. Multiply these record size amounts by the number of rows expected for those tables/classes.

4. Calculate number of bytes for each class.

5. Sum calculated byte count to determine total datafile size (convert to mega- or gigabytes, if needed)

[spacer]

Best practice is to size your database at least 20% larger than calculated above.