Version 1.1.1.117 adds general dump and memory heap dump analysis functionality

Besides a couple of small other changes, there are two new features in this release of Mumbai.

First, you can now analyze Oracle heap dump trace files in Mumbai. Once again, this functionality was inspired by a blog post by Tanel Põder. He created a shell script for aggregating the chunk sizes found in heap dump trace files and while I used this script quite a few times, I found it a bit awkward to have it available on LinuxUnix systems only and not on Windows.

What you can now do is to open a trace file with heap dump information and Mumbai will analyze the trace file and aggregate over the heap names and allocation reason as shown in the screenshot below.

Mumbai will warn you if it finds information about the same heap block (identified by the heap name) more than once, e.g. because the information was dumped to the same trace file twice and you can filter on the last column “Heap block occurrence” to see the aggregated data for the occurrence you wish to see (you might want to filter on the “Trace file line number” column, too).

The second new feature is a dialog to create Oracle memory dump trace files as seen below.

When you check the “Retrieve trace file after execution” box (and the Mumbai42 schema which holds this functionality is available in the database), Mumbai will retrieve the generated trace file and open it and in the case of a memory heap dump trace, you can send it to the heap dump analyzer with another click of a button.
As with lots of functionality in Mumbai, handle with care and make sure you know what you do. Trace files can get quite large and depending on what kind if trace dump you initiate it can bring your database instance to a full stop for some time.

About these ads
This entry was posted in Mumbai. Bookmark the permalink.

2 Responses to Version 1.1.1.117 adds general dump and memory heap dump analysis functionality

  1. Tanel Poder says:

    Nice work!
    Not sure whether you already do this, but it’s worth displaying a warning when the user wants to take a shared pool dump (SGA bit) as it may cause lots of trouble.

    Btw, this script should work on any Unix with shell and awk – not just Linux. I’ve used it on Solaris as well and if it doesn’t work on AIX/HP-UX it should be matter of tweaking/fixing a bug..

    • Yes, I’ll add a general warning in this window, since I do not know what might be side effects of initiating other memory dumps. But then, I would probably need a warning in lots of places.

      Regarding your shell script, I used it only on Linux, which is why I wrote it like this. I’ll correct that.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s