Monthly Archives: Январь 2012

To be or not to be?… Standard Edition or Standard Edition One?

From time to time we all meet the need to determine the edition of installed Oracle Database software.

In case of Enterprise Edition it is very simple:

SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production

But in case of Standard Edition or Standard Edition One we can’t be sure. Previous select returns the same result for both editions:

SQL> select * from v$version;   
BANNER 
-------------------------------------------------------------------------------- 
Oracle Database 11g Release 11.2.0.1.0 - 64bit Production

So there is another way to determine the exact edition type installed.

We need to find install log. In Windows by default they are located under ‘C:\Program Files\Oracle\Inventory\logs’. Search for following string: ‘- Database edition’ and you’ll catch the ball:

- Disk space : required 3,29 GB available 169,15 GB
- Source location : C:\Distr\oracle\11g\win 64\database\install\..\stage\products.xml
- Install method : Typical installation
- Database edition : Standard Edition (Install database software only)
- Oracle base : C:\Tools\Oracle\product
- Software location : C:\Tools\Oracle\product\11.2.0\dbhome_1

Or:

- Disk space : required 3,29 GB available 168,75 GB
- Source location : C:\Distr\oracle\11g\win 64\database\install\..\stage\products.xml
- Install method : Typical installation
- Database edition : Standard Edition One (Install database software only)
- Oracle base : C:\Tools\Oracle\product
- Software location : C:\Tools\Oracle\product\11.2.0\db_home

‘COMPATIBLE’… Confusing minds parameter.

Compatible.. What is compatible with what?

Setting COMPATIBLE=’10.0.0′ in Oracle 11g seems promising for 10g developers. Some of them could think ‘I don’t need to modify my code to migrate to 11g’.

But the purpose of this parameter is completely different. It makes Oracle to create and operate with file structures as different version. And the only thing someone can do is to upgrade or downgrade an Oracle version. I don’t think someone would downgrade, but upgrade procedure I’ll describe a little bit later.

‘COMPATIBLE’ is a static parameter. Setting COMPATIBLE=’10.0.0′  in previously created 11g DB will cause an error:

Connected to:
 Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
 With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> alter system set compatible='10.2.0' scope=spfile;
System altered.
SQL> shutdown immediate;
 Database closed.
 Database dismounted.
 ORACLE instance shut down.
SQL> startup mount
 ORACLE instance started.
 Total System Global Area 810053632 bytes
 Fixed Size 2180104 bytes
 Variable Size 490736632 bytes
 Database Buffers 310378496 bytes
 Redo Buffers 6758400 bytes
 ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version 10.2.0.0.0
 ORA-00202: control file: 'C:\TOOLS\ORACLE\PRODUCT\ORADATA\ORCL11G\CONTROL01.CTL'

Recreating a controlfile will cause another error — wrong version of SYSTEM01.DBF.

What Is Compatibility for Oracle Database?

To be continued

1. Introduction

Hello!

I started this blog not from the very beginning of my carrier as an Oracle DBA.

Long time ago, about 6 years to be honest, I’d started to work with an Oracle Database. That were first weak steps.  Now I have passed the first certification exam out of 3 for OCP 10g and want to go further.

Nikolay.

%d такие блоггеры, как: