Importing the metadata and completing the upgrade
Complete the steps in Upgrading in CentOS or Upgrading in Ubuntu.
If the metadata repository is hosted on Derby, skip this step.
If the metadata repository is hosted on Oracle, log in to
sqlplus
as the user created in Configuring Oracle to host the metadata repository and run the/opt/striim/conf/DefineMetadataReposOracle.sql
andDefineMeteringReposOracle.sql
scripts to create new repository tables.If the metadata repository is hosted on PostgreSQL, log in to
psql
as the user created in Configuring PostgreSQL to host the metadata repository and run the/opt/striim/conf/DefineMetadataReposPostgres.sql
andDefineMeteringReposPostgres.sql
scripts to create new repository tables.On each server in the cluster, enter the following command to copy your Striim configuration (adjust as necessary if you backed up your files to a different location):
cp /opt/striim/conf-backup/startUp.properties /opt/striim/conf
If you are upgrading from 3.9.8 or later, also enter the following commands:
cp /opt/striim/conf-backup/sks.jks /opt/striim/conf cp /opt/striim/conf-backup/sksKey.pws /opt/striim/conf sudo chown striim /opt/striim/conf/sks.jks sudo chown striim /opt/striim/conf/sksKey.pws
If you are upgrading from 3.9.8 or later, skip this step.
On each server in the cluster, edit
/opt/striim/startUp.properties
and delete the lines for WAClusterPassword and WAAdminPassword.If you are upgrading from 3.9.8 or later, skip this step.
On one server, run
sudo su - striim /opt/striim/bin/sksConfig.sh
and enter passwords for the Striim keystore and the admin and sys users. If hosting the metadata repository on Oracle or PostgreSQL, enter that password as well (see Configuring Striim's metadata repository). If you are using a Bash or Bourne shell, characters other than letters, numbers, and the following punctuation marks must be escaped:, . _ + : @ % / -
Copy
sks.jks
snfsksKsy.pwd
from/opt/striim/conf/
on that server to/opt/striim/conf/
on all other servers and on all servers assign ownership of those files to Striim:sudo chown striim sks.jks sudo chown striim sksKey.pwd
Import the metadata. On the server where you exported the metadata when Preparing to upgrade and exporting the metadata, enter the following commands:
If the metadata repository is hosted on Derby:
cd /opt/striim sudo bin/tools.sh -A import -F export.json -f <old version>
For example, if upgrading from 3.8.4:
sudo bin/tools.sh -A import -F export.json -f 3.8.4
If the metadata repository is hosted on Oracle:
cd /opt/striim sudo bin/tools.sh -A import -F export.json -f <old version> -r oracle
If the metadata repository is hosted on PostgreSQL:
cd /opt/striim sudo bin/tools.sh -A import -F export.json -f <old version> -r postgres
When import is complete, reboot that system to verify that Striim restarts automatically.
Alternatively, to start without rebooting:
For CentOS 6.x or Ubuntu 14.04, enter the following commands:
If the metadata repository is hosted on Derby, on the Derby host only:
sudo start striim-dbms
Wait ten seconds, then enter:
sudo start striim-node sudo tail -F /opt/striim/logs/striim-node.log
For CentOS 7.x or Ubuntu 16.04 or later, enter the following commands:
If the metadata repository is hosted on Derby, on the derby host only:
sudo systemctl enable striim-dbms sudo systemctl start striim-dbms
Wait ten seconds, then enter:
sudo systemctl enable striim-node sudo systemctl start striim-node sudo tail -F /opt/striim/logs/striim-node.log
When you see the message
Please go to ... to administer, or use console
, Striim is running.Log in to verify that Striim is running, then reboot the other servers in the cluster, or start each server manually using the commands above.
Reload any open processors (see Loading and unloading open processors).
Upgrade and start all Forwarding Agents (see Upgrading Forwarding Agents).