MX 2.x)

Creating the SQL/MX triggers for the LOB columns in the base tables to ensure that orphan LOB data does not

occur in a LOB table.

Information about using the JDBC/MX Lob Admin Utility is provided in these topics.

Running the JDBC/MX Lob Admin Utility

Help Listing from the JDBC/MX Lob Admin Utility

Using SQL/MX Triggers to Delete LOB Data

Running the JDBC/MX Lob Admin Utility

Run the JDBC/MX Lob Admin utility in the OSS environment.

The format of the command is:

java [java_options] JdbcMxLobAdmin [prog_options] [table_name]

java_options

The java_options are properties that can be specified on the java command line in the -D option.

Property Specification Description

jdbcmx.blobTableName

Specifies the LOB table for using BLOB columns. Required if BLOB

columns are involved. See LOB Table Name Properties.

jdbcmx.clobTableName

Specifies the LOB table for using CLOB columns. Required if CLOB

columns are involved. See LOB Table Name Properties.

jdbcmx.catalog

Sets the default catalog. See Default Catalog and Schema.

jdbcmx.schema

Sets the default schema. See Default Catalog and Schema.

program_options

prog_option Description

-help Displays help information

-exec Runs the SQL statements that are generated.

-create

Generates SQL statements to create LOB tables. These statements describe

the architecture of the tables and, therefore, provide a description of the

LOB tables.

-trigger

Generates SQL statements to create triggers for the designated table. The

table must exist.

-unicode

Generates SQL statements to create unicode LOB tables. Use only for

CLOB

data.

Generate SQL statements to drop triggers for the designated table. The table