The event database is required to support persistence of
events. If you ran the createDB.sh script, you have already created
and populated the event database. If you did not use the createDB.sh
script, run the generated DDL scripts to populate the event database.
About this task
Populate the event database using the DDL scripts that were
generated by the administrative console.
Procedure
- Copy, to your working directory, the following generated
DDL script files from /WebSphere/V6R1M0/DeploymentManager/profiles/default/databases/event/cluster_name/dbscripts/db2zos/ddl (where cluster_name is
the name of the cluster to which the network deployment cell belongs):
- catalogSeed.ddl
- cr_db.ddl
- cr_db_catalog.ddl
- cr_tbl.ddl
- cr_tbl_catalog.ddl
- ins_metadata.ddl
- Assign the appropriate permissions to the copy of each
file:
chmod 755 catalogSeed.ddl
- Edit the values in the file to suit your needs. Change
the database names and the storage group names to meet your naming
requirements. The names that you specify in the file must match the
values that you entered in the response file that provided input to
the configuration script.
Note: The files are provided in ASCII format.
If the tools that you use to view, edit, and run the scripts require
the scripts to be in EBCDIC format, use the
iconv command
to convert the file to EBCDIC. For example:
iconv –t IBM-1047 –f ISO8859-1 catalogSeed.ddl >
catalogSeed_EBCDIC.ddl
If you the convert the file from ASCII format to EBCDIC
but need to run the file in ASCII format, use iconv to
convert the file back to ASCII. For example:
iconv -t ISO8859-1 -f IBM-1047 catalogSeed_EBCDIC.ddl >
catalogSeed.ddl
- Run the customized scripts using the tool of your choice. For example, DBUtility.sh or SPUFI.
Results
The event database is now populated.