Bug Report

[PatrikHysky]

Since upgrading from 3.2.9 to 3.3.0, pip no longer installs a prebuilt wheel on our Python 3.11 Linux x86_64 environment and instead downloads ibm_db-3.3.0.tar.gz and attempts to build locally. The build process exceeds memory limits in our Kubernetes/OpenShift CronJob and is OOMKilled with 256 MB RAM. Version 3.2.9 downloads and installs ibm_db-3.2.9-cp311-cp311-manylinux2014_x86_64.whl successfully with just 128 MB RAM.

Install log with 3.3.0 (fail):

Collecting ibm_db
Downloading ibm_db-3.3.0.tar.gz (315 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 315.3/315.3 kB 45.1 MB/s eta 0:00:00
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: still running...
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Building wheels for collected packages: ibm_db
Building wheel for ibm_db (pyproject.toml): started
OOMKilled

Install log with 3.2.9 (sucess):

installing ibm_db
Collecting ibm_db==3.2.9
Obtaining dependency information for ibm_db==3.2.9 from https://files.pythonhosted.org/packages/12/9d/9c0c4cf2eacfdfd5faf2f878ca1e2fdb02640a21f3defa2390c0d41c85cc/ibm_db-3.2.9-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl.metadata
Downloading ibm_db-3.2.9-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl.metadata (35 kB)
Downloading ibm_db-3.2.9-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl (44.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 44.0/44.0 MB 34.3 MB/s eta 0:00:00
Installing collected packages: ibm_db
Successfully installed ibm_db-3.2.9

• Operating System Name: Linux x86_64
• Python Version: 3.11
• ibm_db version: 3.3.0

[Earammak]

@PatrikHysky,

Thanks for reporting the issue and for sharing the install logs.

Starting with ibm_db 3.3.0, the Linux wheel build was updated to use the newer IBM Db2 CLI Driver v12.1.x. This newer CLI Driver has additional runtime requirements on Linux: glibc >= 2.34 and CPU support for the x86_64-v2 instruction set. Because of this, the official Linux wheels for ibm_db 3.3.0 are built with the newer manylinux_2_34 image instead of the older manylinux2014 image used by previous releases such as 3.2.9.

If your container/base image is based on an older Linux distribution, for example RHEL 8 / UBI 8 or another image with glibc < 2.34, pip will not consider the ibm_db 3.3.0 Linux wheel compatible with that environment. In that case pip falls back to the source distribution, ibm_db-3.3.0.tar.gz, and tries to build locally. The local build requires significantly more memory than installing a prebuilt wheel.

That is why ibm_db 3.2.9 installs successfully in the same environment: that release had a manylinux2014_x86_64 wheel compatible with older glibc versions.

You can use one of the following workarounds:

1. Use a newer Linux base image that provides glibc >= 2.34, such as RHEL 9 / UBI 9, Debian 12, Ubuntu 22.04 or newer. Then pip should be able to install the compatible prebuilt ibm_db 3.3.0 wheel.

2. If you must stay on the older base image, continue using ibm_db 3.2.9 for now, since it provides a manylinux2014 wheel compatible with that environment.

3. Build ibm_db 3.3.0 from source using the older CLI Driver v11.5.9, and perform that build in an environment with enough memory. For example:

   export CLIDRIVER_VERSION=v11.5.9
   pip install ibm_db --no-binary :all: --no-cache-dir

   After building, you can publish the resulting wheel to your internal package repository and install that prebuilt wheel in the low-memory CronJob environment.

To confirm the compatibility condition in your container, please share the output of:

ldd --version
python -m pip debug --verbose

Based on the logs, this does not look like a pip installation bug. It is expected fallback behavior when no compatible prebuilt wheel is available for the current Linux/glibc platform.

Thanks