{"id":13012,"date":"2019-11-15T16:08:17","date_gmt":"2019-11-15T15:08:17","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/"},"modified":"2019-11-15T16:08:17","modified_gmt":"2019-11-15T15:08:17","slug":"elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/","title":{"rendered":"Elapsed time of Oracle Parallel Executions are not shown correctly in AWR"},"content":{"rendered":"

As the elapsed time (time it takes for a task from start to end, often called wall-clock time) per execution of parallel queries are not shown correctly in AWR-reports, I thought I setup a testcase to find a way to get an elapsed time closer to reality. <\/p>\n

REMARK: To use AWR (Automatic Workload Repository) and ASH (Active Session History) as described in this Blog you need to have the Oracle Diagnostics Pack licensed.<\/p>\n

I created a table t5 with 213K blocks:<\/p>\n

\nSQL> select blocks from tabs where table_name='T5';\n \n    BLOCKS\n----------\n    213064\n<\/pre>\n
In addition I enabled Linux-IO-throttling with 300 IOs\/sec through a cgroup on my device sdb to ensure the parallel-statements take a couple of seconds to run:<\/p>\n
\n[root@19c ~]# CONFIG_BLK_CGROUP=y\n[root@19c ~]# CONFIG_BLK_DEV_THROTTLING=y\n[root@19c ~]# echo \"8:16 300\" > \/sys\/fs\/cgroup\/blkio\/blkio.throttle.read_iops_device\n<\/pre>\n
After that I ran my test:<\/p>\n
\nSQL> select sysdate from dual;\n \nSYSDATE\n-------------------\n14.11.2019 14:03:51\n \nSQL> exec dbms_workload_repository.create_snapshot;\n \nPL\/SQL procedure successfully completed.\n \nSQL> set timing on\nSQL> select \/*+ parallel(t5 2) full(t5) *\/ count(*) from t5;\n \n  COUNT(*)\n----------\n  50403840\n \nElapsed: 00:00:05.63\nSQL> select \/*+ parallel(t5 2) full(t5) *\/ count(*) from t5;\n \n  COUNT(*)\n----------\n  50403840\n \nElapsed: 00:00:05.62\nSQL> select \/*+ parallel(t5 2) full(t5) *\/ count(*) from t5;\n \n  COUNT(*)\n----------\n  50403840\n \nElapsed: 00:00:05.84\nSQL> select \/*+ parallel(t5 2) full(t5) *\/ count(*) from t5;\n \n  COUNT(*)\n----------\n  50403840\n \nElapsed: 00:00:05.73\nSQL> select \/*+ parallel(t5 2) full(t5) *\/ count(*) from t5;\n \n  COUNT(*)\n----------\n  50403840\n \nElapsed: 00:00:05.63\nSQL> select \/*+ parallel(t5 2) full(t5) *\/ count(*) from t5;\n \n  COUNT(*)\n----------\n  50403840\n \nElapsed: 00:00:05.74\nSQL> exec dbms_workload_repository.create_snapshot;\n \nPL\/SQL procedure successfully completed.\n<\/pre>\n
Please consider the elapsed time of about 5.7 seconds per execution.<\/p>\n
The AWR-report shows the following in the “SQL ordered by Elapsed time”-section:<\/p>\n
\n        Elapsed                  Elapsed Time\n        Time (s)    Executions  per Exec (s)  %Total   %CPU    %IO    SQL Id\n---------------- -------------- ------------- ------ ------ ------ -------------\n            67.3              6         11.22   94.5   37.4   61.3 04r3647p2g7qu\nModule: SQL*Plus\nselect \/*+ parallel(t5 2) full(t5) *\/ count(*) from t5\n<\/pre>\n
I.e. 11.22 seconds in average per execution. However, as we can see above, the average execution time is around 5.7 seconds. The reason for the wrong elapsed time per execution is that the elapsed time for the parallel slaves is summed up to the elapsed time even though the processes worked in parallel. Thanks to the column SQL_EXEC_ID (very useful) we can get the sum of the elapsed times per execution from ASH:<\/p>\n
\nSQL> break on report\nSQL> compute avg of secs_db_time on report\nSQL> select sql_exec_id, qc_session_id, qc_session_serial#, count(*) secs_db_time from v$active_session_history\n  2  where sql_id='04r3647p2g7qu' and sample_time>to_date('14.11.2019 14:03:51','dd.mm.yyyy hh24:mi:ss')\n  3  group by sql_exec_id, qc_session_id, qc_session_serial#\n  4  order by 1;\n \nSQL_EXEC_ID QC_SESSION_ID QC_SESSION_SERIAL# SECS_DB_TIME\n----------- ------------- ------------------ ------------\n   16777216\t      237                  16626           12\n   16777217\t      237                  16626           12\n   16777218\t      237                  16626           10\n   16777219\t      237                  16626           12\n   16777220\t      237                  16626           10\n   16777221\t      237                  16626           10\n                                             ------------\navg                                                    11\n \n6 rows selected.\n<\/pre>\n
I.e. the 11 secs correspond to the 11.22 secs in the AWR-report.<\/p>\n
How do we get the real elapsed time for the parallel queries? If the queries take a couple of seconds we can get the approximate time from ASH as well by subtracting the sample_time at the beginning from the sample_time at the end of each execution (SQL_EXEC_ID):<\/p>\n
\nSQL> select sql_exec_id, extract (second from (max(sample_time)-min(sample_time))) secs_elapsed \n  2  from v$active_session_history\n  3  where sql_id='04r3647p2g7qu'\n  4  and sample_time>to_date('14.11.2019 14:03:51','dd.mm.yyyy hh24:mi:ss')\n  5  group by sql_exec_id\n  6  order by 1;\n \nSQL_EXEC_ID SECS_ELAPSED\n----------- ------------\n   16777216         5.12\n   16777217        5.104\n   16777218         4.16\n   16777219        5.118\n   16777220        4.104\n   16777221        4.171\n \n6 rows selected.\n<\/pre>\n
I.e. those numbers reflect the real execution time much better.<\/p>\n
REMARK: If the queries take minutes (or hours) to run then you have to extract the minutes (and hours) as well of course. See also the example I have at the end of the Blog. <\/p>\n
The info in V$SQL is also not very helpful:<\/p>\n
\nSQL> set lines 200 pages 999\nSQL> select child_number, plan_hash_value, elapsed_time\/1000000 elapsed_secs, \n  2  executions, px_servers_executions, last_active_time \n  3  from v$sql where sql_id='04r3647p2g7qu';\n \nCHILD_NUMBER PLAN_HASH_VALUE ELAPSED_SECS EXECUTIONS PX_SERVERS_EXECUTIONS LAST_ACTIVE_TIME\n------------ --------------- ------------ ---------- --------------------- -------------------\n           0      2747857355    67.346941          6                    12 14.11.2019 14:05:17\n<\/pre>\n
I.e. for the QC we have the column executions > 0 and for the parallel slaves we have px_servers_executions > 0. You may actually get different child cursors for the Query Coordinator and the slaves. <\/p>\n
So in theory we should be able to do something like:<\/p>\n
\nSQL> select child_number, (sum(elapsed_time)\/sum(executions))\/1000000 elapsed_time_per_exec_secs \n  2  from v$sql where sql_id='04r3647p2g7qu' group by child_number;\n \nCHILD_NUMBER ELAPSED_TIME_PER_EXEC_SECS\n------------ --------------------------\n           0                 11.2244902\n<\/pre>\n
Here we do see the number from the AWR again.<\/p>\n
So in future be careful when checking the elapsed time per execution of statements, which ran with parallel slaves. The number will be too high in AWR or V$SQL. Further analysis to get the real elapsed time per execution would be necessary.<\/p>\n
REMARK: As the numbers in AWR do come from e.g. dba_hist_sqlstat, the following query provides “wrong” output for parallel executions as well:<\/p>\n
\nSQL> column begin_interval_time format a32\nSQL> column end_interval_time format a32\nSQL> select begin_interval_time, end_interval_time, ELAPSED_TIME_DELTA\/1000000 elapsed_time_secs, \n  2  (ELAPSED_TIME_DELTA\/EXECUTIONS_DELTA)\/1000000 elapsed_per_exec_secs\n  3  from dba_hist_snapshot snap, dba_hist_sqlstat sql \n  4  where snap.snap_id=sql.snap_id and sql_id='04r3647p2g7qu' \n  5  and snap.BEGIN_INTERVAL_TIME > to_date('14.11.2019 14:03:51','dd.mm.yyyy hh24:mi:ss');\n \nBEGIN_INTERVAL_TIME              END_INTERVAL_TIME                ELAPSED_TIME_SECS ELAPSED_PER_EXEC_SECS\n-------------------------------- -------------------------------- ----------------- ---------------------\n14-NOV-19 02.04.00.176 PM        14-NOV-19 02.05.25.327 PM                67.346941            11.2244902\n<\/pre>\n
To take another example I did run a query from Jonathan Lewis from
\nhttps:\/\/jonathanlewis.wordpress.com\/category\/oracle\/parallel-execution<\/a>:<\/p>\n
\nSQL> @jonathan\n \n19348 rows selected.\n \nElapsed: 00:06:42.11\n<\/pre>\n
I.e. 402.11 seconds<\/p>\n
AWR shows 500.79 seconds:<\/p>\n
\n        Elapsed                  Elapsed Time\n        Time (s)    Executions  per Exec (s)  %Total   %CPU    %IO    SQL Id\n---------------- -------------- ------------- ------ ------ ------ -------------\n           500.8              1        500.79   97.9   59.6   38.6 44v4ws3nzbnsd\nModule: SQL*Plus\nselect \/*+ parallel(t1 2) parallel(t2 2)\n leading(t1 t2) use_hash(t2) swa\np_join_inputs(t2) pq_distribute(t2 hash hash) ca\nrdinality(t1,50000) *\/ t1.owner, t1.name, t1.typ\n<\/pre>\n
Let’s check ASH with the query I used above (this time including minutes):<\/p>\n
\nselect sql_exec_id, extract (minute from (max(sample_time)-min(sample_time))) minutes_elapsed,\nextract (second from (max(sample_time)-min(sample_time))) secs_elapsed \nfrom v$active_session_history\nwhere sql_id='44v4ws3nzbnsd'\ngroup by sql_exec_id\norder by 1;\n \nSQL_EXEC_ID MINUTES_ELAPSED SECS_ELAPSED\n----------- --------------- ------------\n   16777216\t              6       40.717\n<\/pre>\n
I.e. 06:40.72 which is close to the real elapsed time of 06:42.11<\/p>\n","protected":false},"excerpt":{"rendered":"
As the elapsed time (time it takes for a task from start to end, often called wall-clock time) per execution of parallel queries are not shown correctly in AWR-reports, I thought I setup a testcase to find a way to get an elapsed time closer to reality. REMARK: To use AWR (Automatic Workload Repository) and […]<\/p>\n","protected":false},"author":35,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,59],"tags":[96,1743,1742],"type_dbi":[],"class_list":["post-13012","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-oracle","tag-oracle","tag-parallel-execution","tag-parallel-query"],"acf":[],"yoast_head":"\nElapsed time of Oracle Parallel Executions are not shown correctly in AWR - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Elapsed time of Oracle Parallel Executions are not shown correctly in AWR\" \/>\n<meta property=\"og:description\" content=\"As the elapsed time (time it takes for a task from start to end, often called wall-clock time) per execution of parallel queries are not shown correctly in AWR-reports, I thought I setup a testcase to find a way to get an elapsed time closer to reality. REMARK: To use AWR (Automatic Workload Repository) and […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-11-15T15:08:17+00:00\" \/>\n<meta name=\"author\" content=\"Clemens Bleile\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@ifgtxD2SrQ8r!YuXj\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Clemens Bleile\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/\"},\"author\":{\"name\":\"Clemens Bleile\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0ac04011f60f2e93c115358d0789c2da\"},\"headline\":\"Elapsed time of Oracle Parallel Executions are not shown correctly in AWR\",\"datePublished\":\"2019-11-15T15:08:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/\"},\"wordCount\":516,\"commentCount\":0,\"keywords\":[\"Oracle\",\"Parallel Execution\",\"parallel query\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/\",\"name\":\"Elapsed time of Oracle Parallel Executions are not shown correctly in AWR - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-11-15T15:08:17+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0ac04011f60f2e93c115358d0789c2da\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Elapsed time of Oracle Parallel Executions are not shown correctly in AWR\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0ac04011f60f2e93c115358d0789c2da\",\"name\":\"Clemens Bleile\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g\",\"caption\":\"Clemens Bleile\"},\"description\":\"Clemens Bleile has more than 30 years of IT experience, thirteen in Oracle Support and fifteen in Oracle Consulting. He is specialized in Oracle Database Performance Tuning (SQL Tuning, DB Tuning) and developing an Oracle DB IT architecture (highly available, low-maintenance, cost efficient storage of data). He is an expert in problem analysis and resolution. Prior to joining dbi services, Clemens Bleile was Manager of the EMEA Database Performance team at the Oracle Global Customer Support Services. Clemens Bleile is Oracle Certified Professional 11g, 12c and Oracle Certified Expert for Performance Management and Tuning and holds a Master Degree, Business Information Systems from the Fachhochschule Furtwangen, Germany.\",\"sameAs\":[\"https:\/\/www.dbi-services.com\",\"https:\/\/x.com\/ifgtxD2SrQ8r!YuXj\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/clemens-bleile\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Elapsed time of Oracle Parallel Executions are not shown correctly in AWR - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/","og_locale":"en_US","og_type":"article","og_title":"Elapsed time of Oracle Parallel Executions are not shown correctly in AWR","og_description":"As the elapsed time (time it takes for a task from start to end, often called wall-clock time) per execution of parallel queries are not shown correctly in AWR-reports, I thought I setup a testcase to find a way to get an elapsed time closer to reality. REMARK: To use AWR (Automatic Workload Repository) and […]","og_url":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/","og_site_name":"dbi Blog","article_published_time":"2019-11-15T15:08:17+00:00","author":"Clemens Bleile","twitter_card":"summary_large_image","twitter_creator":"@ifgtxD2SrQ8r!YuXj","twitter_misc":{"Written by":"Clemens Bleile","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/"},"author":{"name":"Clemens Bleile","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0ac04011f60f2e93c115358d0789c2da"},"headline":"Elapsed time of Oracle Parallel Executions are not shown correctly in AWR","datePublished":"2019-11-15T15:08:17+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/"},"wordCount":516,"commentCount":0,"keywords":["Oracle","Parallel Execution","parallel query"],"articleSection":["Database Administration & Monitoring","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/","url":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/","name":"Elapsed time of Oracle Parallel Executions are not shown correctly in AWR - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-11-15T15:08:17+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0ac04011f60f2e93c115358d0789c2da"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/elapsed-time-of-oracle-parallel-executions-are-not-shown-correctly-in-awr\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Elapsed time of Oracle Parallel Executions are not shown correctly in AWR"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0ac04011f60f2e93c115358d0789c2da","name":"Clemens Bleile","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g","caption":"Clemens Bleile"},"description":"Clemens Bleile has more than 30 years of IT experience, thirteen in Oracle Support and fifteen in Oracle Consulting. He is specialized in Oracle Database Performance Tuning (SQL Tuning, DB Tuning) and developing an Oracle DB IT architecture (highly available, low-maintenance, cost efficient storage of data). He is an expert in problem analysis and resolution. Prior to joining dbi services, Clemens Bleile was Manager of the EMEA Database Performance team at the Oracle Global Customer Support Services. Clemens Bleile is Oracle Certified Professional 11g, 12c and Oracle Certified Expert for Performance Management and Tuning and holds a Master Degree, Business Information Systems from the Fachhochschule Furtwangen, Germany.","sameAs":["https:\/\/www.dbi-services.com","https:\/\/x.com\/ifgtxD2SrQ8r!YuXj"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/clemens-bleile\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13012","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/35"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=13012"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13012\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=13012"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=13012"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=13012"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=13012"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}