Changing the development database type using the setdbtype command

After you install WebSphere Commerce Developer, the development environment is configured to use the Apache Derby database. To change the database type to DB2, Oracle, or back to Apache Derby, run the setdbtype command. Ensure that the database you are switching to exists in your network. Changing development database types does not carry over any schema customizations or custom data to the new database.

Note:

If you want to switch development databases after you install the latest fix pack, you must update to the new database manually by running the updatedb command. The new database is restored to bootstrap state after you switch databases.
If you switch development databases, you must re-enable any features that you are using from WebSphere Commerce feature packs
When you specify a DB2 password, make sure that it meets the naming restrictions for WebSphere Commerce databases. If restricted characters are used in database passwords, you can encounter connection errors when you use utilities that take these passwords as input on the command-line, including setdbtype. For more information, see Troubleshooting: Database connection errors when utilities run from a command-line interface
Oracle database is not supported on WebSphere Commerce Developer Express Edition. See Troubleshooting: No data inserted after running setdbtype command.

Before you begin

If you change the database to IBM i, install APAR JR36284.
If you are using a remote database, install the appropriate DB2 client to access the remote DB2 database. For more information, see your DB2 documentation.
1. If you are using a remote database, install the appropriate Oracle client to access the remote Oracle database. For more information, see the Oracle documentation.
2. Create a database.
3. Create an Oracle database user.
  Note: Ensure that the user has enough table space or that Auto Extend is set to Yes in the data file. Grant the user the following privileges: create procedure, create session, create synonym, create table, create trigger, create view, and create materialized view.
If you want to switch the database type to DB2 V9.7, install WebSphere Commerce Version 7.0 with fix pack 1 before you run the setdbtype command.

Procedure

Stop the WebSphere Commerce Test Server.
Stop the WebSphere Commerce development database.
Go to the WCDE_installdir/bin directory.
Run the following command to restore your WebSphere Commerce development database and workspace:
```
restoreDefault.bat
```
You now have the default environment with a Derby database.
Run one of the following commands, depending on the database you are switching to:
- setdbtype db2 DB2_HOME dbName dbAdminID dbAdminPassword dbUserID dbUserPassword [dbHost dbServerPort dbNode] [createdb]
- setdbtype oracle ORACLE_HOME dbName dbAdminID dbAdminPassword dbUserID dbUserPassword [dbHost dbServerPort] [createdb]
- setdbtype cloudscape [createdb]
- setdbtype iseries dbName dbHost dbUserID dbUserPassword [createdb]
  Note: The iSeries and createdb parameters are not variables. Type as iseries and createdb
Where:

DB2_HOME

The root directory of DB2. For example, C:\IBM\SQLLIB

ORACLE_HOME

The root directory of the Oracle DBMS. For example, C:\oracle\product\11.1.0\client_1

dbName

The name of the database. For example, mall.

dbAdminID

The database administrator's ID. For example, db2admin or oracle.

dbAdminPassword

The associated password for dbAdminID

dbUserID

The database user ID that connects to the database.

dbUserPassword

The associated password for dbUserID

dbHost

Optional: The host name of a remote database server.

dbServerPort

Optional: The port number of the remote database server.

dbNode

Optional: The node name of the remote database.

createdb

Optional: If specified, the command creates a new empty database.
After you run the setdbtype command, and before you publish any stores in the new database, run the resetstores command to clean the store database.
1. Open a command prompt and change to the WCDE_installdir/bin directory.
2. Run the following command:
```
resetstores.bat
```
  Note: Running the resetstores script will remove all stores, including the starter stores published by default.
If you are using a database that existed before the fix pack was installed, manually run the updatedb command.
From a command prompt, run the following command:
- WCDE_installdir\bin\updatedb.bat cloudscape
- WCDE_installdir/bin/updatedb.bat db2 database_name database_user_name database_user_password
- WCDE_installdir/bin/updatedb.bat oracle database_name database_user_name database_user_password database_host server_port
- WCDE_installdir/bin/updatedb.bat iseries database_name database_user_name database_user_password database_host
Where:

database_name

The name of your WebSphere Commerce Developer database. For example, WCDE_installdir/db/mall

database_user_name

The name of your WebSphere Commerce Developer database user.

database_user_password

The WebSphere Commerce Developer database user password.

database_host

The database server host name.

server_port

The database server host port number.
Re-enable any features that you are using, see WebSphere Commerce feature packs.
If you enabled search, rebuild the search index.
Optional: If your database was customized to include custom columns or tables, you must update your database to include these changes.
Verify that the script ran successfully by checking that the string BUILD SUCCESSFUL is at the end of the WCDE_installdir/logs/setdbtype.log log file

What to do next

Manually redeploy your store.