What is the meaning of database version in Oracle


What is the meaning of database version in Oracle?

When I say that I have installed Oracle database 11.2.0.2.0, what actually is this 11.2.0.2.0

Let’s see what all this is about:

Oracle database software has a version number. Say our database version is 11.2.0.2.0

11.2.0.2.0: The first digit is the major release number.  When we say 9i, 10g or 11g we mean the major release number.

11.2.0.2.0: This second digit is the maintenance release number. This is usually called only "release". For example when you say 11g Release 1 or 11g Release 2 in fact you are mentioning maintenance release number. Maintenance releases are full installations. It means that all files are replaced during upgrade. Maintenance releases contain bug fixes and new features for database.

11.2.0.2.0: This third digit is the release number for Oracle application servers. For database software, it should be 0.

11.2.0.2.0: The fourth digit is called component specific release number. It shows the patch set version that has been applied to database. As of 11g, the patch sets are now full installations. They contain bug fixes and add new features to database. However the number of new features is not as high as maintenance releases. Its scope is limited. The bugs fixed by patch sets are not listed in patch inventory.

11.2.0.2.0: The last digit is called platform specific release number. Patch set updates use this fifth number. A patch set update (PSU) is a collection of patches distributed 4 times a year by Oracle (every 3 months). They contain patches for most common bugs and security holes. They don't add a new feature to database. They are not full installations. Only faulty files on your database are replaced. Oracle recommends installing patch sets even if you haven't hit any of the bugs fixed in those patch sets.

Comments

Post a Comment

Back To Top

Popular posts from this blog

How to save video from Internet Explorer

error 18 at 0 depth lookup: self signed certificate

How to check fragmentation in MySQL tables