A fresh view on Oracle
Oracle has released it’s first patch set for Oracle Database 11g Release 2 (11.2.0.2).
See the README at Oracle® Database Patch Set Notes 11g Release 2 (11.2.0.2) Patch Set 1 and Metalink Note ID 1189783.1 at Important Changes to Oracle Database Patch Sets Starting With 11.2.0.2 for more information.
I knew in Oracle 11g with Automatic Memory Management (AMM), the database was able to give unused memory back to the OS, controlled by MEMORY_TARGET and MEMORY_MAX_TARGET.
This mechanism is present in 11g since day 1 (in 2007), but I never actually played with it.
The Oracle documents state the following:
MEMORY_TARGET specifies the Oracle system-wide usable memory.
MEMORY_MAX_TARGET (…) decide on a maximum amount of memory that you would want to allocate to the database for the foreseeable future.
So my guess is, MEMORY_MAX_TARGET (static) is the maximum you can set MEMORY_TARGET (dynamic) to. A couple of days ago, I wanted to experiment a bit with these memory settings.
[Read the rest of this entry...]
They have finally arrived, the Windows 64 and 32 bit versions of Oracle 11gR2.
Download Oracle Database 11g Release 2 for Windows
The 64 bit version was released a bit earlier, so I was hoping the 32 bit version would not come… Why do we want the 32 bit versions? Older systems? Ancient systems! Why…?!
Now I don’t have an excuse to update my almost 10 years old Windows XP OS (running on 64bit hardware) to a much nicer Windows 7 64 bit. The only excuse now is that I could use 600+ megs of memory… enough to run that XP OS virtually!
In Oracle 11g, the one who is calling a remote site needs to get access to that site. This is done via the Access Control List.
I have written a blog about this error at my Whitehorses Blog: Oracle 11g: Access Control List and ORA-24247.
Happy consulting!