Specification for a minimal installation or testing platform
...
Software Edition
PhixFlow runs on all Oracle Database editions.
If you need to use PhixFlow partitioned tables, you need the Enterprise Edition Partitioning option. Check with you PhixFlow implementation team to see if you need this option.
Pubishing Space
| Note |
|---|
To ensure that PhixFlow can publish data changes, its database must have enough space to hold a copy of the largest table. For Oracle, this space is in the temporary table space. |
Indicative Sizings
Specification for a Small Installation
The following shows indicative sizing for a small installation.
Disk | Size |
Disk 1 | 400 GB |
Disk 1 partitioning
Partition | Approx. Size | Purpose | Mount point |
1 | 20 GB | Operating System |
2 | 20 GB | Paging |
3 |
200 GB | Database files | /u01 or c:/u01 Referred to below as $database |
4 |
100 GB | Application installations and file data | /u02 or c:/u02 Referred to below as $app |
5 |
50 GB | Archive Log space | /archive or c:/archive |
Notes: All file system path names are written using a forward slash ‘/’ directory separator. On Windows forward and back slashes are considered to be equivalent, though there are still a few areas where back slashes must be used.
Specification for a
...
Three Disk groups will have the following usable space:
Disk Group | Nbr Drives | Raid | Approx Usable Space |
Disk Group 1 | 8 * 300GB | 5 (7+1) | 1900GB |
Disk Group 2 | 4 * 146GB | 1+0 | 270GB |
Disk Group 3 | 2 * 146GB | 1+0 | 135GB |
Disk Group 1
...
Medium Installation
For medium and large implementations the database should be configured for high performance throughput. In particular database performance is significantly affected by the way that the database server disks are configured. Organisations requiring this size of server will generally have their own database administrators who are familiar with this level of planning. However, for planning purposes, the following shows an indicative sizing for a set of disks, and the partitioning of each of these disks, for a medium sized installation.
Disk | Size | Used for | Notes |
Disk 1 | 1500 GB | Oracle Data Tablespace | Disk chosen should be optimal for data throughput. |
Disk 2 | 300 GB | Oracle Redo | If this is required (see Backup). |
Disk 3 | 150 GB | Oracle Undo |
Disk 1 Partitioning
Partition | Approx. Size | Purpose | Mount point |
1 | 20 GB | Operating System |
2 | 20 GB | Paging |
3 |
1000 GB | Database files | /u01 or c:/u01 Referred to below as $database | |
4 | 200 GB | Application installations and file data | /u02 or c:/u02 Referred to below as $app |
5 | 100GB | Archive Log | /archive or C:/archive |
Disk
...
2
...
With 4 * 146Gb drives in a Raid 1+0 configuration, there is approximately 270GB of usable space. The server disks should be partitioned as follows:
Partitioning
Partition | Approx. Size | Purpose | Mount point |
1 |
140 GB | Oracle Redo | /redo1 |
2 |
140 GB | Oracle Redo | /redo2 |
Disk
...
3
...
With 2 * 146Gb drives in a Raid 1+0 configuration, there is approximately 135GB of usable space. The server disks should be partitioned as follows:
Partitioning
Partition | Approx. Size | Purpose | Mount point |
1 |
140 GB | Oracle Undo | /undo |