How to Move From the Standard Edition to the Enterprise Edition?

If you are using the Standard Edition of the Oracle Database and want to move to the Enterprise Edition, then complete the following steps:

Ensure that the release number of your Standard Edition server software is the same release as the Enterprise Edition server software.

For example, if your Standard Edition server software is release 12.1.0.2, then you should upgrade to release 12.1.0.2 of the Enterprise Edition.

  • Shut down your database.

If your operating system is Windows, then stop all Oracle services, including the OracleServiceSID Oracle service, where SID is the instance name.

  • Deinstall the Standard Edition server software.
  • Install the Enterprise Edition server software using the Oracle Universal Installer.
  • Select the same Oracle home that was used for the de-installed Standard Edition. During the installation, be sure to select the Enterprise Edition.
  • When prompted, choose Software Only from the Database Configuration screen.
  • Start up your database.

Your database is now upgraded to the Enterprise Edition.
You can verify it from the banner:

SQL> select banner from v$version;

BANNER
——————————————————————————–
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 – 64bit Production
PL/SQL Release 12.1.0.2.0 – Production
CORE 12.1.0.2.0 Production
TNS for Linux: Version 12.1.0.2.0 – Production
NLSRTL Version 12.1.0.2.0 – Production

Advertisements

11g R2 Upgrade Compatibility Matrix

I get a lot of questions these days about how to upgrade our database to 11g R2 .

One of the questions:

From which version of Oracle database to 11g R2  can we do upgrade directly?

You can upgrade directly to 11g R2 from the versions are as follows;

Source Database Target Database
9.2.0.8 or higher 11.2.x
10.1.0.5 or higher 11.2.x
10.2.0.2 or higher 11.2.x
11.1.0.6 or higher 11.2.x

You can not upgrade directly to 11g R2 from some versions . You need to do pre-upgrade for 11g R2 as follows:

Source Database Pre-Upgrade Version Target Database
7.3.3 or lower version 7.3.4 > 9.2.0.8 11.2.x
8.0.5 or lower version 8.0.6 > 9.2.0.8 11.2.x
8.1.7 or lower version 8.1.7.4 > 10.2.0.4 11.2.x
9.0.1.3 or lower version 9.0.1.4 >10.2.0.4 11.2.x
9.2.0.7 or lower version 9.2.0.8 11.2.x

I will wait for any questions about the upgrade to 11g R2.

Talip Hakan Öztürk

Oracle Software Patching Using OPatch – Interim Patches

OPatch is an Oracle utility that assists you to apply interim patches to Oracle’s rdbms software. You can find opatch utility in $ORACLE_HOME/Opatch directory. For example, let’s apply patch number 8943287  to our 10.2.0.5 database.

Applying Patch:

1- Backup Oracle Home directory.

$ tar -cf ora10g.tar ora10g

2- Download patch file p8943287_10205_Linux-x86-64.zip via metalink. And copy it to database server.

3- Unzip the patch file.

$ unzip p8943287_10205_Linux-x86-64.zip

4- Apply patch with opatch utility.

$ cd 8943287

$ ORACLE_HOME/OPatch/opatch apply

To see list of applied patches :

$ORACLE_HOME/OPatch/opatch lsinventory

For example:

$ORACLE_HOME/OPatch/opatch lsinventory

Invoking OPatch 10.2.0.4.9

Oracle Interim Patch Installer version 10.2.0.4.9

Copyright (c) 2009, Oracle Corporation. All rights reserved.

Oracle Home : /oracle/ora10g

Central Inventory : /oracle/oraInventory

from : /etc/oraInst.loc

OPatch version : 10.2.0.4.9

OUI version : 10.2.0.5.0

OUI location : /oracle/ora10g/oui

Log file location : /oracle/ora10g/cfgtoollogs/opatch/opatch2011-10-28_12-14-12PM.log

Patch history file: /oracle/ora10g/cfgtoollogs/opatch/opatch_history.txt

Lsinventory Output file location : /oracle/ora10g/cfgtoollogs/opatch/lsinv/lsinventory2011-10-28_12-14-12PM.txt

——————————————————————————–

Installed Top-level Products (3):

Oracle Database 10g 10.2.0.1.0

Oracle Database 10g Release 2 Patch Set 3 10.2.0.4.0

Oracle Database 10g Release 2 Patch Set 4 10.2.0.5.0

There are 3 products installed in this Oracle Home.

Interim patches (2) :

Patch 8943287 : applied on Fri Oct 21 20:39:46 EEST 2011

Unique Patch ID: 12722995

Created on 23 Aug 2010, 11:45:16 hrs PST8PDT

Bugs fixed:

8943287

——————————————————————————–

Rollback applied patch:

Sometimes a patch is applied to the system may need to take back because of its effect. In this case, rollback is performed as follows.

$ORACLE_HOME/OPatch/opatch rollback -id 8943287

Talip Hakan ÖZTÜRK

Applying 11.1.0.7 PSU (Patch Set Update) to 11.1.0.6 Database

11.1.0.7 PSU (Patch Set Update) to 11.1.0.6 Database
Pre – Applying checks
1- Take backup your Oracle Home directory
$ tar -cf ora11g.tar ora11g
2- Take full database backup
3- Download p6890831_111070_Linux-x86-64.zip file over Metalink
Applying PSU (patch set update)
1- The time_zone check is very important check. it needs to be made and you can check it with this query;
SQL>SELECT version FROM v$timezone_file;

If you are running anything other than version 4, check MetaLink document 568125.1

2- Shutdown the database
SQL>shutdown database
3- Stop the services
$ emctl stop dbconsole
$ lsnrctl stop
4- Unzip p6890831_111070_Linux-x86-64.zip installation file. Run OUI (Oracle Universal Installer) in terminal

$ unzip p6890831_111070_Linux-x86-64.zip
$ cd Disk1
$ ./runInstaller
On the welcome screen click “Next” button

5- Choose the name of oracle home and click “Next” button.

6- Uncheck “I wish to receive security updates via MetaLink” check box. If you want, you can configure this option after installation.

If you unchecked the check box, you will warned. Click “Yes” to continue.

7- After prerequisite checks you can start the installation.

8- After installation of rdbms PSU you must check permissions of newly created folders on operating system.
Now it is time of database upgrade

9- Pre-upgrade checks

SQL> STARTUP UPGRADE
SQL> SPOOL pre_upgrade_check.log
SQL> @?/rdbms/admin/utlu111i.sql
SQL> SPOOL OFF
Examine the pre_upgrade_check.log file. Examine tablespace sizes and database components status

10- Start database in upgrade mode and run the script catupgrd.sql

$ lsnrctl start
$ sqlplus / as sysdba
SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catupgrd.sql
SQL> SPOOL OFF
Examine the patch.log file. If there is error then you must solve the problem and rerun catupgrd.sql script.

11- If there is no error, shutdown database and startup normal.

SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP

12- Post-Upgrade checks

SQL> SPOOL post_upgrade_check.log
SQL> @?/rdbms/admin/utlu111s.sql
SQL> SPOOL OFF
Examine post_upgrade_check.log file.

13- After upgrading database, some objects will be invalid. For recompiling run the following script.

SQL> @?/rdbms/admin/utlrp.sql

14- Check the status of database components.

SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;

Talip Hakan ÖZTÜRK