in this case it is very likely that this is an ASSM issue (e.g. finding free
space, rejecting list problem, etc.) if the object is the table.
I think it is time to stack trace the session to get a better insight into what
is going on. You can find an example on slide 20 to 24 here:
P.S.: There are also trace events (e.g. 10320, 10612) but have a look at the
stack traces first and check if this is an ASSM issue.
Independent Oracle performance consultant and researcher
Sanjay Mishra <dmarc-noreply@xxxxxxxxxxxxx> hat am 17. Mai 2019 um 23:32--
Thanks for the update. Based on the Obj Id with trace on the Insert process,
it is Table itself reported. This table is recently exported and imported and
Index was only created less than a month back. Surprisingly not able to
understand as to why it is doing cell single block physical read to the
table. I will also check your link and do more troubleshooting