RE: Performance problem: Loading data via insert
- From: Abhishek Gurung <abhishek.gurung@xxxxxxxxxxx>
- To: Oracle Freelist <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 14 Mar 2014 12:48:50 +0530
Hi Jeff,
Thanks for replying.Yes we had already gone through this process of using hint
and after testing and checking its pros and cons we decided not to use them.
ReagardsAbhishek
Date: Thu, 13 Mar 2014 14:34:41 -0700
From: jeff.d.smith@xxxxxxxxxx
To: sameer.choudhari@xxxxxxxxx; carlos.sierra.usa@xxxxxxxxx
CC: abhishek.gurung@xxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Performance problem: Loading data via insert
Please read the docs on the NOLOGGING hint before you ever actually use it.
Actually, for any hint, but esp that one. From: Sameer Choudhari
[mailto:sameer.choudhari@xxxxxxxxx]
Sent: Thursday, March 13, 2014 4:43 PM
To: carlos.sierra.usa@xxxxxxxxx
Cc: abhishek.gurung@xxxxxxxxxxx; Oracle Freelist
Subject: Re: Performance problem: Loading data via insert Try tuning your
insert statements with hints like PARALLEL NOLOGGING .
On Friday, 14 March 2014, Carlos Sierra <carlos.sierra.usa@xxxxxxxxx>
wrote:Abhishek, As always, start with the evidence:What facts have you
collected? What is AWR telling you? What are the SQL Traces telling? Which
other diagnostics tools have you used for your case?
Cheers,
Carlos Sierra
blog: carlos-sierra.net
twitter: @csierra_usa
Life's Good! On Mar 13, 2014, at 6:52 AM, Abhishek Gurung
<abhishek.gurung@xxxxxxxxxxx> wrote:
Hi
We are facing a performance problem but unable to identify where is the problem.
We have a production database server where about 8 database instances of oracle
is running.
Daily we insert in each of these database instances about 1-5 GB of data in
different tables.
All database instances are working fine where we are able to load around 2-3 GB
of data within 1hour except
1 where it is taking about 8 hrs to load only 4 GB of data.
When I try to load the same 4GB of data in another database where only one
instance is running and with
very less configuration as compared to the Production server we were able to
load it in 1hr 45 minutes.
Can anyone suggest how can we proceed to identify the problem?
Regards
Abhishek
--
Sent from Google Nexus
Other related posts:
