1503653.1 - should change the comptability to 11.0.0 from 10.2.0.5 before manuelly upgrade?

Question

hi All,
i am trying to follow through the steps.
I will be porting the data from the old box into a new box ( windows 12.1.0.2.0)
I run the pre- tools script -> preupgrd.sql
it give me error or some warning to fix before doing the upgrade.
My question is , before i port over the data via a cold backup, should i first change the compatability to 11.0.0 from 10.2.0.5.0 (source db) then do a cold backup then port over the data to the new box then do the upgrade steps?
of course i can change the init.ora process to 300. As for the rest of the warning, i am not too sure is it necessary for me to do it since i will moving to a new box. Warning likes, EM database control, etc
                         [Update parameters]
         [Update Oracle Database 10.2.0.5.0 init.ora or spfile]
--> If Target Oracle is 32-bit, refer here for Update Parameters:
WARNING: --> "processes" needs to be increased to at least 300
--> If Target Oracle is 64-bit, refer here for Update Parameters:
WARNING: --> "sga_target" needs to be increased to at least 624951296
WARNING: --> "processes" needs to be increased to at least 300
                          [Renamed Parameters]
                     [No Renamed Parameters in use]
                    [Obsolete/Deprecated Parameters]
--> background_dump_dest         11.1       DESUPPORTED  replaced by  "diagnostic_dest"
--> user_dump_dest               11.1       DESUPPORTED  replaced by  "diagnostic_dest"
        [Changes required in Oracle Database init.ora or spfile]
                            [Component List]
--> Oracle Catalog Views                   [upgrade]  VALID    
--> Oracle Packages and Types              [upgrade]  VALID    
--> JServer JAVA Virtual Machine           [upgrade]  VALID    
--> Oracle XDK for Java                    [upgrade]  VALID    
--> Oracle Workspace Manager               [upgrade]  VALID    
--> OLAP Analytic Workspace                [upgrade]  VALID    
--> Oracle Enterprise Manager Repository   [upgrade]  VALID    
--> Oracle Text                            [upgrade]  VALID    
--> Oracle XML Database                    [upgrade]  VALID    
--> Oracle Java Packages                   [upgrade]  VALID    
--> Oracle Multimedia                      [upgrade]  VALID    
--> Oracle Spatial                         [upgrade]  VALID    
--> Data Mining                            [upgrade]  VALID    
--> Expression Filter                      [upgrade]  VALID    
--> Rule Manager                           [upgrade]  VALID    
--> Oracle OLAP API                        [upgrade]  VALID    
                              [Tablespaces]
--> SYSTEM tablespace is adequate for the upgrade.
     minimum required size: 1122 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
     minimum required size: 400 MB
--> SYSAUX tablespace is adequate for the upgrade.
     minimum required size: 619 MB
--> TEMP tablespace is adequate for the upgrade.
     minimum required size: 60 MB
--> EXAMPLE tablespace is adequate for the upgrade.
     minimum required size: 78 MB
                      [No adjustments recommended]
                          [Pre-Upgrade Checks]
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.
ERROR: --> Compatible set too low
     "compatible" currently set at 10.2.0.5.0 and must
     be set to at least 11.0.0 prior to upgrading the database.
     Do not make this change until you are ready to upgrade
     because a downgrade back to 10.2 is not possible once compatible
     has been raised.
     Update your init.ora or spfile to make this change.
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.
WARNING: --> "DMSYS" schema exists in the database
     The DMSYS schema (Oracle Data Mining) will be removed
     from the database during the database upgrade.
     All data in DMSYS will be preserved under the SYS schema.
     Refer to the Oracle Data Mining User's Guide for details.
WARNING: --> Database contains INVALID objects prior to upgrade
     The list of invalid SYS/SYSTEM objects was written to
     registry$sys_inv_objs.
     The list of non-SYS/SYSTEM objects was written to
     registry$nonsys_inv_objs unless there were over 5000.
     Use utluiobj.sql after the upgrade to identify any new invalid
     objects due to the upgrade.
INFORMATION: --> OLAP Catalog(AMD) exists in database
     Starting with Oracle Database 12c, OLAP Catalog component is desupported.
     If you are not using the OLAP Catalog component and want
     to remove it, then execute the
     ORACLE_HOME/olap/admin/catnoamd.sql script before or
     after the upgrade.
INFORMATION: --> Older Timezone in use
     Database is using a time zone file older than version 18.
     After the upgrade, it is recommended that DBMS_DST package
     be used to upgrade the 10.2.0.5.0 database time zone version
     to the latest version which comes with the new release.
     Please refer to My Oracle Support note number 1509653.1 for details.
WARNING: --> Existing schemas with network ACLs exist
     Database contains schemas with objects dependent on network packages.
     Refer to the Upgrade Guide for instructions to configure Network ACLs.
INFORMATION: --> There are existing Oracle components that will NOT be
     upgraded by the database upgrade script.  Typically, such components
     have their own upgrade scripts, are deprecated, or obsolete.
     Those components are:  OLAP Catalog

Answer 1

Not something I've done before but it seems that setting the parameter to 11.0.0 is a pre-requisite.
http://docs.oracle.com/database/121/UPGRD/intro.htm#BHCJHGFA
A full backup isn't neccessary specifically for this upgrade.  Just port your data over, change the compatibile parameter on the spfile/pfile on your target upgrade host and upgrade away.
Your source will be your backup so I would be inclined not to change things on there.
You can ignore some of the warning like EM dbcontrol as it states you can do it manually prior to the upgrade to save time, otherwise it will be done as part of the upgrade process anyway.
Other warnings like. OLAP and the timezone file (timezone is a recommendation) you will need to pay attention to and action, as well as the network ACL warning:
http://docs.oracle.com/database/121/UPGRD/preup.htm#BABEDAFB
http://docs.oracle.com/database/121/UPGRD/preup.htm#BABJGCIC