Use the cr_event_db2 to manually generate
a database configuration script for a DB2® event
database on a Linux®, UNIX®, or Windows® server.
About this task
To manually run the generated database configuration script
for a DB2 event database on
a Linux, UNIX, or Windows system:
Procedure
- On the server system, go to the directory containing the
generated script. The default location is the profile_root/databases/event/node/server/dbscripts/db2
directory; if you specified a value for the outputScriptDir parameter
of the database configuration administrative command, the scripts
are stored in that location instead.
- Using an ASCII text editor, make any required modifications
to the configuration script. The name of the script varies
depending upon the operating system in use:
Windows systems:
cr_event_db2.bat

Linux and UNIX systems: cr_event_db2.sh
- Run the database creation script using the following syntax
(remember to specify the file extension, if applicable):
cr_event_db2 [client|server] db_user [db_password]
The
parameters are as follows:- client|server
- Indicates whether the database is a client or server. You must
specify either client or server.
- db_user
- The database user ID. This parameter is required.
- db_password
- The password for the database user. If you do not specify a password
for a client database, you are prompted for it.
For example, the following command would create
the DB2 event database for a
client database, using the user ID
db2admin and the
password
mypassword:
cr_event_db2 client db2admin mypassword
- Restart the server. For a federated node, you
must also stop and restart the node agent using the stopNode and startNode commands.
What to do next
After you finish configuring the database, you can use
the administrative console to test the database configuration. To
do this, navigate to the appropriate JDBC data source and select the Test
Connection option.