When using Oracle, the following initial database configuration is recommended. However, some of the options below may need to change over time as the work carried out by PhixFlow increases.
General
Option | Setting |
Oracle Edition | See Oracle planningPlanning |
Version | See System Requirements and Compatibility. Patches should be applied as advised by Oracle. |
NLS_CHARACTERSET | AL32UTF8 |
NLS_LANG | american_america. AL32UTF8 (Not used by PhixFlow. For support purposes only) |
NLS_SORT | BINARY |
NLS_COMP | BINARY |
NLS_NCHAR_CHARACTERSET | NCHARS are not used by PhixFlow however set to AL32UTF8 |
sga_max_size | At least 2 GB For larger systems, this should be provided by the sizing process. |
SID | phixflow |
Connection Type | Dedicated |
Max Number of Connections | Variable, depending on system size and workload. Typically >100. For larger systems, this should be provided by the sizing process. |
Storage Type | Any, subject to throughput requirements. |
Storage / Tablespaces
Tablespace Name | Size | I/O Rate (Mb/s sustained) |
(Redo Logs) | 3 x 0.5Gb | 10Mb/s |
CONFIG_DATA_01 | 2 GB | 0.5Mb/s |
ANALYSIS_DATA_01 | 100 GB | 10Mb/s |
UNDOTBS1 (UNDO) | 10GB | 10Mb/s |
...
- The storage area sizes and I/O Rates are for a typical small server using conventional hard disk drives, and should be revised as part of the sizing process. Rates are quoted in Megabytes
- The I/O Rates are for sustained data transfers spanning many tens of minutes. Peak transfer rates, assuming transfers to/from fast memory buffers, may be much higher, but are not significant unless solid-state disks are used.
Datapump
To support maintenance backups, the following datapump directory is required configured as:
CREATE DIRECTORY dpump_phixflow AS ‘/u02/phixflow/dbexport’;
Database User
The following Oracle user should be set up:
...