FAQ
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;
export
PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/oracle/bin:/u01/app/oracle/product/10.2.0/db_1/bin;

/u01/app/oracle/product/10.2.0/db_1/bin/imp sysadm/ full=y
recordlength=65535 commit=n buffer=999999999
log=/u01/app/oracle/scripts/logs/hr89uat_imp.log
file=/u03/oradata/exports/orlhr/orlhr1.dmp,/u03/oradata/exports/orlhr/orlhr2.dmp,/u03/oradata/exports/orlhr/orlhr3.dmp,/u03/oradata/exports/orlhr/orlhr4.dmp,/u03/oradata/exports/orlhr/orlhr5.dmp,/u03/oradata/exports/orlhr/orlhr6.dmp,/u03/oradata/exports/orlhr/orlhr7.dmp,/u03/oradata/exports/orlhr/orlhr8.dmp,/u03/oradata/exports/orlhr/orlhr9.dmp,/u03/oradata/exports/orlhr/orlhr10.dmp,/u03/oradata/exports/orlhr/orlhr11.dmp

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

Waited ----------

log file sync 2899646 0.97
2097.17
SQL*Net message to client 5818723 0.00
4.34
SQL*Net message from client 5818723 1.49
3862.41
db file sequential read 14054600 0.82
7958.39

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.

Search Discussions

  • Cary Millsap at Jun 6, 2008 at 4:06 pm
    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.

    Cary Millsap
    http://method-r.com
    http://carymillsap.blogspot.com

    On Fri, Jun 6, 2008 at 8:55 AM, steve montgomerie
    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;
    export
    PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/oracle/bin:/u01/app/oracle/product/10.2.0/db_1/bin;

    /u01/app/oracle/product/10.2.0/db_1/bin/imp sysadm/ full=y
    recordlength=65535 commit=n buffer=999999999
    log=/u01/app/oracle/scripts/logs/hr89uat_imp.log
    file=/u03/oradata/exports/orlhr/orlhr1.dmp,/u03/oradata/exports/orlhr/orlhr2.dmp,/u03/oradata/exports/orlhr/orlhr3.dmp,/u03/oradata/exports/orlhr/orlhr4.dmp,/u03/oradata/exports/orlhr/orlhr5.dmp,/u03/oradata/exports/orlhr/orlhr6.dmp,/u03/oradata/exports/orlhr/orlhr7.dmp,/u03/oradata/exports/orlhr/orlhr8.dmp,/u03/oradata/exports/orlhr/orlhr9.dmp,/u03/oradata/exports/orlhr/orlhr10.dmp,/u03/oradata/exports/orlhr/orlhr11.dmp

    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
    ---------------------------------------- Waited ----------
    ------------
    log file sync 2899646 0.97
    2097.17
    SQL*Net message to client 5818723 0.00
    4.34
    SQL*Net message from client 5818723 1.49
    3862.41
    db file sequential read 14054600 0.82
    7958.39

    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.
    --
    http://www.freelists.org/webpage/oracle-l
  • Yong Huang at Jun 9, 2008 at 2:40 am
    Steve,

    In addition to what Cary said, you can tell what protocol "SQL*Net message to
    (or from) client" waits are really using by looking at its p1 value, preferably
    in hex:

    $ sqlplus user/pass

    SQL> select p1raw from v$session where sid = 2186;

    P1RAW

    0000000062657100

    62, 65, 71 in hex are beq in ASCII. 2186 is my current session connected
    locally, sqlplus user/pass. SQL*Net does not necessarily mean TCP, at least in
    this context.

    Yong Huang

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouporacle-l @
categoriesoracle
postedJun 6, '08 at 1:55p
activeJun 9, '08 at 2:40a
posts3
users3
websiteoracle.com

People

Translate

site design / logo © 2022 Grokbase