To enable your database administrator to create or alter
the data store tables manually, you must generate data definition
language (DDL) statements.
About this task
Use the sibDDLGenerator command to generate
the DDL statements that the database administrator needs to create
the tables for the messaging engine data store. Use the sibDBUpgrade command
to generate the DDL statements that the database administrator needs
to alter the tables for the messaging engine data store.
Procedure
-
At a command prompt, issue the sibDDLGenerator to create or
sibDBUpgrade command to alter the data store tables and redirect the output to a
file.
For information on these command-line utilities, refer to
sibDDLGenerator command and
sibDBUpgrade
command.
Important: If you want to process the DDL statements with a command line
processor that requires the statements to conform to a specific format, use the optional parameters
that control the format of the DDL statements. For example, if each statement must end with a
semicolon, use -statementend
;
To access the IBM® i
command line, or run an IBM i command line program, use
the STRQSH command to start a Qshell session. For more information, see Configuring Qshell to run WebSphere scripts using wsadmin scripting.
- Send the output file to your database administrator to
process the DDL statements that are generated. The DDL statements
can be ported across operating systems, for example, you can generate
the DDL statements on a machine running the Windows operating
system and then run them on a machine running the z/OS® operating
system.
The DDL statements can be processed
by using SPUFI.
Attention:
- Your database administrator can modify the DDL statements, but must
not modify the table names or the column names in any way because
doing so might prevent the messaging engine from starting.
- If the DDL statements are to be run on the z/OS operating
system, your database administrator must change the VCAT name in the
first line of the DDL statements (the create storage group statement)
to a valid high-level qualifier for their system.
- Service integration bus does not support padded values in the XID column of the SIBXACTS table.
Hence, any database parameter setting that might add padded values to the column must not be applied
to the database.
For example, changing the value of the RETVLCFK DB2
parameter from NO to YES might introduce padded values.
For
more information about the RETVLCFK parameter, see VARCHAR
FROM INDEX field (RETVLCFK subsystem parameter) in the DB2 documentation.