Sunday, December 31, 2017

My Upcoming Speaker Events in H1 2018

Hi everybody,

I'd like to share with you the plans for my upcoming speaking activities for the first half of 2018:

  • Israel Oracle User (ILOUG) Group Tech Days 2018 (Jan 22-23) - Very excited to present a session in one of the best Oracle conferences that ever took place in my country. I will be presenting a session titled "Winning Performance Challenging in Oracle Multitenant" on January 23rd about how to effectively monitor and diagnose performance issues in Oracle Multitenant environments and if needed implement resource management plans to ensure high QoS (Quality of Service) for the pluggable databases.
  • Rocky Mountain Oracle User Group (RMOUG) Training Days (Feb 20-22) - This will be my first time attending (and speaking) at this event. I will deliver 2 sessions:
    • "Winning Performance Challenging in Oracle Multitenant"- similar to the one I will be presenting at ILOUG
    • "Oracle Database Locking Mechanism Demystified" - In this session I will be talking about the concepts of Oracle Database locking mechanism, advanced locking scenarios, best practices to avoid performance issues which relate to blocked SQLs, and ways to investigate lock issues using Oracle dictionary views and performance monitoring tools
  • Independent Oracle User Group (April 22-26) - IOUG Collaborate is definitely my favorite Oracle Conference in the world - it's a combination of great location and very technical presentations. I got accepted to present the following sessions:
    • ASM Concepts, Architecture and Best Practices - Since it was introduced back in 2003 with Oracle 10g, ASM became an essential part of almost every Oracle DBA's life. In this session you will learn ASM from A to Z - starting with the basic concepts of the ASM all the way to the new features of ASM and important best practices that will help you increase the performance and stability of your Database environments.
    • Oracle Data Guard for Beginners - Oracle Data Guard is one of the most important options in the Oracle Database as it allows organizations to ensure high availability, data protection, and disaster recovery for their Oracle database environments. In this session we'll review Oracle Data Guard solution from A to Z.

I invite you all to my sessions and looking forward to meeting you there!

Friday, October 13, 2017

I'm an Oracle ACE - thank you Oracle for this recognition!

Hi everybody,

Yesterday I received the following email from the Oracle ACE Program:

"I am pleased to inform you that you have been accepted to receive the Oracle ACE award. You have been chosen based on your significant contribution and activity in the Oracle technical community. Like your fellow Oracle ACEs, you have demonstrated a proficiency in Oracle technology as well as a willingness to share your knowledge and experiences with the community."

I received this recognition from Oracle and I'm proud to be part of the awesome Oracle ACE family - thank you Oracle ACE Program!

Thank you IOUG (Independent Oracle User Group) for choosing me to present sessions at IOUG Collaborate 16 & 17 and also for inviting me to present on behalf of the IOUG at Oracle OpenWorld 2016 & 2017. I would also like to thank additional local user groups: DOAG, AOUG, OUNG for choosing me to speak at their annual user group conferences.

Here is a link to my Oracle ACE page:

Tuesday, October 10, 2017

ODC Appreciation Day : Online Move Data File Operation

I've decided to dedicate my ODC Appreciation Day blog post to "Online Move Data File Operation" - a feature which has been introduced in Oracle 12c.
As a quick background to this blog post, ODC (Oracle Developer Community) appreciation day is Tim Hall's (Oracle-Base) initiative which started last year (when it was OTN Appreciation Day).

So what is online move data file operation?

Moving data files is a common-use case, for example, when the DBA would like to move data files to a faster/larger disk. Another common use case is when DBA would like to migrate the files from traditional file systems to Oracle's Automatic Storage Management (more information about Oracle ASM is available in my ODC published article :

