Oracle requisites

<< Click to Display Table of Contents >>

Navigation:  Bizagi Engine > Bizagi system administration > Database server configuration > Database requisites >

Oracle requisites

Overview

Bizagi Engine requires a database server for your processes repository.

Oracle database is supported for the database server configuration.

 

 

Supported versions and editions

The following are supported:

 

VERSION

VERSION NUMBER

Oracle 12c

12.1.0.2 or above

Oracle 11g R2

11.2.0.3 or above

 

Supported for Standard and Enterprise editions.

Express (XE) edition is not supported.

 

note_pin

Supported character sets for Oracle databases are both Unicode and non-Unicode. However, take into consideration the following:

Migrating Oracle databases to Unicode (from non-unicode character sets) is not supported.

For Unicode Oracle databases,

String attributes will hold a maximum of 1000 characters.

If you need more than 1000 characters, extended text attributes should be used.

 

Prerequisites and recommendations

When configuring your Oracle database, version 11g R2, keep in mind:

 

1. If you are using archiving (enabling the Archive mode), we recommend to use 2 destinations for your archivelog.

 

2. We recommend using Automatic Shared Memory Management (ASMM configuration).

It is also required to assign a minimum of:

4 Giga bytes for the size of the SGA memory.

3 Giga bytes for the size of the PGA memory.

 

 

PGA_SGA

 

3. We recommend assigning a block size of at least 8000 bytes, and assigning 300 processes.

 

Block_and_Processes

 

4. We recommend using 4 redo logs groups, and each one of them assigned to use 3 Giga bytes.

 

note_pin

Note that the above recommendations are strictly the minimum prerequisites to set your Oracle 11g instance.

Further sizing considerations will depend on your project's characteristics, and a detailed analysis to determine scalability and additional demands, is recommended as well.

 

RAC considerations

When using an Oracle cluster (i.e, RAC), consider the usual recommendations as issued by the vendor itself (i.e Oracle), such as using a high speed network connection for Heartbeat purposes.

 

Required Bizagi configuration

To use an Oracle instance to work with Bizagi, you need to create a specific user to be used by Bizagi.

You will need to create the user that Bizagi relies on, in your Oracle instance by running a script.

This user is called the BizagiAdmon user.

 

 

note_pin

For projects running in a .NET platform, you will need as an additional step, to install the ODP.NET component at the Bizagi server.

 

Verifying Oracle configuration

Carry out the steps described next, to ensure that your Oracle instance is set to work with Bizagi.

 

 

Which version do I have?

To determine your version of Oracle, connect to your database instance and run:

select * from v$version;

 

When using Oracle 11g R2, you should ensure that your version is 11.2.0.3.x or higher:

 

Oracle11Version

 

 

Checking the required configuration

Create a specific user to be used by Bizagi.

Bizagi relies on a Oracle user for administration and project tasks (i.e, to create the metadata structure of a Bizagi project, create backups, etc).

This user is called BizagiAdmon and it is a prerequisite to create a Bizagi project at an Oracle instance.

 

To create the user by running a SQL script, follow these instructions:

 

Connect to your Oracle instance as the sys user (sysdba)

 

ConnectSysdba

 

Edit the ConfigureInstanceForBizAgi-[Oracle_Version].sql. script

Locate Bizagi installation path and browse into the Project model's database folder (by default at C:\Program Files\BizAgi\BizAgi Enterprise\ProjectModel\Database\).

For Oracle 11g R2, edit the script called ConfigureInstanceForBizAgi-11g.sql.

 

note_pin

The aforementioned script has a .basql file extension.

In other to retrieve the actual script, ensure you rename this file to a .zip and then extract its contents.

 

To edit the script, make sure you remove the comment lines that define the following variables, and edit their values:

BA_TABLES_DATAFILES_DIR: Should be replaced with the path where you want to create the tablespaces datafiles.

BA_LOBS_DATAFILES_DIR: Should be replaced with the path where you want to create the datafiles holding Bizagi LOBS.

BA_INDEXES_DATAFILES_DIR: Should be replaced with the path where you want to create the indexes datafiles.

BA_BACKUP_PATH: Should be replaced with the path where you want to store automatic backups.

BA_BIZAGIADMON_PASSWORD: Should be replaced with the password for the BizagiAdmon user.

 

BizAgiAdmonScript

 

Run the script.

Run the edited script and make sure it is a successful operation.

 

ExecuteBizAgiAdmon

 

note_pin

This script is subject to change in each Bizagi version.

Therefore, you should take the mentioned script that corresponds exactly to the installed version of Bizagi.

 

 

Configure the optimizer.

The following is applicable to Oracle versions 12 and it is a recommended guideline due to Oracle's report on BUG 21615091 (https://support.oracle.com/rs?type=bug&id=21615091).

Connect with an user with DBA rights (e.g, DBA, SYSTEM) and run the following script to configure the optimizer:

ALTER SYSTEM SET "_optimizer_reduce_groupby_key" = FALSE;

 

 

 

Additional step

If your project is running in a .NET platform, you will need to install the ODP.NET component as described at Installing Oracle Data Provider.