Windows: Using UMDH Tracing to Gather Memory Diagnostics for Oracle Executables
(Doc ID 2281972.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Microsoft Windows x64 (64-bit)
Sometimes OS tracing is needed to analyze memory leaks for Oracle executables. Should you be asked by Support to provide such tracing the general method is described in the Microsoft Document “Using UMDH to Find a User-Mode Memory Leak” available at https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/using-umdh-to-find-a-user-mode-memory-leak
The following article describes this in a bit more detail and specifically using the example of an Oracle process.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|PART A: Installing the Windows Debugging Tools.|
|PART B: - Setting up the Windows OS environment|
|PART C: - Using UDHM to Trace a Process.|