Search

Top 60 Oracle Blogs

Recent comments

March 2014

Index Rebuild, the Need vs the Implications Support Note 989093.1 (Getting Better)

Once upon a time, Oracle Support had a note called Script: Lists All Indexes that Benefit from a Rebuild (Doc ID 122008.1) which lets just say I didn’t view in a particularly positive light :) Mainly because it gave dubious advice which included that indexes should be rebuilt if: Deleted entries represent 20% or more of […]

Pure Storage and Delphix

chocolate_peanutbutter

Joint webinar:

Super Charge Database Deployments

 

 

pure_storage  delphix_logo_color

Oracle EMEA Virtual Developer Days 2014

Aanstaande dinsdag 4 maart wordt er door Oracle een Oracle EMEA Virtual Developer Day georganiseerd. Je kunt je hiervoor gratis inschrijven en live, via het...
class="readmore">Read More

Hotsos 2014 Presentation

Just a quick note that I’ve added a zip file with my presentation at Hotsos yesterday which includes the scripts that I demoed. You can find it on the Whitepapers/Presentations page. Or you can just click this link:

SQL Gone Bad – But Plan Not Changed!

Next codemonth: Jira integration!

This months project will be in the same line as last month. It will be an oracle integration to the issue tracking system Jira from Atlassian. There are two big use cases for me in this. One, is that a lot of my customers have bought the Confluence->Jira pack, so beeing able to integrate the database directly to issues and tasks, can make a lot of things easier and more effective. .... read more on my blog

Recurring Conversations – Incremental Statistics (Part 2)

In the first part, I explained that Incremental Statistics are designed to allow a partitioned tables Global Statistics to be updated based on a combination of

1) Statistics gathered by analysing the contents of one or more partitions that have just been loaded or have been updated (and see this blog post for more depth on what 'updated' means!)

2) The statistics of existing partitions which are represented by synopses that are already stored in the SYSAUX tablespace.

Using this combination, we can avoid scanning every partition in the table every time we want to update the Global Stats which is an expensive operation that is likely to be unfeasible every time we load some data into a large table.

Flashback Fail ?

Sitting in an airport, waiting for a plane, I decided to read a note (pdf) about Flashback data archive written by Beat Ramseier from Trivadis.  I’d got about three quarters of the way through it when I paused for thought and figured out that on the typical database implementation something nasty is going to happen after approximately 3 years and 9 months.  Can you guess why ?

Next codemonth: Jira integration!

This months project will be in the same line as last month. It will be an oracle integration to the issue tracking system Jira from Atlassian. There are two big use cases for me in this. One, is that a lot of my customers have bought the Confluence->Jira pack, so beeing able to integrate the database directly to issues and tasks, can make a lot of things easier and more effective.

JIRA_UTL Tutorial 1: Creating an issue

So the first tutorial will show how to create a jira issue directly from the database. We will create two types of issues, a bug and a subtask to an existing issue.

Auto Sample Size

In the past I have enthused mightily about the benefits of the approximate NDV mechanism and the benefit of using auto_sample_size to collect statistics in 11g; however, as so often happens with Oracle features, there’s a down-side or boundary condition, or edge case. I’ve already picked this up once as an addendum to an earlier blog note on virtual stats, which linked to an article on OTN describing how the time taken to collect stats on a table increased dramatically after the addition of an index – where the index had this definition: