11gR2 to 12cR1 Upgrade


[oracle@testvm admin]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Wed Jul 3 15:47:41 2013

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


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options

SQL> @utlu121i.sql
DOC>############################################################################
DOC>
DOC>
DOC> Note that the new preupgrd.sql script replaces the utlu121i.sql script
DOC>  and earlier versions of the Pre-Upgrade Information Tool.
DOC>
DOC>  The Pre-Upgrade Information Tool, which now consists of preupgrd.sql
DOC>  and utluppkg.sql.
DOC>
DOC>  1. Make sure preupgrd.sql and utluppkg.sql (located in the admin
DOC>     directory of the new installation of Oracle Database 12.1) are
DOC>     accessible while connected to your source database, which is the
DOC>     database to be upgraded
DOC>
DOC>  2. Connect to your source database using an account with DBA privileges
DOC>      and execute the preupgrd.sql script.
DOC>
DOC>  For more information on the Pre-Upgrade Information Tool, see the
DOC>  Oracle Database Upgrade Guide.
DOC>
DOC>
DOC>############################################################################

SQL> @preupgrd.sql

Loading Pre-Upgrade Package...
Executing Pre-Upgrade Checks...
Pre-Upgrade Checks Complete.
************************************************************

Results of the checks are located at:
 /oracle/product/cfgtoollogs/test/preupgrade/preupgrade.log

Pre-Upgrade Fixup Script (run in source database environment):
 /oracle/product/cfgtoollogs/test/preupgrade/preupgrade_fixups.sql

Post-Upgrade Fixup Script (run shortly after upgrade):
 /oracle/product/cfgtoollogs/test/preupgrade/postupgrade_fixups.sql

      ************************************************************

         Fixup scripts must be reviewed prior to being executed.

      ************************************************************

      ************************************************************
                   ====>> USER ACTION REQUIRED  <<====
      ************************************************************

 The following are *** ERROR LEVEL CONDITIONS *** that must be addressed
                    prior to attempting your upgrade.
            Failure to do so will result in a failed upgrade.

           You MUST resolve the above errors prior to upgrade

      ************************************************************


SQL> @/oracle/product/cfgtoollogs/test/preupgrade/preupgrade_fixups.sql



Pre-Upgrade Fixup Script Generated on 2013-07-03 15:48:22  Version: 12.1.0.1 Build: 006
Beginning Pre-Upgrade Fixups...

**********************************************************************
Check Tag:     DEFAULT_PROCESS_COUNT
Check Summary: Verify min process count is not too low
Fix Summary:   Review and increase if needed, your PROCESSES value.
**********************************************************************
Fixup Returned Information:
WARNING: --> Process Count may be too low

     Database has a maximum process count of 150 which is lower than the
     default value of 300 for this release.
     You should update your processes value prior to the upgrade
     to a value of at least 300.
     For example:
        ALTER SYSTEM SET PROCESSES=300 SCOPE=SPFILE
     or update your init.ora file.
*****************************************************************


*****************************************************************
Check Tag:     EM_PRESENT
Check Summary: Check if Enterprise Manager is present
Fix Summary:   Execute emremove.sql prior to upgrade.
*****************************************************************
Fixup Returned Information:
WARNING: --> Enterprise Manager Database Control repository found in the database

     In Oracle Database 12c, Database Control is removed during
     the upgrade. To save time during the Upgrade, this action
     can be done prior to upgrading using the following steps after
     copying rdbms/admin/emremove.sql from the new Oracle home
   - Stop EM Database Control:
    $> emctl stop dbconsole

   - Connect to the Database using the SYS account AS SYSDBA:

   SET ECHO ON;
   SET SERVEROUTPUT ON;
   @emremove.sql
     Without the set echo and serveroutput commands you will not 
     be able to follow the progress of the script.
*****************************************************************


*****************************************************************
Check Tag:     DBMS_LDAP_DEPENDENCIES_EXIST
Check Summary: Check for dependency on DBMS_LDAP package
Fix Summary:   Network Objects must be reviewed manually.
*****************************************************************
Fixup Returned Information:
WARNING: --> Existing DBMS_LDAP dependent objects

     Database contains schemas with objects dependent on DBMS_LDAP package.
     Refer to the Upgrade Guide for instructions to configure Network ACLs.
     USER APEX_030200 has dependent objects.
*****************************************************************


*****************************************************************
Check Tag:     AMD_EXISTS
Check Summary: Check to see if AMD is present in the database
Fix Summary:   Manually execute ORACLE_HOME/oraolap/admin/catnoamd.sql script to remove OLAP.
*****************************************************************
Fixup Returned Information:
INFORMATION: --> OLAP Catalog(AMD) exists in database

     Starting with Oracle Database 12c, OLAP is desupported.
     If you are not using the OLAP Catalog component and want
     to remove it, then execute the 
     ORACLE_HOME/oraolap/admin/catnoamd.sql script before or 
     after the upgrade.
*****************************************************************


*****************************************************************
                      [Pre-Upgrade Recommendations]
*****************************************************************

                        *****************************************
                        ********* Dictionary Statistics *********
                        *****************************************

Please gather dictionary statistics 24 hours prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
    EXECUTE dbms_stats.gather_dictionary_stats;

^^^ MANUAL ACTION SUGGESTED ^^^


           **************************************************
                ************* Fixup Summary ************

 4 fixup routines generated INFORMATIONAL messages that should be reviewed.

**************** Pre-Upgrade Fixup Script Complete *********************

SQL> EXECUTE dbms_stats.gather_dictionary_stats;

SQL> exit



[oracle@testvm ~]$ . /oracle/product/db/12.1.0/dbhome/bin/oraenv

ORACLE_SID = [test] ? 
The Oracle base remains unchanged with value /oracle/product

[oracle@testvm ~]$ cd /oracle/product/db/12.1.0/dbhome/bin/

[oracle@testvm bin]$ ./dbua

















[oracle@testvm ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Thu Jul 4 11:38:44 2013

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


Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> select banner from v$version;

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

SQL> EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS

PL/SQL procedure successfully completed.


SQL> select count(*) from dba_objects where status like 'INVALID';

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

SQL> exit




Hi guys I'm having doubt in timezone of 12c. If you know kindly share your information and also post if any steps I missed.