Striim 3.9.7 documentation

Moving the metadata repository to Oracle or PostgreSQL

To move the metadata repository from the Striim internal Derby instance to Oracle or PostgreSQL, do the following. This will require bringing down the Striim cluster, so you should schedule it for a maintenance window.

  1. Follow the instructions in Configuring Oracle to host the metadata repository or Configuring PostgreSQL to host the metadata repository.

  2. Stop the Derby instance (striim-dbms) and all servers in the Striim cluster (see Starting and stopping Striim).

  3. On the server running Derby, export the metadata:

    cd /opt/striim
    sudo bin/tools.sh -A export -F export.json
    
  4. Follow the instructions in Configuring Oracle to host the metadata repository or Configuring PostgreSQL to host the metadata repository.

  5. Make a backup copy of startUp.properties:

    cd /opt/striim/conf
    cp startUp.properties *.bak
  6. On each server in the cluster, edit startUp.properties to reflect the new repository host.

    For Oracle:

    MetadataDb=oracle
    MetaDataRepositoryLocation=<connection URL>
    MetaDataRepositoryDBname=striimrepo
    MetaDataRepositoryUname=striimrepo
    MetaDataRepositoryPass=<encrypted password for Oracle user>

    If you use an SID, the connection URL has the format jdbc:oracle:thin:@<IP address>:<SID>, for example, jdbc:oracle:thin:@192.0.2.0:orcl. If you use a service name, it has the format jdbc:oracle:thin:@<IP address>/<service name>, for example, jdbc:oracle:thin:@192.0.2.0/orcl. In a high availability active-standby or RAC environment, specify all servers, for example, MetaDataRepositoryLocation=jdbc:oracle:thin:@(DESCRIPTION_LIST=(LOAD_BALANCE=off)(FAILOVER=on)(DESCRIPTION= (CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST= 192.0.2.100)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=racdb.localdomain)))(DESCRIPTION= (CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST= 192.0.2.101)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=racdb.localdomain)))) (see Features Specific to JDBC Thin for more information.)

    For PostgreSQL:

    MetadataDb=postgres
    MetaDataRepositoryLocation=<connection URL>
    MetaDataRepositoryDBname=striimrepo
    MetaDataRepositoryUname=striim
    MetaDataRepositoryPass=<encrypted password for PostgreSQL user>

    The PostgreSQL connection URL has the format <IP address>:<port>/striimrepo, for example 192.0.2.100:5432/striimrepo. In a high availability environment, specify the IP addresses of both the primary and standby servers, separated by a comma, for example, 192.0.2.100,192.0.2.101:5432/striimrepo.

  7. On the server where you exported the metadata, import it.

    For Oracle:

    cd /opt/striim
    sudo bin/tools.sh -A import -F export.json -f 3.9.7 -r oracle
    

    For PostgreSQL:

    cd /opt/striim
    sudo bin/tools.sh -A import -F export.json -f 3.9.7 -r postgres
    
  8. Stop Derby from starting automatically.

    sudo systemctl disable striim-dbms

    If you are Running Striim as a process in Linux or OS X, set NO_DERBY=true as an environment variable before running server.sh.

  9. Restart the Striim cluster (see Starting and stopping Striim).