If you are using a Standard Edition database (Release prior to 11gR1), then you can change it to an Enterprise Edition database.
Step 1
Standard Edition database software should be same as the Enterprise Edition database software.
Step 2
Shutdown the database
Step 3
Shut down your all oracle services including oracle database
Step 4
De-install the Standard Edition oracle software
Step 5
Install the Enterprise Edition server software using the Oracle Universal Installer.
Step 6
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.
Step 7
Start up your database.
Your database is now upgraded to the Enterprise Edition.
Tips:
- You can only convert Standard Edition Database to the Enterprise Edition Database by using above method.
- If you want to convert from an Enterprise Edition database to a Standard Edition database, you must use Export/Import operation. Without Export/Import you can not convert.
Inside Story:
- The Enterprise Edition contains data dictionary objects which are not available in the Standard Edition. If you just install the Standard Edition software, then you will end up with data dictionary objects which are useless. Some of them might be invalid and possibly create problems when maintaining the database.
- The Export/Import operation does not introduce data dictionary objects specific to the Enterprise Edition, because the SYS schema objects are not exported. Oracle recommends using the Standard Edition EXP utility to export the data.
- After the Import in the Standard Edition database, you are only required to drop all user schemas related to Enterprise Edition features, such as the MDSYS account used with Oracle Spatial.
———————OR——————————
Recently I needed to change a standard edition database to Enterprise Edition. Here are the steps I followed from documentation
Since the same “SQL.BSQ” script is used to create the database for each version, the databases are internally almost identical. The conversion process is therefore not very complicated.
The following steps need to be taken to convert your SE database to an EE:
Backup the database
De-install the SE software
Install the EE software (optionally on Unix in a new ORACLE_HOME)
If you have an existing database, point your ORACLE_SID to this pre-existing database
Startup the database
Run the “catalog.sql” and “catproc.sql” scripts, as usual.
Your database is now using the Enterprise Edition (EE) version of the software.
Ensure that the release number of your Standard Edition server software is the same release as the Enterprise Edition server software.
For example, if Standard Edition server software is release 9.2.0.1.0, then you have to use release 9.2.0.1.0 of the Enterprise Edition.
For the subsequent patch set levels, it may be better to replace point number 5 & 6 with the following points
- Startup the database in migrate/upgrade mode
- Run the catupgrd.sql script of the current patch set level?
——————————————–OR———————————————————-
How to Convert Database from Standard to Enterprise Edition
APRIL 25, 2013 LEAVE A COMMENT
You are using a Standard Edition (SE) database and want to convert it to the Enterprise Edition (EE) because functionality you require is not part of the SE.
The following steps need to be taken to convert your SE database to an EE:
- Backup the database.
Make a backup copy of files under $Oracle_Home/network/admin. This ensures that the listener is configured after you complete the steps in this procedure.
Back up all database files under the current Oracle home that you need to keep.
On Linux, back up $Oracle_Home/dbs/.
On Windows, back up $Oracle_Home/database/. - De-install the SE software (note that this step is not essential to the conversion as such)
- Install the EE software (optionally in a new ORACLE_HOME)
- If you have an existing database, point your ORACLE_SID to this pre-existing database
- Startup the database
- Run the ìcatalog.sqlî and ìcatproc.sqlî scripts
(the execution of these two scripts may be not mandatory in all the cases but better to run them because of complexity of data dictionary and to be sure that all EE objects are created) - Recompile all invalid objects in the database by executing utlrp.sql script. You can execute this script 2-3 times to validate the dependencies.
Your database is now using the Enterprise Edition (EE) version of the software.
NOTE:
Since Oracle 11.2, the installer offers next to the Enterprise Edition (EE) and the Standard Edition (SE) also a Standard Edition One (SE1).
The same method as described can be used to convert SE1 to EE.
Because SE has all the features of SE1 but allows for RAC like EE (refer to Note 1084132.1), the same method should also be applicable for converting SE1 to SE.
For the subsequent patch set levels
Replace the steps: - Startup the database
- Run the ìcatalog.sqlî and ìcatproc.sqlî scripts, as usual.
with: - Startup the database in migrate/upgrade mode
- Run the catpatch.sql/catupgrd.sql script of the current patch set level
Please refer to the actual patch set readme
If you are using a Windows OS:
If you have an existing database the DB Service will have to be re-created once the Software is re-installed (via ORADIM).
If a backup of the database is taken and then the Software is de-installed, the service gets removed. It will need to be re-created once the new software is installed or you wonít be able to connect to the database.
