With the INMEMORY clause you can specify 4 sub-clauses:
- The MEMCOMPRESS clause specifies whether and how compression is used
- The PRIORITY clause specifies the priority (“order”) in which the segments are loaded when the IMCS is populated
- The DISTRIBUTE clause specifies how data is distributed across RAC instances
- The DUPLICATE clause specifies whether and how data is duplicated across RAC instances
The aim of this post is not to describe these attribues in detail. Instead, (more...)
I strive to keep the number non-technical posts on this blog to the minimum. However, there are days when a non-technical post has to be written. This is one of such days.
Oracle Corporation, concerned about legal and ethical issues, not only provides to its employees a document entitled Code of Ethics and Business Conduct, but also expects that every employee adheres with the standards that the document sets. For the purpose of (more...)
The aim of this post is not to explain how the APPROX_COUNT_DISTINCT function works (you find basic information in the documentation and in this post written by Luca Canali), but to show you the results of a test case I run to assess how well it works.
Here’s what I did…
I created a table with several numerical columns (the name of the column shows how many distinct values it contains), loaded 100 million (more...)
Every new Oracle Database patch introduces not only documented features, but also undocumented ones. In this short post I would like to provide information about an enhancement of the RESULT_CACHE hint.
According the documentation, the RESULT_CACHE hint has no parameter. But, as of 126.96.36.199, at least the SNAPSHOT parameter is supported. Its purpose is to specify how much time (in seconds) after the creation the result cache entry has to (more...)
This is just a short post to point out that the downloadable files are available here. You can download either a ZIP or a TAR file containing all files, or single files.
Since every file has its own URL, you can also directly executed them in SQL*Plus. For example:
I’m sorry for the delay!
Several people asked me how much I changed in the second edition. The short answer is… A LOT.
The main goals set for the revision of the book were the following:
- Add content about Oracle Database 11g Release 2 and Oracle Database 12c Release 1.
- Remove content about Oracle9i and Oracle Database 10g Release 1.
- Add content that was “missing” in the first edition (for example, features like hierarchical profiler, active session history, AWR and (more...)
Few days ago the second edition of Troubleshooting Oracle Performance was finally published. Today, I updated the pages on this site that provide information about the book. It goes without saying that the new pages cover the second edition. Hence, from here you can access the description, the table of contents, the forewords written by Jonathan Lewis and Cary Millsap, as well as a page with some errata. Yes, as for the first edition, (more...)
After about four months without any speaking engagements, over the next three months I’ll have the opportunity to speak at several events. I’m looking forward to meet you at one of them!
April 3, I’ll be in Baden-Dättwil to speak about “ASH Analytics” at an event organized by SOUG. Since this is a new presentation covering some stuff that I wrote for the second edition of TOP, I’m looking forward to see how it works.
The company I work for, Trivadis, is very pleased to organize, on the 10th and 11th of June, an outstanding seminar with top guest speakers in Zurich. This year’s focus will be on the Oracle query optimizer, also known as a cost-based optimizer (CBO).
The query optimizer is not only one of the most complex pieces of software that constitutes the Oracle kernel; it is also one of the most unappreciated. Why? To make the (more...)
Today, while tuning a fairly complex query experiencing wrong cardinality estimates, I noticed something I was not aware of. Hence, I thought to write this short post to illustrate how to reproduce the problem I experienced…
- Create the test table (notice the correlation between the data of the two columns):
SQL> CREATE TABLE t
3 SELECT mod(rownum,50) AS n1, mod(rownum,50) AS n2
4 FROM dual
5 CONNECT BY level < = 1000;