ALECDC, ARGLTP, XDPCTRLS, FNDLIBR writing core files

After moving the storage to Solaris 10 or cloning from Solaris 8 box to Solaris 10 box, in a few instances the /var/crash/cores directory was reaching 100%. It was full of cores written by ALECDC, ARGLTP, XDPCTRLS, FNDLIBR, MSONEW, MSCSLD etc. I logged an SR with Oracle and they asked me for a stack trace. Metalink Note 1812.1 describes how to get a stack trace from a core file. Here's what I did:

Stack trace for ARGLTP

$ adb /apps11i/erp/appl/ar/11.5.0/bin/ARGLTP
1207343405-ARGLTP-16927-66128-54055-tsgsd1007-sun4u
core file = 1207343405-ARGLTP-16927-66128-54055-tsgsd1007-sun4u -- program
``
/apps11i/erp/appl/ar/11.5.0/bin/ARGLTP'' on platform SUNW,Netra-T12
SIGSEGV: Segmentation Fault
$c
libc.so.1`strcmp+0x60(174ba4, 73737431, 0, 0, 1d1900, 1d18e0)
afppre+0x1cc(2a9900, 262b50, 50, 50, ff1ea2b4, ff1f29f8)
fdpcls+0x3e4(4e, 1c3df4, 1c3de4, 1c3c00, 1c3c00, 1)
main+0x7704(14fc30, 14fc74, ffbf9efc, a, 2a5e28, 7f80)
_start+0xdc(0, 0, 0, 0, 0, 0)
$q

We nailed it finally after long discussions with Oracle. It was a bug. After ATG_PF.H RUP6 when concurrent programs try to write Completed successfully, a variable was not initialized in the code. Because of this even though the concurrent program completed successfully, it used to coredump before it was able to write to its log file: Completed successfully. Applying Patch 6815663 resolved this issue.