Convert "10.2.0.4 SE+CPU" to "10.2.0.4 EE+CPU"

Wednesday, July 14, 2010

In this test case I will convert "Oracle 10.2.0.4 SE + CPU" to "Oracle 10.2.0.4 EE + CPU".

I’ve installed "Oracle 10.2.0.4 SE+CPU" on my test machine and created database for test purpose. Database resides on Linux 32bit operating system.


My steps:

1. Install Oracle 10.2.0.1 EE software to different location.
During software installation I will keep my database running and won’t touch 10.2.0.4 SE installation.

2. Upgrade 10.2.0.1 EE software to 10.2.0.4 version and apply CPU.

3. Shutdown database and listener + take cold backup.

4. Copy parameter file (init.ora/spfile.ora) from SE/dbs to EE/dbs.

5. Copy tnsnames.ora, listener.ora and sqlnet.ora from SE/network/admin to EE/network/admin.

6. Change ORACLE_HOME environment variable to point database to new EE home.

7. If necessary change /etc/oratab entries to point new EE home.

8. Startup database and listener.

9. Run the catalog.sql and catproc.sql scripts.

10. Run utlrp.sql to recompile invalid objects.

11. Later you can remove SE installation using OUI (if everything went OK).


Small checks:

SQL> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
PL/SQL Release 10.2.0.4.0 - Production
CORE    10.2.0.4.0      Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production

5 rows selected.

SQL> select count(*) from dba_objects where status<>'VALID';

 COUNT(*)
----------
        0

1 row selected.


Check Alert.log -> OK.


Maybe some steps are unnecessary or incorrect so if you have any suggestion or correction please leave it in a comment and I will add correction.

Thanks!


Share/Bookmark

4 comments:

  • Damir Vadas (aka Funky)

    What about dba_registry content?

    All is valid?

    Rg,
    Damir Vadas
    http://damir-vadas.blogspot.com

  • Marko Sutic

    It seems that everything is valid:


    SQL> select comp_name, version, status from dba_registry;

    COMP_NAME VERSION STATUS
    -------------------------------------------------- -------------------------------------------------- --------------------
    Spatial 10.2.0.4.0 VALID
    Oracle interMedia 10.2.0.4.0 VALID
    Oracle Enterprise Manager 10.2.0.4.0 VALID
    Oracle XML Database 10.2.0.4.0 VALID
    Oracle Text 10.2.0.4.0 VALID
    Oracle Expression Filter 10.2.0.4.0 VALID
    Oracle Rules Manager 10.2.0.4.0 VALID
    Oracle Workspace Manager 10.2.0.4.3 VALID
    Oracle Data Mining 10.2.0.4.0 VALID
    Oracle Database Catalog Views 10.2.0.4.0 VALID
    Oracle Database Packages and Types 10.2.0.4.0 VALID
    JServer JAVA Virtual Machine 10.2.0.4.0 VALID
    Oracle XDK 10.2.0.4.0 VALID
    Oracle Database Java Packages 10.2.0.4.0 VALID

    14 rows selected.

    Regards,
    Marko

  • Damir Vadas (aka Funky)

    Marko,

    When you connect through SQLPlus to that instance, what do you get?
    I.E:

    SQL*Plus: Release 10.2.0.1.0 - Production on Sri Kol 4 10:02:15 2010

    Copyright (c) 1982, 2005, Oracle. All rights reserved.


    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, Real Application Clusters, OLAP, Data Mining
    and Real Application Testing options

    SQL>

    This is also some prove about version...amateur but good enough.

    However still would not use this in production.
    Rg,
    Damir Vadas
    http://damir-vadas.blogspot.com/

  • Marko Sutic

    I get:

    $ sqlplus "/as sysdba"

    SQL*Plus: Release 10.2.0.4.0 - Production on Wed Aug 4 12:39:19 2010

    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.


    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options

    SQL>


    This is nice check to find out more information about client version also.

    Thx for comment ;)

    Enjoy!

  • Post a Comment