Re: SQL*Net message from client waits on local import
Date: Fri, 6 Jun 2008 11:06:27 -0500
The *SQL*Net message from client* events instrument the write()/read() call combination that the Oracle kernel makes, regardless of what protocol adapter you use. You'll still see the events, but the latencies should be smaller if you use bequeath or ipc than if you use a thicker-stack communication protocol like tcp.
On Fri, Jun 6, 2008 at 8:55 AM, steve montgomerie <stmontgo_at_gmail.com> wrote:
> Some background...
> Upgrade db from Windows 2003 Oracle 9208 to OEL Oracle 10.2.0.4 the old
> fashioned way with import/export
> Export dump files to new Linux server and go with the import!
> export LD_LIBRARY_PATH=/u01/app/oracle/product/10.2.0/db_1/lib;
> export ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1;
> export ORACLE_SID=HR89PAR1;
> export ORAHOME=/u01/app/oracle/product/10.2.0/db_1;
> /u01/app/oracle/product/10.2.0/db_1/bin/imp sysadm/<password> full=y
> recordlength=65535 commit=n buffer=999999999
> What I see from tkprof is the usual suspects along with SQL*Net message
> from client waits.
> Elapsed times include waiting on following events:
> Event waited on Times Max. Wait Total
> ---------------------------------------- Waited ----------
> log file sync 2899646 0.97
> SQL*Net message to client 5818723 0.00
> SQL*Net message from client 5818723 1.49
> db file sequential read 14054600 0.82
> So why am I seeing a SQL*NET wait? There are 8000 + tables and I see lots
> of little waits here and there, nothing really large.
> I thought that my import would be connecting in a bequeath type fashion and
> would therefore not expect to see any SQL*NET waits.