Skip to main content

PL/SQL Brain Teaser: when does a COMMIT not commit?

So your users make changes to tables (with great care and security, through your PL/SQL API), your app calls this procedure and that function. At some point along the way, a COMMIT statement is executed successfully in a user's session.

Yet that same user's session still has uncommitted changes!

Huh? How is this possible?

Think you know? Comment below!

Comments

  1. The commit was within an autonomous transaction.

    ReplyDelete
  2. commit write nowait/batch?

    ReplyDelete
  3. Autonomous Transaction :allows you to leave the context of the calling transaction, perform an independent transaction, and return to the calling transaction without affecting it's state.Hence the uncommitted changes in the users session are still significant.

    ReplyDelete
  4. Autonomous transaction! Love the brain teaser!!

    ReplyDelete
  5. Just few untested random use-cases in a hurry. Feel free to correct.
    1. Dirty data is in bulk collected collections. Processing commits in loop.
    2. View with instead of trigger. Trigger only uses partial data to update.
    3. Part of dirty data is written to a external table on really slow IO device.
    4. Distributed transaction. Part of dirty data has to be updated on some other DB.
    5. Call to external service from API with part of dirty data.
    6. Trigger on table allows selective data to update?

    ReplyDelete
  6. It all depends where in the process chain the commit was executed, if there were any dml statements after it, and if any rollback (to savepoint) was executed...

    ReplyDelete
  7. And here are some thoughts offered up on LinkedIn:

    * Is the commit statement outside the procedure? It so, it may be out of scope. Is there a rollback somewhere in the procedure or function?

    * The procedure having COMMIT might have executed with autonomously. So the user changes outside that procedure are still in process and not yet committed.

    ReplyDelete
  8. And now my answer: definitely, the answer in my mind is that the COMMIT statement was executed within an autonomous transaction subprogram.

    If you include

    PRAGMA AUTONOMOUS_TRANSACTION;

    in the declaration section of your procedure or function, then a COMMIT in that subprogram will commit only those changes made in the scope of that subprogram.

    Other outstanding changes in my session will NOT be committed.

    Now as to your comments:

    @stanley, I'd love to hear more explanation about some of your items, as they are outside my area of expertise. I am not sure if a distributed xaction applies here, since I reference the "user's session".

    @john, certainly any DML statements executed after the commit would be uncommitted. ROLLBACK TO before the commit would remove outstanding changes. After the commit? Well, the teaser has to do with state of session right after the commit (implied: before other actions take place).

    Thanks for participating!

    ReplyDelete

Post a Comment

Popular posts from this blog

Get rid of mutating table trigger errors with the compound trigger

When something mutates, it is changing. Something that is changing is hard to analyze and to quantify. A mutating table error (ORA-04091) occurs when a row-level trigger tries to examine or change a table that is already undergoing change (via an INSERT, UPDATE, or DELETE statement). In particular, this error occurs when a row-level trigger attempts to read or write the table from which the trigger was fired. Fortunately, the same restriction does not apply in statement-level triggers.

In this post, I demonstrate the kind of scenario that will result in an ORA-04091 errors. I then show the "traditional" solution, using a collection defined in a package. Then I demonstrate how to use the compound trigger, added in Oracle Database 11g Release1,  to solve the problem much more simply.

All the code shown in this example may be found in this LiveSQL script.

How to Get a Mutating Table Error

I need to implement this rule on my employees table:
Your new salary cannot be more than 25x th…

Table Functions, Part 1: Introduction and Exploration

August 2018 update: please do feel encourage to read this and my other posts on table functions, but you will learn much more about table functions by taking my Get Started with PL/SQL Table Functions class at the Oracle Dev Gym. Videos, tutorials and quizzes - then print a certificate when you are done!


Table functions - functions that can be called in the FROM clause of a query from inside the TABLE operator - are fascinating and incredibly helpful constructs.

So I've decided to write a series of blog posts on them: how to build them, how to use them, issues you might run into.

Of course, I am not the first to do so. I encourage to check out the documentation, as well as excellent posts from Adrian Billington (search for "table functions") and Tim Hall. Adrian and Tim mostly focus on pipelined table functions, a specialized variant of table functions designed to improve performance and reduce PGA consumption. I will take a look at pipelined table functions in the latte…

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post.

PL/SQL is a strongly-typed language. Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type).

PL/SQL offers a wide array of pre-defined data types, both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package).

Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types.

You can't really declare your own "user-defined" scalars, though you can define subtypes from those scalars, which can be very helpful from the perspective…