Portal, V6.1

---

 

Transferring DB2 for i5/OS manually

This section provides information on how to manually transfer data to the IBM DB2 for i5/OS database you have set up.

Before you begin:
Ensure that the following prerequisites are met:

• Supported database software is installed.

• Databases and users are set up.

Prerequisites

Preparing for creation of databases

Create user profiles

Creating remote databases

Modifying database properties

• The steps for transferring data to another supported database section provides instructions for manually transferring data. Instead of performing the following steps, use the configuration wizard, which is a graphical user interface, to transfer data to another supported database.

Steps for transferring data to another supported database

1. Stop both WAS and the WebSphere Portal server:

   Option	Description
   WAS	stopServer server1 -username adminid -password passwd
   WebSphere Portal	stopServer WebSphere_Portal -username adminid -password passwd

2. Create the database schemas using the following commands:

   1. Change to the directory WP_PROFILE/ConfigEngine

   2. Create schemas for the Community, Customization, Release, JCR, Feedback, and LikeMinds domains: ConfigEngine.sh create-database

3. Validate configuration properties using the following commands:

   • ConfigEngine.sh validate-database-driver -DTransferDomainList=release,customization,community,jcr,feedback,likeminds

   • ConfigEngine.sh validate-database-connection -DTransferDomainList=release,customization,community,jcr,feedback,likeminds

4. Transfer the database:

   1. Enter the following command:

      • ConfigEngine.sh database-transfer

      Use SBMJOB to submit the Qshell script as a batch job to run in *BASE pool when *INTERACT pool does not have 1GB or more of allocated memory. For example: SBMJOB CMD(STRQSH CMD(ConfigEngine.sh database-transfer))

   2. After running this task, a message is added to the log files to verify that this task was successful. Check the log files. If the configuration fails, verify the values in the wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties files and then repeat this step.

5. Start the WebSphere Portal server: startServer WebSphere_Portal

 

Parent topic

Preparing DB2 for i5/OS

 

Previous topic:

Modifying database properties

Next topic:

Verifying database connections

---