Exadata Storage Indexes

Storage Indexes is one of the most significant features of Exadata that run at the storage cells. However, is also the feature which is the least (if at all) controllable by the user (developer/dba). You cannot control when they will be build, for which columns they will be build for, and  for which columns the storage indexes will remain as the database workload evolves. So it is a true "black box" and totally different to what we have been used from good old database indexes.

The following links from Richard Foote's Oracle Blog are very insightfull on how storage indexes really work:
First goes the introductory series of posts:

• Exadata Strorage Indexes - part I
• Exadata Strorage Indexes - part II
• Exadata Strorage Indexes - part III
• Exadata Strorage Indexes - part IV
• Exadata Strorage Indexes - part V

And then is the comparison series between SIs and database indexes (check out the last one on the "magic" 8-column limit):

• Storage Indexes vs Database Indexes - part I
• Storage Indexes vs Database Indexes - part II
• Storage Indexes vs Database Indexes - part III
• Storage Indexes vs Database Indexes - part IV

Enjoy,
Oracle Learner.

How to connect to Exadata

How can one connect to an Exadata? In our example we will assume a half rack Exadata, which means that at the database layer we have a 4-node database RAC.

At the server side, we need to install a local listener on each database node. So we have 4 listeners "listening" for Exadata connections.

At the client side we assume the so-called "Local Naming Method" for name resolving, which simply means that we have at the client side a tnsnames.ora  file with an appropriate tns entry. But what should be an appropriate tns entry for connecting to our Exadata?