If you postponed creating required tables for your existing
Common database by selecting the Delay execution of database
scripts (must select if using a remote database) check
box on the Database configuration panel in the Profile Management
Tool, you or your database administrator must create the tables manually.
You can do this using scripts that the Profile Management Tool generates
during profile creation or augmentation.
Before you begin
This topic assumes that you created or augmented a stand-alone
server or deployment manager profile using the procedure in one of
the following topics:
It also assumes that in the Database configuration panel in the
Profile Management Tool, you selected the
Use an existing
database radio button and chose to delay creation of the
tables by selecting the
Delay execution of database scripts
(must select if using a remote database) check box.
About this task
Because a WebSphere ESB installation
requires the Common database and its tables to function, if you did
not allow the Profile Management Tool to create the tables automatically,
you or your database administrator must now create the tables manually
by using scripts that the Profile Management Tool generated during
the profile creation or augmentation.
Procedure
- Go to the directory containing the table creation script createDBTables on i5/OS® platforms, createDBTables.sh on Linux® and UNIX® platforms, or createDBTables.bat on Windows® platforms. You specified
its location in the Database script output directory field
on the Database configuration panel in the Profile Management Tool. By default, this location is:
profile_root/dbscripts/CommonDB/db_type/db_name

profile_root/dbscripts/CommonDB/db_type/db_name
profile_root\dbscripts\CommonDB\db_type\db_name
The variable db_type represents the supported
database product, and db_name represents the name
of the database.
- Use your standard database definition tools, native commands,
and procedures to create the required tables by running this script. The script contains only basic statements for creating databases,
tables, and indexes.
What to do next
After the tables are created successfully, before starting
the server or deployment manager, be sure the database is running
even if it is installed locally. Then start the server or deployment
manager from the profile's First steps console to ensure there are
no errors. You can check the
SystemOut.log and
SystemErr.log files
for errors. These files are found in the following locations:
- profile_root/logs/server_name,
for a stand-alone profile
- profile_root/logs/dmgr, for a deployment
manager profile