. . "No product should produce a core dump. Core dumps warrant the creation of a bug report. (Update existing bug reports, as appropriate.) Product Support Staff should attach the core file to the report. Moreover, staff must gather the following information from users:\n\n 1. Does the database and operating system contain all current patches?\n 2. Are the patches associated with stability problems?\n 3. Do Unix kernel tuning parameters match parameters specified by database and o/s documentation?\n 4. Does the machine have adequate memory and processor resources?\n 5. Was the database agent re-linked against the database?\n 6. Is PortHigh set in the [Protocol TCP] section of the Multi-Tier Session Rules Book? This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation.\n 7. What happens when users comparison test the following ReUse values:\n \u2014 ifsame process, upto 5\n \u2014 ifsame application, upto 5\n \u2014 ifsame database, upto 5\n 8. Finally, Multi-Tier users should perform the following test:\n \u2014 login to the machine that contains the OpenLink server components.\n \u2014 Run oplshut -s on the command-line.\n \u2014 Compare the output to the Windows Task Manager or Unix ps -ef.\n \u2014 Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps." . .