Skip to main content

Configuring Validata Historian

You may host Validata Historian (Validata's metadata repository) on Derby, Oracle, or PostgreSQL. By default, Validata uses the integrated, preconfigured Derby instance. To use PostgreSQL instead, follow the instructions in this section.

Caution

When Validata is processing very large amounts of data at high velocity, Derby may fail to reclaim the unused space in the metadata repository, resulting in it eventually filling all available disk space and crashing. In this situation, Validata will crash and restart will fail. To work around this issue, we recommend hosting Validata Historian on Oracle or PostgreSQL instead.

As a short-term workaround for Derby, use the following command to compress the metadata repository tables:

validata/bin/derbyTools.sh -A compressDb

This uses a lot of Derby resources, so it should be performed when Validata is not busy.

Changing the Derby password

In a production environment, we strongly recommend changing the Derby password from its default. The JAVA_HOME environment variable must be set for the ./changeDerbyPassword.sh script to work.

  • Stop Validata and Derby.

  • Open a terminal and change to the validata directory.

  • Change the password in Derby:

    • sudo su - validata ./bin/changeDerbyPassword.sh

  • When prompted, enter the username waction, the current password (in a new installation, the password is w@ct10n), and the new password.

  • Change the password in Validata's keystore:

    • sudo su - validata ./bin/sksConfig.sh -p

  • Restart Derby and Validata.

Configuring Oracle to host Validata Historian

We do not recommend hosting Validata Historian on the same Oracle instance you use for other Striim or third-party products.

You may host Validata's metadata repository on any version of Oracle that is supported by the bundled JDBC driver ojdbc-21.6.jar.

  1. Copy the SQL scripts /opt/validata/conf/DefineMetadataReposOracle.sql and DefineMeteringReposOracle.sqlto the Oracle host.

  2. Using sqlplus, log in to Oracle as an administrator and create the user Validata will use to create, write to, and read from the repository tables (replace ****** with a strong password):

    create user validatarepo identified by ******;
grant connect, resource to validatarepo;

  3. Log out of sqlplus, log in again as the user you just created, and run the DefineMetadataReposOracle.sql and DefineMeteringReposOracle.sql scripts.

Configuring PostgreSQL to host Validata Historian

We do not recommend hosting Validata Historian on the same Oracle instance you use for other Striim or third-party products.

You may host Validata Historian on any version of PostgreSQL that is supported by the bundled JDBC driver postgresql-42.4.0.jar.

  1. Copy the SQL scripts /opt/validata/conf/DefineMetadataReposPostgres.sql and DefineMeteringReposPostgres.sql to the PostgreSQL host.

  2. Using psql, connect to PostgreSQL as an administrator and create the user Validata will use to create, write to, and read from the repository tables (replace ****** with a strong password):

    sudo -u postgres psql
create user validata with password '******';
create database validatarepo;
grant all on database validatarepo to validata;
\q

  3. Connect again as the user you just created, create a schema, set the search path, and run the DefineMetadataReposPostgres.sql and DefineMeteringReposPostgres.sql scripts:

    psql -U validata -d validatarepo;
create schema validata;
alter role validata set search_path to validata;
\q
psql -U validata -d validatarepo -f DefineMetadataReposPostgres.sql
psql -U validata -d validatarepo -f DefineMeteringReposPostgres.sql