Oracle Upgrade (10.2.0.1-& gt; 10.2.0.3)

Generally, after Oracle software is installed, Oracle will be patched before the database is created. Of course, it doesn't matter if the database is not installed. Next we will introduce the upgrade process of Oracle after the database is created, DB: Oracle 10G R2 10.2.0.1; OS: Red Hat Linux as 4. Oracle Installation Reference:

I. Preparations before Upgrade

First, download and upload the patch package to the database server, because I tried to use the 32-bit Oracle 10G R2 10.2.0.1 in Linux. The complete patch is p5337014_10203_linux.zip. The patch goes directly to the Oracle official website. Pay attention to the corresponding version.

1. decompress the patch package to obtain the Disk1 folder.

2. the backup database and Oracle-related directories must be full backup. Cold backup is recommended. Once an upgrade encounters a problem, the recovery is faster.

Ii. Upgrade Oracle software

1. Install the patch package and use the graphics terminal. VNC usage reference:

2. Run the root. sh script as the root user.

3. Run the root. sh script as root. After the script is complete, the Oracle software upgrade is complete.

3. Upgrade the database

After the Oracle software upgrade is complete, do not start the database. Otherwise, the following error will be reported:

ORA-00704: bootstrap process failure.

ORA-39700: database must be opened with UPGRADE option

Error 704 happened during db open, shutting down database

USER: terminating instance due to error 704.

Instance terminated by USER, pid = 7819

ORA-1092 signalled during: alter database open...

There are two ways to upgrade the database: DBUA graphical mode and manual upgrade mode. manual upgrade is recommended. DBUA is easy to operate in graphical mode. You only need to follow the prompts to proceed step by step. Note that if the database to be upgraded is not in the list, you need to modify/etc/oratab to add the corresponding SID, during the upgrade process, select the "compile invalid objects after upgrade" option. If no backup is available before the upgrade, you can select the backup database when using DBUA. DBUA performs cold backup and requires sufficient space. If no error is reported after the execution is completed as prompted, finish.

Manually use echo $ ORACLE_SID to check whether the database to be upgraded is used. If not, use export $ ORACLE_SID = sid to modify it. Then log on to SQLPLUS as a DBA and perform the following operations:

SQL> startup upgrade

SQL> spool/u01/upgrade. log

SQL> @? /Rdbms/admin/catupgrd. SQL -- wait a long time

If this step is successfully executed, more than half of the Data upgrade has been completed. Restart the database and compile invalid objects. Because catupgrd. SQL may cause some data objects to be INVALID. Use the statement: select count (1) from dba_objects where status = 'invalid' to check whether there are INVALID objects. If yes, run utlrp. invalid SQL compilation object.

SQL> shutdown immediate;

SQL> startup

SQL> @? /Rdbms/admin/utlrp. SQL -- wait a long time

After compilation, query the table space, user, user object, and other information. If there is no problem, OK, our Database Upgrade is successful. Then back up the database and open the application. When we query an object, some objects with names similar to BIN $ BD34RX + 6TCJEK54334w = $0 may appear. These objects are deleted in the recycle BIN and can be ignored.