Troubleshooting Worksheet -- Multi-Tier Driver, System Stability Use this form to gather information which will help us better assist you. If possible, follow up with a client-side ODBC trace and the Request Broker Log. System Information What product are you using? What are the names of the files that you downloaded? What is the product version and release number? What is the name and version of the o/s containing your Multi-Tier client components? Provide the output of uname -a for unix and linux machines. What is the name and version of the o/s containing your Multi-Tier server components? Provide the output of uname -a for unix and linux machines. Problem Description Provide the text of any error message you experience. Describe any problem that does not produce error text. Describe the steps that you take to reproduce the problem. Provide Data Source Name Connection Parameters. Client Environment What are your client communications settings? Server Environment Have you set PortHigh in your server's oplrqb.ini file? Provide your server's oplrqb.ini file for verification. Have the latest, relevant patches been applied to your database and server operating system? List your kernel tuning parameters. Unix users provide the output of ulimit -a for verification. What is your machine's physical memory? What is your machine's processor count? Did you install your server components on the database native server? If not, did you install your server components on a machine containing the database native client? What is your database native client version? Problem Isolation Is this a consistent problem or a problem that has occured after a period of stability? Is the problem associated with heavy load? If so, please describe. Does the problem produce core files, stack traces, Dr. Watsons, or Progress protraces? If so, please submit the relevant file or Watson error. Is the problem associated with a recent database or o/s patch or upgrade? Is the problem associated with the implementation of anti-virus software? Does the problem correspond with errors in the database native error log? Please provide the log for evidence. Does the database native transaction monitor show anomalous activity? Is the problem associated with an excess number of OpenLink database agent processes? Does ps -ef show more OpenLink agent processes than oplshut -s ?