Prior to Oracle 12c, there was no way to accomplish this task with zero downtime. Common solution was to take the entire tablespace or data file offline, move it to the new location, change the location using the "ALTER DATABASE" command (which  essentially changes the location in the Oracle's control file) and then bring the tablespace/file online again; however, during this operation the entire tablespace or datafile won't be accessible. Better approach to mitigate the downtime was to change the tablespace or data file to be in a read-only mode which will at least allow queries to be executed against the data which reside on that tablespace/file - but it's still not favorable because DMLs/DDLs cannot be executed during that operation.

Oracle 12c allows us to do this completely online with zero downtime - while the database is open and users are accessing the data file. I've presented this feature with several syntax examples as part of my IOUG Collaborate 16 presentation - "Best New Features of  Oracle Database 12c" (slide deck is available here:

You could also find several examples and even a short video which demonstrates this cool feature in the Oracle documentation:


Whether running Oracle databases on premise or in the cloud, this feature is very useful. When Larry Ellison spoke at Oracle OpenWorld 2017 keynotes about Oracle 18c and Oracle's option of to ensure having up to 30 minutes down-time a year with their cloud offering, this feature is another useful way  that can help when it comes to ensuring zero impact on the customer's applications (among the many other Oracle's HA & DR features - such as ASM, RAC Rolling Upgrades, Active Data Guard, Flashback, etc.)

My Oracle OpenWorld 2017 Presentation - Slide Deck is Now Available!

Last week, on October 1st, I've presented a session at Oracle OpenWorld about Database consolidation using Oracle Multitenant option.
I was invited to speak on behalf of the IOUG (Independent Oracle User Group) at Oracle OpenWorld for the second year in a row! Thank you IOUG for this great opportunity! It was fun (as always).

I got several requests to share my presentation - so here you go:

Oracle OpenWorld 2017 was a great experience, with some exciting announcements about the future Oracle 18c release (I will write a separate blog post about this upcoming release).

I'd also like to thank everybody who attended my session, and hope to see you again next year!

Thursday, August 31, 2017

Common misconception about how Oracle handles deadlocks


In today's blog post, I'd like to uncover a common misconception about how Oracle handles deadlocks, but first let's talk about what deadlock is. Deadlock is a locking scenario that occurs when two or more sessions are blocked as they wait because of a lock that is being held by the other session. Oracle Database automatically detects this scenario and handles this because otherwise, they will wait forever as both of them are blocked and waiting to each other’s locked resources. But the question is how does Oracle handle this? some would say that Oracle handles these scenarios by terminating one of the sessions which is known to be as the "deadlock victim" - well, that's wrong. Others would say that by rolling-back the entire transaction of one of the sessions - well, that's also wrong. So how Oracle really handles deadlock scenarios?

Deadlock Illustration

Let's see a quick example of how deadlock occurs

Step 1

Session #1 performs an update of a row (employee #151) and acquires a lock on that row

SQL> UPDATE employee
          SET first_name = 'David'
          WHERE employee_id = 151;

1 row updated.

Step 2

Session #2 performs an update of a row (employee #39) and acquires a lock on that row

SQL> UPDATE employee
          SET first_name = 'Greg'
          WHERE employee_id = 39;

1 row updated. 

Step 3

Session #1 performs an update of a row (employee #39) and is now waiting since a lock has been acquired on the same row which has not been released yet as session #2 transaction is still active

UPDATE employee
          SET first_name = 'Mark'
          WHERE employee_id = 39;

Step 4

Session #2 performs an update of a row (employee #151) and is now waiting since a lock has been acquired on the same row which has not been released yet as session #1 transaction is still active.  

SQL> UPDATE employee
          SET first_name = 'John'
          WHERE employee_id = 151;

At this stage both sessions (session #1 and session #2) are blocked  and waiting to each other’s locked resources - that's exactly what deadlock is.

So how Oracle handles deadlock scenarios?

The way Oracle handles deadlock scenarios is not by terminating one of the sessions or performing a transaction-level rollback, it's actually just by performing a statement-level rollback to one of the sessions.  The session that its statement is being rolled back, will encounter an “ORA-00060: Deadlock detected while waiting for resource.” error message (that will also be recorded in the alert log file).