Oracle ODBC tracing
Hi all,
I have an application that connects to a backend Oracle 9i database via Oracle ODBC driver. Everything was fine until we upgraded to 9.6.0.5 ODBC driver. Now the application server service stops. Looking at the application dump log it looks like it is possibly a Oracle ODBC driver memory leak that is caused by what the application is calling possible via a SQL statement. I would like to enable SQL trace on the ODBC driver, but was wondering if it causes a lot of performance issues? I could then see what SQL statement is being called at the time of a crash. It happens here and there and so far cannot reproduce. Anyone have experience with this?
Thanks,
Raek
|