C
General Repository Guidelines

Repository Sizing

This section provides guidelines for determining storage requirements and disk space allocation for your Oracle Enterprise Manager repository.

Space requirements can vary greatly as a result of what Oracle Enterprise Manager tools you are licensed to use and the amount of data generated by the work you perform. In addition, the growth of the repository could vary slightly depending upon the database version in which the repository is created.

If you choose to create a new repository from a typical installation session and accept the default configuration for the repository, a new OEM_REPOSITORY tablespace will be created. The OEM_REPOSITORY tablespace contains repository objects for the Oracle Enterprise Manager Console and all separately licensable Packs regardless if you have installed or purchased licenses for them. In addition, depending on the database version in which the repository is created, the repository could initially allocate between 6 - 26 MB of hard disk space.

Depending on how you actually use Oracle Enterprise Manager products, the repository size may increase. To determine by how much your repository could grow, refer to the table below. To accommodate an increase in repository size, the default OEM_REPOSITORY tablespace is automatically configured to autoextend. For example, if you have created the default OEM_REPOSITORY tablespace which allocates 4 MB for using Capacity Planner for a single, small database, but you actually plan to use Capacity Planner on a more regular basis - for example, for three large databases - then you should expect the size of your repository to increase by approximately 16 MB. In such situations, the tablespace would autoextend automatically to accommodate the increase.

If you choose to create a new repository from a typical installation session and want to use an existing tablespace, follow these steps to determine how much disk space the repository will use:

1. Review the "Product" column to find the products you are using.

2. Identify those actions you perform with each product in the "If you..." column.

3. Add the corresponding hard disk space requirements for those actions from the "Then allocate..." column. The total of these requirements is the expected size of your repository.

Product	If you...	Then allocate...
Oracle Enterprise Manager Console	use only the Console save little (if anything) in job history	4 - 9 MB
Oracle Diagnostics Pack	collect less than 4 MB of Trace Data use Capacity Planner for a single, small database over a few days	35 MB
	collect between 4 - 20 MB of Trace Data · use Capacity Planner for a single, medium-sized database over several months	60 MB
	collect between 20 - 60 MB of Trace Data · use Capacity Planner for up to three large databases over several months	120 MB
Oracle Tuning Pack	save less than: 50 tuned SQL statements 5 scoped tuning sessions 10 tablespace jobs in job history	less than 15 MB
	save between: 50 - 150 tuned SQL statements 5 - 15 scoped tuning sessions 10 - 30 tablespace jobs in job history	15 - 45 MB
	save more than: 150 tuned SQL statements 15 scoped tuning sessions 30 tablespace jobs in job history	more than 90 MB
Oracle Change Management Pack	for a schema with approximately 500 objects · 1 baseline, with 2 saved versions of baseline· 1 saved comparison· 1 change plan (propagate the schema)	20 MB
	For a schema with approximately 500 objects. 2 baselines, with 2 saved versions of baseline· 2 saved comparisons· 5 change plans	40 MB
	For a schema with approximately 500 objects· 5 baselines, with 2 saved versions of baseline· 5 saved comparisons, with 2 versions each· 10 change plans	100 MB
Oracle Management Pack for Oracle Applications	use Capacity Planner for a single, small database over a few days	4 MB
	use Capacity Planner for a single, medium-sized database over several months	10 MB
	use Capacity Planner for up to three large databases over several months	20 MB
Oracle Management Pack for SAP R/3	use Capacity Planner for a single, small database over a few days	4 MB
	use Capacity Planner for a single, medium-sized database over several months	10 MB
	use Capacity Planner for up to three large databases over several months	20 MB
Oracle Standard Management PackFoot 1	for a schema with approximately 500 objects· 1 baseline, with 2 saved versions of baseline· 1 saved comparison	20 MB
	for a schema with approximately 500 objects· 2 baselines, with 2 saved versions of baseline· 2 saved comparisons	35 MB
	for a schema with approximately 500 objects· 5 baselines, with 2 saved versions of baseline· 5 saved comparisons, with 2 versions each	80 MB

1 While the other separately licensable Packs are available with Oracle9i Enterprise Edition, the Oracle Standard Management Pack is only available with Oracle9i standard edition.

For example, if you:

• use the Console regularly but typically do not save large output to the job history (approximately 7 MB)

• collect approximately 45 MB of Trace Data (approximately 45 MB)

• use Capacity Planner very little (approximately 4 MB)

• save approximately 100 tuned SQL statements, 11 scoped tuning sessions and 25 tablespace jobs in job history (approximately 32 MB)

The total of all these space allocations (7 MB + 45 MB + 4 MB + 32 MB) is 88 MB. Thus, you should allocate approximately 88Mb for your repository.