Using the Pre-Upgrade Information Tool

Nel documento Oracle® Database Upgrade Guide 10g (pagine 34-38)

The Pre-Upgrade Information Tool is a SQL script that ships with the new Oracle Database 10g release, and must be copied to and run from the environment of the database being upgraded. Complete the following steps to run the Pre-Upgrade Information Tool:

1. Log in to the system as the owner of the Oracle home directory of the new Oracle Database 10g release.

Note: If you use Oracle Label Security, you must perform a custom install because it is not part of the standard installation.

See Also:

"Run the Oracle Net Configuration Assistant" on page 3-11

"Upgrade the Database Using the Database Upgrade Assistant" on page 3-11

2. Copy the following file from the ORACLE_HOME/rdbms/admin directory of the new Oracle Database 10g release to a directory outside of the Oracle home, such as the temporary directory on your system:

utlu102i.sql

Make a note of the new location of this file.

3. Log in to the system as the owner of the Oracle home directory of the database to be upgraded.

4. Change to the directory outside of the Oracle home directory that you copied files to in Step 2.

5. Start SQL*Plus.

6. Connect to the database instance as a user with SYSDBA privileges.

7. Set the system to spool results to a log file for later analysis:

SQL> SPOOL info.log 8. Run utlu102i.sql:

SQL> @utlu102i.sql

9. Turn off the spooling of script results to the log file:

SQL> SPOOL OFF

Then, check the spool file and examine the output of the upgrade information tool.

You named the spool file in Step 7; the suggested name was info.log.

The following is an example of the output generated by the Pre-Upgrade Information Tool:

Oracle Database 10.2 Upgrade Information Utility 05-25-2005 05:19:08 .

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: 583 MB

.... AUTOEXTEND additional space required: 163 MB --> TEMP tablespace is adequate for the upgrade.

.... minimum required size: 58 MB

.... AUTOEXTEND additional space required: 38 MB --> CWMLITE tablespace is adequate for the upgrade.

.... minimum required size: 16 MB

--> DRSYS tablespace is adequate for the upgrade.

.... minimum required size: 27 MB

.... AUTOEXTEND additional space required: 7 MB

--> EXAMPLE tablespace is adequate for the upgrade.

.... minimum required size: 150 MB

.... AUTOEXTEND additional space required: 1 MB --> ODM tablespace is adequate for the upgrade.

.... minimum required size: 10 MB

--> XDB tablespace is adequate for the upgrade.

.... minimum required size: 48 MB

.... AUTOEXTEND additional space required: 3 MB --> SYSAUX tablespace is adequate for the upgrade.

.... minimum required size: 61 MB

.... AUTOEXTEND additional space required: 11 MB .

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

Update Parameters: [Update Oracle Database 10.2 init.ora or spfile]

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

WARNING: --> "shared_pool_size" needs to be increased to at least 178499994 WARNING: --> "java_pool_size" needs to be increased to at least 67108864

WARNING: --> "streams_pool_size" is not currently defined and needs a value of at least 50331648

WARNING: --> "session_max_open_files" needs to be increased to at least 20 .

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

Deprecated Parameters: [Update Oracle Database 10.2 init.ora or spfile]

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

-- No deprecated parameters found. No changes are required.

.

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

Obsolete Parameters: [Update Oracle Database 10.2 init.ora or spfile]

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

--> "hash_join_enabled"

--> "max_enabled_roles"

.

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

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

...The 'JServer JAVA Virtual Machine' JAccelerator (NCOMP) ...is required to be installed from the 10g Companion CD.

--> Oracle XDK for Java [upgrade] VALID --> Oracle Java Packages [upgrade] VALID --> Oracle Text [upgrade] VALID --> Oracle XML Database [upgrade] VALID --> Oracle Workspace Manager [upgrade] VALID --> Oracle Data Mining [upgrade] VALID --> Messaging Gateway [upgrade] VALID --> OLAP Analytic Workspace [upgrade] UPGRADED --> OLAP Catalog [upgrade] VALID --> Oracle OLAP API [upgrade] UPGRADED --> Oracle interMedia [upgrade] VALID ...The 'Oracle interMedia Image Accelerator' is ...required to be installed from the 10g Companion CD.

--> Spatial [upgrade] VALID --> Oracle Ultra Search [upgrade] VALID

... To successfully upgrade Ultra Search, install it from ... the 10g Companion CD.

--> Oracle Label Security [upgrade] VALID

... To successfully upgrade Oracle Label Security, perform ... a Custom install and select the OLS option.

.

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

Miscellaneous Warnings

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

WARNING: --> Workspace Manager replication is in use.

.... Drop OWM replication support before upgrading:

.... EXECUTE dbms_wm.DropReplicationSupport;

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 contains stale optimizer statistics.

.... Refer to the 10g Upgrade Guide for instructions to update .... statistics prior to upgrading the database.

.... Component Schemas with stale statistics:

.... SYS .... XDB .... OLAPSYS .... MDSYS

WARNING: --> Database contains INVALID objects prior to upgrade.

.... USER SYS has 1 INVALID objects.

WARNING: --> Database contains globally authenticated users.

.... Refer to the 10g Upgrade Guide to upgrade SSL users.

WARNING: --> OLS requires post-upgrade action to update policy triggers.

.... Run rdbms/admin/olstrig.sql after the upgrade.

.

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

SYSAUX Tablespace:

[Create tablespace in the Oracle Database 10.2 environment]

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

--> New "SYSAUX" tablespace

.... minimum required size for database upgrade: 500 MB .

The following sections describe the output of the Pre-Upgrade Information Tool.

Database

This section displays global database information about the current database, such as the database name, release number, and compatibility level. A warning is displayed if the COMPATIBLE initialization parameter needs to be adjusted before the database is upgraded.

Logfiles

This section displays a list of redo log files in the current database whose size is less than 4 MB. For each log file, the file name, group number, and recommended size is displayed. New files of at least 4 MB (preferably 10 MB) need to be created in the current database. Any redo log files less than 4 MB must be dropped before the database is upgraded.

Tablespaces

This section displays a list of tablespaces in the current database. For each tablespace, the tablespace name and minimum required size is displayed. In addition, a message is displayed if the tablespace is adequate for the upgrade. If the tablespace does not have enough free space, then space must be added to the tablespace in the current database. Tablespace adjustments need to be made before the database is upgraded.

Nel documento Oracle® Database Upgrade Guide 10g (pagine 34-38)