Reconfiguring the data store connection

Reconfigure the data store if the connection for the data store changes.

  1. Make a backup of the database. On the database server that runs DB2 Universal Database for IBM Security Identity Manager, complete the following steps:

    1. Log on as the instance owner. For example: db2admin.

    2. Close all connections to the ISIM database. Stop DB2 Universal Database or any other tools. If necessary, run the following command to force all connections to close:

      db2 force application al.

    3. Back up the data store database:

      db2 backup database IDM_DB to OLD_DB2_BACKUP_DI. Where:

      • IDB_DB is the name of ISIM data store database. For example: idmdb
      • OLD_DB2_BACKUP_DIR is a directory path to store the backup. For example:

        Linux or UNIX systems
        /tmp/db2

        Windows systems
        c:\temp\db2

  2. Restore the backup of the database.

    Install the new version of DB2 Universal Database. For this reconfiguration, ensure that we create the database instance and database with the same name. Users must have the same rights and privileges as setup on the previous system..

    To create a database instance and a database, see Database installation and configuration.

    Copy the contents of ISIM data store backup directory to the target server. For example: tmp/db2.

    Ensure that the database instance owner we create has permission to read the target directory and files within. To restore the DB2 Universal Database data on the target database server, complete the following steps:

    1. Launch DB2 command line.

      Windows
      1. Start the Windows command prompt.
      2. Run the following command:

        set DB2INSTANCE=isiminst where isiminst is the database instance.

      3. Run db2cmd to start the DB2 command line.

      Linux
      Run the command su - isiminst where isiminst is the database instance.

    2. In the DB2 command line, enter the following commands to restore the database using the migrated DB2 data:restore db idmdb from OLD_DB2_TEMP_DATAWhere:
      • idmdb is ISIM data store database name.
      • OLD_DB2_TEMP_DATA is the location of the migrated DB2 data that you copied over from the previous version. For example: c:\temp\db2
    3. Stop and start the DB2 server to reset the configuration.

      After we create ISIM data store database, stop, and start the DB2 server to allow the changes to take effect. Enter the following commands:

      • db2stop
      • db2start
      If the db2stop fails and the database remains active, enter the following command to deactivate the database:
      • db2 force application all

      • Then, enter the db2stop command again.

  3. For the Identity data store, clear the Service Integration Bus.

    For reconfiguration of the Identity data store, we must clear out the Service Integration Bus (SIB) from the restored database. To clear out theService Integration Bus on the target DB2 server, complete the following steps:

    1. Stop ISIM server.
    2. Stop the Cluster Manager server.
    3. Ensure that the ISIM database is running (IDMDB).
    4. Start the DB2 command line.

      Windows
      1. Start the Windows command prompt.
      2. Run the following command:

        set DB2INSTANCE=isiminst where isiminst is the database instance.

      3. Run db2cmd to start the DB2 command line.

      Linux
      Run the command su - isiminst where isiminst is the database instance.

    5. In the DB2 command line, enter the DELETE SQL statements that you require to delete all data from the tables in the Service Integration Bus schemas.Enter the following commands for each of the Service Integration Bus schema in your environment:
      db2 connect to your itimdb name user yourid using password
db2 "delete from schema.SIB000" 
db2 "delete from schema.SIB001" 
db2 "delete from schema.SIB002" 
db2 "delete from schema.SIBCLASSMAP" 
db2 "delete from schema.SIBKEYS" 
db2 "delete from schema.SIBLISTING" 
db2 "delete from schema.SIBOWNER" 
db2 "delete from schema.SIBOWNERO" 
db2 "delete from schema.SIBXACTS"
db2 commit 
      The number in the schema name depends on the number of the node in the cluster. The schema is ITIML00n where n is the number of the node -1. By default, IBM Security Identity Manager creates schemas ITIMS000, ITIML000, ITIML001, and ITIML002 for up to three nodes. In an environment that has one, two, or three nodes, enter the following commands. 
      db2 connect to your itimdb name user yourid using password 
db2 "delete from ITIMS000.SIB000" 
db2 "delete from ITIMS000.SIB001" 
db2 "delete from ITIMS000.SIB002" 
db2 "delete from ITIMS000.SIBCLASSMAP" 
db2 "delete from ITIMS000.SIBKEYS" 
db2 "delete from ITIMS000.SIBLISTING" 
db2 "delete from ITIMS000.SIBOWNER" 
db2 "delete from ITIMS000.SIBOWNERO" 
db2 "delete from ITIMS000.SIBXACTS"
db2 "delete from ITIML000.SIB000" 
db2 "delete from ITIML000.SIB001" 
db2 "delete from ITIML000.SIB002" 
db2 "delete from ITIML000.SIBCLASSMAP" 
db2 "delete from ITIML000.SIBKEYS" 
db2 "delete from ITIML000.SIBLISTING" 
db2 "delete from ITIML000.SIBOWNER" 
db2 "delete from ITIML000.SIBOWNERO" 
db2 "delete from ITIML000.SIBXACTS" 
db2 "delete from ITIML001.SIB000" 
db2 "delete from ITIML001.SIB001" 
db2 "delete from ITIML001.SIB002" 
db2 "delete from ITIML001.SIBCLASSMAP" 
db2 "delete from ITIML001.SIBKEYS" 
db2 "delete from ITIML001.SIBLISTING" 
db2 "delete from ITIML001.SIBOWNER" 
db2 "delete from ITIML001.SIBOWNERO" 
db2 "delete from ITIML001.SIBXACTS" 
db2 "delete from ITIML002.SIB000" 
db2 "delete from ITIML002.SIB001"
db2 "delete from ITIML002.SIB002"
db2 "delete from ITIML002.SIBCLASSMAP" 
db2 "delete from ITIML002.SIBKEYS" 
db2 "delete from ITIML002.SIBLISTING" 
db2 "delete from ITIML002.SIBOWNER" 
db2 "delete from ITIML002.SIBOWNERO" 
db2 "delete from ITIML002.SIBXACTS"  
db2 commit
      If we add a fourth node to the cluster, the schema ITIML003 is created. The total schema is ITIMS000,TIML000, ITIML001, ITIML002, and ITIML003. So in addition to the previous delete statements, we must execute the nine delete SQL statements for schema ITIML003. The SIMOWNER0 might not exist in all Identity data store environments. If it does not exist and the delete statement fails, we can ignore the failure.
    6. Start the Cluster Manager server.
    7. Start ISIM server.

  4. Reconfigure the data store.

    1. From ISIM administrative console, click Menu > Database Configuration.

    2. Select the existing data store to set up and click Reconfigure. Provide the details and click Save Configuration.

    3. Restart the server to complete the process.

Parent topic: Virtual appliance configuration