db2jdbcbind - Db2 JDBC package binder command
This utility is used to bind or rebind the JDBC packages to a Db2 database.
JDBC and CLI share the same packages. If the CLI packages have already been bound to a database, then it is not necessary to run this utility and vice versa.
Authorization
One of the following authorities:
- DBADM
- BINDADD privilege if a package does not exist, and one of:
- IMPLICIT_SCHEMA authority on the database if the schema name of the package does not exist
- CREATEIN privilege on the schema if the schema name of the package exists
- ALTERIN privilege on the schema if the package exists
- BIND privilege on the package if it exists
Required connection
This command establishes a database connection.
Command syntax
Command parameters
- -help
- Displays help information, all other options are ignored.
- -url jdbc:db2://servername:portnumber/dbname
- Specifies a JDBC URL for establishing the database connection. The Db2 JDBC type 4 driver is used to establish the connection.
- -user username
- Specifies the name used when connecting to a database.
- -password password
- Specifies the password for the user name.
- -collection collection ID
- The collection identifier (CURRENT PACKAGESET), to use for the packages. The default is NULLID. Use this to create multiple instances of the package set. This option can only be used in conjunction with the Connection or DataSource property currentPackageSet.
- -size number of packages
- The number of internal packages to bind for each Db2 transaction isolation level and holdability setting. The default is 3, and the maximum value is 253. Since there are four Db2 isolation levels and two cursor holdability settings, there will be 4x2=8 times as many dynamic packages bound as are specified by this option. In addition, a single static package is always bound for internal use.
- -tracelevel
- Identifies the level of tracing, only required for troubleshooting.
