The script content on this page is for navigation purposes only and does not alter the content in any way.
The following sections describe how to configure and use the WebLogic Type 4 JDBC driver for DB2:
OpenLink ODBC Driver for DB2 (Express Edition) for Mac OS X. Installation Guide. The OpenLink ODBC Driver for DB2 (Express Edition) is distributed as a Disk image (DMG) file. Specifies the collection ID for the packages that are used by an instance of the DB2 Universal JDBC Driver at run time. The data type of jdbcCollection is. Db2jcc4.jar - This driver is based on the JDBC 4 or later specifications The db2jcc.jar driver is now deprecated. After version 3.72, which is delivered with DB2 Version 11.1 for Linux, UNIX, and Windows Modification Pack 1 Fix Pack 1, db2jcc.jar will include no new features.
DB2 Driver Classes
The driver classes for the WebLogic Type 4 JDBC DB2 driver are as follows:
Use these driver classes when configuring a JDBC data source in your WebLogic Server domain.
J2EE Connector Architecture Resource Adapter Class
The ManagedConnectionFactory class for the Informix resource adapter is:
com.weblogic.resource.spi.InformixManagedConnectionFactory
DB2 URL
The connection URL format for the DB2 driver is:
where:
For example:
DB2 UDB for Linux, UNIX, and Windows
DB2 UDB for z/OS and iSeries
DB2 Connection Properties
Table 3-1 lists the JDBC connection properties supported by the DB2 driver, and describes each property. You can use these connection properties in a JDBC data source configuration in your WebLogic Server domain.
Note:
All connection property names are case-insensitive. For example, Password is the same as password. Required properties are noted as such. The data type listed for each connection property is the Java data type used for the property value in a JDBC data source.
To specify a property, use the following form in the JDBC data source configuration:
property=value .
Table 3-1 DB2 Connection Properties
Performance Considerations
Setting the following connection properties for the DB2 driver as described in the following list can improve performance for your applications:
CatalogIncludesSynonyms
The
DatabaseMetaData.getColumns method is often used to determine characteristics about a table, including the synonym, or alias, associated with a table. If your application accesses DB2 v7.x for Linux/UNIX/Windows, DB2 for z/OS, or DB2 for iSeries and your application does not use database table synonyms, the driver can improve performance by ignoring this information. The driver always returns synonyms for the DatabaseMetaData.getColumns() method when accessing DB2 v8.x and higher for Linux/UNIX/Windows.
CatalogOptions
Retrieving synonym information is expensive. If your application does not need to return this information, the driver can improve performance. Default driver behavior is to include synonyms in the result set of calls to the following DatabaseMetaData methods:
getColumns() , getExportedKeys() , getFunctionColumns() , getFunctions() , getImportedKeys() , getIndexInfo() , getPrimaryKeys() , getProcedureColumns() , and getProcedures() . If your application needs to return synonyms for getColumns() calls, the driver can emulate getColumns() calls using the ResultSetMetaData object instead of querying database catalogs for the column information. Using emulation can improve performance because the SQL statement formulated by the emulation is less complex than the SQL statement formulated using getColumns() .
CatalogSchema
To improve performance, views of system catalog tables can be created in a catalog schema other than the default. The DB2 driver can access the views of catalog tables if this property is set to the name of the schema containing the views. The default catalog schema is SYSCAT for DB2 for Linux/UNIX/Windows, SYSIBM for DB2 for z/OS, and QSYS2 for DB2 for iSeries.
To ensure that catalog methods function correctly, views for specific catalog tables must exist in the specified schema. The views that are required depend on your DB2 database. See Non-Default Schemas for Catalog Methods for views for catalog tables that must exist in the specified schema.
EnableBulkLoad
For batch inserts, the driver can use native bulk load protocols instead of the batch mechanism. Bulk load bypasses the data parsing usually done by the database, providing an additional performance gain over batch operations. Set this property to true to allow existing applications with batch inserts to take advantage of bulk load without requiring changes to the code.
EncryptionMethod
Data encryption may adversely affect performance because of the additional overhead (mainly CPU usage) required to encrypt and decrypt data.
InsensitiveResultSetBufferSize
To improve performance when using scroll-insensitive result sets, the driver can cache the result set data in memory instead of writing it to disk. By default, the driver caches 2 MB of insensitive result set data in memory and writes any remaining result set data to disk. Performance can be improved by increasing the amount of memory used by the driver before writing data to disk or by forcing the driver to never write insensitive result set data to disk. The maximum cache size setting is 2 GB.
MaxPooledStatements
To improve performance, the driver's own internal prepared statement pooling should be enabled when the driver does not run from within an application server or from within another application that does not provide its own prepared statement pooling. When the driver's internal prepared statement pooling is enabled, the driver caches a certain number of prepared statements created by an application. For example, if the
MaxPooledStatements property is set to 20, the driver caches the last 20 prepared statements created by the application. If the value set for this property is greater than the number of prepared statements used by the application, all prepared statements are cached.
SendStreamAsBlob
If the large binary objects you insert or update are stored as Blobs, performance can be improved by sending the binary stream as Blob data. In this case, this property should be set to true.
StripNewLines
If you know that the SQL statements used in your application do not contain newline characters, the driver can improve performance by omitting the parsing required to remove them.
UseCurrentSchema
If your application needs to access tables and views owned only by the current user, performance of your application can be improved by setting this property to true. When this property is set to true, the driver returns only tables and views owned by the current user when executing
getTables() and getColumns() methods. Setting this property to true is equivalent to passing the user ID used on the connection as the schemaPattern argument to the getTables() or getColumns() call.
Setting the locationName on AS/400
When connecting to a DB2 database running on AS/400, you must set the
locationName property:
The following is an excerpt of the Java client:
Creating a DB2 Package
A DB2 package is a control structure on the DB2 server produced during program preparation that is used to execute SQL statements. The DB2 driver automatically creates all DB2 packages required at connection time. If a package already exists, the driver uses the existing package to establish a connection.
Note:
The initial connection may take a few minutes because of the number and size of the packages that must be created for the connection. Subsequent connections do not incur this delay.
When the driver has completed creating packages, it writes the following message to the standard output: DB2 packages created.
By default, DB2 packages created by the DB2 driver contain 200 dynamic sections and are created in the NULLID collection (or library). In most cases, you do not need to create DB2 packages because the DB2 driver automatically creates them at connection time. If required, you can create DB2 packages in either of the following ways:
Creating a DB2 Package Using dbping
To create a package on the DB2 server with the WebLogic Type 4 JDBC DB2 driver, you can use the WebLogic Server
dbping utility. The dbping utility is used to test the connection between your client machine and a DBMS via a JDBC driver. Because the WebLogic Type 4 JDBC DB2 driver automatically creates a DB2 package if one does not already exist, running this utility creates a default DB2 package on the DB2 server.
For details about using the
dbping utility to create a DB2 package, see 'Creating a DB2 Package with dbping' in Command Reference for Oracle WebLogic Server.
Creating a DB2 Package Using Connection Properties
You can create a DB2 package automatically by specifying specific connection properties in the initial connection URL. Table 3-2 lists the connection properties you should use in your initial connection URL when you create a DB2 package:
Note:
This method is not recommended for use with WebLogic Server JDBC data sources because every connection in the data source uses the same URL and connection properties. When a JDBC data source with multiple connections is created, the package would be recreated when each database connection is created.
Table 3-2 Connection Properties for an Initial Connection URL When Creating DB2 Packages
Db2 Jdbc Connection String
Using
CreateDefaultPackage=TRUE creates a package with a default name. If you use CreateDefaultPackage=TRUE , and you do not specify a CollectionId, the NULLID CollectionId is created.
Note:
To create new DB2 packages on DB2 for Linux/UNIX/Windows, you must use ReplacePackage=true in conjunction with CreateDefaultPackage=true . If a DB2 package already exists, it will be replaced when ReplacePackage=true .
Example for DB2 for Linux/UNIX/Windows:
The following URL creates DB2 packages with 400 dynamic sections. If any DB2 packages already exist, they will be replaced by the new ones being created.
Example for DB2 for z/OS and iSeries:
The following URL creates DB2 packages with 400 dynamic sections.
Notes About Increasing Dynamic Sections in the DB2 Package
A dynamic section is the actual executable object that contains the logic needed to satisfy a dynamic SQL request. These sections are used for handles and prepared statements and the associated result sets.
In some cases, you may need to create DB2 packages with more than the default number of dynamic sections (200). Consider the following information if your application requires DB2 packages with a large number of dynamic sections:
Data Types
Table 3-3 lists the data types supported by the DB2 driver and how they are mapped to JDBC data types.
Table 3-3 DB2 Data Types
Footnote 1 Supported only for DB2 v8.1 and v 8.2 for Linux/UNIX/Windows.
Footnote 2 Supported only for DB2 v8.1 and v 8.2 for Linux/UNIX/Windows.
Footnote 3 Supported only for DB2 v8.1 and v 8.2 for Linux/UNIX/Windows, DB2 for z/OS, and DB2 V5R2 and V5R3 for iSeries (see Large Object (LOB) Support).
Footnote 4 Supported only for DB2 v8.1 and v 8.2 for Linux/UNIX/Windows, DB2 7.x v8.1, and v8.2 for z/OS, and DB2 V5R2 and V5R3 for iSeries (see Large Object (LOB) Support).
Footnote 5 Supported only for DB2 v8.1 and v 8.2 for Linux/UNIX/Windows, DB2 7.x v8.1, and v8.2 for z/OS, and DB2 V5R2 and V5R3 for iSeries (see Large Object (LOB) Support).
Footnote 6 Supported only for DB2 for z/OS, and DB2 V5R2 and V5R3 for iSeries.
See Large Object (LOB) Support for more information about the Blob, Clob, and DBClob data types. See Returning and Inserting/Updating XML Data for more information about the XML data type.See Appendix B, 'GetTypeInfo' for more information about data types.
Returning and Inserting/Updating XML Data
For DB2 V9.1 for Linux/UNIX/Windows, the DB2 driver supports the XML data type. By default, the driver maps the XML data type to the JDBC CLOB data type, but you can choose to map the XML data type to the BLOB data type by setting the
XMLDescribeType connection property to a value of blob.
Returning XML Data
The driver can return XML data as character or binary data. For example, given a database table defined as:
and the following code:
The driver returns the XML data from the database as character or binary data depending on the setting of the
XMLDescribeType property. By default, the driver maps the XML data type to the JDBC CLOB data type. If the following connection URL mapped the XML data type to the BLOB data type, the driver would return the XML data as binary data instead of character data:
Character Data
When
XMLDescribeType=clob , XML data is returned as character data. The result set column is described with a column type of CLOB and the column type name is xml.
When
XMLDescribeType=clob , your application can use the following methods to return data stored in XML columns as character data:
The driver converts the XML data returned from the database server from the UTF-8 encoding used by the database server to the UTF-16 Java String encoding.
Your application can use the following method to return data stored in XML columns as ASCII data:
The driver converts the XML data returned from the database server from the UTF-8 encoding to the ISO-8859-1 (latin1) encoding.
Note:
The conversion caused by using the getAsciiStream() method may create XML that is not well-formed because the content encoding is not the default encoding and does not contain an XML declaration specifying the content encoding. Do not use the getAsciiStream() method if your application requires well-formed XML.
When
XMLDescribeType=blob , your application should not use any of the methods for returning character data described in this section. In this case, the driver applies the standard JDBC character-to-binary conversion to the data, which returns the hexadecimal representation of the character data.
Binary Data
When
XMLDescribeType=blob , the driver returns XML data as binary data. The result set column is described with a column type of BLOB and the column type name is xml.
When
XMLDescribeType=blob , your application can use the following methods to return XML data as binary data:
The driver does not apply any data conversions to the XML data returned from the database server. These methods return a byte array or binary stream that contains the XML data encoded as UTF-8.
When
XMLDescribeType=clob , your application should not use any of the methods for returning binary data described in this section. In this case, the driver applies the standard JDBC binary-to-character conversion to the data, which returns the hexadecimal representation of the binary data.
Inserting/Updating XML Data
The driver can insert or update XML data as character or binary data regardless of the setting of the
XMLDescribeType connection property.
Character Data
Your application can use the following methods to insert or update XML data as character data:
The driver converts the character representation of the data to the XML character set used by the database server and sends the converted XML data to the server. The driver does not parse or remove any XML processing instructions.
Your application can update XML data as ASCII data using the following methods:
The driver interprets the data supplied to these methods using the ISO-8859-1 (latin 1) encoding. The driver converts the data from ISO-8859-1 to the XML character set used by the database server and sends the converted XML data to the server.
Binary Data
Your application can use the following methods to insert or update XML data as binary data:
The driver does not apply any data conversions when sending XML data to the database server.
Authentication
Authentication protects the identity of the user so that user credentials cannot be intercepted by malicious hackers when transmitted over the network. See Authentication for an overview.
The DB2 driver supports the following methods of authentication:
The driver's
AuthenticationMethod connection property controls which authentication mechanism the driver uses when establishing connections. See Using the AuthenticationMethod Property for information about setting the value for this property.
Using the AuthenticationMethod Property
The
AuthenticationMethod connection property controls which authentication mechanism the driver uses when establishing connections.
When
AuthenticationMethod=kerberos , the driver uses Kerberos authentication when establishing a connection. The driver ignores any values specified by the User property and Password properties.
When
AuthenticationMethod=encryptedUIDPassword , AuthenticationMethod=encryptedPassword , or AuthenticationMethod=clearText (the default), the driver uses user ID/password authentication when establishing a connection. The User property provides the user ID. The Password property provides the password. The set of credentials that are passed to the DB2 server depend on the specified value:
If any of these values are set, the driver also can use data encryption by setting the
EncryptionMethod property.
When
AuthenticationMethod=client , the driver uses the user ID of the user logged onto the system on which the driver is running when establishing a connection. The DB2 database server relies on the client to authenticate the user and does not provide additional authentication. The driver ignores any values specified by the User property and Password properties.
Configuring User ID/Password Authentication
To configure user ID/password authentication:
Configuring Kerberos Authentication
This section provides requirements and instructions for configuring Kerberos authentication for the DB2 driver.
Product Requirements
Verify that your environment meets the requirements listed in Table 3-4 before you configure the driver for Kerberos authentication.
Table 3-4 Kerberos Authentication Requirements for the DB2 Driver
Configuring the Driver
During installation of the WebLogic Server JDBC drivers, the following files required for Kerberos authentication are installed in the
WL_HOME serverlib folder, where WL_HOME is the directory in which you installed WebLogic Server:
To configure the driver:
Specifying User Credentials for Kerberos Authentication
By default, when Kerberos authentication is used, the DB2 driver takes advantage of the user name and password maintained by the operating system to authenticate users to the database. By allowing the database to share the user name and password used for the operating system, users with a valid operating system account can log into the database without supplying a user name and password.
There may be times when you want the driver to use another set of user credentials. For example, many application servers or Web servers act on behalf of the client user logged on the machine on which the application is running, rather than the server user.
If you want the driver to use user credentials other than the server user's operating system credentials, include code in your application to obtain and pass a javax.security.auth.Subject used for authentication as shown in the following example.
Obtaining a Kerberos Ticket Granting Ticket
To use Kerberos authentication, the application user first must obtain a Kerberos Ticket Granting Ticket (TGT) from the Kerberos server. The Kerberos server verifies the identity of the user and controls access to services using the credentials contained in the TGT.
If the application uses Kerberos authentication from a Windows client, the application user does not need to explicitly obtain a TGT. Windows Active Directory automatically obtains a TGT for the user.
If the application uses Kerberos authentication from a UNIX or Linux client, the user must explicitly obtain a TGT. To explicitly obtain a TGT, the user must log onto the Kerberos server using the kinit command. For example, the following command requests a TGT from the server with a lifetime of 10 hours, which is renewable for 5 days:
where user is the application user.
Refer to your Kerberos documentation for more information about using the kinit command and obtaining TGTs for users.
Configuring Client Authentication
Set the
AuthenticationMethod property to client. See Using the AuthenticationMethod Property for more information about setting a value for this property.
Data Encryption
The DB2 driver now supports SSL encryption for DB2 V5R3 and higher for iSeries. SSL secures the integrity of your data by encrypting information and providing authentication. The DB2 driver supports both SSL server authentication and SSL client authentication.
See SSL Encryption for more information.
Note:
Data encryption may adversely affect performance because of the additional overhead (mainly CPU usage) required to encrypt and decrypt data.
Configuring SSL Encryption
Note:
Connection hangs can occur when the driver is configured for SSL and the database server does not support SSL. You may want to set a login timeout using the LoginTimeout property to avoid problems when connecting to a server that does not support SSL.
To configure SSL encryption:
Non-Default Schemas for Catalog Methods
To ensure that catalog methods function correctly when the
CatalogSchema property is set to a schema other than the default schema, views for the catalog tables listed in Table 3-5 must exist in the specified schema. The views that are required depend on your DB2 database.
Table 3-5 Catalog Tables for DB2
Reauthentication
The DB2 driver supports reauthentication for the following databases:
Before performing reauthentication, applications must ensure that any statements or result sets created as one user are closed before switching the connection to another user.
Your application can use the
setCurrentUser() method in the ExtConnection interface to switch a user on a connection.
The
setCurrentUser() method accepts driver-specific reauthentication options. The options supported for the DB2 driver are:
CURRENT_SCHEMA
Specifies the name of the current schema. The value must be a valid DB2 schema name.
If the
setCurrentUser() method is called and this option is not specified or the value is set to #USER# , the schema is switched to the schema of the current user. If the setCurrentUser() method is called and this option is specified as an empty string, only the user is switched; the schema is not switched.
CURRENT_PATH
Specifies the current path for the database to use when locating stored procedures and functions. The value must be a valid path name for the
DB2 CURRENT PATH special register.
If the
setCurrentUser() method is called and this option is not specified or the value is set to #USER# , the path is switched to the path of the current user. If the setCurrentUser() method is called and this option is specified as an empty string, only the user is switched; the path is not switched.
SQL Escape Sequences
See Appendix C, 'SQL Escape Sequences for JDBC' for information about SQL escape sequences supported by the DB2 driver.
Isolation Levels
The DB2 driver supports the isolation levels listed in Table 3-6. JDBC isolation levels are mapped to the appropriate DB2 transaction isolation levels as shown. The default isolation level is
Read Committed .
Table 3-6 Supported Isolation Levels
Footnote 1 Supported for DB2 iSeries versions that do not enable journaling.
Using Scrollable CursorsAs400 Jdbc Connection String
The DB2 driver supports scroll-insensitive result sets and updatable result sets.
Note:
When the DB2 driver cannot support the requested result set type or concurrency, it automatically downgrades the cursor and generates one or more SQLWarnings with detailed information.
JTA Support
To use distributed transactions through JTA with the DB2 driver, you must use one of the following database versions:
Large Object (LOB) Support
Retrieving and updating Blobs is supported by the DB2 driver with the following databases:
Retrieving and updating Clobs is supported by the DB2 driver with all supported DB2 databases. The DB2 driver supports Clobs up to a maximum of 2 GB with the following DB2 databases:
The DB2 driver supports retrieving and updating Clobs up to a maximum of 32 KB with all other supported DB2 databases.
Retrieving and updating DBClobs is supported by the DB2 driver with the following databases:
Batch Inserts and Updates
The DB2 driver uses the native DB2 batch mechanism. By default, the methods used to set the parameter values of a batch performed using a PreparedStatement must match the database data type of the column with which the parameter is associated.
DB2 servers do not perform implicit data conversions, so specifying parameter values that do not match the column data type causes the DB2 server to generate an error. For example, to set the value of a Blob parameter using a stream or byte array when the length of the stream or array is less than 32 KB, you must use the
setObject() method and specify the target JDBC type as BLOB; you cannot use the setBinaryStream() or setBytes() methods.
To remove the method-type restriction, set the
BatchPerformanceWorkaround property to true. For example, you can use the setBinaryStream() or setBytes() methods to set the value of a Blob parameter regardless of the length of the stream or array; however, the parameter sets may not be executed in the order they were specified. Performance may be decreased because the driver must convert the parameter data to the correct data type and re-execute the statement.
Note:
Db2 Jdbc ConnectionWhen you create a data source in the Administration Console, the Administration Console sets the BatchPeformanceWorkaround connection property to true by default.
For data sources used as a JMS JDBC store that use the WebLogic Type 4 JDBC driver for DB2, the BatchPerformanceWorkaround property must be set to true.
Parameter Metadata Support
The DB2 driver supports returning parameter metadata as described in this section.
Insert and Update Statements
The DB2 driver supports returning parameter metadata for all types of SQL statements with the following DB2 databases:
For DB2 v7x for Linux/UNIX/Windows and DB2 V5R1 for iSeries, the DB2 driver supports returning parameter metadata for the following forms of Insert and Update statements:
where operator is any of the following SQL operators: =, <, >, <=, >=, and <>.
Select Statements
The DB2 driver supports returning parameter metadata for all types of SQL statements with the following DB2 databases:
For DB2 v7x for Linux/UNIX/Windows and DB2 V5R1 for iSeries, the DB2 driver supports returning parameter metadata for Select statements that contain parameters in ANSI SQL 92 entry-level predicates, for example, such as COMPARISON, BETWEEN, IN, LIKE, and EXISTS predicate constructs. Refer to the ANSI SQL reference for detailed syntax.
Parameter metadata can be returned for a Select statement if one of the following conditions is true:
The following Select statements show further examples for which parameter metadata can be returned:
ANSI SQL 92 entry-level predicates in a WHERE clause containing GROUP BY, HAVING, or ORDER BY statements are supported. For example:
Joins are supported. For example:
Fully qualified names and aliases are supported. For example:
Stored Procedures
The DB2 driver supports returning parameter metadata for stored procedure arguments.
ResultSet Metadata Support
If your application requires table name information, the DB2 driver can return table name information in ResultSet metadata for Select statements. By setting the
ResultSetMetaDataOptions property to 1, the DB2 driver performs additional processing to determine the correct table name for each column in the result set when the ResultSetMetaData.getTableName() method is called. Otherwise, the getTableName() method may return an empty string for each column in the result set.
The table name information that is returned by the DB2 driver depends on whether the column in a result set maps to a column in a table in the database. For each column in a result set that maps to a column in a table in the database, the DB2 driver returns the table name associated with that column. For columns in a result set that do not map to a column in a table (for example, aggregates and literals), the DB2 driver returns an empty string.
The Select statements for which ResultSet metadata is returned may contain aliases, joins, and fully qualified names. The following queries are examples of Select statements for which the
ResultSetMetaData.getTableName() method returns the correct table name for columns in the Select list:
The table name returned by the driver for generated columns is an empty string. The following query is an example of a Select statement that returns a result set that contains a generated column (the column named 'upper').
The DB2 driver also can return schema name and catalog name information when the
ResultSetMetaData.getSchemaName() and ResultSetMetaData.getCatalogName() methods are called if the driver can determine that information. For example, for the following statement, the DB2 driver returns 'test' for the catalog name, 'test1' for the schema name, and 'foo' for the table name:
The additional processing required to return table name, schema name, and catalog name information is only performed if the
ResultSetMetaData.getTableName() , ResultSetMetaData.getSchemaName() , or ResultSetMetaData.getCatalogName() methods are called.
Rowset Support
The DB2 driver supports any JSR 114 implementation of the RowSet interface, including:
J2SE 1.4 or higher is required to use rowsets with the driver.
See
http://www.jcp.org/en/jsr/detail?id=114 for more information about JSR 114.
Auto-Generated Keys Support
The DB2 driver supports retrieving the values of auto-generated keys. An auto-generated key returned by the DB2 driver is the value of an auto-increment column.
An application can return values of auto-generated keys when it executes an Insert statement. How you return these values depends on whether you are using an Insert statement that contains parameters:
An application can retrieve values of auto-generated keys using the
Statement.getGeneratedKeys() method. This method returns a ResultSet object with a column for each auto-generated key.
Database Connection Property
The new Database connection property can be used as a synonym of the
DatabaseName connection property.
If both the Database and DatabaseName connection properties are specified in a connection URL, the last of either property positioned in the connection URL is used. For example, if your application specifies the following connection URL, the value of the Database connection property would be used instead of the value of the DatabaseName connection property.
DatabaseName Connection Property
The LocationName connection property is only supported when connecting to DB2 for z/OS or iSeries to specify the name of the DB2 location. Now, your application can use the DatabaseName connection property when you are connecting to DB2 for Linux/UNIX/Windows, z/OS, or iSeries.
When connecting to DB2 for Linux/UNIX/Windows, the DatabaseName connection property specifies the name of the database. Made wijaya bali drivers for mac. When connecting to DB2 for z/OS or iSeries, the DatabaseName connection property specifies the name of the DB2 location.
New Data Types
The DB2 driver now supports:
Table 3-7 and Table 3-8 list these data types and describe how they are mapped to JDBC data types.
Table 3-7 DB2 Graphic Data Types
Table 3-8 New DB2 Data Types Supported for DB2 v9.1 for z/OS
See Appendix B, 'GetTypeInfo' for a description of the data types returned by the getTypeInfo() method.
For more information about using the XML data type, see Returning and Inserting/Updating XML Data.
For information about other data types supported by the DB2 driver, see Data Types.
SQL Procedures for z/OS
SQL Procedures now are supported for DB2 v9.1 for z/OS.
IPv6 Support
The DB2 driver now supports IPv6 for DB2 v9.1 for z/OS.
For more information about IPv6, see Using IP Addresses.
Bulk Load
The driver supports DataDirect Bulk Load, a feature that allows your application to send large numbers of rows of data to the database in a continuous stream instead of in numerous smaller database protocol packets. Similar to batch operations, performance improves because far fewer network round trips are required. Bulk load bypasses the data parsing usually done by the database, providing an additional performance gain over batch operations.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |