Upgrading databases

If you plan to leave the database on the same system, no special configuration is required. If you're moving to a new database engine or system, migrate the system first, then upgrade.

If you're upgrading to a version whose database schema is different from the previous version, the application automatically detects the difference after you've upgraded. When you next start the application and go to the Admin Console, you will be prompted to start the database upgrade. This is a necessary step before you can start using the application after an upgrade. You don't need to run any database-related upgrade scripts unless you are moving to a different database engine.

To upgrade the database:

  1. Shut down all the services.
  2. If you're using the same database engine (for example, moving SQL Server to SQL Server), back up and restore the database to the new instance.
  3. If you're using a different database engine after the upgrade (for example, moving Oracle to PostgreSQL), use scripts and ETL tools to build the database and transfer the data. For more information about the properties you need to pay attention to when migrating a database, see Restoring database with persistent properties.
  4. Start new web servers and point them to the new database engine.
  5. After you restart Jive, the upgrade process begins, and the database schema is upgraded.

Note that if you upgrade from Jive 7.x.x, on Oracle databases, you may get an error because the null constraint already exists. The error may look like this: 

java.sql.SQLException: ORA-01442: column to be modified to NOT NULL is already NOT NULL

This error does not affect the installation, and you should ignore it.