The situation: do an explain plan for a SQL which contains table names without schema qualifiers, which reside in a schema other than my own. To explain the SQL without any modifications, alter session set current_schema was used. connect me@db alter session set current_schema=other explain plan for select this, that from there ; select * …
Beware of explain plan in combination with alter session set current_schema weiterlesen
Redo volume is related to archive log volume, but not identical. Here is and SQL to get the actual cumulated redo sizes from the AWR. select * from ( SELECT TO_CHAR(begin_interval_time, 'yyyymmddhh24mi') tm, s2.instance_number, (s2.value - s1.value)/1024/1024 redo_size FROM dba_hist_sysstat s1 , dba_hist_sysstat s2, dba_hist_snapshot sn WHERE s1.stat_name = 'redo size' and s2.stat_name = 'redo …
In analysis of SQL stats, execution times are cumulated for all parallel servers. This makes it difficult to derive the correct execution times from the AWR. Create some test data: The test script: Output: Though the SQL runtime was 1,27s, the accumulated elapsed time in v$sqlstats is 17,07s, due to the fact that all parallel …
How to estimate the parallel degree for historical SQL weiterlesen
The living room computer was set up to go to S3 sleep (non hybrid) after 15 minutes of inactivity. But still with having all settings correct, the computer would not go to sleep properly. Screen and audio would turn off, but the computer itself remains more or less active, even when entering standby through the …
Interesting problem with standby in windows 10 (solved) weiterlesen
To avoid ORA-15410, when adding disks of mixed sizes. http://blog.trivadis.com/b/robertbialek/archive/2014/10/28/asm-disk-size-check-with-oracle-12c-release-1-ora-15410.aspx
Try this: select true from dual; ORA-00904: "TRUE": ungültiger Bezeichner The reason behind this behavior is that TRUE and FALSE are only available in PL/SQL, not in SQL. Booleans are simply not usable in SQL queries. How to work around this limitation? The SYS.DIUTIL package's BOOL_TO_INT() function provides a hint. Let's see. declare n number; v_true …
