<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Oracle Wire Protocol in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721604#M788147</link>
    <description>Shalom Shiv,&lt;BR /&gt;&lt;BR /&gt;The articles above define this as ODBC access. This is the least desireable of the possible Oracle access methods. ODBC is more likely to have support and performance issues than oracle client for example.&lt;BR /&gt;&lt;BR /&gt;Yes, it runs TCP/IP.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Wed, 01 Feb 2006 05:11:55 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2006-02-01T05:11:55Z</dc:date>
    <item>
      <title>Oracle Wire Protocol</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721600#M788143</link>
      <description>what is the use of wire protocol ? Does it run over tcp/ip ?</description>
      <pubDate>Tue, 31 Jan 2006 19:04:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721600#M788143</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2006-01-31T19:04:54Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle Wire Protocol</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721601#M788144</link>
      <description>I seen web based programmers used to tell SAs this thing. &lt;BR /&gt;&lt;BR /&gt;Yes u r right, it binds to the TCP/IP suite &lt;BR /&gt;via http.&lt;BR /&gt;&lt;BR /&gt;For more details&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://java.sun.com/j2se/1.4.2/docs/guide/jpda/jdwp-spec.html" target="_blank"&gt;http://java.sun.com/j2se/1.4.2/docs/guide/jpda/jdwp-spec.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Chan</description>
      <pubDate>Tue, 31 Jan 2006 19:10:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721601#M788144</guid>
      <dc:creator>Chan 007</dc:creator>
      <dc:date>2006-01-31T19:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle Wire Protocol</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721602#M788145</link>
      <description>Hi Shivkumar,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;A DBMS is written using an application programming interface (API), which is specific to that database. For example, an Oracle 9i database has its own version of the API specification (called Net9), which must run on each client application.&lt;BR /&gt;&lt;BR /&gt;Developers write applications compliant to the ODBC specification and use ODBC drivers to access the database. The ODBC driver communicates with the vendor's native API. Then, the native API passes instructions to another vendor-specific low-level API. Finally the wire protocol API communicates with the database&lt;BR /&gt;&lt;BR /&gt;The wire protocol architecture eliminates the need for the database's native API (for example, Net9), so the driver communicates directly to the database through the database's own wire level protocol. This effectively removes an entire communication layer&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Indira A</description>
      <pubDate>Tue, 31 Jan 2006 20:02:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721602#M788145</guid>
      <dc:creator>Indira Aramandla</dc:creator>
      <dc:date>2006-01-31T20:02:30Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle Wire Protocol</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721603#M788146</link>
      <description>Hi Shiv, &lt;BR /&gt;&lt;BR /&gt;Some links that should shed light for you, &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://media.datadirect.com/download/docs/odbc/odbcref/oracle.html" target="_blank"&gt;http://media.datadirect.com/download/docs/odbc/odbcref/oracle.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://forums.datadirect.com/ddforums/thread.jspa?messageID=3663" target="_blank"&gt;http://forums.datadirect.com/ddforums/thread.jspa?messageID=3663&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Tue, 31 Jan 2006 23:13:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721603#M788146</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-01-31T23:13:23Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle Wire Protocol</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721604#M788147</link>
      <description>Shalom Shiv,&lt;BR /&gt;&lt;BR /&gt;The articles above define this as ODBC access. This is the least desireable of the possible Oracle access methods. ODBC is more likely to have support and performance issues than oracle client for example.&lt;BR /&gt;&lt;BR /&gt;Yes, it runs TCP/IP.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 01 Feb 2006 05:11:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721604#M788147</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-02-01T05:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle Wire Protocol</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721605#M788148</link>
      <description>Hi Shiv, &lt;BR /&gt;&lt;BR /&gt;SOAP is also a wire protocol like IIOP for CORBA, ORPC for DCOM, or Java Remote Method Protocol (JRMP) for Java Remote Method Invocation (RMI). I think, Oracle uses SOAP and XML in 9i. It runs on TCP/IP Layer. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.javaworld.com/javaworld/jw-03-2001/jw-0330-soap.html" target="_blank"&gt;http://www.javaworld.com/javaworld/jw-03-2001/jw-0330-soap.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Wed, 01 Feb 2006 05:54:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721605#M788148</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-02-01T05:54:12Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle Wire Protocol</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721606#M788149</link>
      <description>What is the word "wire" stands for with respect to this technologies ? Thanks.</description>
      <pubDate>Wed, 01 Feb 2006 13:49:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721606#M788149</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2006-02-01T13:49:40Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle Wire Protocol</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721607#M788150</link>
      <description>hi shiv,&lt;BR /&gt;&lt;BR /&gt;In fact, Wire refers to the IP protocol. &lt;BR /&gt;&lt;BR /&gt;When referring to data path over WAN, IP, the protocol that is actually on the wire, does not care which path the PDU takes, nor does it care what order the PDUs arrive.  With multiple paths to it's destination, a TCP/IP "conversation" may use all the paths at once, &lt;BR /&gt;and the client will have to reassemble that "conversation."  This will add to the delay.   &lt;BR /&gt;&lt;BR /&gt;the above is an extract from metalink note: &lt;BR /&gt;Note:1005123.6 - Tuning SQL*Net for better performance &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;hope this helps!&lt;BR /&gt;&lt;BR /&gt;kind regards&lt;BR /&gt;yogeeraj&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Feb 2006 02:25:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-wire-protocol/m-p/3721607#M788150</guid>
      <dc:creator>Yogeeraj_1</dc:creator>
      <dc:date>2006-02-02T02:25:13Z</dc:date>
    </item>
  </channel>
</rss>

