Database space required for operation - HiRDB (Tuning Manager (HTnM))
return to main contents page
return to "Management server" contents page
A Tuning Manager server uses HiRDB for the database.
This appendix describes how to estimate the database size (total database capacity) of the Tuning Manager server required for operations.
The initial total database capacity is 2 GB. You can increase the total database capacity up to 32 GB, as necessary.
Use the formula shown below to calculate the total database size. If the result of the calculations is in between 2 GB and 32 GB, you will need to increase the total database capacity. 
If the result of the calculations exceeds 32 GB, you will need to modify the retention period for the capacity data or polling schedule.
For details on how to increase the total database capacity, how to modify or increase the retention period for the capacity data or polling schedule, see the Tuning Manager Server Administration Guide.
Formula for estimating the total database capacity:
The following formula can be used to estimate the total database size needed for the Tuning Manager server.
total-database-size (in GB) =
(18,530*P*S*C (see 3)
+ 7,050*L*S*C(see 3)
+ 270*(THPV+L/2(see 1))*M
+ 800*(F+FM)*H*C(see 3)
+ 320*F*M2
+ 2,600*D*H*C(see 3)
+ 29,630*DM1*H*C(see 3)
+ 3,170*HOST*H*C(see 3)
+ 7,340*VM*H*C(see 3)
+ 10,100*DS*H*C(see 3)
+ 290*DS*M2)/1,0243
+1.15
+0.45 (see 2)
Notes: 1. Do not divide L by 2 if the number of externally connected logical devices exceeds one-half of the total number of logical devices. Instead, read the L/2 portion as "L".
2. Add this value only when you are using Agent for Oracle.
3. Set variable C as shown below:
C = The number of resources changed data per month/The total number of the monitoring resources
If one Tuning Manager server monitors under 128,001 resources, set variable C = 1
Table 1 Variables used in the formula
Variable Description Acceptable values
P The number of storage system ports A positive number
L The number of logical devices A positive number
DPV The number of Dynamic Provisioning
volumes
A positive number
F The number of file systems A positive number
FM Average number of file systems mounted
per month
A positive number
D The number of device files A positive number
DM(see 1) The number of MPIO device files A positive number
HOST The number of virtualization servers A positive number
VM The number of virtual machines A positive number
DS The number of datastores A positive number
M(see 2) The number of capacity data collections A positive number
S The retention period for historical data of a storage system configuration A positive number (indicating the number of months)
H The retention period for historical data of a host configuration A positive number (indicating the number of months)
C The ratio of changed data per month A decimal number
Notes: 1. If Agent for Server System is running on a host in an MPIO environment, depending on the path management program in use, you might need to use the variable DM instead of the variable D for the number of device files. 
To check whether you need to do so, Agent for Server System is running on a host in an MPIO environment, depending on the path management program in use, you need to assign the number of device files to the variable DM instead of the variable D. 
To check whether you need to assign the number of device files to the variable DM, see Table 2 Whether it is necessary to use the variable DM for the number of device files in an MPIO environment.
2. The default value for the number of capacity data collections (variable M) is 141. If the retention period or polling schedule for capacity data is modified, this value will also be changed.
Table 2 Whether it is necessary to use the variable DM for the number of device files in an MPIO environment
OS Path management program Whether it is necessary
to use the variable DM
Windows Dynamic Link Manager No
Other than Dynamic Link Manager Yes
Solaris Any path management program Yes
AIX No
HP-UX Yes
Linux Yes
The formula for estimating the total database capacity needs to be used if the interval for adding a resource and the interval for changing the resource configuration satisfy the conditions listed in the following table.
Table 3 Conditions under which to use the formula for estimating the total database capacity
Classification Resource Interval for adding a resource (average) Interval for changing the configuration (average)
storage system storage system Once a day Once a day
Port controller Once a month Once a month
Port Once every three months Once a day
Host group Once a month Once a month
CLPR Once a month Once a month
Processor Once every three months
per port
Once every three months
per port
DKA pair Once a day Once a day
Parity group Once a month Once a month
Concatenated parity group Once a month Once a month
Physical drive Once every three months
per port
Once every three months
per port
Logical device Once a month Once a month
LU path Once a month Once a month
Label Once a month Once a month
Dynamic Provisioning
volume
Once a month Once a month
SLPR Once a month Once a month
Mapping information for a
port and the host WWN
Once every three months Once every three months
Host Host Once a month Once a month
Device file Once a month Once a month
Disk group Once a month Once a month
File system Once a month Once a month
Port Once a day Once a day
Path Once a day Once a day
MPIO environment path Once a month Once a month
Hypervisor Virtualization server Once a month Once a month
Virtual machine Once a month 10 times a month
Datastore Once a month Once a month
WWN of the virtualization
server managed by Device
Manager
Once every three months Once every three months
Mapping information for a
virtualization server and its datastores
Twice a month Twice a month
Mapping information for a
virtual machine and its
datastores
Twice a month Twice a month
Mapping information for a
datastore and its logical
devices
Twice a month Twice a month
Mapping information for a
datastore and the storage
subystem ports
Twice a month Twice a month
Switch Switch Once a day Once a day
Port Once every three months Once every three months
Oracle Oracle instance Once a day Once a day
Tablespace Once every three months Once every three months
Data file Once every three months
per tablespace
Once every three months
per tablespace