This is a known bug with MTS. It is not anything to do with DDB::Oracle. If you take all of the SQL statements in your program(s) and execute them in the same manner as an on-line app would execute them, you would most likely encounter the same problem.
As for not using MTS, you could most likely persuade your DBA to give you a TNS address which makes a dedicated connection. ----------------- Ron Reidy Lead DBA Array BioPharma, Inc. -----Original Message----- From: Tristan Greaves [mailto:[EMAIL PROTECTED] Sent: Thursday, September 23, 2004 4:48 AM To: [EMAIL PROTECTED] Cc: Tim Bunce Subject: RE: DBD::Oracle and ORA-600 [16365] errors Hi again, I have a small update on the above issue which we were experiencing upon occasion. Firstly, our versions of DBD::Oracle are quite old and I am recommending to our operations team that they are upgraded as soon as feasible. (Oldest on one server is v1.03 !) Secondly, Oracle say they have had other reports of the ORA-600 [16365] error which were rectified by disabling MTS. Our DBA informs me that this isn't an option on our current configuration (I'll have to find out the specific reasons). We aren't doing anything clever with DBD::Oracle -- Oracle say we are tripping the error by our applications sending new requests before reading existing data (as per Metalink), but we are using DBI and DBD::Oracle "straight". This error occurs about once per week, and there is no real pattern. It requires an Oracle restart when it happens though, which is a pain! What could the link be between MTS, DBD::Oracle and this error? Thanks, Tris. This electronic message transmission is a PRIVATE communication which contains information which may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. Please notify the sender of the delivery error by replying to this message, or notify us by telephone (877-633-2436, ext. 0), and then delete it from your system.
