Disk space (Agent for Oracle)
return to main contents page
return to "Application server" contents page
This section provides estimates of the amount of disk space required for Agent for Oracle.
Disk space requirements for the entire system
The disk space requirements for Agent for Oracle depend on the file sizes of the following data:
- Agent Store database
- Number of Agent for Oracle instances
- Agent log
The following table shows the disk space requirements for the entire system, based on the above.
Table 1 Agent for Oracle disk space requirements for the entire system
Status of Agent for
Oracle
Disk space requirements (megabytes)
Windows
Server
HP-UX(IPF) Solaris AIX Linux
During
installation (see 1)
10 40 25 40 20
Initial
condition (see 2)
110 140 125 140 120
Operation a + b a + b a + b a + b a + b
Legend: a: Sum of the disk spaces for each instance
The disk space requirement for a single instance can be calculated as follows:
- In Windows: c + d + 20
- In UNIX: c + d + 18
b: Disk space requirements for installation
c: Disk space requirements for the Store database
d: File size of an agent log
The maximum file size of an agent log is 128 megabytes.
Notes: 1. Disk capacity of twice as much of the program unit capacity is required at installation.
2. The status in which a single instance of Agent for Oracle is set up and only System Stat Summary Interval (PI) records are specified for collection.
Disk space requirements for each installation directory
Table 2 Agent for Oracle disk Space requirements for each installation directory
Directory
name
Status of Agent for
Oracle
Disk space requirements (megabytes)
Windows
Server
HP-UX(IPF) Solaris AIX Linux
%SystemDrive% During
installation
16 --- --- --- ---
Installation
directory for
Tuning Manager
series programs
During
installation
12 --- --- --- ---
Initial
condition*
110 --- --- --- ---
Operation a + b --- --- --- ---
/opt During
installation
--- 111 77 78 75
/opt/jp1pc During
installation
--- 111 77 78 75
Initial
condition*
--- 211 177 178 175
Operation --- a + b a + b a + b a + b
Legend: ---: Not applicable
a: Sum of the disk spaces for each instance*
The disk space requirement for a single instance can be calculated as follows:
- In Windows: c + d +e + 18
- In UNIX: c + d + 18
b: Disk space requirements for installation
c: Disk space requirements for the Store database
d: File size of an agent log
The maximum file size of an agent log is 128 megabytes.
e: Disk space requirements for the jpcOcollect program
For details about the disk space requirements for the jpcOcollect program, see Disk space requirements for the jpcOcollect program.
*The status in which a single instance of Agent for Oracle is set up and only System Stat Summary Interval (PI) records are specified for collection.
Disk space requirements for the jpcOcollect program
The following table describes the disk space requirements for the jpcOcollect program:
Table Disk space requirements for the jpcOcollect program
Monitored
object
Disk space requirements for the jpcOcollect program (megabytes)
Windows HP-UX(IPF) Solaris AIX Linux
Oracle 10g 1 --- --- --- ---
Oracle 11g 1 --- --- --- ---
Oracle 12c 1 --- --- --- ---
Disk space requirements for Store database version 1.0
All records of one record type are stored in the same file in the Store database version 1.0. 
Table 3 Disk space requirements for the Store database shows the formula for estimating the amount of disk space required for Store database version 1.0 for each record type.
Table 3 Disk space requirements for the Store database
Record type Formula for estimating disk space requirements (bytes)
PI record type (X1 + ... + Xa + 3,500 xa)
PD record type (Y1 + ... + Yb + 700 xb)
Legend: X: Disk space for each record of the PI record type that collects historical
dataX can be calculated by the following formula:X = {d x e+ (c + 1900) x {(d xe)/(65,250 - c) + 1} (see 1)} x f x 1.5
Y: Disk space for each record of the PD record type that collects historical dataY can be calculated by the following formula:
Y = {d xg + (c + 1900) x {(d x e)/(65,250 -c) + 1} (see 1) x (g/e) (see 2)} x 1.5
a: Number of records of the PI record type that collect historical data
b: Number of records of the PD record type that collect historical data
c: Size of the fixed part of each record that collects historical data (see 3)
d: Size of the variable part of each record that collects historical data (see 3)
e: Number of instances for each record that collects historical data (1 for a single instance record) (see 6)
f: Among records of the PI record type, number of stored records for each record that collects historical data (see 4)
g: Among records of the PD record type, a maximum number of stored records for each record that collects historical data (see 5)
Notes: 1. In the {(d x e)/(65,250 -c) + 1} calculation, the decimal part is discarded.
2. In the (g/e) calculation, the decimal part is discarded.
3. For details about the sizes of the fixed and variable parts of each record, see the section that describes Agent for Oracle records in the Tuning Manager Application Reports Reference.
4. For records of the PI record type, the collected data is summarized automatically over a certain fixed period (hour, day, week, month, and year). 
Thus, you must take into consideration the number of records to be stored over the applicable period. 
Table 4 Defaults for retention period and number of records for PI record type lists the default values for the retention period and the number of records.
5. For details about the maximum number of stored records, see the chapter that describes management of the Store database, and the section that describes the properties of the Agent Store service in the Tuning Manager Agent Administration Guide. 
The default number of records to be stored for records of each PD record type is 10,000.
6. The following table shows how to calculate the number of instances for each record. Use SQL*Plus or a similar program to access the Oracle Database to be monitored, and execute an SQL statement to obtain the number of instances.
 If a calculation method for the target record is provided in the table, use that method. The following describes how to use SQL*Plus to obtain the number of instances.
