Thank you for the advice. We have reviewed these settings. Here's the kicker, however - another installation, same OS level and patches, same memory, identical kernel params exhibits no errors. So, could this error be a symptom of shared memory? I found an article on HP's site regarding shared memory fragmentation and the inability of a 32-bit app to secure the segment it needs. Could this be my culprit? If not, I'll lookt into increasing max proc /threads and shmmax. Thanks again!