Re: High Version Count with usage of Parallel Query
- From: "Leyi Zhang (Kamus)" <kamusis@xxxxxxxxx>
- To: hkchital@xxxxxxxxxxxxxx
- Date: Thu, 5 Aug 2010 16:05:06 +0800
Based on my experience.
1. NEVER use PQ in OLTP system.
2. Remember to change degree to 1 after rebuild index with parallel.
--
Kamus <kamusis@xxxxxxxxx>
Visit my blog for more : http://www.dbform.com
Join ACOUG: http://www.acoug.org
On Wed, Aug 4, 2010 at 10:08 PM, Hemant K Chitale
<hkchital@xxxxxxxxxxxxxx> wrote:
>
> An update on this :
> Setting DEGREE 1 and/or creating the right index so as to have the
> optimizer use an Index Range Scan instead of Parallel FullTableScan has
> "resolved" the high version count.
>
>
>> Date: Tue, 06 Jul 2010 23:27:33 +0800
>> To: oracle-l@xxxxxxxxxxxxx
>> From: Hemant K Chitale
>> Subject: High Version Count with usage of Parallel Query
>>
>> I have a few queries that are wrongly using PQ (by having a Parallel
>> DEGREE set on the Tables). Unfortunately, they run very frequently, from
>> multiple sessions.
>> Not always do they get the requisite number of PQ slaves.
>> I will be getting these change to No-Parallel operations.
>
> <deleted>
>
>
>
> Hemant K Chitale
>
> http://hemantoracledba.blogspot.com
>
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
