Linux clustered server: Transfer IBM DB2 for i manually
View the steps to manually transfer data to the IBM DB2 Universal Database™ for i database you have set up. As an alternative to the manual database transfer procedure described here, we can use the configuration wizard to complete the database transfer task. However, we cannot specify all settings through the configuration wizard.
For example, regardless of the method used to transfer data, you must run a configuration task to create JMS
resources as described in this topic.
Before beginning:
Ensure that the following prerequisites are met:
- Supported database software is installed.
- Databases and users are set up.
- Stop the WebSphere_Portal server:
- stopServer WebSphere_Portal -username wpadmin -password foo
- Validate configuration properties using the ConfigEngine.sh validate-database -DWasPassword=foocommand.
Add -DTransferDomainList to the validating task to specify the domains to validate;
for example...
To validate all domains, do not specify this parameter.
- Transfer the database:
Important:
Do not execute the database-transfer task as a background process.
This might cause the task to stall.
- Set -DTransferDomainList to include only the domains to transfer.
For example, to transfer only the JCR domain we can enter the following command: ConfigEngine.sh database-transfer -DTransferDomainList=jcr
-DWasPassword=foo
- This note only applies when transferring databases from IBM DB2 for i to another server with IBM DB2 for i. If we are transferring databases from a database other than IBM DB2 for i, we can skip this note. 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 -DWasPassword=foo)
- Log output is written to:
WP_PROFILE/ConfigEngine/log/ConfigTrace.log
If the configuration fails, verify the values in the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files and then repeat this step.
- Start the WebSphere Portal server.
If you have additional nodes already configured, compare the following file on all nodes with the file from the primary node.
Ensure all instances of the file are identical:
WP_PROFILE/PortalServer/jcr/lib/com/ibm/icm/icm.properties
If the files are not identical, copy icm.properties from the primary node on which you ran the database-transfer task to the node.
- Stop the portal server on the secondary nodes.
- Copy
WP_PROFILE/PortalServer/jcr/lib/com/ibm/icm/icm.properties
from the primary node and replace icm.properties on the secondary nodes.
- Start the portal server on the secondary nodes.
Parent: Linux clustered server: Set up IBM DB2 for i
Previous: Linux clustered server: Grant privileges to IBM DB2 for i database users
Next: Linux clustered server: Verify IBM DB2 for i database connections