Filter
Top Products
Chapter 10. Pre-migration steps 191
Draft Document for Review July 28, 2004 7:33 pm 6320ch_before_migration.fm
d. Click Yes on the Confirmation dialog window. The WebSphere Application
Server Administrative Console will close automatically.
Ensue that all database background processes and connections are
terminated by typing the following commands from a DB2 command line:
DB2 terminate
DB2 force application all
2. Take a offline backup of the database in the WebSphere Commerce Suite
V5.1 environment by typing the following commands from a DB2 command
line:
DB2 backup database <database name> to <target drive>
3. Start the WebSphere Application Server again.
4. Copy the backup folder to the WebSphere Commerce V5.6 system.
5. Create a database user in WebSphere Commerce V5.6 environment (in the
operating system) with the same name, password and access privileges as
the database user in WebSphere Commerce Suite V5.1.
6. Restore the database you just copied into the WebSphere Commerce V5.6
system by typing the following command from a DB2 command line:
DB2 restore database <source database name> from <backup directory>
taken at <backup timestamp> into <target database name>
Note: DB2 will automatically migrate the database from version 7 to
version 8, after it has successfully restored the database.
The database can fail during migration (SQL2519N) if the database
configuration values are too small. If the above error occurs, do the
following to migrate the database manually:
1. Get the database configuration values
db2 get db cfg for <database>
2. Write down the values for logfilsiz, logprimary and logsecond
3. Increase the above value, for example by doubling the values:
db2 update db cfg for <WC_db> using logfilsiz <new value>
db2 update db cfg for <WC_db> using logprimary <new value>
db2 update db cfg for <WC_db> using logsecond <new value>
4. Migrate the database
db2 migrate database <WC_db> user <user> using <password>
5. Restore the configuration values to the original values.