Database Disk Configuration
Database disk configuration and usage is the biggest bottleneck for an ActiveMatrix BPM system. Since BPM (excepting Pageflows) makes heavy use of the database, ensuring that the disk system for the database is well configured is essential, as well as understanding how the physical disks are configured on which the Oracle data and temp files are located.
Ensure that the main database files for ActiveMatrix BPM are on a fast disk system, separated from the operating system and other heavily used databases. The database files for the ActiveMatrix BPM database need to be resized according to the expected amount of data to be used during system operation.
The following SQL can be used to list tablespaces, their sizes, and the percentage free:
set linesize 140
SELECT df.tablespace_name TABLESPACE, df.total_space TOTAL_SPACE,
fs.free_space FREE_SPACE, df.total_space_mb TOTAL_SPACE_MB,
(df.total_space_mb - fs.free_space_mb) USED_SPACE_MB,
fs.free_space_mb FREE_SPACE_MB,
ROUND(100 * (fs.free_space / df.total_space),2) PCT_FREE
FROM (SELECT tablespace_name, SUM(bytes) TOTAL_SPACE,
ROUND(SUM(bytes) / 1048576) TOTAL_SPACE_MB
FROM dba_data_files
GROUP BY tablespace_name) df,
(SELECT tablespace_name, SUM(bytes) FREE_SPACE,
ROUND(SUM(bytes) / 1048576) FREE_SPACE_MB
FROM dba_free_space
GROUP BY tablespace_name) fs
WHERE df.tablespace_name = fs.tablespace_name(+)
ORDER BY fs.tablespace_name;
The specific BPM data and temp files should be on separate disks. Monitoring of the operating disks on the Oracle system and use of the Oracle Enterprise Manager’s (OEM) I/O monitoring can help identify any bottlenecks.