One of the new things in 11g is the possibility to set the method of how to enforce the validation / encoding of your XML document, straight away via embedding these options in your binary XML storage structure. It is just a small entry in the manual, but I think an important one. That’s why I wrote this small post, to emphasize this.
These extra options can be enabled during the creation of your binary XMLType table / column(s).
You have the option to use:
This is a bummer and then again it is not. I am thinking lately a lot about how to bring the conceptual XML(DB) world into the Oracle Relational world, or in other words “what is needed to make XML fast – given an Oracle database 11g atmosphere”. One my ramblings was: OK given the XML free format, how do I a create an environment that’s very high selective based on indexing and or breaking up XML fragments in physical segments (therefore hopefully being more selective) that can be handled more easily by the Oracle Optimizer (even given items like, creation solutions for, XML deficiencies like data redundancy etc).
Anyway…
Searching the internet I came up with this excellent (it helped me one step further in my exploring brain matter path) link regarding indexing called:
What’s more, and this brings me back awfully close to home (Holland / Amsterdam), I looked up the used references by Shweta Agrawal. One of them was called:
Tomorrows presentation at AMIS, will be my first test run for my UKOUG presentation in December, Birmingham. It took me a while to get the red herring from my braincells onto a Powerpoint presentation. To be honest, I am still not really pleased with it. It lacks some coherency, but I almost now for sure that it will be there when I start of and introduce my audience into the wonderful (sometimes confusing) world of XMLDB.
I will address a lot of DBA viewpoints on to the matter.
Read more…
Bad Behavior has blocked 345 access attempts in the last 7 days.