IBM Support

How Is a Memory Dump Taken?

Technote (FAQ)


Question

It has been determined that a memory dump must be taken on a Domino server to further narrow down a problem. How is this done?

The following errors are some that would require the collection of a memory dump:

    "Maximum Number of Memory Segments that Notes Can Support Has Been Exceeded."

    "Insufficient Memory."

    "Insufficient Memory. NSF Pool is Full."

Answer

Note: When you create a memory dump on your Domino server, the file is always saved with the same file name (memory.dmp). As a result, if the preceding memory.dmp file is not removed (or renamed) prior to initiating a subsequent memory dump, the information in the file will be overwritten. For information about avoiding that, refer to the document titled "How To Avoid Memory Dumps Being Overwritten on a Domino Server" (#193090).


Method 1:

To create a Notes memory dump, do the following:

1. From an operating system prompt, switch to the Notes program directory.

2. Issue one of the following commands, depending on whether the server is R4 or R5:

R4 Servers: notes server -m
R5 Servers: nserver -m

NOTE: For Unix machines (Solaris, AIX, HP-UX), the command is: server -m

This will create a file called MEMORY.DMP that will be placed in the Notes\Data directory.

NOTE: If the memory dump is being collected on a Domino partitioned server, the following command should be issued after switching to the Notes program directory and before the memory dump is actually taken (this will set the partition on which the memory dump will be taken):

Set Notespartition="x" (where "x" represents the number of the partition on which you want to run the memory dump.)

The MEMORY.DMP file should be sent in to Lotus Notes Support for analysis.

Method 2:

Another way to take a memory dump is with the following command on the server console:

    sh memory dump

This will yield the memory available, including virtual memory on the server console. It will also create a MEMORY.DMP file in the Domino\Data directory in R4 and R5 and, by default, in the IBM_TECHNICAL_SUPPORT directory in Domino 6.x. For example:
    > sh memory dump
    Memory Available (including virtual): 1,295.62890625 Mbytes
    05/03/2005 03:04:08 PM Created memory dump file 'c:\651\data\IBM_TECHNICAL_SUPPORT\memory_2005_05_03@15_04_04.dmp'

To pipe the available memory out to a file instead of viewing it on the server console, enter the following server console command:
    sh memory dump >memory.txt

This command will still give you a MEMORY.DMP in either the data directory or in the data\IBM_TECHNICAL_SUPPORT directory, as well as a MEMORY.TXT in the Domino program directory.

Method 3:

At the Domino server console (as opposed to at an OS command prompt), type the following and press ENTER:

load server -m

This will create a memory.dmp file in the data directory.


HOW TO TAKE A MEMORY DUMP ON AS/400 PLATFORM

The following are instructions for collecting the memory dump on the AS/400 platform:

1. Execute the AS/400 command, WRKDOMSVR, to access the Domino console of the server experiencing the memory issue.

2. Select option 8 next to the desired server to work with the Domino console.

3. Issue the following Domino command from the console to create the memory dump: Show Memory Dump

4. The message "Memory Available: ### Mbytes" will appear on the console when the dump is complete and the file MEMORY.DMP is created.

5. The MEMORY.DMP file is placed in the data directory of the server, and its contents replaced during each run of the command.

6. When you use F3 to exit the Domino console and return to the WRKDOMSVR display, press F11 to change the view and identify the server's data directory if necessary.

Supporting Information:

If an error is involved, the memory dump should be taken at the time of the error ( before the server is rebooted). If a server is suspected of experiencing a memory leak without any error messages, periodic memory dumps should be collected.

Document information

More support for: IBM Domino

Software version: 6.0, 6.5, 7.0, 8.0, 8.5, 9.0

Operating system(s): AIX, IBM i, Linux, Solaris, Windows, z/OS

Reference #: 1086202

Modified date: 05 May 2005