My Oracle Support Banner

Windows: exspad<PID>.err Files Remain Forever After Executing exectask.exe (Doc ID 2178935.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database - Standard Edition - Version and later
Microsoft Windows x64 (64-bit)


Many exspad<PID>.err files are created under "%TEMP%\CVU_<PSR>_<Server_name>$\scratch" directory after executing exectask.exe and they remain there forever, each file size is 0 byte.

If Oracle Clusterware is monitored by Oracle Enterprise Manager (OEM), exspad<PID>.err files can be accumulated because OEM frequently uses exectask.exe.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.