Database Upgradation from oracle 9.2.0.8 to oracle11gR2

Question

Hi
we are using AIX 5.3 TL 10 SP4 and we are upgrading DB from oracle9.2.0.8 to oracle 11.2.0.2
i am having some doubt from below pre-upgrade scripts out put.
oratst@ebsdevdb on /tmp # sqlplus "/as sysdba"
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Jul 4 10:11:48 2011
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL> spool 11202_upgrade.txt
SQL> @utlu112i.sql
Oracle Database 11.2 Pre-Upgrade Information Tool 07-04-2011 10:17:06
Script Version: 11.2.0.2.0 Build: 001
Database:
--> name: EBSTEST
--> version: 9.2.0.8.0
--> compatible: 9.2.0
--> blocksize: 8192
--> timezone file: V1
Logfiles: [make adjustments in the current environment]
--> The existing log files are adequate. No changes are required.
Tablespaces: [make adjustments in the current environment]
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 8546 MB
--> TOOLS tablespace is adequate for the upgrade.
.... minimum required size: 8 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
--> AR_TABLE tablespace is adequate for the upgrade.
.... minimum required size: 33497 MB
--> FND_TABLE tablespace is adequate for the upgrade.
.... minimum required size: 45447 MB
--> AMVD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> ASOD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> CCTD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> IBUD tablespace is adequate for the upgrade.
.... minimum required size: 1 MB
--> IEMD tablespace is adequate for the upgrade.
.... minimum required size: 5 MB
--> IEOD tablespace is adequate for the upgrade.
.... minimum required size: 4 MB
--> JTFD tablespace is adequate for the upgrade.
.... minimum required size: 135 MB
--> OKCD tablespace is adequate for the upgrade.
.... minimum required size: 34 MB
--> XDPD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> XNPD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> APPS_UNDOTS1 tablespace is adequate for the upgrade.
.... minimum required size: 849 MB
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:
WARNING: --> "compatible" must be set to at least 10.1.0
--> If Target Oracle is 64-Bit, refer here for Update Parameters:
WARNING: --> "compatible" must be set to at least 10.1.0
WARNING: --> "shared_pool_size" needs to be increased to at least 532 MB
WARNING: --> "java_pool_size" needs to be increased to at least 128 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]
--> optimizer_max_permutations 10.1 OBSOLETE
--> row_locking 10.1 OBSOLETE
--> undo_suppress_errors 10.1 OBSOLETE
--> max_enabled_roles 10.1 DEPRECATED
--> enqueue_resources 10.2 OBSOLETE
--> sql_trace 10.2 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
--> JServer JAVA Virtual Machine [upgrade] VALID
--> Oracle XDK for Java [upgrade] VALID
--> Real Application Clusters [upgrade] INVALID
--> Oracle Text [upgrade] VALID
--> Oracle XML Database [install]
--> Oracle Java Packages [upgrade] VALID
--> Oracle interMedia [upgrade] VALID
--> Spatial [upgrade] VALID
Miscellaneous Warnings
WARNING: --> Passwords exist in some database links.
.... Passwords will be encrypted during the upgrade.
.... Downgrade of database links with passwords is not supported.
WARNING: --> Deprecated CONNECT role granted to some user/roles.
.... CONNECT role after upgrade has only CREATE SESSION privilege.
WARNING: --> Database is using a timezone file older than version 14.
.... After the release migration, it is recommended that DBMS_DST package
.... be used to upgrade the 9.2.0.8.0 database timezone version
.... to the latest version which comes with the new release.
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.
.... Use utluiobj.sql after the upgrade to identify any new invalid
.... objects due to the upgrade.
.... USER ADWANIAH has 1 INVALID objects.
.... USER APPS has 34 INVALID objects.
.... USER CHAKKACHANSA has 1 INVALID objects.
.... USER FA_USER has 9 INVALID objects.
.... USER SYSSEL has 2 INVALID objects.
.... USER SYSTEM has 30 INVALID objects.
.... USER XXITDFINAD has 7 INVALID objects.
WARNING: --> SYSTEM schema default tablespace has been altered.
.... The SYSTEM schema default tablespace is currently set to TOOLS.
.... Prior to upgrading your database please reset the
.... SYSTEM schema default tablespace to SYSTEM using the command:
.... ALTER USER SYSTEM DEFAULT TABLESPACE SYSTEM;
WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER APPS has dependent objects.
Recommendations
Oracle recommends gathering dictionary statistics prior to
upgrading the database.
To gather dictionary statistics execute the following commands
while connected as SYSDBA:
EXECUTE dbms_stats.gather_schema_stats('CTXSYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('DBSNMP',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('MDSYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('ORDPLUGINS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('ORDSYS',options=>'GATHER'
estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('OUTLN',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('SYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('SYSTEM',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
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.
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.
SYSAUX Tablespace:
[Create tablespace in the Oracle Database 11.2 environment]
--> New "SYSAUX" tablespace
.... minimum required size for database upgrade: 500 MB
From above output script
1)SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 8546 MB
From system tablespace minimum required size means free space from system tablespace or total size of system tablespace?
i am going to use dbua utility for upgrade means does it alter tablespace as per output of scripts or we need to manually alter tablespace size as per requirement?
2)WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER APPS has dependent objects.
what is above warning and how can i configure ACL's for APPS User?
Thanks
With Regards
A-Z

Answer 1

Hi
oratst@ebsdevdb on /ebdbh/11g/data/cfgtoollogs/dbua/ebstest/upgrade1 # more Upgrade_Directive.log
Connected.
ODMA_DIRECTIVE:VERSION:9.2.0.8
ODMA_DIRECTIVE:MIGRATE_SID:
ODMA_DIRECTIVE:ORA:IGNORE:06512:
ODMA_DIRECTIVE:ORA:FATAL:00600:
ODMA_DIRECTIVE:ORA:FATAL:01012:
ODMA_DIRECTIVE:ORA:FATAL:01031:
ODMA_DIRECTIVE:ORA:FATAL:01034:
ODMA_DIRECTIVE:ORA:FATAL:01078:
ODMA_DIRECTIVE:ORA:FATAL:01092:
ODMA_DIRECTIVE:ORA:FATAL:01109:
ODMA_DIRECTIVE:ORA:FATAL:01119:
ODMA_DIRECTIVE:ORA:FATAL:01507:
ODMA_DIRECTIVE:ORA:FATAL:01722:
ODMA_DIRECTIVE:ORA:FATAL:03113:
ODMA_DIRECTIVE:ORA:FATAL:03114:
ODMA_DIRECTIVE:ORA:FATAL:07445:
ODMA_DIRECTIVE:ORA:FATAL:12560:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01650:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01651:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01652:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01653:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01654:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01655:
ODMA_DIRECTIVE:ORA:RECOVER_ROLL:01562:
ODMA_DIRECTIVE:ORA:RECOVER_INIT:04031:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:rdbms/admin/catupgrd.sql:
ODMA_DIRECTIVE:BOUNCE_DATABASE:UPGRADE:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:rdbms/admin/catuppst.sql:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:sqlplus/admin/help/hlpbld.sql helpus.sql:
Thanks
With Regards
A-Z