IBM Data Management Community Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems. Join / Log in
I face a very strange issues, running DB2 126.96.36.199 on Debian Buster virtualized with Proxmox.
We have several hypervisors, several of them are AMD EPYC 7371 based and when I CREATE DATABASE on a virtual machine running on one of these everything runs smoothly.
A new AMD EPYC 7343 hypervisor is now available, and when I migrate the exact same virtual machine on it, "CREATE DATABASE" hangs with two db2sysc hitting 100%. In db2diag, nothing happens after "DB2SPCAT Views recreated", while the next step on the other hypervisors is "FUNCTION: DB2 Common, Cryptography, cryptContextRealInit, probe:2716".
I checked the AESNI with openssl and it works fine in both contexts.
I also tried to limit the CPU flags to the very basic set without more success.
CREATE DATABASE is not only symptom but as it is can easily be reproduced I use it for debugging.
I'm a bit lost here with the next steps for debugging, any help would be greatly appreciated.
You may want to review the system requirements for running Db2. IBM provides a list of supported distributions and hypervisors. While you may be able to run in other environments, you may run in to strange issues like what you're seeing.
Here is the report for Db2 11.5.8 Standard Edition on Linux:
Hi!As Ian stated - if you consider "production level" Db2 installation - you are strongly advised to follow and adhere to system requirements for running Db2.For my personal amusement I set up Debian (Debian 12) installation in Oracle Virtual Box VM and I installed Db2 V11.5.8.One of the red lights should grab your attention was message from db2prereqcheck:However - if you know Db2 prerequisites and how to address them - you may complete installation:As you can see - SAMPLE database was created and is accessible.I would suspect your virtualizer as guilty party.I would not run production workload on my Debian distribution in Virtual Box though.
Thanks for your answers, we tried with Ubuntu 20 on the same hypervisor and did not face the issue.
I will follow your advice and switch to a supported OS.
Thank a lot for your replies.
I would strongly advise to switch to Supported OS (for example Ubuntu 2204 - which is LTS) under Supported virtualiser ...