Error while taking GC heap Dump using Microsoft PerfView

Question

Hello,
When I try to take heap dump for an application process using Microsoft
PerfView , error observed
and the error log given below. Can you please let me know the root cause for his issue ?
Steps followed
From the PerfView UI, choose “Take Heap Snapshot,” located on the Memory menu.
And choose the process to capture
Click the “Dump GC Heap” button or simply double click on the process name.
Error Log
Completed: Dumping GC Heap to C:\Install\TM\PerfView\TestProcess.gcDump   (Elapsed Time: 1.156 sec)
Error: HeapDump failed with exit code 1
Directory TestProcess.gcdump does not exist
Started: Dumping GC Heap to C:\Install\TM\PerfView\TestProcess.1.gcDump
Collecting a GC Heap SnapShot for process 1704
[Taking heap snapshot of process '1704' ID 1704 to TestProcess.1.gcdump.  This can take 10s of seconds to minutes.]
During the dump the process will be frozen.   If the dump is aborted, the process being dumped will need to be killed.
Starting dump at 8/08/2014 3:55:15 PM
Starting Heap dump on Process 1704 running architecture AMD64.
set _NT_SYMBOL_PATH=SRV*C:\Users\UserId\AppData\Local\Temp\3\symbols*http://msdl.microsoft.com/download/symbols
Exec: "C:\Users\UserId\AppData\Roaming\PerfView\VER.2014-08-08.13.49.17.346\AMD64\HeapDump.exe"  /MaxDumpCountK=250 "1704" "TestProcess.1.gcdump"
Looking for C:\Users\UserId\AppData\Roaming\PerfView\VER.2014-08-08.13.49.17.346\Microsoft.Diagnostics.FastSerialization.dll
Dumping process 1704 with id 1704.
Process Has DotNet: False Has JScript: False Has ClrDll: False
HeapDump Error: Could not dump either a .NET or JavaScript Heap.  See log file for details
Completed: Dumping GC Heap to C:\Install\TM\PerfView\TestProcess.1.gcDump   (Elapsed Time: 1.172 sec)
Error: HeapDump failed with exit code 1
Directory TestProcess.1.gcdump does not exist

Answer 1

Hi,
Below is the DDL taken from different database. Will this be enough ? One more thing please, what shall be the password should it be DMSYS.....since this will not be used by me but system.
CREATE USER "DMSYS" PROFILE "DEFAULT" IDENTIFIED BY "*******" PASSWORD EXPIRE DEFAULT TABLESPACE "SYSAUX" TEMPORARY TABLESPACE "TEMP" QUOTA 204800 K ON "SYSAUX" ACCOUNT LOCK
GRANT ALTER SESSION TO "DMSYS"
GRANT ALTER SYSTEM TO "DMSYS"
GRANT CREATE JOB TO "DMSYS"
GRANT CREATE LIBRARY TO "DMSYS"
GRANT CREATE PROCEDURE TO "DMSYS"
GRANT CREATE PUBLIC SYNONYM TO "DMSYS"
GRANT CREATE SEQUENCE TO "DMSYS"
GRANT CREATE SESSION TO "DMSYS"
GRANT CREATE SYNONYM TO "DMSYS"
GRANT CREATE TABLE TO "DMSYS"
GRANT CREATE TRIGGER TO "DMSYS"
GRANT CREATE TYPE TO "DMSYS"
GRANT CREATE VIEW TO "DMSYS"
GRANT DROP PUBLIC SYNONYM TO "DMSYS"
GRANT QUERY REWRITE TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_JOBS_RUNNING" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_REGISTRY" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_SYS_PRIVS" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_TAB_PRIVS" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_TEMP_FILES" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_LOCK" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_REGISTRY" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_SYSTEM" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_SYS_ERROR" TO "DMSYS"
GRANT DELETE ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT INSERT ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT SELECT ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT UPDATE ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT SELECT ON "SYS"."V_$PARAMETER" TO "DMSYS"
GRANT SELECT ON "SYS"."V_$SESSION" TO "DMSYS"
The other database has the DMSYS and the status is EXPIRED & LOCKED but I'm still able to take the dump using datapump??