Configuring the Database Schemas | ||
---|---|---|
Previous | Next | |
Planning the Installation | Deployment and Configuration Overview |
This section explains how to configure the database schemas for the repository and data locations.
Before installing Semarchy Convergence for MDM, you must create an Oracle schema for the repository. You can create it manually or use your database administration interface for this purpose. In this section, we provide a sample script for creating this schema. Make sure to adapt this script to your database configuration.
CREATE USER <repository_user_name> IDENTIFIED BY
<repository_user_password> DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP;
GRANT CONNECT,RESOURCE TO <repository_user_name>;
Note: Store the values of the
<repository_user_name>
and<repository_user_password>
as you will need them later for creating the datasource to access the repository.
You do not need to create the data locations schemas at installation time, but it is recommended to plan them as part of the installation and configuration effort. You can create them manually or use your database administration interface for this purpose. In this section, we provide a sample script for creating a data location schema. Make sure to adapt this script to your database configuration and duplicate it to create the schemas for all data locations.
CREATE USER <data_location_user_name> IDENTIFIED BY
<data_location_user_password> DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP;
GRANT CONNECT,RESOURCE TO <data_location_user_name>;
Note: Store the values of the
<data_location_user_name>
and<data_location_user_password>
as you will need them later for creating the datasource to access the data location.
Note: The repository and data locations do not necessary need to be located in the same Oracle instance. The same schema should not be used for the repository and a data location, and you cannot use the same schema for several data locations.
The following considerations should be taken into account when sizing the repository schema:
To purge the logs:
Note: It is possible to trigger job logs purges through web services. The Administration Service exposes such operations.
The following considerations should be taken into account when sizing the data location schema:
A recommended original sizing is to add the source data volume pushed for each entity by all publishers (the overall input) and multiply it by a factor of 10. It is recommended after the original sizing to monitor the size of the data location schema in the normal course of operations and adjust the sizing appropriately.
Note: The same sizing considerations applies to both the data and temporary tablespaces in the case of the data locations, as the database engine is used for most of the processing effort in the certification process.
Data Retention Policies can be created to define the volume of data to retain in the data locations, and Data Purges can be scheduled to trigger the pruning of unnecessary data. Defining Retention Policies is covered in the "Securing Data" chapter of the "Semarchy Convergence for MDM Developer’s Guide". Data Purges are described in the "Managing Execution" chapter of the "Semarchy Convergence for MDM Administration Guide".
Previous | Top | Next |
Planning the Installation | Deployment and Configuration Overview |