MX 2.x)

-drop

must exist.

-out Writes the SQL statements to a specified file in OSS file space.

table_name

The table_name represents a base table that contains LOB columns. The table_name is of the form:

[catalogName.][schemaName.]baseTableName

For information about catalog, schema, and table names, see the SQL/MX Reference Manual.

Help Listing from the JDBC/MX Lob Admin Utility

The command to display JDBC/MX Lob Admin utility help appears below followed by the help listing.

java JdbcMxLobAdmin -help

Company, LP.

java [<java_options>] JdbcMxLobAdmin [<prog_options>] [<table_name>]

<java_options> is:

[-Djdbcmx.clobTableName=<clobTableName>]

[-Djdbcmx.blobTableName=<blobTableName>]

[-Djdbcmx.catalog=<catalog>]

[-Djdbcmx.schema=<schema>]

<prog_options> is:

[-exec] [-create] [-trigger] [-help] [-drop] [-out <filename>]

where -help - Display this information.

-exec - Execute the SQL statements that are generated.

-create - Generate SQL statements to create LOB tables.

-trigger - Generate SQL statements to create triggers for <table_name>.

-unicode - Generate SQL statements to create unicode LOB tables

(CLOB only).

-drop - Generate SQL statements to drop triggers for <table_name>.

-out - Write the SQL statements to <filename>.

<clobTableName> | <blobTableName> is:

<table_name> is:

[<catalogName>.][<schemaName>.]<baseTableName>

<baseTableName> is the table that contains LOB column(s).

<lobTableName> is the table that contains the LOB data.

Using SQL/MX Triggers to Delete LOB Data

Use the JDBC/MX Lob Admin Utility to generate triggers to delete LOB data from the LOB table when the base row

is deleted. These triggers ensure that orphan LOB data does not occur in the LOB table. To manage the triggers, use

these JDBC/MX Lob Admin Utility options:

-trigger

Generates SQL statements to create triggers.

-drop

Generates SQL statements drop triggers.