Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix memory errors in Docker 1.2.0 #5

Closed
jbonhag opened this issue Sep 26, 2014 · 2 comments
Closed

Fix memory errors in Docker 1.2.0 #5

jbonhag opened this issue Sep 26, 2014 · 2 comments

Comments

@jbonhag
Copy link
Owner

jbonhag commented Sep 26, 2014

Seems like DB2 is running out of memory, even while running in privileged mode and with shmmax set.

IBM sez:

At a minimum, a DB2 database system requires 256 MB of RAM. For a system running just a DB2 product and the DB2 GUI tools, a minimum of 512 MB of RAM is required. However, 1 GB of RAM is recommended for improved performance. These requirements do not include any additional memory requirements for other software that is running on your system.
When determining memory requirements, be aware of the following:
DB2 products that run on HP-UX Version 11i for Itanium-based systems require 512 MB of RAM at a minimum.

For IBM® data server client support, these memory requirements are for a base of five concurrent client connections. You will need an additional 16 MB of RAM per five client connections.
Memory requirements are affected by the size and complexity of your database system, and the extent of database activity and the number of clients accessing your system.

For DB2 server products, the self-tuning memory feature simplifies the task of memory configuration by automatically setting values for several memory configuration parameters. When enabled, the memory tuner dynamically distributes available memory resources among several memory consumers including sort, the package cache, the lock list and buffer pools.
DB2 requires paging, also called swap to be enabled. This configuration is required to support various functions in DB2 which monitor or depend on knowledge of swap/paging space utilization. The actual amount of swap/paging space required varies across systems and is not solely based on memory utilization by application software. It is only strictly required by DB2 on the Solaris and HP platforms due to their use of early paging space allocation.

A reasonable minimum swap/paging space configuration for most systems is 25-50% of RAM. Solaris and HP systems with many small databases or multiple databases tuned by STMM might require a paging space configuration of 1 x RAM or higher. These higher requirements are due to virtual memory pre-allocated per database / instance, and retained virtual memory in the case of STMM tuning multiple databases. Additional swap/paging space might be wanted to provision for unanticipated memory overcommitment on a system.

@jbonhag
Copy link
Owner Author

jbonhag commented Sep 26, 2014

Here's a dump of the error (sent from inside a Ubuntu 14.04 container):

https://gist.github.com/anonymous/b693cd719fb276c3fde5

@jbonhag jbonhag closed this as completed Oct 29, 2014
@jbonhag
Copy link
Owner Author

jbonhag commented Oct 29, 2014

This is really a duplicate of #2 .

@jbonhag jbonhag reopened this Oct 29, 2014
@jbonhag jbonhag closed this as completed Oct 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant