After creating the initial structures to scrape some JSON content of Wikipedia, as mentioned in…
When learning new things, I always try to apply it to a hopefully useful and…
I was looking at a 3rd party application running in an Oracle 11.2 database. I listed the source code of one of the packages and noticed that it contained 5 versions of the same procedure. I have never done any Oracle development so I am not a PL/SQL expert and this seemed strange to me at first.
This happened in an Oracle 18.104.22.168.0 database: A developer reported problems when running a CREATE
There was has been various on going discussions about the every growing “always on” or “always available” aspect of modern life. Most of us do something like the follow each day:
I wrote a blog post some time ago about using a file share witness with a minimal windows failover cluster configuration that consists of two cluster nodes. In this blog post, I told I was reluctant to use a witness in this case because it introduces a weakness in the availability process.
When using direct path read, oracle reads the blocks from the disk. The buffer cache is not being used.
Then, when oracle begins to read a segment using direct path read, it flush its dirty blocks to disk (A dirty block is a block that does not have the same image in memory and on disk). During that time, the session that triggered the direct path read is waiting for the “enq: KO – fast object checkpoint” wait event.
In this post, I just want to see with my own eyes that the dirty blocks being flushed to disk belong only to the segment being read.
When you are working with and developing Decision Trees by far the easiest way to visualise these is by using the Oracle Data Miner (ODMr) tool that is part of SQL Developer.Developing your Decision Tree models using the ODMr allows you to explore the decision tree produced, to drill in on each of the nodes of the tree and to see all the statistics etc that relate to each node and branch of the tree.