Transfer DB2 manually

 

+
Search Tips   |   Advanced Search

 

You are here

  1. Planning for DB2

  2. Installing DB2

  3. Creating databases and users for DB2

  4. Transfer DB2 manually (Current task) or Transferring between databases manually

  5. Verifying database connections

 

Before you begin

Before configuring databases, ensure that the following prerequisites are met:

  • Supported database software is installed.

  • Databases and users are correctly setup for use by IBM WebSphere Portal.

If you are using IBM DB2 Universal Database Enterprise Server Edition Fix Pack 11 or 12, complete the following steps prior to database transfer. Failure to follow these steps will cause the database transfer to hang at the task action-process-constraints. If you are using DB2 client to connect to a remote DB2 server, on the DB2 client edit...

/home/db2inst1/sqllib/cfg/db2cli.ini

...and add the following to the end of the file...

  • For Fix Pack 11: 

    [COMMON]
DYNAMIC=1

    An empty line is required after the dynamic=1 at the end of the file.

  • For Fix Pack 12: 

    [COMMON]
ReturnAliases=0

    An empty line is required after the ReturnAliases=0 at the end of the file.

 

Password Considerations

For security reasons, you should not store passwords in the wpconfig.properties, wpconfig_dbdomain.properties, and wpconfig_dbtype.properties files. IBM recommends that you edit each of the properties files prior to running a configuration task, inserting the passwords needed for that task. After the task has run, you should delete all passwords from each file.

Alternatively, we can specify the password on the command line using the following syntax:

  • UNIX:

    ./WPSconfig.sh task_name -Dpassword_property_key=password_value

  • Windows:

    WPSconfig.bat task_name -Dpassword_property_key=password_value

As with other properties, each password property must have the -D prefix and be set equal to (=) a value. If you have multiple properties in a single command, use a space character between each -Dproperty=value setting. Tips:

 

Steps for transferring data to another supported database

To transfer WebSphere Portal, Member Manager, and DB2 Content Manager databases to DB2.

