Execute these steps to upgrade an existing Connect database schema.
If Connect is installed in /opt/connect/kc, go to the install subdirectory (i.e. /opt/connect/kc/install).

Run updatedb.sh (sh updatedb.sh)
Run seeddb.sh (sh seeddb.sh)

When using seeddb.sh, you must specify which company entity you wish to upgrade. For example:

sh ./seeddb.sh Default

where Default is the default company.

If your instance has more than one company, this step will need to be performed for each company. For example:

sh ./seeddb.sh Company1

sh ./seeddb.sh Company2

sh ./seeddb.sh Company3

etc.
Note: The updatedb and seeddb scripts require the database.connect property in the database.properties file to be unencrypted.

Troubleshooting

Updatedb will write a log file in /opt/connect/kc/initdb/logs.

Seeddb will write a log file in /opt/connect/kc/logs.

Encrypting and Re-Encrypting Database Passwords

If you have configured a non-default encryption provider, you must convert the user passwords in the database to the new encryption scheme. To do this, run the cryptoutil utility:

cd /opt/connect/kc/install
sh cryptoutil.sh -migrate 

This will re-encrypt each user password using the new encryption scheme.