ASM & RDBMS Interactions: Opening a Datafile

Once your RDBMS instance has found the ASM instance it is relying on, what happens when the RDBMS needs to actually open a file that is held on ASM storage?

It seems fairly straightforward. The RDBMS maintains a series of connections to the ASM instance via the Onnn background processes. Requests to open a file go via these background processes to the ASM instance. The ASM instance then sends the extent map to the RDBMS instance.

The RDBMS can then use the extent map to perform I/O direct to the file. It is important to bare in mind that the I/O requests from the RDBMS do not go via the ASM instance, but straight to the devices by using the extent map.

The ASM instance only looks after the metadata that describes diskgroups and extent allocations. It would not be efficient for the RDBMS to have to send it’s I/O via the ASM instance and this does not happen.


2 thoughts on “ASM & RDBMS Interactions: Opening a Datafile

  1. Jarneil,

    How do you measure the time it took to return the exent map? I mean Is it recorded anywhere?


  2. well, I see there is a wait event:

    extent map load/unlock

    could be worth checking for this if you are experiencing issues.

    Note, as you may know with 10g the full map is passed, but 11g optimises this by not sending all extents to begin with.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s