Windows: exspad<PID>.err Files Remain Forever After Executing exectask.exe
Last updated on SEPTEMBER 04, 2016
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Oracle Database - Standard Edition - Version 22.214.171.124 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms