Posts tagged Oracle 11gR2
Availability is a highly desirable aspect of Fusion Middleware application. Planned downtime therefore sounds quite silly. However, the introduction of changes to applications has typically been associated with the roll out and redeployment of the application causing disruption of service – through loss of existing conversations and unavailability during the deployment process. Several approaches and mechanisms are available in the Oracle stack that will help substantially reduce the loss of uptime because of changes to applications.
First of all, many types of changes may be implemented through run time configuration, rather than software change requiring redeployment of application artifacts. This approach requires good design of aspects of applications that may require modification and the construction of run time mechanisms for applying and processing such changes. The design time at run time capabilities of several Fusion Middleware products go a long way in supporting this approach.
Additionally, several FMW components support short or even long term co-existence of different versions of applications. This means that existing conversations can complete even when a new More >
Its time to enlist. It really is. At least regarding the XMLDB related sessions and presentations during Oracle Open World 2009. As far as I have seen today, the hands-on workshop has almost no seats left and more than half already enlisted for my XMLDB New Features and XMLDB Performance related presentation.
Oracle Open World doesn’t have much XMLDB related sessions, until now from the 1800+ sessions, I only counted a dozen or so. If you want to have a peak of the ones I found, have a look at the following Oracle OTN XMLDB Forum thread.
I enlisted for most, as long as they didn’t interfere with my presentation schedule, if not only that I am very anxious about Mark Drake’s presentations about Google API mashups etc combined with the XMLDB functionality in the database and the, probably extended version of how to build an APEX content management system based on the versioning and filler capabilities of the XMLDB Repository. During OOW 2008, Carl Backstrom, helped and co-presented this APEX / XMLDB joined venture and, alas, this demo app. of the XFILES light weight XMLDB CMS based on APEX, never had (at least yet More >
So, if I would wonder what is the purpose of this almost "hidden" feature called flash cache and were this came from (also see my post Oracle RDBMS 11gR2 – Flash Cache), now I know. I didn’t have the chance to follow Mr. Ellison’s launch event, but reading Alex Gorbatchev’s blog post on the Pythian web site Unveiling the OLTP Oracle Database Machine & Exadata v2 is enough explanation in the "why" and "how". Flash cache is one of the pillars that make the synergy with the Sun Exadata machine.
As Alex stated:
Exadata Storage Servers
Storage Servers are based on Sun Fire X4275. Again top of the shelf Intel Xeon 5500 Nehalem processors.
Capacity increased — SAS disks are 600 GB (+33%) and SATA disks are 2 TB which doubles what ODBM v1 offered. We all know that big disks are bad but that’s where Sun FlashWire technology comes into play with flash cache on the controllers (5+TB for the full ODBM).
This is what Ellison said about Flash cache:
“These are not Flash disks. Make no mistake — these are no Flash disks. This is a memory hierarchy made up of DRAM in our database servers and Flash in our storage servers with very sophisticated algorithms, not simple LRU — we know for doing a More >
There is a Metalink note (563802.1) that has a very good example how XML data storage, partitioning can be achieved in Oracle version 126.96.36.199.0 (the first officially supported XMLDB database functionality) and onwards. Partitioning can be used in such XML situations to spread the I/O load and it also supports, if done correctly, the XMLDB functionality / Oracle database, to use query re-writes during XPath or XQuery statements. See for more information about Query Rewrite support the Oracle XMLDB Developers Guide.
The "new" equi-partitioning functionality, supported from 188.8.131.52.0, but now described in more detail in the 11gR2 XMLDB Developers Manual, also propagates / partitions all underlying structures. As described in the Metalink note: "In Oracle release 11g the partitioning model is equi-partitioning which means that the underlying storage tables are partitioned too along with the default table partitioning structure. In previous releases only the default table is partitioned, but the underlying storage tables for the types are not."
So explained in more detail, before 184.108.40.206.0 only the "xdb:defaultTable", in the following example table "TESTELEMENT", is partitioned More >
One of the other small but very useful new features in the Oracle 11gR2 database is the addition of a PREPROCESSOR parameter for the create EXTERNAL table statement. This PREPROCESSOR clause gives you the ability to execute an executable or executable (shell) script that handles your data before it gets presented. The PREPOCESSOR clause is part of the ORACLE_LOADER access driver
The Oracle 11gR2 Database Utilities Manual states:<code>The preprocessor program converts the data to a record format supported by the access driver and then writes the converted record data to standard output (stdout), which the access driver reads as input. SQL> CREATE TABLE xtab (recno varchar2(2000)) 2 ORGANIZATION EXTERNAL ( 3 TYPE ORACLE_LOADER 4 DEFAULT DIRECTORY data_dir 5 ACCESS PARAMETERS ( 6 RECORDS DELIMITED BY NEWLINE 7 PREPROCESSOR execdir:'zcat' 8 FIELDS (recno char(2000))) 9 LOCATION ('foo.dat.gz')) 10 REJECT LIMIT UNLIMITED;</code> <code> SQL> CREATE TABLE xtab (recno varchar2(2000)) 2 ORGANIZATION EXTERNAL ( 3 TYPE ORACLE_LOADER 4 DEFAULT DIRECTORY data_dir 5 ACCESS PARAMETERS ( More >