migratedb utility (database migration script)

If migrating the WebSphere Commerce database using the command line, review this information to understand the parameters required for the migratedb command.

The following section describes the syntax to use for the database migration script. Some optional parameters might not be applicable to your migration path. Read the detailed parameter descriptions to see which ones apply.

Cloudscape database tier migration is only available for the WebSphere Commerce development environment.

dbtype database_type

The database type you are migrating. Any of the following values can be assigned to database_type:

db2

AIX|Linux|Solaris|Windows:

Specifies that you are migrating a DB2 database.

oracle

AIX|Solaris|Windows:

Specifies that you are migrating an Oracle database.

I5/OS|os400

Specifies that you are migrating a DB2 for i5/OS database.

-dbname database_name

Database you are migrating.

  • I5/OS|database_name is the relational database where your WebSphere Commerce schema runs, as displayed in the relational database directory (as viewed from the WRKRDBDIRE command).

    • For a remote database tier migration, (where you specify the -remoteDB true parameter), database_name represents the host name of the machine where your WebSphere Commerce database is located.

  • AIX|Linux|Solaris|Windows:

    database_name is the WebSphere Commerce database that you are migrating (for example, mall).

  • database_name is a file path to the database. For example, WCDE_installdir\db\mall, where WCDE_installdir represents the installation path for WebSphere Commerce Developer.

-dbuser database_user_ID

Database user ID.

  • I5/OS|database_user_ID is the instance user profile of the previous WebSphere Commerce version database that you are migrating. This should be the same as your schema name.

  • AIX|Linux|Solaris|Windows:

    database_user_ID is the user ID to connect to the previous WebSphere Commerce version database that you are migrating (for example, mydbuser for DB2 databases or oracle for Oracle databases).

  • If you do not use the -dbuser parameter, the database tier migration script creates a default value for it.

-dbpass database_password

  • Database user ID password. If you do not enter this parameter, the migration script will prompt you to enter it.

  • I5/OS|database_password is the password for the instance user profile of the WebSphere Commerce database that you are migrating. If you do not supply it on the command line, the migration script will prompt you to enter it in.

  • AIX|Linux|Solaris|Windows:

    database_password is the password for the user ID to connect to the WebSphere Commerce database that you are migrating (for example, mypasswd for DB2 databases or oraclepw for Oracle databases). If you do not supply it on the command line, the migration script will prompt you to enter it in.

  • If you do not use the -dbpass parameter, the database tier migration script will use a WebSphere Commerce default value for it.

-from version

Specifies the version of the WebSphere Commerce database from which you are migrating. For WebSphere Commerce databases, enter 55, 56, or 561.

-instanceName instance

Specifies the WebSphere Commerce instance name for the database that you are migrating (for example, demo). If you do not use this parameter, the script uses "WC_DE_default_instance", for the development environment.

Where:

WCDE_installdir

Represents the installation path for WebSphere Commerce Developer, Version 6.0. The default installation path is:

  • drive:\WCToolkitEE60.

  • drive:\WCToolkitPro60.

  • drive:\WCToolkitExpress60.

  • If you use the -instanceName parameter, it creates a subdirectory under the WCDE_installdir\logs\WCIM\ instance directory.

-defaultLocale locale

The locale for your system. It can be any of the supported WebSphere Commerce locales such as en_US, fr_FR, and so on. If this parameter is not specified, the locale of the operating system that is found by the JVM is used as the default.

-ldap true | false

This parameter specifies whether the LDAP server is being used with WebSphere Commerce to store user information. The default is false.

-schema schema_name

  • (DB2)

    • AIX|Linux|Solaris|Windows:

      Database schema name. This parameter is mandatory when the schema name is not the same as the database user ID. If this parameter is not specified, the migration script assumes the schema name is the same as the database user ID.

  • If the -schema parameter is not used, the database tier migration script uses " APP" as the default.

I5/OS|(Oracle) -hostname host_name

Specifies the fully qualified host name of the machine where your database resides. (for example, myhost.montreal.ca). If - remotedb is true, this parameter is required.

(Oracle) -port port_number

Specifies the Oracle listener port number. Typically, this is port 1521 by default.

AIX|Linux|Solaris|Windows:

-TABDEF tabdef

The tablespace containing the tables that uses the default page size (usually 4K); the default is USERSPACE1.

-INDEXDEF indexdef

The tablespace containing the indexes of those tables in tabdef, the default is USERSPACE1.

-TAB8K tab8k

The tablespace containing the tables that use an 8K page size; the default is TAB8K.

-INDEX8K index8k

The tablespace containing the indexes of those tables in tab8k, the default is TAB8K.

--TAB16K tab16k

The tablespace containing the tables that use a 16K page size; the default is TAB16K.

-INDEX16K index16k

The tablespace containing the indexes of those tables in tab16k, the default is TAB16K.

The custom table spaces specified must exist in the current DB2 system.

AIX|Linux|Solaris|Windows:

Use these parameters if your DB2 database uses customized table spaces as opposed to the default table spaces, USERSPACE1, TAB8K, and TAB16K. For example, if you have customized your WebSphere Commerce database to use say, MYUSERSPACE, MYTAB8K, MYTAB16K, use the following:

The following parameters are not applicable for migrations from WebSphere Commerce, version 5.5 or from WebSphere Commerce - Express:

The following parameters are required only if you want to modify the default log directory or file name:

-logDir log_directory

Directory where the database tier migration log file will be generated. The default directory is as follows:

  • AIX|Linux|Solaris|Windows:

    WC_installdir/instances/instance/migration/logs

  • I5/OS: WC_userdir/instances/instance/migration/logs

-logFile log_file_name

Database tier migration log file name. The default log file name is migratedbxx_yyyy.mm.dd_hh.mm.ss.log. Where xx is either 55, 56, or 561.

-logLevel level

Specifies the amount of information on the database tier migration that is logged. The valid log levels are:

None

No information or error messages are logged.

Error

Only error messages are logged.

Normal

All error messages and events are logged. It is the recommended option for most database tier migrations as it only requires in the order of 10 KB of storage for most migrations.

Verbose

All errors, events, and other information is logged, including all SQL statement information. This option is recommended if you encounter errors and need to debug them. It requires in the order of one or two MB of storage for most migrations. This is the default.

Debug

Similar to the Verbose option, but includes some additional debug information. Recommended if you encounter errors and need to debug them. It requires in the order of one or two MB of storage for most migrations.

-precheck

Runs the database premigration checker to check the status of your database prior to migrating it. Running the database premigration checker prior to performing the database tier migration is recommended.

I5/OS|-remoteDB true

Specifies that the database is on a system that is remote from the system where you run the migratedb command.

Related tasks

Migrate the WebSphere Commerce database

Extending the data migration script


Related Reference

Data migration plan file