With end of July 2010 support for Oracle 10g Release 2 ends. You can order (at additional costs of course) so called extended support to get support until July 2011. After this date there is so called “Sustaining Support” which offers support for several more years.
Update: I was told the first year of Extended Support is free of charge (Thanks Martin!). So customers have a little bit more time to test and upgrade.
See the following picture for the support end dates:
So if you start with new projects i´d strongly recommend to use Oracle 11g Release 2 at best or if 11g R2 is not an options 11g R1.
I just found Oracle released 10.2.0.5.0 patchset for the following platforms:
See Doc ID 1088172.1 for a list of fixed problems.
This is a short posting about an error i found today.
This errors prevents the import of tables with lob columns when using traditional import, deferred segment creation and an altered tablespace name.
For this i created a test case in which we
- In the source database (10.2.0.4.0 on 64-bit Linux):
- create a user named TEST1 having a default tablespace named TEST1
- create a small table with a CLOB in it
- export the schema with traditional import
- transfer the dump to the destination database
- In the destination database (11.2.0.1.0 on 64-bit Linux)
- create a user names TESTNEU with a default tablespace TESTNEU
NOTE: There is no tablespace TEST1 in the destination database; this is important
- trying to import the table… hitting a bug documented below in detail
Note: While blogging this for a fried i was in hurry; i will rewrite some paragraphs with evening… but the problem should become clear while reading…
Read more…
Some time ago i´ve seen a discussion on OTN about ASM and thin provisioned volumes.
Hi there, sorry for the x-post from database-general but it was suggested that I do so.
Anyhow, we've got 11g (11.1.0.7 with the 6851110 ASM patch recently applied) running on
OEL 5 x86_64, with ASM connected to a raw, thin-provisioned ISCSI volume partitioned for
+DATA and +FRA, and in every case where we do so, the SAN device reports within a few
weeks that the whole volume has been allocated even though the DB (configured with
autoextend on) is only holding about one tenth of the amount of available space on the
device. What this means in systems terms is that somehow ASM is marking writes to nearly
every block on the drive if only momentarily.
In the original thread, there was speculation that a process of indexing AUs has led to
the dirtying of the whole volume, but this would make more sense if the whole disk had been
allocated immediately rather than over the course of a few weeks. My question is: what else
could account for this behavior, and what steps can I take to help ensure that ASM behaves
correctly in a thin-provisioned volume? (by "correctly" I mean writes contiguous blocks of
data and doesn't dirty the whole thing)
Yesterday i had some spare time available to dig a little bit deeper. I had a Windows-based system at hand and performed some smaller tests.
Read more…
The following illustrates the installation of Oracle 11g Release 2 database on Windows. Installation is quite straight forward.
Before installing the database you can optionally install grid infrastructure which offers some nice feature – for instance Oracle Restart and ASM. The install guide for grid infrastructure can be found here.
Read more…
The following pictures show the grid infrastructure installation of Oracle 11g Release 2 for Windows. This is a rather short posting without much text because the pictures are quite self-explaining.
Requirements
Windows
Note there is no grid infrastructure or ASM for 32-bit Windows!
According to the documentation the following Windows versions are certified for Oracle 11g Release 2:
- Windows Server 2003 x64 with service pack 1 or higher.
- Windows Server 2003 R2 x64
- Windows Server 2008 x64 Standard, Enterprise, Datacenter, Web, and Foundation editions.
- Windows Server 2008 R2 x64 Standard, Enterprise, Datacenter, Web, and Foundation editions
Windows Core Editions are NOT supported!
Storage
For storing your database you can use the following storage options:
- plain file system (NTFS recommended or FAT)
- ASM
- Oracle NFS for Windows
In this guide we are using ASM for storing our data files.
I just tried installing Oracle 11g Relese 2 on Windows 2008 R2 64-bit and Windows 2008. The system were installed with Windows 2008 and 2008 R2 standard edition 64-bit on a VMWARE server with 4 core with two core assigned to each virtual machine.
Until now i was unable to install it successfully. It always failed with:
[INS-20802] Grid Infrastructure Configuration failed
This is a short blog post about my findinds. Maybe someone else experience this issue as well and leaves a comment.
Read more…
I have written an guest article (direct link) for Preston de Guises fine blog on how to use networker client on opensolaris.
As of April 5th Oracle released Oracle 11g Release 2 for Windows 32-bit and 64-bit. The software can be donwloaded from OTN.
Update: I just noticed neither Clusterware (aka “RAC”) nor ASM are available for 32-bit Windows.
Oracle 10g introduced the SGA_TARGET and SGA_MAX_SIZE parameter which dynamically resized many SGA components on demand. With 11g Oracle developed this feature further to include the PGA as well – the feature is now called “Automatic Memory Management” (AMM) which is enabled by setting the parameter MEMORY_TARGET.
Automatic Memory Management makes use of the SHMFS – a pseudo file system just like /proc. Every file created in the SHMFS is created in memory.
Unfortunately using MEMORY_TARGET or MEMORY_MAX_SIZE together with Huge Pages is not supported. You have to choose either Automatic Memory Management or HugePages. In this post i´d like to discuss AMM and Huge Pages.
Read more…
