NonStop Server Guide for BEA WebLogic Server 8.1

HP NonStop Server Guide for BEA WebLogic Server 8.1—529891-001

9-1

Managing the SQL/MX Tables for

BLOB and CLOB Data

Creating SQL/MX Tables

Providing Properties to the JDBC Driver

Creating SQL/MX Tables

WebLogic Server uses Large Objects (LOBs) in its application. LOBs are stored by

SQL/MX in a special manner and can only be accessed by configuring a JDBC

Connection Pool to use either the com.tandem.sqlmx.SQLMXDriver driver or the

com.hp.nsk.xares.WLSTxSQLMXDataSource driver. See Configuring the JDBC

Connection Pools for SQL/MX in Section 6.

WebLogic Server stores both Binary Large Object (BLOB) data and Character Large

Object (CLOB) data. The JDBC driver implementation of BLOB/CLOB requires the

existence of two special tables to store the BLOB/CLOB data. Generically, these tables

are called a blobtable (for BLOB data) and a clobtable (for CLOB data). When data is

inserted or updated in a base table (a table containing a column with a BLOB or CLOB

datatype), the JDBC driver places a reference to the blobtable or clobtable in the base

table and stores the actual BLOB/CLOB data in the blobtable or clobtable.

Providing Properties to the JDBC Driver

You must identify the location of these tables to the supported driver by specifying their

names as properties to the driver. You use the JAVA_OPTIONS environment variable

to supply the properties as follows:

export JAVA_OPTIONS=

-Djdbcmx.blobTableName=mycat.myschema.ZZWLI_BLOBTABLE

-Djdbcmx.clobTableName=mycat.myschema.ZZWLI_CLOBTABLE

mycat is the catalog name of your catalog and myschema is the name of your

schema.

For ease of use, you can put the export statement in a shell script that you execute

each time you start your application.

Note. These three lines should be typed as one line.