First step would be to see which object is responsible for all the IO, in
my experience it’s usually down to one index.
Have a look at
for how I’ve tackled this before.
It might be you’ve got a “bad index” or it might be that you’ve got an okay
index that turned “bad”.
We had a case where an index exploded and was purely ITL for the first few
thousands leaf blocks, we reset the sequence (told to by support) which
meant that all our inserts had to scan those few thousand leaf blocks to
insert one row.
First step is identifying the object
On Fri, 17 May 2019 at 16:47, Sanjay Mishra <dmarc-noreply@xxxxxxxxxxxxx>
We have a table with around a billion rows with one Primary Key. Number of
columns in the table are fewer than 10 and all are numbers data type.
Application is doing few million inserts but running very slow. It is
Exadata with two node and 10CPU and good SGA (bufer Cache 10G). Waits are
coming heavily only for "cell single block physical read" for Insert
process. While doing SQL Monitor shows it is doing high IO like more than
100G for simple Insert. Oracle version is 12.2.
Any suggestions as what can be the reason for this wait event in this