Re: Desperate plea for Help: failed ODBC requests

From: ptran <pnt_at_wt.net>
Date: Thu, 10 Dec 1998 08:05:55 -0600
Message-ID: <74okrg$aib$1@news4.wt.net>

With ODBC problems, I'd probably start troubleshooting from the client = first.

1. From the PC running the front-end app, start ODBC Admin.
2. Turn on TRACE and specify where you want your LOG at.
2. Run the App until it crashes.
3. Examine the LOG. Since the LOG will stop at the point of failure, =

Start from the end of the file and work your way back up. Look for the = offending SQL statement.
You may have a kick-ass SQL which ODBC timed-out on. Or a PL/SQL proc = that Oracle couldn't compile...

Listener.log & Sqlnet.log only help when you have connection problems.

    J Sukumaran wrote in message <366F02E8.F236BCF0_at_us.oracle.com>...     Similar to what Sybrand mentioned, you can check your connectivity = on your server too.

    Here is what to do.
$echo $ORACLE_HOME

    This will give you your oracle home directory. From there type
$cd network/log

    Once inside there have a look at the following files - listener.log = and sqlnet.log

    There will be some error messages there. If you want me to have a = look at them,

    email it to me.
    My e-mail id is jsukumar_at_us.oracle.com     If you could not find anything in that file, maybe you may have to = set the trace on the

    server side.
    You can do that by issuing the following command.
$lsnrctl

    LSNRCTL>trace listener
    This will create a file in the following directory -      $ORACLE_HOME/network/trace
    You can look at that too.

    Thanks

    Jyotheesh Sukumaran

    dcho_at_mail.arco.com wrote:

        I am in charge of implementing an off-the-shelf ODBC front-end = program with

        Oracle as the backend database. The program intermittenly fails = to execute

        certain tasks and now I might be sandwiched between two vendors = neither of

        whom is willing to take serious responsibility (how typical). 
        The vendor of the ODBC front-end program claims that the problem =
is 
        environmental and that the server either "drops or ignores the =
requests due to 
        packet failures."  And although I haven't apporoached Oracle =
about it, I doubt 
        that they will lift a finger to help me troubleshoot the =
server's ODBC 
        connectivity issues with an obsecure front-end program from an =
obsecure vendor 
        (please email me if you want to know more about the program). 

        As a starter, I have one question:  Does the server maintain a =
log of ODBC 
        requests from clients?  If so, where can I find it (Note that I =
am not an 
        Oracle expert, so please be gentle in your response) 

        I now find myself at the end of the rope.  This vendor does not =
provide 
        technical support for Oracle, so they tend to place all blame on =
the backend 
        database whenever elusive problems arise.  Your help will be =
greatly 
        appreciate it. 

        From Very Frustrated 

        -----------== Posted via Deja News, The Discussion Network =
==---------- 
        http://www.dejanews.com/       Search, Read, Discuss, or Start =

Your Own        Received on Thu Dec 10 1998 - 08:05:55 CST