. For long we know the misleading ‘db file sequential read’ which is what we call ‘random reads’ from storage point of view and ‘db file scattered read’ that is what we call ‘sequential reads’ from storage point of view. The DISPLAY_NAME clarifies everything: single block reads vs. multiblock reads.<\/p>\n ‘db file parallel read’ is a batch of random reads, used by prefetching for example, which reads multiple blocks but non contiguous. ‘log file parallel write’ is ‘parallel’ only because you can have multiplexed files. DISPLAY_NAME is less misleading with ‘log file redo write’. You can look at the others where DISPLAY_NAME is very clear about the operation: ‘online move’ for some operations on files, ‘commit’ for the well know log file sync… <\/p>\n Of course they are also described in the Database Reference documentation.<\/p>\n","protected":false},"excerpt":{"rendered":" By Franck Pachot . The oracle wait event names were originally implemented for the oracle rdbms developers and are now use by the database users to troubleshoot performance issues. The consequence is that the name may be misleading because they have a meaning from the internal point of view. Here is some clarification about them.<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[96,209],"type_dbi":[],"class_list":["post-9668","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-oracle","tag-oracle-12c"],"acf":[],"yoast_head":"\n
\nThe oracle wait event names were originally implemented for the oracle rdbms developers and are now use by the database users to troubleshoot performance issues. The consequence is that the name may be misleading because they have a meaning from the internal point of view. Here is some clarification about them.
\n
\nIn 12c<\/em> the clarification is easy because we have a new DISPLAY_NAME column in the V$EVENT_NAME view:<\/p>\n\nSQL> select wait_class,name, display_name from v$event_name where display_name != name order by 1,2;\nWAIT_CLASS NAME DISPLAY_NAME \n-------------- ----------------------------------- ----------------------------------------------\nAdministrative concurrent I\/O completion online move datafile IO completion \nAdministrative datafile copy range completion online move datafile copy range completion \nAdministrative wait for possible quiesce finish quiesce database completion \nCommit log file sync commit: log file sync \nConfiguration log buffer space log buffer full - LGWR bottleneck \nIdle LGWR real time apply sync standby apply advance notification \nOther DFS db file lock quiesce for datafile offline \nOther Image redo gen delay redo resource management \nOther datafile move cleanup during resize online move datafile resize cleanup \nSystem I\/O control file sequential read control file read \nSystem I\/O control file single write control file write \nSystem I\/O db file parallel write db list of blocks write \nSystem I\/O log file parallel write log file redo write \nSystem I\/O log file sequential read log file multiblock read \nSystem I\/O log file single write log file header write \nUser I\/O db file parallel read db list of blocks read \nUser I\/O db file scattered read db multiblock read \nUser I\/O db file sequential read db single block read \nUser I\/O db file single write db single block write <\/code><\/pre>\n
\n‘db file parallel write’ is similar, for DBWR to write a batch of blocks. The DISPLAY_NAME clarifies everything: ‘db list of blocks’.<\/p>\n
\nThe ‘log buffer space’ has a DISPLAY_NAME that is more focused on the cause: ‘log buffer full – LGWR bottleneck’<\/p>\n