Progress package installation on Db2LUW database server

Data Integrity Suite

Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2025

Learn how the Db2 driver manages package creation automatically and how to explicitly create or update Db2 packages if needed.

Automatic Db2 Package Creation

The Db2 driver automatically creates all required Db2 packages the first time it connects to a database. By default, these packages:

  • Contain 200 dynamic sections
  • Are created in the NULLID collection (or library)
Note: The initial connection may take a few minutes because the driver must create several large packages. This delay only occurs during the first connection. Once the packages are created, the driver writes the following message to the standard output: DB2 packages created.

When to Explicitly Create Db2 Packages

In most cases, you do not need to manually create Db2 packages, as the driver handles this automatically. However, you may need to explicitly create or update packages in the following situations:

  • You want to pre-create packages to avoid delays during the first connection.
  • You need to update existing packages with new versions.
  • Your organization requires manual package management for security or compliance reasons.

Prerequisites

Before creating Db2 packages manually, ensure you have the following:

  • Access to the appropriate list (*.lst) and bind (*.bnd) files for your operating system.
  • BINDADD privileges on the target database. Consult your database administrator to confirm your privileges.
  • Access to the Db2 command-line utility on the database server.

Steps to Explicitly Create Db2 Packages

  1. Install the List and Bind Files Copy the required *.lst and *.bnd files to a directory on the database server.

  2. Start the Db2 Command-Line Utility Open a terminal or command prompt and navigate to the directory where you placed the files.

  3. Connect to the Database Use the following command to connect to your database:

    connect to database_name user authorization_name using password

    Replace database_name with the name of your database, authorization_name with your user name, and password with your password.

  4. Bind the List File Execute the following command to create or update the Db2 packages:

    bind @list_file grant public                    

    Replace list_file with the name of the list file you want to bind. This command will create packages with 200 dynamic sections in the NULLID collection. If packages already exist, they will be replaced.

Note: The user ID performing the bind operation must have BINDADD privileges on the database.

Troubleshooting

If you encounter issues during package creation:

  • Verify that you have the correct privileges (BINDADD) on the database.
  • Ensure you are using the correct list and bind files for your operating system.
  • Check for error messages in the command-line output for more details.