Migrating databases from a multi-database Db2uInstance

Multiple databases per Db2uInstance is not supported in Db2 Operator V2. If you have multiple-databases per Db2uInstance in your current Legacy operator deployment, you can move secondary databases to their own Db2uInstance.

About this task

Important: This topic is for Db2 Operator V2 deployments. If you are currently using a legacy deployment, refer to the documentation in Legacy deployment documentation. If you are unsure which deployment type you are using, use the version checker.

Db2 Operator V2 does not support multiple databases within a single Db2uInstance. If your legacy deployment uses this configuration, move each secondary database to its own Db2uInstance by backing it up, restoring it to a new instance, and then removing it from the original instance.

Procedure

  1. Create a new Db2uInstance. For more information, see Deploying Db2 using a custom resource.
  2. On the existing Db2uInstance, backup the database. For more information, see Backing up and restoring a Db2 or Db2 Warehouse database.
  3. On the new Db2uInstance, restore the database using the backup from step 2. For more information, see Restoring a Db2 or Db2 Warehouse database.
  4. Once the secondary database is successfully restored, drop the secondary database from the existing Db2uInstance using the manage_databases command.