Key Manager Oracle Database Migration

This section provides instructions about how to migrate the Key Manager database from Oracle 11 to Oracle 12.

Prevent Key Manager from running jobs during the procedure.

a. To prevent Key Manager from picking up new jobs, set the back-end setting at Settings→General→Backend→Max Processes to 0. Wait for all running jobs to finish.

b. Stop the Key Manager services. If using agents, also stop Tectia Server.
Export the old Key Manager Oracle database using a method approved by your internal organization.
Move the database export file to the new Oracle 12 database server.
On the new Oracle 12 database server, import the Key Manager database file.
On Key Manager servers, edit the /opt/sshmgr/app/localsettings.py file to reflect the changes in the database. Typically you need to edit the following lines:
```
'NAME': 'databaseSID',
'HOST': 'database.address.example.com',
```
The NAME parameter takes the database SID.
The HOST parameter takes the address of the database.

Make sure Key Manager servers can connect to the new database machine, and if needed have Key Manager server addresses whitelisted in the database configuration.
Optional: If the database user password has changed, run the following command on any Key Manager server:
```
# /opt/sshmgr/bin/ssh-mgr-setup --change-db-passwd
```
Start the new database.
Restart any Key Manager services that were stopped during the upgrade. Also restore the Max Processes settings to their former values. Your Key Manager instance should now be running against the new database version. You may verify that all the data and functionality matches to the pre-upgrade state.