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 PlanningSystem Requirements and Compatibility.
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.
...
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 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. |
...
Option | Setting |
SQL Server Edition | Standard or Enterprise |
Version | See Compatibility Guide and Upgrade Planning System Requirements and Compatibility. |
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 |
...
Installation
Option | Setting |
Version | See Compatibility Guide and Upgrade PlanningSystem Requirements and Compatibility. |
| Max Server Memory | At least 2 GB |
The following configuration parameters must be set in my.cnf | |
datadir | Ensure that the data dir being used has sufficient space for the initial period of PhixFlow operation. This is in the [mysqld] section of the my.cnf file. |
| binlog_format | mixed This must be added to the [mysqld] section of the my.cnf file. |
wait_timeout | 28800 (this is the default, but some installation processes set this to a much lower value) This must be in the [mysqld] section of the my.cnf file. |
| The following configuration parameters can optionally be set in my.cnf | |
| log_bin_trust_function_creators | 1 This If set in my.cnf, this must be added to the [mysqld] section of the my.cnf file. For details on why this setting is recommended - and the alternatives if you do not want to set in this my.cnf , - see Running non-deterministic functions |
Example
If you add all parameters above to the my.cnf, including the optional parameters, then the end of the [mysqld] section of you your my.cnf file should look something like this:
| Code Block |
|---|
[mysqld] ... datadir = /var/lib/mysql ... wait_timeout = 28800 ... binlog_format = mixed log_bin_trust_function_creators = 1 |
Database
The following settings are parameters of required for the PhixFlow database required by a PhixFlow installation.
| Note |
|---|
All of these parameters are reflected in the example MariaDB database creation command in Configure the Database. |
You will need a database, and a login with all privileges on that database. The database must be created with the following options:
...
PhixFlow's migration scripts sometimes require the use of non-deterministic functions. To run, these require either a setting (log_bin_trust_function_creators) to be updated, or to be run with sufficient privileges.
...
You can permanently allow non-deterministic functions to run in migration scripts by updating updating the setting log_bin_trust_function_creators in the my.cnf file. This is convenient, because you don't have to remember to make any changes to your session when migrating. However, if running PhixFlow migration scripts. If you don't want to make this permanent change, see the following section.
Setting Instructions for setting log_bin_trust_function_creators in the my.cnf file is an optional parameter recommended are given in MariaDB installation.
Session change to allow non-deterministic functions
You can either do this in a session, or to make the setting update permanent (that is, it will persist after a database restart) add it to the my.cnf file.If you do not update the log_bin_trust_function_creators setting in my.cnf, you must make sure that your session either has this setting updated, or that you run migration scripts with sufficient privileges. Full details for doing this are given in Upgrading PhixFlow.
Publishing space
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Notes
Windows / Antivirus
MariaDB is not compatible with on-access anti-virus software so this must be disabled for the MariaDB data folder(s).