(Jeff Smith) Virtual columns made their debut in Oracle Database 11g. They are a value that’s not stored with the row, rather they are computed as queried.

(mwidlake) A few days ago I was introduced (or re-introduced) to USERENV(‘COMMITSCN’) by Jonathan Lewis. This is an internal function that allows limited access to the SCN of your transaction.

(Brendan Tierney) The following is the fourth set of demo code from my video on using R in the Oracle Database. Check out the video before using the following code. The blog post for the video will be updated to contain links to all blog posts that have the various demo code.

(Bobby Curtis) This morning I was working on an Oracle Management Repository (OMR) for a test Enterprise Manager that is used by a few consultants I work with. When I logged into the box, I found that the OMR was down. When I went to start the database, I was greeted with ORA-01172 and ORA-01151.

(Martien van den Akker) Last few days I spent with describing a Throttle mechanism using the DB Adapter. Today the ‘Distributed Polling’ functionality of the DB Adapter was mentioned to me, which uses the SKIP LOCKED clausule of the database.

(connormcdonald) Within a CONNECT BY statement, you can order siblings, that is, under a particular branch of the hierarchy, the child entries can be ordered, but you still preserve the hierarchy.

(Richard Harrison) Today we were moving some schemas from database A to database B – all was pretty much fine apart from some messages about bad index stats right at the end where it was failing to import some metadata against an object that didn’t exist

(stewashton) This is my third post about temporal tables that don’t allow overlaps. I’m going to add support for temporal gaps, which will also allow objects to stop existing at some point.

(connormcdonald) In 12c, one of the nice changes to come along is that partition maintenance operations can now be done on multiple partitions, for example

(Randolf Geist) It’s probably not that well known that Oracle can actually rollback / re-start the execution of a DML statement should the cursor become invalidated. By rollback / re-start I mean that Oracle actually performs a statement level rollback (so any modification already performed by that