November 2016

I am now an ex-ACE Director

How apt that this should be my next blog post, following So long, and thanks for all the fish. I’ve been an Oracle ACE Director since 2009, and watched the program evolve in form considerably over that time. It’s always difficult to maintain high quality advocacy as a program grows – my time as part of the OakTable ‘junta’ … Continue reading "I am now an ex-ACE Director"

I am now an ex-ACE Director

How apt that this should be my next blog post, following So long, and thanks for all the fish. I’ve been an Oracle ACE Director since 2009, and watched the program evolve in form considerably over that time. It’s always difficult to maintain high quality advocacy as a program grows – my time as part of the OakTable ‘junta’ … Continue reading "I am now an ex-ACE Director"

James Morle

Code enhancements without changing code

An interesting suggestion came through on AskTom this week, which prompted the following exploration.

Let us assume you are populating a table with


INSERT INTO EMP SELECT * FROM SOURCE_EMPS

and it falls over with


ORA-12899: value too large for column

To capture the data that caused that error is not trivial. Of course, we could edit the code to perform DML error logging but of course, that means changing the source code, which means change control, testing, red tape etc etc etc. Is there a better way ? Perhaps there is.

What keeps database administrators awake at night and the search for the promised land

What keeps you and me awake at night? When I was a consultant for a Fortune 500 company in Southern California, we were getting beaten up to prove that databases were being backed up correctly and that disaster recovery would work. The truth of the matter was that we didn’t even have an accurate list of all the databases and databases would go down for days without anybody noticing which means that they were not even being monitored correctly. In fact, the yet unsolved NoCOUG murder mystery...(read more)