My Oracle Support Banner

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

Last updated on FEBRUARY 27, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Oracle Database - Standard Edition - Version 11.2.0.4 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
Microsoft Windows x64 (64-bit)

Symptoms

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.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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