Basic commands (db2level) not running on no cost Db2 Community Edition 11.5.5 (latest)

Question

The previous DB2 Express-C versions were working fine over the years, but the basic commands not running on no cost Db2 Community Edition 11.5.5 (latest) .

after installing the Db2 Community Edition 11.5.5, when running the db2level command, it gives the error:

SQL1022C  There is not enough memory available to process the command.

and below links didn't help:

• https://www.ibm.com/support/pages/error-sql1022c-there-not-enough-memory-available-process-command-after-changing-hostname-db2-server
• https://www.ibm.com/support/pages/running-db2level-db2-command-window-returning-sql1022c

Some my findings are:

db2set' not working  - DBI1302E  Invalid parameter detected.

'db2set -all' working   - DB2_EXTSECURITY=YES

'db2level' - SQL1022C  There is not enough memory available to process the command.

'db2start' not working - SQL1390C  The environment variable DB2INSTANCE is not defined or is invalid.

DB2 icon not presented on taskbar

db2 get dbm cfg | find "SYSADM"  - not working (no output)

db2 get dbm cfg - DB21018E  A system error occurred. The command line processor could not continue processing.

db2 update dbm cfg using sysadm_group DB2ADMNS - DB21018E  A system error occurred. The command line processor could not continue processing.

---

• Followed the same recommended steps (for DB2 installation) as being following since DB2 9.7 version (on WIN 8.1 machine + RAM 8 GB).
• My logged-in user is machine administrator
• The supplied user is 'db2admin'
• Now on the problem machine, OS is Windows 10 Pro + RAM 8 GB.
• 1. Ran the setup.exe after extracting the downloaded zip
• 2. From the DB2 Setup Launchpad > Install a Product > DB2 Version 11.5.5.0 Server Editions > Install Now > then installed with all default settings
• DB2 setup installed successfully but DB2 commands not working as explained above

---

Answer 1

I had the same issue but after installing db2 with administrator privileges (starting setup.exe as an admin) the issues were gone and everything was set up as expected.