Gino,

    I take it in the errlog.log file you just see a DMA469 - process died
message - nothing else...!!

   We have an open issue with CA on this - we're calling it the "silent
death"...!!!

    Here are some things I would try: -

    1) Check for core files in the directory you start ingres from...

         if you find any, use the debugger to find out if related and raise
support call with CA

    2) If no core files - reconfigure system to use ingres threads (rather
than OS threads) and restart the system

          ingsetenv II_THREAD_TYPE=INTERNAL

We found one of our silent deaths was being caused by a generated SQL
statment having a huge SQL IN clause... It was causing a stack overflow in
ingres which managed to escape all error trapping. Only with IngresThreads
did the errortrap get invoked and give us some idea of the culprit (plus up
stack size / fix SQL generator). Once you have this info, you can switch
back to OS threads. Doesn't mean its the answer but at least you can get a
more stable system.

 Hope this gives you a start...

 Gary