Striim 4.0.4 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. Back up Derby as described in Backing up the metadata repository host.

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

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

    cd /opt/striim
    sudo bin/tools.sh -A export -F export.json
    
  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 and change the value of MetaDataRepositoryLocation to reflect the new repository host (see the Oracle or PostgreSQL section of Setting startUp.properties for the metadata repository).

  7. On each server in the cluster, update the metadata repository user's password in the Striim keystore:

    cd /opt/striim
    sudo su - striim bin/sksConfig.sh -p
  8. 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 4.0.4 -r oracle
    

    For PostgreSQL:

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

    sudo systemctl disable striim-dbms

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

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