in reply to Re^2: fetchall_arrayref({}) call freezing
in thread fetchall_arrayref({}) call freezing

Okay.... No matter what I do, I get nothing in the ODBC trace file, even though I know for a fact that I am shoving data across the pipe. Even a DBA that I know is confused about that fact.
  • Comment on Re^3: fetchall_arrayref({}) call freezing

Replies are listed 'Best First'.
Re^4: fetchall_arrayref({}) call freezing
by mje (Curate) on Mar 13, 2014 at 12:01 UTC

    The most common reason for this is a permission problem with the file specified as the trace file. However, I've sometimes also seen this if something else has an ODBC connection open when you enable tracing.

    Depending on how recent your windows is there is also now an enable system wide tracing option in the odbc administrator.

      I have tried to use the enable all traces, and it still doesn't do anything. Also, the directory is FC to the SQL account.

        As I said. Sometimes you have to stop all processes using ODBC before the tracing takes effect. Other than that I've no idea why you cannot get a trace file. It does sort of stink a bit that something else may be wrong on this machine.