Re: Huge plain inserts response time bad with db file sequential read wait event.

Hello Rakesh,

> a) Why INSERT is spending more time on db file sequential reads for PK index?

We can not make any reliable statement based on the given data (e.g. array inserts, DML restart, I/O latency histograms, etc.?) but you might be able to run SQLd360 (https://github.com/sqldb360/sqldb360/archive/v18.3.zip) for the SQL-ID g4cf65js6kjf0 and send us the output.

> b) Why CPU costing is showing as off in the execution plan for OGG queries only?

The most common reason might be that you have an old PLAN_TABLE in combination with DBMS_XPLAN usage - this results in the misleading "cpu costing is off" message.

Best Regards
Stefan Koehler

Independent Oracle performance consultant and researcher Website: http://www.soocs.de
Twitter: _at_OracleSK

> Rakesh Ra <rakeshra.tr_at_gmail.com> hat am 20. Dezember 2018 um 18:48 geschrieben:
>
> Can someone guide as to,
>  
> a) Why INSERT is spending more time on db file sequential reads for PK index?
> b) Why CPU costing is showing as off in the execution plan for OGG queries only?
>
>  
> Regards,
> RRA

--
http://www.freelists.org/webpage/oracle-l