|
How to
apply Oracle patch set in general?
|
More Resources by
Google: |
|
|
|
|
By:
John Kazerooni
The
instructions for installing Oracle patch set in general and it will assume a minimal familiarity
with the Oracle Universal Installer and version of upgrade is in the forth level of release
x.x.x.?.0.0,
for example 8.1.7.?.? up.
You must
remember that applying a patch for each release could be different and the following instruction are
not applicable to any specific patch. Please read and study the patch instruction before applying
them to your system.
As with any maintenance operation, Oracle Corporation
recommends that you back up your Oracle software before making any changes to it.
|
Notes
-
On UNIX systems, if you require /usr/ucb in your
search path, make sure that it comes after /usr/bin and/or /usr/ccs/bin in the $PATH
setting.
-
If an inadvertent attempt is made to apply Patch Sets
that applies to 8.1.7 release or up, then if it is not applicable a warning dialog box entitled Dependencies
is displayed like the following message:
There are no patches that need to be applied from the patch set Oracle8i Patchset 8.1.7.4.0
|
1.
Log in to the oracle account and make sure the
environment is set to the correct ORACLE_HOME and ORACLE_SID.
2.
Uncompress and un-tar the downloaded patch set file into a
new directory.
3.
Shut down the existing Oracle Server instance with normal or
immediate priority. I.e.: Shutdown all instances (cleanly) if running Parallel Server. Stop all
listener, agent and other processes running in or against the ORACLE_HOME to be installed into.
4.
Start the installer:
o
If the Installer was installed during the installation, then
run the installer from within the $ORACLE_HOME/bin directory.
o
If the Installer was not installed during the installation,
then run the installer from within the top-level directory on the original Oracle version.
5.
You may install the Patch Set through either an interactive
or a silent installation.
o
To perform an interactive installation using the Oracle
Universal Installer graphical interface:
1.
Start the installer from whichever of the above directories
is appropriate on your installation:
% ./runInstaller
2.
Follow the steps given below within the installer:
1.
On the Welcome screen, click the Next button.
This will display the File Locations screen.
2.
Click the Browse button for the Source...
entry field and navigate to the stage directory where you unpacked the Patch Set tar file.
3.
Select the products.jar file. Click the Next
button
The products file will be read and the installer will load the product
definitions. The products to be loaded will be displayed.
4.
Verify the products listed and then click on the Install
button.
5.
Once the installation has completed successfully, it will
display End of Installation. Click on Exit and confirm to exit the installer.
2.
Copy the response file template provided in the response
directory where you unpacked the Patch Set tar file.
3.
Edit the values for all fields labeled as "<Value
Required>" according to the comments and examples in the template.
4.
Start the installer from whichever of the directories
described in Step 4 applies to your situation passing as the last argument the full path of the
response file template you have edited locally with your own value of ORACLE_HOME and FROM_LOCATION:
% ./runInstaller
-silent -responseFile <full_path_to_your_response_file>
6.
If you have previously installed Oracle Label Security then add object files to
library. This step is necessary because the installation of this patch set removes Oracle Label
Security object files from RDBMS library.
Link in ols .o files using the
following steps:
cd $ORACLE_HOME/lbac/lib
make -f lbac.mk xkzl
make -f lbac.mk ilbac
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk ioracle
7.
Disabling system triggers.
Before performing the next step, you must first set _SYSTEM_TRIG_ENABLED = FALSE in the
initialization parameter file. To do this add the following line to your init<sid>.ora file
and restart the database (see Note 149948.1 in Metalink for more information on this issue).
_system_trig_enabled=false
8.
Invoke SQL*Plus (sqlplus), connect as internal and run the
following:
select *
from duc$ where PACK='JIS$INTERCEPTOR$' ;
If no rows were returned go to the next step. If a row was returned delete it using the following:
delete from
duc$ where PACK='JIS$INTERCEPTOR$' ;
commit;
9.
Invoke SQL*Plus (sqlplus), connect as internal
(/ as sysdba) and run the
following SQL scripts with
event
10520 set. NOTE: This event is not intended for regular database operation and when turned on
below by the 'ALTER SESSION' command will automatically be turned off by the subsequent 'CONNECT'
command.
ALTER
SESSION SET EVENTS '10520 TRACE NAME CONTEXT FOREVER, LEVEL 10';
?/rdbms/admin/catalog.sql
?/rdbms/admin/catproc.sql
?/rdbms/admin/catrep.sql (This
only needs to be run if you are using symmetric/advanced replication. This is not necessary for
sites using dblinks and read-only snapshots if symmetric/advanced replication is not installed)
CONNECT / AS SYSDBA;
update obj$ set status=5 where type#=29 and owner#!=0;
commit;
10.
You can ignore this step if you have already executed it
as part of a previous patch set install.
If Java has previously been loaded into the database, invoke SQL*Plus (sqlplus),
connect as internal and run the following SQL DDL command(* Note:If Java has not previously been
loaded into the database, skip this step).:
SQL> create or replace java system
2 /
(Note that the / (slash) is important to ensure the execution of the command).
To ensure the correct installation of the XDK in the database run the following 2 scripts (Bug
2115227):
$ORACLE_HOME/oracore/admin/initxml.sql
$ORACLE_HOME/rdbms/admin/catxsu.sql
|
* To determine whether Java
has previously been loaded into the database:
invoke SQL*Plus (sqlplus), connect as internal and run the following:
SQL> select count(*) from all_objects where object_type like 'JAVA%';
Java is installed if you get a
non zero result returned from the query.
|
11.
12.
You can ignore this step if you have already executed it
as part of a previous patch set install:
If Java has previously been
loaded into the database, invoke SQL*Plus (sqlplus), connect as internal and run the following
scripts which are located in $ORACLE_HOME/javavm/install ( Note: If Java has not
previously been loaded into the database, you can skip this step):
load_jis.sql
jisja.sql
initjsp.sql
jspja.sql
Notes:
When running the $ORACLE_HOME/javavm/install/jisja.sql script the following error may be reported
and can be ignored:
call jis_exit_java_session(0)
ERROR at line 1:
ORA-29515: exit called from Java code with status 0
Bug 1459233 was filed against
this problem which is fixed in 9i.
13.
If you deleted a row from duc$ in step 8 then reinsert it
again. Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL:
insert into
duc$ (OWNER, PACK, PROC, FIELD1, OPERATION#, SEQ) values ('SYS', 'JIS$INTERCEPTOR$', 'USER_DROPPED',
0, 1, 1);
commit;
14.
Enabling system triggers.
You must either remove _SYSTEM_TRIG_ENABLED from the initialization parameter file or explicitly set
it to TRUE before attempting any other patch set post-install steps. Restart the database.
15.
This step is optional - it will recompile all invalid
PL/SQL packages now rather than when accessed for the first time - you can also use
utlrcmp.sql to parallelize this.
Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL
script:
o
?/rdbms/admin/utlrp.sql
16.
Execute the following steps only if you have installed Oracle interMedia Text in the
database you are attempting to modify:
o
If you have not previously unlocked the ctxsys account and supplied a password for that
account, you need to do so. (If you have needed to use Oracle Text in any way prior to applying the
patchset, you will have already performed this step, and you can skip this.) Do so by issuing the
following statement:
ALTER USER ctxsys IDENTIFIED BY <passwd> ACCOUNT UNLOCK;
1.
If you have already installed 8.1.7.2 or 8.1.7.3, go directly to step 7 below.
2.
If you have already installed 8.1.7.1,
go directly to step 5 below.
3.
CONNECT ctxsys/<passwd>;
4.
@?/ctx/admin/upgrade/u0801071.sql
5.
CONNECT ctxsys/<passwd>;
6.
@?/ctx/admin/upgrade/u0801072.sql
7.
CONNECT / AS SYSDBA;
8.
@?/ctx/admin/upgrade/s0801074.sql
9.
CONNECT ctxsys/<passwd>
10.
@?/ctx/admin/dr0pkh.sql
11.
@?/ctx/admin/dr0plb.sql
12.
@?/ctx/admin/dr0type.plb
13.
@?/ctx/admin/dr0typec.plb
17.
You can ignore this step if you have already executed it
as part of a previous patch set install:
The installation of this patch set fixes a potential security hole in the
XSQL Servletl. The patchset installation does not, however, modify any of the Oracle HTTP Server
configuration files to reflect changes to the XSQL Servlet installation. If you have previously
installed the Oracle HTTP Server, you will need to update one of the configuration files manually
after the patchset installation is complete. If you do not do so, the XSQL Servlet may not work in
the context of the Oracle HTTP Server after the patchset is installed. To update your Oracle HTTP
Server configuration, perform the following steps:
1) Edit the file: $ORACLE_HOME/Apache/Jserv/conf/jserv.properties
2) Search for the string: "XSQLConfig.xml File location"
3) Modify the parameter wrapper.classpath on the line immediately
following the above string to read: $ORACLE_HOME/oracore/admin
4) Save the file.
18.
You can ignore this step if you have already executed it
as part of a previous patch set install:
The installation of this patch set fixes a
potential security hole in the PL/SQL XML parserl. To load the new XML parser in to the database, run the following script as user
SYS:
? /xdk/plsql/parser/bin/load.sql
19.
If you are using the RMAN catalog then upgrade it as follows:
o
rman catalog
<user/passwd@alias>
o
upgrade catalog;
o
upgrade catalog;
The post install actions are now complet.
|