Here’s a funny little glitch – typical of the sort of oddity that creeps into the data dictionary from time to time – cut-n-pasted from 11.1.0.7:
SQL> select count(*) from user_indexes; COUNT(*) ---------- 1074 1 row selected. SQL> select count(*) from user_objects where object_type = 'INDEX'; COUNT(*) ---------- 917 1 row selected.
We seem to have 157 indexes that aren’t indexes – what could they be. Perhaps a small enhancement to our query on user_indexes (the one that has the larger result) will help:
Just a quick note to point out that the official white paper version of the TCO study I talked about in a previous post (Exadata vs. IBM P-Series) is now available on the Oracle web site here:
Cost Comparison – Oracle Exadata Database Machine vs. IBM Power Systems
The most interesting part of the study (in my opinion) is the quotes from the participants that are using Exadata. These quotes provide some insight into how people feel about the platform after having systems in production for a while (note that all the interviews were done prior to the release of the X3-2). I should also point out that these customers are not typical Oracle reference customers. They were interviewed by a third party and promised anonymity as part of the study.
We’ve all done that common administrative task of:
- find the HWM in a datafile
- resize the datafile down to that mark.
But sometimes, you might get what appears to be a problem:
Here’s a tablespace I created a while back…
SQL> create tablespace DEMO
2 datafile ‘C:\ORACLE\ORADATA\DB112\DATAFILE\DEMO.DBF’ size 100m
3 extent management local uniform size 1m;
Tablespace created.
After a while I wanted to reclaim that 100 megabytes back, so I looked at the high water mark in DBA_EXTENTS
SQL> select max(block_id+blocks)*8192/1024/1024 high_mb
2 from dba_extents
3 where tablespace_name = ‘DEMO’;
HIGH_MB
———-
2
So, if the high water mark is 2meg, all I need so now is resize the file….
A couple of weeks ago I was making my way through the office. As I came towards the end of the large, open-plan room I became aware that there was someone following behind me so, on passing through the door I held it briefly for the person behind me {there was no where else they could be going}, turned left and through the next door – and again held it and this time looked behind me to see if the person was still going the same way as I. The lady behind gave me the strangest look.
The strange look was reasonable – the door I’d just held for her was the one into the gentleman’s bathroom. *sigh*
<..Part one intro and examples
<….Part two Permissions
I’ve noticed that there has not been a lot of traffic on this series on Row Level Security (data masking) so far – maybe due to how I am presenting the material? So here is a summary to date in picture/diagram format:
A substantial part of the people I encounter present using OSX on a Macbook. I am not sure how much of these people use Apple’s Keynote for presenting, but I like Keynote very much for various reasons, like a cleaner interface. This blogpost is about some handy tips and tricks I learned using a few years of presenting around the world. If you don’t use OSX, this blogpost is probably not for you.
The previous post reminded me of another (fairly special) case where the order of operations in an execution plan seems to be wrong according to the “traditional” strategy for reading execution plans. Here’s a simple select statement with its execution plan to demonstrate the point:
Recent comments
3 years 5 weeks ago
3 years 17 weeks ago
3 years 22 weeks ago
3 years 22 weeks ago
3 years 27 weeks ago
3 years 48 weeks ago
4 years 16 weeks ago
4 years 46 weeks ago
5 years 30 weeks ago
5 years 31 weeks ago