run uold_release.sql, where old_release refers to the release you had installed prior to upgrading. see table 3-2 to choose the correct script. each script provides a direct upgrade from the release specified in the "old release" column. the "old release" is the release from which you are upgrading.
to run a script, enter the following:
sql> @uold_release.sql
table 3-2 upgrade scripts
old release run script
7.3.4 u0703040.sql
8.0.6 u0800060.sql
8.1.7 u0801070.sql
9.0.1 u0900010.sql
see also:
"determine your upgrade path to the new release" if the old release you had installed prior to upgrading is not listed in table 3-2
make sure you follow these guidelines when you run the script:
you must use the version of the script supplied with the new release 9.2 installation.
you must run the script in the new release 9.2 environment.
you only need to run one script, even if your upgrade spans more than one release. for example, if your old release was 8.1.7, then you only need to run u0801070.sql.
the script you run creates and alters certain dictionary tables. it also runs the catalog.sql and catproc.sql scripts that come with the new 9.2 release, which create the system catalog views and all the necessary packages for using pl/sql.
the following components are upgraded by running the uold_release.sql script:
oracle9i catalog views
oracle9i packages and types
display the contents of the component registry to determine which components need to be upgraded:
sql> select comp_name, version, status
from dba_registry;
the following is an example of the output you will see when issuing this query:
turn off the spooling of script results to the log file:
sql> spool off
then, check the spool file and verify that the packages and procedures compiled successfully. you named the spool file in step 13; the suggested name was upgrade.log. correct any problems you find in this file and rerun the appropriate upgrade scripts if necessary. you can rerun any of the scripts described in this chapter as many times as necessary.
shut down and restart the instance to reinitialize the system parameters for normal operation. the restart will also perform release 9.2 initialization for jserver java virtual machine and other components.
sql> shutdown immediate
executing this clean shutdown flushes all caches, clears buffers, and performs other housekeeping activities. these measures are an important final step to ensure the integrity and consistency of the newly upgraded oracle9i database.
also, if you encountered a message listing obsolete initialization parameters when you started the database in step 11, then remove the obsolete initialization parameters from the initialization parameter file now.
upgrade any remaining components that existed in the previous database. see "upgrading specific components".
the following components require separate upgrade steps:
oracle text
oracle ultra search
oracle spatial
oracle intermedia
oracle visual information retrieval
run utlrp.sql to recompile any remaining stored pl/sql and java code.
sql> @utlrp.sql
verify that all expected packages and classes are valid:
sql> select count(*) from dba_objects where status='invalid';
sql> select destinct object_name from dba_objects where status='invalid';
verify that all components are valid and have been upgraded to release 9.2:
sql> select comp_name, version, status
from dba_registry;
your database is now upgraded to the new 9.2 release. complete the procedures described in chapter 4, "after upgrading a database".
11. 创建spfile
sql>create spfile from pfile;
12. 查看报警日志文件,发现temp file找不到:
errors in file d:/oracle/admin/wjsfms/bdump/wjsfms_dbw0_2200.trc:
ora-01186: file 201 failed verification tests
ora-01157: cannot identify/lock data file 201 - see dbwr trace file
ora-01110: data file 201: 'd:/oracle/oradata/wjsfms/temp01.dbf'
wed nov 10 10:29:22 2004
file 201 not verified due to error ora-01157
wed nov 10 10:29:22 2004
errors in file d:/oracle/admin/wjsfms/bdump/wjsfms_dbw0_2200.trc:
ora-01157: cannot identify/lock data file 202 - see dbwr trace file
ora-01110: data file 202: 'd:/oracle/oradata/wjsfms/temp2.ora'
ora-27041: unable to open file
sql>select a.name,b.file#,b.name from ts$ a,v$tempfile b where a.ts#=b.ts#;
