There was a discussion on the OTN General database forum, in which the OP asked creating a table with just one row and restricting that table to just one row. Here is my attempt at it.
If it happens and you are in and around the Sydney area 1-2 weeks from now then you might be interested in taking part in these events.
I was troubleshooting a new GNS (Grid Name Services) functionality and noticed a-trace-level parameter in the GNS process string. Unfortunately there is no description in the documentation or MOS on how to change it to generate invaluable diagnostic information. NOTE: I am sure the documentation will be updated in Database 12c version (c for Cloud. For the time being the following should work for you.
It’s that time of the year again — Oracle OpenWorld time — and it’s my pleasure to announce our regular Oracle bloggers meetup again this year. We all know that Oracle community has grown this year so we expect to see folks from all the different technologies including MySQL, Java, Sun hardware folks in addition to the core Oracle database and apps crowd.
As a follow up from my previous post on Exadata Design, where I question the use of dimensions for certain attributes in data warehouses, I figured I should test whether HCC works with tables that have more than 255 columns, It does. Here’s my test case.
Michigan OakTable Symposium (MOTS) is a unique event taking place just before Oracle OpenWorld — 16-17 September. Why unique? This is the first conference (is it not?) where all presenters are members of OakTable Network, a group that gathers number of like-minded IT professionals with scientific approach to Oracle database technology and to the life in general.
As of this afternoon, version 22.214.171.124.1 of Oracle’s Exadata storage server software, is out in the wild. This is the first publicly available version of the 126.96.36.199 branch, a major release including a full OS image with an update to Oracle Enterprise Linux 5.5. A number of bugs causing cell server crashes and hangs have been fixed, including 9472035, 9870117, and 9722560.
en creating an index, Oracle versions 10g and above automatically compute optimizer statistics. And even before that, 9i had a COMPUTE STATISTICS clause to accomplish the same thing. Not only does it save the time and effort of running DBMS_STATS, but it also saves the disk I/O involved in such an operation, since all rows are available in the course of index creation.
Oracle Exadata V2 is a very well balanced database machine combined with smart and innovative software. One of these innovative features is the Storage Index – a game changing feature in my opinion.As with any feature, there are intended use cases, limitations and caveats. Use it right, and amazing performance gains can be achieved. Use it wrong, and nothing will happen. This is what is great about storage indexes in particular. They are there, without any overhead. It’s only a question of how to leverage them, in addition or combination withevery other feature that Oracle Exadata has to offer.
I’m not aware of any TPC results for Exadata V2. However a TPC-C test was run in late 2009 using a Sun F5100 flash array on Sun T5540 servers, setting a record for the benchmark that still stands. The Oracle wiki has a great overview of the various benchmarks and what they actually measure.