For Windows, be sure that DB2 is started by checking the 'service'. If attempts to re-start DB2 result in a 'logon failure' message, then go to the DB2 properties and reenter the password.

  1. Locate the following files and create a backup copy of each before changing any values:

  2. Edit the properties files and enter the values that are appropriate for the environment.

    Notes:

    • The WebSphere Portal database can be used to hold information for applications such as Document Manager, Personalization, Feedback and Likeminds. In this case, the user should similar naming conventions for property values such as release.DbName, jcr.DbName, feedback.DbName, and likeminds.DbName. For example:

      • releaseDbName=wpsdb

      • jcr.DbName=jcrdb

      • feedback.DbName=fdbkdb

      • likeminds.DbName=lkmddb

    • Do not change any settings other than those that are specified in these steps. For instructions on working with these files, see Configuration properties reference for a complete properties reference, including default values.

    • If you are using a remote database, be sure to enter the values for the remote server.

    • Use / instead of \ for all platforms.

    • Some values, shown here in italics, might need to be modified to your specific environment.

    • There might be additional database properties other than those listed here. Only change the properties within this table; skip all other properties.

    • If you are following the recommended architecture in Planning for DB2, the Value listed for each property in the following table represents the DB2 -specific information that is required to configure WebSphere Portal to DB2.

    • Depending on which database domain has to be configured, dbdomain may need to be replaced by:

      • release

      • customization

      • community

      • jcr

      • feedback

      • likeminds

      • wmm

    Update the following properties in the file wpconfig_dbdomain.properties.

    Property Value
    dbdomain.DbType

    The type of database used to store information for WebSphere Portal.

    Value type: Alphanumeric text string Recommended value:

    • DB2 : db2

    dbdomain.DbName The name of the WebSphere Portal domain database and schema.

    Notes:

    • This value is also the database element in the dbdomain.DbUrl property.

    • Non-Windows platforms when using DB2 only. This value is the TCPIP Alias for the database.

    • For Oracle, this value should match the 'ORACLE_SID'.

    Value type: Alphanumeric text string

    Notes:

    • For DB2 and DB2 for z/OS, this value cannot exceed 8 characters and can only contain letters and numbers. Refer to the database documentation for more information.

    • For DB2, this value must be different from the value of dbdomain.XDbName.

    • If you change the name of the WebSphere Portal data source due to a database migration, manually update this property in the portal_server_root/config/wpconfig_dbdomain.properties file to maintain the proper resource reference mapping.

    Default value for all domains: wpsdb

    dbdomain.DbUrl

    The database URL used to access the WebSphere Portal database with JDBC. The value must conform to standard JDBC URL syntax.

    The database element of this value should match the value of dbdomain.DbName.

    Value type: Alphanumeric text string, conforming to standard JDBC URL syntax Recommended:

    • DB2 : jdbc:db2:wpsdb

    dbdomain.DbUser

    The user ID for the database administrator.

    Notes:

    • For SQL Server and non-wmm databases only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same.

    • For Oracle and SQL Server servers, this value must be set to FEEDBACK, which corresponds to the user FEEDBACK in the database. If the user you are using is an administrative user that has authority over the FEEDBACK schema, the administrative user should be entered for the dbdomain.DbUser property.

    Value type: Alphanumeric text string

    Default:

    • Release: db2admin
    • Community: db2admin
    • Customization: db2admin
    • JCR: db2admin
    • WMM: db2admin
    • Feedback: db2admin
    • LikeMinds: db2admin

    Recommended: wpsdbusr (for databases other than DB2 )

    dbdomain.DbPassword

    The password for the database administrator.

    A value must be set for this property; it cannot be empty.

    Value type: Alphanumeric text string

    Default value for all domains: ReplaceWithYourDbAdminPwd

    dbdomain.XDbName

    The database loop back alias that needs to be set if you plan to use the create-local-database-db2 task.

    Notes:

    • For DB2, this value must be different from the value of dbdomain.DbName.

    Value type: Alphanumeric text string

    Default:

    • Release: wps6TCP
    • Community: wps6TCP
    • Customization: wps6TCP
    • WMM: wps6TCP
    • JCR: wps6TCP
    • Feedback: fdbk6TCP
    • LikeMinds: lmdb6TCP

    dbdomain.DbNode

    The value for the node database.

    Required for non-Windows platforms when using DB2 only.

    Value type: Alphanumeric text string

    Default values:

    • Release: wpsNode
    • Community: wpsNode
    • Customization: wpsNode
    • JCR: wpsNode
    • WMM: wpsNode
    • Feedback value: pznNode
    • LikeMinds value: pznNode

    dbdomain.DataSourceName

    The name of the data store that WebSphere Portal uses to communicate with its databases.

    Notes:

    • If the DbUser, DbUrl, and DbPassword are not the same across domains, this value must differ from the DataSourceName of the other domains.

    • The value for dbdomain.DataSourceName should not be set to the same value as dbdomain.DbName.

    Value type: Alphanumeric text string

    Default values:

    • Release: wpsdbDS
    • Community: wpsdbDS
    • Customization: wpsdbDS
    • JCR: JCRDS
    • WMM: wpsdbDS
    • Feedback: feedback5
    • LikeMinds: lmdbDS

    Update the following properties in the file wpconfig_dbtype.properties.

    Database type properties
    Property Value
    DbSafeMode

    This only applies to database-specific tasks. If this property is set to true, database-specific tasks, such as create/modify/drop database, will not be performed. The property should be used if a pre-configured database (from a previous installation) already exists. If the property is set to false, the database will be updated and the pre-existing database configuration will be overwritten.

    Recommended: false

    Default: false

    db2.DbDriver

    The name of class that SqlProcessor will use to import SQL files.

    Recommended: COM.ibm.db2.jdbc.app.DB2Driver

    Default: COM.ibm.db2j.jdbc.DB2Driver (Cloudscape )

    db2.DbLibrary

    The directory and name of the.zip or.jar file that contains the JDBC driver class

    Recommended: db2_install/java/db2java.zip

    In UNIX environments, use a colon (:) instead of a semi-colon (;) to separate multiple paths.

    Default: D:/IBM /SQLLIB/java/db2java.zip

    Update the following properties in the file wpconfig.properties.

    WebSphere Application Server properties
    Property Description
    WasPassword

    The password for WebSphere Application Server security authentication.

    If a value is specified for WasPassword, a value must also be specified for WasUserid. If WasPassword is left blank, WasUserid must also be left blank.

    Value type: Alphanumeric text string

    Recommended: Set this value according to your own environment.

    Default: ReplaceWithYourWASUserPwd

    If you have come to this step while creating databases and users, please return to that section of the Information Center now. Otherwise, continue with the next step.

  3. Save the file.

  4. Perform this step only if you are installing multiple instances of WebSphere Portal with DB2 on AIX. Change the maximum numdb MAX_NETBIOS_CONNECTIONS to increase the default configured number of databases. For example, enter the following command at the database prompt: 

    set client MAX_NETBIOS_CONNECTIONS 254
    A message indicates success if the number was increased.

  5. Open a command prompt, and change to the directory portal_server_root/config.

  6. If WebSphere Portal is on UNIX, export the DB2 user profile that you created when installing DB2 onto the administrative user using the following command. This gives that administrative user rights over DB2. 

    . /home/db2inst1/sqllib/db2profile
    where db2inst1 represents your database instance

    You must complete this step before running database tasks and before enabling security in order to create a suitable JDBC driver.

  7. Enter the following commands to validate configuration properties.

  8. From the same command prompt as the previous steps, change to the directory portal_server_root/config.

  9. Stop both server1 and the WebSphere Portal server.

    • Enter the following command:

      • UNIX:

        ./stopServer.sh server1 -user admin_userid -password admin_password

      • Windows:

        stopServer.bat server1 -user admin_userid -password admin_password

      • i5/OS:

        stopServer -profileName profile_root -user admin_userid -password admin_password

        ...where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.

      ...where server1 is the name of the WebSphere Application Server administrative server, and profile_root is the name given to the WebSphere Application Server profile in use.

    • Enter the following command:

      • UNIX:

        ./stopServer.sh WebSphere_Portal -user admin_userid -password admin_password

      • Windows:

        stopServer.bat WebSphere_Portal -user admin_userid -password admin_password

      • i5/OS:

        stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password

        ...where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.

  10. To transfer the database, perform this step:

    1. Enter the following commands to run the configuration task.

      • UNIX:

        ./WPSconfig.sh database-transfer -Drelease.DbPassword=password -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password -Dwmm.DbPassword=password -Dfeedback.DbPassword=password -Dlikeminds.DbPassword=password

      • Windows:

        WPSconfig.bat database-transfer -Drelease.DbPassword=password -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password -Dwmm.DbPassword=password -Dfeedback.DbPassword=password -Dlikeminds.DbPassword=password

    2. After running this task, a message indicating success should result. Check the log files to verify that this task was successful. If the configuration fails, verify the values in the wpconfig_dbdomain.properties file, and then repeat this step.

  11. After transferring the database tables, perform a reorg check to improve performance.

    1. Connect to a database with the following command: 

      db2 connect to database_alias user db2admin_userid using password

      Additional options may be required if additional security has been installed. Refer to DB2 Universal Database commands by example for links to a downloadable command reference.

    2. Once connected, run the following commands from the DB2 prompt: Windows: 

      db2 reorgchk update statistics on table all > xyz.out
      Look in the reorg column for entries marked with a * (star or asterisk) in the file xyz.out. For each line with a *, note the tablename and run the following command for each tablename: 

      db2 reorg table tablename db2 terminate c:\> db2rbind database_name -l db2rbind.out -u db2_admin -p password
      UNIX : 

      db2 reorgchk update statistics on table all > xyz.out
      Look in the reorg column for entries marked with a * (star or asterisk) in the file xyz.out. For each line with a *, note the tablename and run the following command for each tablename: 

      db2 reorg table tablename db2 terminate db2rbind database_name -l db2rbind.out -u db2_admin -p password

    3. The output file db2rbind.out will only be created if there is an error for the above db2rbind command.

  12. Change to the directory was_profile_root/bin.

  13. Enter the following command to restart the server: startServer WebSphere_Portal

Next steps You have completed this step. Continue to the next step:

 

Parent topic:

Transferring all domains