PhixFlow Help

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

PhixFlow stores configuration, analysis and task data in any of Oracle, SQL Server or MariaDB (a dialect of MySQL). For version compatability, please refer to Compatibility Guide and Upgrade Planning.

There are many issues to consider when installing a database, several of which will be concerned with your company’s own internal procedures, backup policies etc. The notes below describe just the core requirements which will enable the installation of PhixFlow to be completed. However, the DBA who carries out the installation should ensure that the database is configured to be performant for the volumes of data that PhixFlow is expected to process.

In normal operation, the database will require the usual ongoing management e.g. monitoring database files to ensure that the database does not run out of space. Over time, the data held in the PhixFlow database will grow naturally as more Controls are configured. However, model designers should ensure that archive policies are configured within PhixFlow to free up space when data is no longer needed.

Oracle

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

PhixFlow runs on all Oracle Database editions.

PhixFlow partitioned streams (optional) require the Enterprise Edition Partitioning option.

Version

See Compatibility Guide and Upgrade Planning.

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


  1. 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
  2. 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:

User

SQL Script

phixflow

CREATE USER phixflow PROFILE DEFAULT

IDENTIFIED BY <password>

DEFAULT TABLESPACE CONFIG_DATA_01

QUOTA UNLIMITED ON CONFIG_DATA_01

QUOTA UNLIMITED ON ANALYSIS_DATA_01

ACCOUNT UNLOCK;


GRANT CREATE SESSION TO phixflow;

GRANT CREATE TABLE TO phixflow;

GRANT CREATE VIEW TO phixflow;

GRANT READ,WRITE ON DIRECTORY phixflow_dpump TO phixflow;


Microsoft SQL Server

When using SQL Server, 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.

Server

Option

Setting

SQL Server Edition

Standard or Enterprise

Version

See Compatibility Guide and Upgrade Planning.

Service Name

(Please provide to PhixFlow installation consultant)

Collation Character set

Latin1_General_CI_AS

Max Server Memory

At least 2 GB

Server Authentication

SQL Server and Windows Authentication Mode

Logins

Create a new login as follows:

Parameter

Setting

Login Name

phixflow

Authentication

SQL Server

Password

Please provide to the PhixFlow installation consultant

Enforce password policy

No

Default database

Set to phixflow once the phixflow database has been created (below)

Default language

As appropriate

Database

Create a new database as follows:

Parameter

Setting

Name

phixflow

Owner

phixflow

Collation

Latin1_General_CI_AS

READ_COMMITTED_SNAPSHOT

ON

Filegroups

Name

Default

PRIMARY

Yes

ANALYSIS_DATA


Database Files

Logical Name

Setting

phixflow

Type:                  Rows Data

Filegroup:           PRIMARY

Initial Size:         2000 MB

Autogrowth:       10% Unrestricted (or as per management policy)

Path:                    (As per management policy)

phixflow_data_01

Type:                  Rows Data

Filegroup:                            ANALYSIS_DATA

Initial Size:         100,000 MB

Autogrowth:       10% Unrestricted (or as per management policy)

Path:                    (As per management policy)

phixflow_log

Type:                  Log

Initial Size:         1000 MB

Autogrowth:       10% Unrestricted (or as per management policy)

Path:                    (As per management policy)

MariaDB

MariaDB is a dialect of MySQL.

When using MariaDB, 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.

Server

Option

Setting

Version

See Compatibility Guide and Upgrade Planning.

The following configuration parameters must be set

datadir

A directory on a partition set up to store the MySQL data files.

character_set_server

utf8

collation_server

utf8_bin

Max Server Memory

At least 2 GB

Logins

Create a new login as follows:

Parameter

Setting

Login Name

phixflow

Password

Please provide to the PhixFlow installation consultant

Database

Create a new database as follows:

Parameter

Setting

Name

phixflow

Notes

Windows / Antivirus

MariaDB is not compatible with on-access anti-virus software so this must be disabled for the MariaDB data folder(s).

  • No labels