Sorry small correction on the trace. If object is 540334 then it is "cell
multiblock Physical read" but obj#=0 is "cell single block physical read" There
is One "cell multiblock Physical read" after several rows on "cell multiblock
Physical read"
name='cell single block physical read' ela=1511 celhas=12345555
diskhash=12345555 bytes=8192 obj#0 time=11111111name='cell multiblock physical
read' ela=1511 celhas=12345555 diskhash=12345555 bytes=8192 obj#540334
time=11111111
These are the only one taking 95% of time for the query.
Sanjay
On Wednesday, December 13, 2017 7:44 PM, Sanjay Mishra
<smishra_97@xxxxxxxxx> wrote:
I checked and found that in 10046 trace, there are around 1mil rows with
obj#=0 and around 100K with obj#=540334 which is the object I am updating.
Sanjay
On Wednesday, December 13, 2017 7:33 PM, Sanjay Mishra
<dmarc-noreply@xxxxxxxxxxxxx> wrote:
Hi
I am running an update on Advance row compress table by selecting data from
another table on Unique Seq No. Runing Select from other table is very fast and
even running Select instead of update columns is very fast BUT WHEN update
comes, it is taking almost an hour to just update 5 mil Records. Does Compress
for OLTP be factor for so many single block phsuicall Read as I am monitoring
the trace and what it is doing is name='cell single block physical read'
ela=1511 celhas=12345555 diskhash=12345555 bytes=8192 obj#0
time=11111111name='cell single block physical read' ela=1511 celhas=12345555
diskhash=12345555 bytes=8192 obj#540334 time=11111111
So can see doing this against obj#0 and obj#540334
Any help is appreciated.
TIASanjay
