RE: Slow Export
- From: "M Rafiq" <rafiq9857@xxxxxxxxxxx>
- To: rlsmith@xxxxxxx, Mark.Bobak@xxxxxxxxxxxxxxx, tanel.poder.003@xxxxxxx, oracle-l@xxxxxxxxxxxxx
- Date: Wed, 01 Feb 2006 10:26:27 -0500
Thanks for update.
Regards
Rafiq
From: "Smith, Ron" <rlsmith@xxxxxxx>
Reply-To: rlsmith@xxxxxxx
To: <Mark.Bobak@xxxxxxxxxxxxxxx>, "M Rafiq"
<rafiq9857@xxxxxxxxxxx>,<tanel.poder.003@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
Subject: RE: Slow Export
Date: Wed, 1 Feb 2006 08:43:42 -0600
It was the trace in the SQLNET.ORA. The trace file had gotten to be over
2G.
I remove the commands. Turned off the trace. The exports ran in 40 minutes
instead of 9 hours!
Thanks for your help!
Ron
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Bobak, Mark
Sent: Tuesday, January 31, 2006 3:59 PM
To: Smith, Ron; M Rafiq; tanel.poder.003@xxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Slow Export
Interesting. SQL*Net trace level 16 dumps a LOT of stuff to disk.
It's possible that the combination of the SQL*Net trace writes and the exp
writes are killing your I/O. When the export runs remotely, the SQL*Net
trace writes still happen, but the export writes are on another host.....
It's worth commenting that stuff out of youe sqlnet.ora. Also, if this is
at all a busy database, you may want to clean out
/oracle_rdbms/app/oracle/product/8.1.7/network/trace which probably has lots
of useless *.trc files in it.
I'd comment those lines from sqlnet.ora and try re-running the exp.
-Mark
--
Mark J. Bobak
Senior Oracle Architect
ProQuest Information & Learning
"There are 10 types of people in the world: Those who understand binary,
and those who don't."
-----Original Message-----
From: Smith, Ron [mailto:rlsmith@xxxxxxx]
Sent: Tuesday, January 31, 2006 4:55 PM
To: M Rafiq; Bobak, Mark; tanel.poder.003@xxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Slow Export
Found this in the SQLNET.ORA file. Added to try to diagnose another
problem. About the time the exports started running slow.
TRACE_LEVEL_CLIENT=16
TRACE_DIRECTORY_CLIENT=/oracle_rdbms/app/oracle/product/8.1.7/network/trace
TRACE_TIMESTAMP_CLIENT = ON
TNSPING works well.
Ron
-----Original Message-----
From: M Rafiq [mailto:rafiq9857@xxxxxxxxxxx]
Sent: Tuesday, January 31, 2006 3:43 PM
To: Smith, Ron; Mark.Bobak@xxxxxxxxxxxxxxx; tanel.poder.003@xxxxxxx;
oracle-l@xxxxxxxxxxxxx
Subject: RE: Slow Export
Ron,
Is there any recent change to your local tnsnames.ora file. May be any
bracket is missing or format error. How about your tnsping to that database
work from local server?
Regards
Rafiq
From: "Smith, Ron" <rlsmith@xxxxxxx>
Reply-To: rlsmith@xxxxxxx
To: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxxxxx>,<tanel.poder.003@xxxxxxx>,
"ORACLE-L" <oracle-l@xxxxxxxxxxxxx>
Subject: RE: Slow Export
Date: Tue, 31 Jan 2006 15:26:19 -0600
No, I found I can run truss. Just don't know how since we usually can't run
those type utilities.
The only waits are SQL*NET waits, to and from the client. About 350 but no
time associated with the wait.
The export is local. If done remotely the export runs much faster, back to
normal times.
Thanks!
Ron
-----Original Message-----
From: Bobak, Mark [mailto:Mark.Bobak@xxxxxxxxxxxxxxx]
Sent: Tuesday, January 31, 2006 3:15 PM
To: Smith, Ron; tanel.poder.003@xxxxxxx; ORACLE-L
Subject: RE: Slow Export
Hmm....so, they explicitly deperm access to the truss binary? On most
Sun
servers, it's in /usr/bin, and you should not need root permission to truss
an oracle owned process. If you can login as the user who started the
database (presumably oracle), that should be good enough to do the trace.
Unless they really do explicitly deperm the binary. If that's true, I'd
argue that's a battle you need to fight, in order to do you job well, you
need access to O/S level tools like truss. (I know, I know, easier said
than done....;-))
As for the V$SESSION_WAIT output, what do you mean by "looks low"? Are
you
seeing waits? What are they?
Also, regarding Tanel's last question, are you exporting locally, or
over
the network?
-Mark
--
Mark J. Bobak
Senior Oracle Architect
ProQuest Information & Learning
"There are 10 types of people in the world: Those who understand
binary,
and those who don't."
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Smith, Ron
Sent: Tuesday, January 31, 2006 3:55 PM
To: tanel.poder.003@xxxxxxx; ORACLE-L
Subject: RE: Slow Export
I had to restart the export. Ran 8.5 hours this time.
V$Session_Wait looks low right now.
I have never used the Truss command. Unix admins don't give us access.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Tanel Põder
Sent: Tuesday, January 31, 2006 2:45 PM
To: ORACLE-L
Subject: Re: Slow Export
Are you exporting over network or locally in the server?
V$SESSION_EVENT, V$SESSION_WAIT and truss -c should sufficient
to reveal
the cause..
Tanel.
----- Original Message -----
From: Smith, Ron <mailto:rlsmith@xxxxxxx>
To: tanel.poder.003@xxxxxxx ; ORACLE-L
<mailto:oracle-l@xxxxxxxxxxxxx>
Sent: Tuesday, January 31, 2006 2:36 PM
Subject: RE: Slow Export
There are several exports in different databases,
exporting various size
objects. The thing is, this started about the middle of December.
Before that, everything was fine.
Ron
Important Notice!
If you are not the intended recipient of this e-mail message, any use,
distribution or copying of the message is prohibited.
Please let me know immediately by return e-mail if you have received
this
message by mistake,
then delete the e-mail message.
Thank you.
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
