This issue is not simply a "memory" issue. Perhaps you have run into the same issue that hit me. In an attempt to increase the security of my system, I removed the DB2 user(s) from the Windows Administrators group, assuming that the DB2 user simply needed to be in the DB2ADMINS group. Apparently, a process must need to be an Administrator (or something more than a DB2ADMIN at least) to allocate the type of memory that DB2 is trying to allocate. So, you may want to check to see if your DB2 user(s) are in the Administrator group.