To use SQL*Plus to obtain the number of instances:
a. Start SQL*Plus.
b. As a user who has the following privileges, connect to the Oracle Database to be monitored:
CREATE SESSION
SELECT ANY DICTIONARY
SELECT ANY TABLE
c. For the record for which you want to check the number of instances, execute the SQL statement shown in Table 5 Methods for calculating the number of instances for records.
d. The value shown in the COUNT(*) column is the number of instances for the target record.
�@
�@ �@ �@ Note: The number of instances is dynamic information about the monitored Oracle Database.  �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@
Since the number of instances dynamically changes due to factors such as the number of connections with the monitored Oracle Database, use the maximum of the obtained values for your estimate.
�@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@
�@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@ �@
Table 4 Defaults for retention period and number of records for PI record type
Data type Retention period Number of records to be stored
(when collection interval is 1 minute)
Minute-by-minute 1 day*1 1,440
Hourly 7 days 168
Daily 1 year 366
Weekly 1 year 52
Monthly 1 year 12
Yearly Unlimited (years-collected) x 1
*1 If you change the retention period from the default value, the Store database size greatly increases.
Therefore, substantial processing time is necessary to convert the data model when installing the updated version.
For an estimate of the required time, see the description of �gBefore starting an upgrade or overwrite installation�hin Preparing to install or upgrade agents.
Also, twice as much capacity is temporarily required in the disk storage Store database.
Therefore, make sure that enough capacity exists.
Table 5 Methods for calculating the number of instances for records
Record ID Number of instances and calculation methods
PI The number of instances is 1.
PI_PIBC SELECT count(*)
FROM v$waitstat
PI_PICS The number of instances is 1.
PI_PIDB The number of instances is 1.
PI_PIDD SELECT count(*)
FROM v$rowcache
PI_PIDF Sum of the results of the following SQL statements:
1. SELECT count(*)
FROM v$datafile a, v$filestat b, sys.dba_data_files c
WHERE a.file#=b.file# AND b.file#=c.file_id
2. SELECT count(*)
FROM v$tempfile a, v$tempstat b, dba_temp_files c
WHERE a.file#=b.file# AND b.file#=c.file_id(+)
PI_PIDG SELECT count(*)
FROM v$asm_diskgroup
PI_PIDS SELECT count(*)
FROM v$dispatcher, v$process
WHERE addr=paddr
PI_PIEV SELECT count(*)
FROM v$session_event a, v$session b
WHERE a.sid=b.sid AND time_waited>=0
PI_PIGC The number of instances is 1.
PI_PIIO SELECT count(*)
FROM v$sess_io a, v$session b, v$process c
WHERE a.sid=b.sid AND b.paddr=c.addr
PI_PILA SELECT count(*)
FROM v$latchholder a, v$session b,
v$latch c, v$latchname d, v$process e
WHERE c.latch#=d.latch# AND a.laddr(+)=c.addr
AND a.pid=e.pid(+) AND e.addr=b.paddr(+)
PI_PILC SELECT count(*)
FROM v$librarycache
PI_PILO SELECT /*+ ORDERED */ count(*)
FROM v$lock a, v$session b
WHERE a.sid=b.sid AND a.block >= 0
PI_PIMT The number of instances is 1.
PI_PIPL SELECT count(*)
FROM v$lock_activity
PI_PIPP
(see 1)
The number of instances is 0.
PI_PIPQ SELECT count(*)
FROM v$pq_slave
PI_PIRS SELECT count(*)
FROM v$rollstat a, v$rollname b, sys.dba_rollback_segs c
WHERE a.usn=b.usn AND c.segment_name=b.name
PI_PIS2 SELECT count(*)
FROM (SELECT DISTINCT sid
FROM v$sesstat a, v$statname b
WHERE a.statistic#=b.statistic#)
PI_PISE SELECT count(*)
FROM v$system_event
PI_PISH SELECT count(*)
FROM v$shared_server a, v$process b
WHERE a.paddr=b.addr
PI_PISR SELECT count(*)
FROM v$sort_segment
PI_PIST SELECT count(*)
FROM v$sysstat
PI_PITR SELECT COUNT(*)
FROM v$transaction a, v$session b
WHERE RAWTOHEX(ses_addr)=RAWTOHEX(saddr)
PI_PITS SELECT count(*)
FROM sys.dba_tablespaces
PI_PMDB The number of instances is 1.
PI_PMDF Sum of the results of the following SQL statements:
1. SELECT count(*)
FROM v$datafile a, v$filestat b, sys.dba_data_files c
WHERE a.file#=b.file# AND b.file#=c.file_id
2. SELECT count(*)
FROM v$tempfile a, v$tempstat b, dba_temp_files c
WHERE a.file#=b.file# AND b.file#=c.file_id(+)
PI_PMTS SELECT count(*)
FROM sys.dba_tablespaces
PD The number of instances is 1.
PI_PCI The number of instances is 1.
PI_PCTS SELECT count(*)
FROM sys.dba_tablespaces
PD_PDAS The number of instances is 1.
PD_PDBA SELECT count(*)
FROM v$backup_async_io
PD_PDBC SELECT count(*)
FROM v$waitstat
PD_PDBP SELECT count(*)
FROM v$buffer_pool a, v$buffer_pool_statistics b
WHERE a.id=b.id
PD_PDBS SELECT count(*)
FROM v$backup_sync_io
PD_PDC SELECT count(*)
FROM v$sqlarea a, sys.audit_actions b
WHERE a.command_type=b.action
PD_PDCF SELECT count(*)
FROM v$controlfile
PD_PDCI SELECT count(*)
FROM v$circuit a, v$session b,
v$process c, v$process d, v$process e
WHERE a.saddr=b.saddr AND a.server=c.addr(+)
AND a.dispatcher=d.addr(+) AND a.waiter=e.addr(+)
PD_PDCS The number of instances is 1.
PD_PDDB The number of instances is 1.
PD_PDDD SELECT count(*)
FROM v$rowcache
PD_PDDF Sum of the results of the following SQL statements:
1. SELECT count(*)
FROM v$datafile a, v$filestat b, sys.dba_data_files c
WHERE a.file#=b.file# AND b.file#=c.file_id
2. SELECT count(*)
FROM v$tempfile a, v$tempstat b, dba_temp_files c
WHERE a.file#=b.file# AND b.file#=c.file_id(+)
PD_PDDK SELECT count(*)
FROM v$asm_disk a, (SELECT group_number FROM v$asm_diskgroup WHERE group_number <> 0) b WHERE a.group_number=b.group_number(+)
PD_PDDL
(see 1)
The number of instances is 0.
PD_PDDO SELECT count(*)
FROM v$db_object_cache
PD_PDDS SELECT count(*)
FROM v$dispatcher, v$process
WHERE addr=paddr
PD_PDEL Number of messages beginning with the following prefixes that are written to the
Oracle alert log at the collection interval specified for the PD_PDEL record:
DBA-, EXP-, IMP-, LCC-, OER-,
ORA-, PCC-, PLS-, RTL-, or TNS
For the number of instances, use the maximum value written to the Oracle alert log
at the collection interval specified for the PD_PDEL record.
The Oracle alert log is a file called alert_Oracle_SID.log in the path that can be
obtained by the following SQL statement:
- Version earlier than Oracle 11g�f
SELECT name, value FROM v$parameter WHERE name=�fbackground_dump_dest�f
- Oracle 11g or later�f
SELECT name, value FROM v$diag_info WHERE name=�fDiag Trace�f
PD_PDES
(see 2)
SELECT count(*)
FROM v$sqlarea, sys.user$
WHERE ( (disk_reads/decode(executions,0,1,executions) > 1000
OR buffer_gets/decode(executions,0,1,executions) > 10000)
AND (parsing_user_id = user#) )
PD_PDEV SELECT count(*)
FROM v$session_event a, v$session b
WHERE a.sid=b.sid AND time_waited>=0
PD_PDGC The number of instances is 1.
PD_PDI The number of instances is 1.
PD_PDIA The number of instances is 1.
PD_PDLA SELECT count(*)
FROM v$latchholder a, v$session b,
v$latch c, v$latchname d, v$process e
WHERE c.latch#=d.latch# AND a.laddr(+)=c.addr
AND a.pid=e.pid(+) AND e.addr=b.paddr(+)
PD_PDLC SELECT count(*)
FROM v$librarycache
PD_PDLO SELECT /*+ ORDERED */ count(*)
FROM v$lock a, v$session b
WHERE a.sid=b.sid AND a.block >= 0
PD_PDLS The number of instances is 1.
PD_PDLW SELECT count(*)
FROM dba_waiters a, v$session b, v$session c
WHERE a.holding_session=b.sid AND a.waiting_session=c.sid
PD_PDMT The number of instances is 1.
PD_PDNH (see
1)
The number of instances is 0.
PD_PDNL The number of instances is 1.
PD_PDO SELECT count(*)
FROM v$option
PD_PDOC SELECT count(*)
FROM v$open_cursor a, v$session b
WHERE a.sid=b.sid
PD_PDOP SELECT count(*)
FROM v$process
PD_PDP SELECT count(*)
FROM v$parameter
PD_PDPQ SELECT count(*)
FROM v$pq_slave
PD_PDPS SELECT count(*)
FROM v$pq_sysstat
PD_PDQU SELECT count(*)
FROM v$queue, v$process
WHERE addr(+)=paddr
PD_PDRL SELECT count(*)
FROM v$resource_limit
PD_PDRS SELECT count(*)
FROM v$rollstat a, v$rollname b, sys.dba_rollback_segs c
WHERE a.usn=b.usn AND c.segment_name=b.name
PD_PDS SELECT count(*)
FROM v$session a, v$process b
WHERE a.paddr=b.addr
PD_PDS2 SELECT count(*)
FROM (SELECT DISTINCT sid
FROM v$sesstat a, v$statname b
WHERE a.statistic#=b.statistic#)
PD_PDS3 The number of instances is 1.
PD_PDSE SELECT count(*)
FROM v$system_event
PD_PDSG SELECT count(*)
FROM v$sgastat
PD_PDSH SELECT count(*)
FROM v$shared_server, v$process
WHERE paddr=addr
PD_PDSM Sum of the results of the following SQL statements:
- SELECT count(*)
FROM sys.dba_segments
- SELECT count(*)
FROM v$sort_segment
PD_PDSQ (see
3)
The number of instance is 0.
PD_PDSR SELECT count(*)
FROM v$sort_segment
PD_PDSS SELECT count(*)
FROM v$sesstat a, v$session b, v$statname c
WHERE a.sid=b.sid AND a.statistic#=c.statistic# AND value>=0
PD_PDST SELECT count(*)
FROM v$sysstat
PD_PDTA SELECT count(*)
FROM v$access a, v$session b
WHERE a.sid=b.sid
PD_PDTF SELECT count(*)
FROM sys.dba_tablespaces
PD_PDTL SELECT count(*)
FROM v$locked_object a, sys.dba_objects b
WHERE a.object_id=b.object_id
PD_PDTR SELECT count(*)
FROM v$transaction a, v$session b
WHERE RAWTOHEX(ses_addr)=RAWTOHEX(saddr)
PD_PDTS SELECT count(*)
FROM sys.dba_tablespaces
PD_PDV SELECT count(*)
FROM product_component_version
PD_PDWA SELECT count(*)
FROM v$session_wait a, v$session b
WHERE a.sid=b.sid AND a.wait_time>=0
PD_STAT The number of instances is 1.
Notes: 1. This record is a reserved record and cannot be used.
2. If the result of the SQL statement is 5 or greater, use 5 as the number of instances.
3. This record can only be used in real time.
Disk space requirements for Store database version 2.0
All records are stored in different directories and files for each summarization unit, date, and record type in the Store database version 2.0.
The following provides estimates for the following information: the amount of disk space required for the Store database version 2.0, the number of files and directories to be created, and the number of files to be opened by the Store service.
- Disk space requirements
The amount of disk space required for the Store database equals the total amount of disk space required for each record type.
 For the PI record type, the disk space requirements equal the total amount of disk space required for each summarization unit.
The formula for estimating the disk space requirements (X) for each record type (unit: bytes) is as follows:
X = {(e + 2) xf + (d + 60) x {((e + 2) x f) / (65,250 -d) + 1} (see 1)} xa / b x (c + 1) x 1.1
a: This value differs for each record type or summarization unit. For details, see Table 6 Values set to a, b, and c.
b: This value differs for each record type or summarization unit. For details, see Table 6 Values set to a, b, and c (see 2).
c: The setting value for the retention period of historical data (see 3). The units specified for this value differ for each record type or summarization unit. For details see Table 6 Values set to a, b, and c.
d: Size of the fixed part of each record that collects historical data (see 4)
e: Size of the variable part of each record that collects historical data (see 4)
f: Number of instances for each record that collects historical data (1 for a single instance record) (see 5). Note that if the number of instances is 2 or more, the value will be rounded up to a multiple of 4. 
For example, if the number of instances is 2, f will be 4. If the number of instances is 1, f will be 1.
Table 6 Values set to a, b, and c
Record
type
Summarization
unit
a b c
PI Minute 1,440 1 + (g - 1) / 60 (see 2) Retention period (unit: days)
Hour 24 1 + (g - 1) / 3,600 (see 2) Retention period (unit: days)
Day 7 1 + (g - 1) / 86,400 (see2) Retention period (unit: weeks)
Week 1 1 + (g - 1) / 604,800 (see2) Retention period (unit: weeks)
Month 1 1 + (g - 1) / 2,592,000(see 2) Retention period (unit:months)
Year 1 1 + (g - 1) / 31,622,400(see 2) Retention period (unit: years)
PD --- 1,440 g / 60 Retention period (unit: days)
Legend: g: The setting value for collection interval of historical data (unit: seconds)
---: Not applicable
Notes: 1. In the calculated value for {((e + 2) xf) / (65,250 - d) + 1}, discard digits after the decimal point.
2. In the calculated value for b of the PI record type, discard digits after the decimal point.
3. Table 7 Default retention period of the PI record type records lists the default retention period of the PI record type records for Store database version 2.0. 
The default retention period of the PD record type records is 7 days.
4. For details about the fixed part and variable part of each record, see the section that describes Agent for Oracle records in the Tuning Manager Application Reports Reference.
5. For details about the number of instances for each record, see the explanation in Disk space requirements for Store database version 1.0.
Table 7 Default retention period of the PI record type records
Data type Retention period
Minute-by-minute 1 day
Hourly 7 days
Daily 54 weeks
Weekly 54 weeks
Monthly 12 months
Yearly No limit
- Number of files
Following is the formula to estimate the number of files (N) to be created by the Store database:
N = 20 + 2 x (
(A11 + A12 + ... +A1m + m) +
(A21 + A22 + ... +A2m + m) +
(A31 + A32 + ... +A3m + m) +
(A41 + A42 + ... +A4m + m) +
(A51 + A52 + ... +A5m + m) +
(11 x m) +
(B1 + B2 + ... +Bn + n)
)
m: Number of records collected by the PI record type record
n: Number of records collected by the PD record type record
A11 - A1m: The setting value of the retention period for the minute-byminute record of each record of the PI record type (unit: days)
A21 - A2m: The setting value of the retention period for the hourly record for each record of the PI record type (unit: days)
A31 - A3m: The setting value of the retention period for the daily record for each record of the PI record type (unit: weeks)
A41 - A4m: The setting value of the retention period for the weekly record for each record of the PI record type (unit: weeks)
A51 - A5m: The setting value of the retention period for the monthly record for each record of the PI record type (unit: months)
B1 - Bn: The setting value of the retention period for each PD record type record (unit: days)
- Number of directories
Following is the formula to estimate the number of directories (N) to be created by the Store database:
N = 25 + 2 x ((A1max) + (A2max) + (A3max) + (A4max) + (A5max) + 11 + (Bmax))
A1max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is minutes (unit: days)
A2max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is hours (unit: days)
A3max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is days (unit: weeks)
A4max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is weeks (unit: weeks)
A5max: The maximum setting value of the retention period for the data where the summarization unit of a record collected by the PI record type is months (unit: months)
Bmax: The maximum setting value of the retention period for each PD record type record (unit: days)
- Number of files to be opened by the Store service
Following is the formula to estimate the number of files (N) to be opened by the Store service:
N = 20 + 2 x (6 x m +n)
m: Number of records collected by the PI record type record
n: Number of records collected by the PD record type record