Steps for upgrading oracle from 9.2.0.1 to 9.2.0.8

Background: Oracle 9.2.0.1.0 is installed on Windows 2003 Server. We plan to upgrade it to version 9.2.0.8 and install the latest security patch April 2008.
1. Upgrade Oracle (administrator user permissions)
(1) download the upgrade package from Metalink. The patch number is 4547809, and the package name is p4547809_92080_winnt.zip, for Windows 32bit.
(2)decompress the ZIP file, and the lower side includes a disk1 and readme.html file. Before installing and upgrading the patch, stop all Oracle-related services in management, stop LSNRCTL in the command prompt, and stop the listener.
(32.16before double-hitting setup.exe under disk, make sure that the environment variable contains the ORACLE_HOME variable and has been correctly set. Otherwise, an error occurs (the error is forgotten ).
(4)double-click setup.exe and automatically upgrade to 9.2.0.8. The command prompt prompts that the component has been installed after the installation is complete.
(5) There is no update component in Step 4, So update is required. You need to enable the Oracle service at this time. It is best to restart the computer, and the Oracle service will start automatically by default.
(6) After logging on to the database as sysdba, SQL> startup installs Oracle with JVM and XDB users to ensure that the parameters shared_pool_size and java_pool_size in init. ora are 150 m. You can view the size of two existing parameters.
SQL> show parameter shared_pool_size
SQL> show parameter java_pool_size
If the size is not 150 m, set it as follows:
SQL> alter system set shared_pool_size = '150m' scope = spfile;
SQL> alter system set java_pool_size = '150m' scope = spfile;
After the setting is successful, shutdown immediate closes the database.
(7) log on to the database as sysdba
Execute SQL> startup migrate
SQL> spool patch. Log
SQL> @ oracle_base \ ORACLE_HOME \ RDBMS \ admin \ catpatch. SQL
SQL> spool off
Spool patch. Log refers to the Update log to patch. log for future check.
Here, oracle_base \ ORACLE_HOME indicates your Oracle directory. If the Oracle installation directory is c: \ oracle \ ora92, the third sentence should be:
SQL> @ C: \ oracle \ ora92 \ rrdbms \ admin \ catpatch. SQL where @ indicates that the following script is executed.
This process lasted about 20 minutes.
(8) shut down the database, start up, and execute another script.
SQL> @ oracle_base \ ORACLE_HOME \ RDBMS \ admin \ utlrp. SQL. After the patch is updated !!
(8) restart the database. After login, select * from V $ version. You can see that Oracle has increased to 9208.

2. Install Oracle Security Patches
(1) patch information: Critical Patch Update note release 9.2.0.8 for Microsoft Windows (32-bit), patch number: 6867138.
(2) the CPU is a transitional patch and must be installed using the Oracle Installation Tool opatch.
Before installing the CPU, check that the corresponding opatch version should be 1.0.0.57, 9.2.0.1 Oracle comes with a version of 55, and download the 57 version from Metalink. The compressed package is p2617419_10102_generic. After decompression, overwrite the opatch directory % ORACLE_HOME % \ opatch.
(3) Stop all Oracle services before installing the security patch with opatch. However, in practice, it is found that the related DLL is still occupied by unknown (I am unknown) programs, resulting in couldn't copy some. DLL file. Therefore, it is recommended to restart the server and enter the security mode.
(4) In safe mode, in the command prompt, directly opatch apply % patch LOCATION %, for example, in my computer patch on D: \ Software \ oracle9 \ p6867138_92080_winnt \ 6867138, then I enter opatch apply D: \ Software \ oracle9 \ p6867138_92080_winnt \ 6867138 in the command prompt to automatically install the security patch.
(5) After the installation is complete, the patch is not successful yet, and it is almost crying ~~~~. Bite your teeth and then come
Run the remove_demo.js script to remove the unstable Oracle HTTP Server demos. Command Prompt CD to the 6867138 directory.
> Cscript // nologo remove_demo.js
(6) import the modified. SQL file to the database:
Start Oracle service, cd % ORACLE_HOME % \ CPU \ cpuapr2008 and run SQL> @ catcpu. SQL after logging on to sysdba
If an invalid object is reported in this process, execute (7). Otherwise, execute (8) directly ).
(7) after cd % ORACLE_HOME % \ RDBMS \ admin, log on to sysdba and run @ utlrp. SQL. Then you can use
SQL> select object_name from dba_objects where status = 'invalid'; check that there is no invalid object.
(8) recompile the view in the database
Cd % ORACLE_HOME % \ CPU \ view_recompile and then sysdba log on and execute SQL> @ recompile_precheck_jan2008cpu. SQL, which is the time to execute the computation.
Shutdown the database and use the migrate method to start up, SQL> startup migrate and then SQL> @ view_recompile_jan2008cpu. SQL to close the database. If there is an invalid object, manually compile, but generally no.

Summary: Different Oracle patches have different approaches, which are really unintelligent. So read readme carefully before, which is a very depressing activity! The installation is not completed !! Crashed ~~~ The above operations are performed directly after the database is created, so the database backup and other work are not taken into account. If you have already done some work using the database, we recommend that you back up the database first to avoid the impact of patches on the database.