Use the cr_event_oracle command to manually
generate a database configuration script for an Oracle event database.
About this task
To manually run the generated database configuration script
for an Oracle event database:
Procedure
- On the server system, go to the directory containing the
generated script. The default location is theprofile_root/databases/event/node/server/dbscripts/oracle
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_oracle.bat

Linux® and UNIX® systems: cr_event_oracle.sh
- Run the database creation script using the following syntax
(remember to specify the file extension, if applicable):
cr_event_oracle password sys_user
sys_password [sid=sid]
[oracleHome=oracle_home]
The
parameters are as follows:- password
- The password for the schema user ID. This parameter is required.
- sys_user
- The user ID that has SYSDBA privileges in the Oracle database
(typically the sys user). This parameter is required.
- sys_password
- The password for the specified sys user ID. If this user ID does
not use a password, type none.
- sid=sid
- The Oracle system identifier (SID). This parameter is optional.
- oracleHome=oracle_home
- The Oracle home directory. This parameter is optional; if you
do not specify a value, a generated path is used.
For example, the following command would create
the Oracle event database using the schema user ID
auser and
the sys user ID
sys:
cr_event_oracle auser sys syspassword sid=event oracleHome=c:\oracle
- 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.