Tuesday, March 8, 2011

Identify Your Oracle Database Software Release



To understand the release nomenclature used by Oracle, examine the following example of an Oracle Database server labeled "Release 10.1.0.1.0".
Oracle Database continues to evolve and can require maintenance, Oracle periodically produces new releases. Not all customers initially subscribe to a new release or require specific maintenance for their existing release. As a result, multiple releases of the product exist simultaneously.As many as five numbers may be required to fully identify a release. The significance of these numbers is

Release Number Format
                      
Note:
Starting with release 9.2, maintenance releases of Oracle Database are denoted by a change to the second digit of a release number. In previous releases, the third digit indicated a particular maintenance release.
Major Database Release Number :  The first digit is the most general identifier. It represents a major new version of the software that contains significant new functionality.
Database Maintenance Release Number :  The second digit represents a maintenance release level. Some new features may also be included.
Application Server Release Number :  The third digit reflects the release level of the Oracle Application Server (OracleAS) .

Component-Specific Release Number : The fourth digit identifies a release level specific to a component. Different components can have different numbers in this position depending upon, for example, component patch sets or interim releases.

Platform-Specific Release Number :  The fifth digit identifies a platform-specific release. Usually this is a patch set. When different platforms require the equivalent patch set, this digit will be the same across the affected platforms.

Checking The Current Release Number :  To identify the release of Oracle Database that is currently installed and to see the release levels of other database components we are using, query the data dictionary view product_component_version. A sample query follows.(We can also query the v$version view to see component-level information.) Other product release levels may increment independent of the database server.

SQL> select * from product_component_version;
PRODUCT                                                  VERSION     STATUS
--------------------------                         -----------  -----------
NLSRTL                                                     10.2.0.1.0   Production
Oracle Database 10g Enterprise Edition           10.2.0.1.0   Production
PL/SQL                                                     10.2.0.1.0   Production

It is important to convey to Oracle the results of this query when we report problems with the software .




Enjoy          J J J



4 comments:

pavan thota said...

Hi Neeraj,

I am learning dba now so i have a question regarding on this,When we apply psu patch or cpu patch it will update version or not.If update means which number(digit) will update.Please clarify this doubt.

pavan thota said...

Hi Neeraj,

I am learning dba now so i have a question regarding on this,When we apply psu patch or cpu patch it will update version or not.If update means which number(digit) will update.Please clarify this doubt.

NEERAJ VISHEN said...

Hi pavan ,

Today , i saw ur comments ... sorry for late reply ...

All PSUs are denoted by the last digit - 10.2.0.4.1, 10.2.0.4.2 etc. When we apply PSU patches it updates the version . for example if we have any existing version 11.2.0.1.0 and when we go for psu patching, then it version will be changed to 11.2.0.1.1 .

For More about patching read the below link .

http://neeraj-dba.blogspot.in/2013/07/what-are-patches-and-how-to-apply.html

Hope this may help you :-)

Anonymous said...

It is quite difficult and controversial issues within the provide stipulated time?
Take your new home or even to moderate wind.

In early 2010, from $73 million, according to the house, sloped enough to take care of this guide.


Feel free to surf to my blog - homepage ()