Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.tools -> Re: HELP - frames/packets being resent (duplicated) for Oracle sql*net connection.

Re: HELP - frames/packets being resent (duplicated) for Oracle sql*net connection.

From: Fuzzy <granta_at_nospam.student.canberra.edu.au>
Date: 2000/07/04
Message-ID: <3962777f.3616209@newshost.interact.net.au>#1/1

On Tue, 4 Jul 2000 15:41:29 +0200, "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote:

>As you have severely edited you output, how can we see it is identical?

Sorry, I thought the Sniffer output line that said: "Retransmission TNS: duplicate of frame 4831" was the give-away there. :-)

>you would have used sqlnet tracing, that would have provided you with lots
>of more insight.

An excellent point ... thanks Sybrand. As you've probably guessed, this is coming from an outsourced networking guy, who's answer to the question "What does the net8 trace show?" was "net what?".

>Three general remarks
>- Before the data of any select statement is sent, a description of all
>columns in that statement, including datatypes etc, will be sent to the
>client. (I learned this from studying sqlnet trace output).

Yep, know this. We'll use trace level 16 to see what's actually in the packets.

>- If a cursor is closed by the client and re-opened by the client all data
>is resent, whether it has changed or not. I noticed this to be a problem in
>an application with numerous listboxes, comboboxes and the like on screen,
>all the underlying cursors were closed as soon as that control lost focus

We know the app doesn't do this - we've been burnt by stupid cursor handling before.

>- ODBC is about the most inefficient mechanism to use in communication with
>an Oracle database.

But until we've done our OLEDB work, it's the only STANDARD way to talk to Oracle (don't get me started on the proprietary coding stuff :-) PL/SQL and OCI are nice if you never want to port your app to other db's).

>If you really want to track the cause (and personally, as it's only 20
>percent and some duplication is inevitable, so I wouldn't bother), you'll
>need to add or change
>trace_level_server = 16 in your sqlnet.ora on the server.
>That will automatically trace *all* sqlnet connections.

Will do. 20% is significant in this instance, as the client is trying to run 20+ people with this product, and file sharing, mail, web, etc over one 32K frame relay that's 4000km (~2500 miles) long. I offered to give them $100 to by two decent modems ... and only got poisonous looks in return :-)

Thanks again.

Ciao
Fuzzy
#;-) Received on Tue Jul 04 2000 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US