Oracle Upgrade -- Pre-Upgrade 10.2.0.4 to 11.2.0.1

Question

Hello,
I want to do an Oracle Upgrade to version 11.2g!
At this point I did some things (in Windows Server 2003 X64):
1-) Install Oracle 10.2.0.1 (DVD Media);
2-) Installation of Oracle patchset 10.2.0.4 (note 871735);
3-) Installation of interim / last generics patch (note 1137346);
4-) Installation of SAP ECC 6.0 SR3 by SAPInst
5-) After SAP installation I did all the corrections in Oracle parameters as it mentioned in note 830576.
As you see above, all the SAP system was well installed!
But now I want to do the Oracle Upgrade process to the last version, Oracle DB 11.2g  (11.2.0.1)... and so I´m following the Upgrade guide "Upgrade to Oracle Database 11g Release 2 (11.2) Windows.pdf" with some SAP notes for Upgrade process.
So I´m at this point in planning chapter where is recommended to check so things in actual database, one of this checks are running some SQL-scripts to perform an Oracle database upgrade with DBUA to release 11.2 (as mentioned in note 1431793 - Oracle 11.2.0: Upgrade Scripts)
I ran two Pre-Scripts, the @pre_upgrade_status.sql and @pre_upgrade_tasks.sql but both outputs showed some warnings and they are worrying me... so what I ask to you is some kind of help in analyse of them and tell me if this issues are relevant for the upgrading process and if so, what you recommend me to do to correct their!
Next I will post here this two log scripts... they are long!!!

Answer 1

PRE_UPGRADE_TASKS.log:
SQL> @pre_upgrade_tasks.sql
PRE-UPGRADE Tasks: === START ===
2010-08-05 18:24:13                                                                               
Recompiling invalid objects
This reduces the number of invalid objects as much as possible.
COMP_TIMESTAMP UTLRP_BGN  2010-08-05 18:24:13                                                      
DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC>   objects in the database. Recompilation time is proportional to the
DOC>   number of invalid objects in the database, so this command may take
DOC>   a long time to execute on a database with a large number of invalid
DOC>   objects.
DOC>
DOC>   Use the following queries to track recompilation progress:
DOC>
DOC>   1. Query returning the number of invalid objects remaining. This
DOC>       number should decrease with time.
DOC>          SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC>   2. Query returning the number of objects compiled so far. This number
DOC>       should increase with time.
DOC>          SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC>   This script automatically chooses serial or parallel recompilation
DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC>   On RAC, this number is added across all RAC nodes.
DOC>
DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC>   recompilation. Jobs are created without instance affinity so that they
DOC>   can migrate across RAC nodes. Use the following queries to verify
DOC>   whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC>   1. Query showing jobs created by UTL_RECOMP
DOC>          SELECT job_name FROM dba_scheduler_jobs
DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC>   2. Query showing UTL_RECOMP jobs that are running
DOC>          SELECT job_name FROM dba_scheduler_running_jobs
DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
COMP_TIMESTAMP UTLRP_END  2010-08-05 18:24:15                                                      
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
                  0                                                                               
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#
                          0                                                                        
Purging Recyclebin
This reduces the time needed for upgrading the database.
Truncating SYS.AUD$
This reduces the time needed for upgrading the database.
Gathering Oracle Dictionary Statistics
This reduces the time needed for upgrading the database.
Running Pre-Upgrade-Information Tool utlu112i.sql
This is a mandatory task for manual database upgrades.
This tool is also run in pre_upgrade_status.sql.
Oracle Database 11.2 Pre-Upgrade Information Tool 08-05-2010 18:24:45                              
Script Version: 11.2.0.1.0 Build: 003                                                              
Database:                                                                               
--> name:          PRD                                                                             
--> version:       10.2.0.4.0                                                                      
--> compatible:    10.2.0                                                                          
--> blocksize:     8192                                                                            
--> platform:      Microsoft Windows x86 64-bit                                                    
--> timezone file: V4                                                                               
Tablespaces: [make adjustments in the current environment]                                         
--> SYSTEM tablespace is adequate for the upgrade.                                                 
.... minimum required size: 905 MB                                                                 
--> PSAPUNDO tablespace is adequate for the upgrade.                                               
.... minimum required size: 84 MB                                                                  
--> SYSAUX tablespace is adequate for the upgrade.                                                 
.... minimum required size: 210 MB                                                                 
--> PSAPTEMP tablespace is adequate for the upgrade.                                               
.... minimum required size: 61 MB                                                                  
Flashback: OFF                                                                               
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]                                
Note: Pre-upgrade tool was run on a lower version 64-bit database.                                 
--> If Target Oracle is 32-Bit, refer here for Update Parameters:                                  
-- No update parameter changes are required.                                                       
--> If Target Oracle is 64-Bit, refer here for Update Parameters:                                  
WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB                           
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]                               
-- No renamed parameters found. No changes are required.                                           
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]                   
--> remote_os_authent            11.1       DEPRECATED                                             
--> background_dump_dest         11.1       DEPRECATED   replaced by  "diagnostic_dest"            
--> user_dump_dest               11.1       DEPRECATED   replaced by  "diagnostic_dest"            
Components: [The following database components will be upgraded or installed]                      
--> Oracle Catalog Views         [upgrade]  VALID                                                  
--> Oracle Packages and Types    [upgrade]  VALID                                                  
Miscellaneous Warnings                                                                             
WARNING: --> Database is using a timezone file older than version 11.                              
.... After the release migration, it is recommended that DBMS_DST package                          
.... be used to upgrade the 10.2.0.4.0 database timezone version                                   
.... to the latest version which comes with the new release.                                       
Recommendations                                                                               
Oracle recommends gathering dictionary statistics prior to                                         
upgrading the database.                                                                            
To gather dictionary statistics execute the following command                                      
while connected as SYSDBA:                                                                               
EXECUTE dbms_stats.gather_dictionary_stats;                                                                               
Oracle recommends removing all hidden parameters prior to upgrading.                                                                               
To view existing hidden parameters execute the following command                                   
while connected AS SYSDBA:                                                                               
SELECT name,description from SYS.V$PARAMETER WHERE name                                        
        LIKE '\_%' ESCAPE '\'                                                                               
Changes will need to be made in the init.ora or spfile.                                                                               
Oracle recommends reviewing any defined events prior to upgrading.                                                                               
To view existing non-default events execute the following commands                                 
while connected AS SYSDBA:                                                                         
  Events:                                                                               
SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2                           
      WHERE  UPPER(name) ='EVENT' AND  isdefault='FALSE'                                                                               
Trace Events:                                                                               
SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2                           
      WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'                                                                               
Changes will need to be made in the init.ora or spfile.                                                                               
PRE-UPGRADE Tasks: === FINISHED ===
SQL> spool off