This evaluation may include the performance of
specific database operations or the overall performance of the database under a significant user load.
Prior to executing the upgrade process on a production database, you should attempt the
upgrade on a test database so any missing components (such as operating system patches) can
be identified and the time required for the upgrade can be measured.
Oracle Database 11g includes the Pre-Upgrade Information Tool called utlu111i.sql. This tool
is included in the installation files in the directory $ORACLE_HOME/rdbms/admin. Copy this script
to a location accessible by the old database, connect to the old database with SYSDBA privileges,
and run this tool from a SQL*Plus session similar to the following:
SQL> spool upgrade_11g_info.txt
SQL> @utlu111i.sql
SQL> spool off
Review the file upgrade_11g_info.txt for adjustments you should make before performing the
actual upgrade; these adjustments include increasing the size of tablespaces, removing obsolete
initialization parameters, and revoking obsolete roles such as CONNECT. As of Oracle Database 11g,
the CONNECT role only contains the CREATE SESSION privilege. You need to grant permissions
to users with the CONNECT role before upgrading. Here is a query you can use to identify users
granted the CONNECT role:
SELECT grantee FROM dba_role_privs
WHERE granted_role = 'CONNECT' and grantee NOT IN (
'SYS', 'OUTLN', 'SYSTEM', 'CTXSYS', 'DBSNMP',
'LOGSTDBY_ADMINISTRATOR', 'ORDSYS',
'ORDPLUGINS', 'OEM_MONITOR', 'WKSYS', 'WKPROXY',
'WK_TEST', 'WKUSER', 'MDSYS', 'LBACSYS', 'DMSYS',
'WMSYS', 'OLAPDBA', 'OLAPSVR', 'OLAP_USER',
'OLAPSYS', 'EXFSYS', 'SYSMAN', 'MDDATA',
'SI_INFORMTN_SCHEMA', 'XDB', 'ODM');
Prior to performing a direct upgrade, you should analyze the data dictionary tables.
Pages:
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145