Oracle 10g Enterprise Edition vs. Standard Edition – feature matrix
How many times did you find yourself looking whether a certain feature is part of Oracle Standard Edition or it requires an Enterprise license?
I used to find myself in that situation quite often. I know there is a feature matrix somewhere but every time I end up looking for it over and over again. Worse yet – often I can’t even recall that magic combination of keywords leading to the page I need.
As it always happens, I find something by a chance when I don’t need it. Today is no different but this time I’m posting the reference in the blog so that me and anyone else can use this magic link – Metalink Note 271886.1 Differences Between Different Editions of Oracle Database 10G.
It includes all version of Oracle 10g databases:
-
Standard Edition One
-
Standard Edition
-
Enterprise Edition
-
Personal Edition
The first part of the document lists options available for EE. They are actually included into Personal Edition as well with few exceptions. Note that these option must be licensed separately in addition to an Enterprise Edition license. As usual – your salesman will be happy to take your call. ;-)
More interesting is the second part of the document with the feature matrix. This note rocks!
PS: Funny one – the feature matrix in the note says that “Backup and recovery” is not available for Standard and Standard One Editions so you won’t be able to have a backup with SE. ;-) OK, OK – read the comments there. ;-)
Update 02-Nov-2006:
Here is another good reference – Oracle Database Licensing Information 10g Release 2. This document includes Express Edition as well.
In the first chapter, you find detailed description of five editions, feature matrix, special cases (such as RAC with SE), CRS licensing, “Processor” definition and ratings and much more. For example, did you know that you don’t need a separate license for a database dedicated to an RMAN repository?
Chapter 2 covers separately licensed database options as well as management packs. Noticed one funny fragment there in description of Oracle Change Management Pack – “The Change Management Pack includes the following features: … Update database object definitions (ALTER TABLE) …”. Have you ever run ALTER TABLE on your database? ;)
So now, dear reader, we hope we have helped you figure out something you needed to know. It turns out that you can help us here at Pythian with something we need to know! If you are aware of a DBA requirement within your organization, salaried or consulting, please pop in your email address here:
We respect your privacy and will not share your address with any third party. As a thank you for just participating, we will enter you into a monthly draw for a year’s membership in the ACM, which includes access to 600 books from the O’Reilly Bookshelf Online, 500 books from Books24×7 and 3000 online courses from SkillSoft, including tons of courseware on Oracle, SQL Server, and MySQL.
Category: Group Blog Posts
Tags:
given that I am on Std edition – I think it kind of works like Murphy’s law – any and every good feature we would need is either not licensed with Std Edition or not a part of the Std edition install.
Well, you should look at it this way – the fewer fancy features you use the less chances you have to get in trouble – hit a bug, misconfigure something, etc. Be optimistic!
I’m doing some research for a bank who doesn’t see why they need to spend 800 per user per proc core for EE when they could spend 300 for SE. Can they mix? That is, can they use EE in production and SE in the dissater recovery site. They will need to replicate or pass updates at the end of each day from production to dr. Manually is ok. Thoughts? Thanks,
A bit late for the follow up but a proper DR solution must have the same hardware and software so I wouldn’t even think about it.
I am switching from Oracle 10g EE to SE.
What measures i should take to ensure the integrity of my data?
Will i need to re-create all the tablespace, schemas/users
afresh while importing my EE database dump to SE database?
pratap,
In general you would need to make sure you don’t have any objects and features that are not supported in SE. Also, I would recommend to verify that you don’t carry along the internal schemas that are part of certain EE options. The world won’t brake if you do take them over to SE but it will be just a garbage in your new DB.
Obviously, test, test and test.
I am developing central database for a organization using Oracle 10g standard edition. I want to implement c2 audit in this. How it can be done?
And I need to use Oracle 10g Express Edition for staging database. I need to keep it in sync with central database(both the database are not connected). How can it be done?
Thanks.
Sharad, your requirements are pretty broad and I’m not sure it has a lot to do with this blog post. If you have already the architecture in mind and need to clarify support for certain features, let me know.
There are plenty of ways for for replicating the data. C2 Audit project seems to be quite demanding and I’m not sure Oracle XE is up to the job in this case — Oracle doesn’t release any patchsets for XE or security patches.
Thanks Alex.
What can be the possible ways to sync a database(express edition) with the database having standard edition?
I need to develop a DWH using SE, I would like to know the features I can use and the ones I can´t.
I mean, bitmap indexes, materialized views and so on.
Hi,
I have imported one of dump (having 80GB) from oracle 10g EE to SE using impdp. But in SE one of query is taking too much time. In there query there is VARCHAR2 column comparsion between two tables, in one table the column is PK and in another table its indexed column. Could you please any body suggest what might be the reason? Why its not taking much time in EE where as its taking too much execution time in SE? Is there any versison differces?
Thanks
Ramana
@Ramana:
I will not reply to your question directly because of this — http://www.BattleAgainstAnyGuess.com.
There might be lots of reasons for that and most likely it has nothing to do with differences between SE and EE.