Oracle Universal Installer OUI patching tips
Oracle Database Tips by Donald Burleson
By Steve Karam, the world's youngest Oracle ACE
and Oracle certified Master.
I?m not a big fan of ignoring errors with the Oracle Universal Installer (OUI),
and we all have our own patching horror stories. The trickiest part of
patching is the makefile which link-edits the Oracle executables. When I
ran across this makefile error, one I was loathe to ignore or cancel:
Error in invoking
target 'all_no_orcl ipc_g' of makefile
Now, an experienced Oracle installer/patcher/troubleshooter/slave
knows full well that most of these problems are compiler related, and this one
was no different. I was patching a 10.2.0.1.0 RAC installation to 10.2.0.3.0.
To fix the problem, simply go to
Oracle's Open Source Downloads and download the latest binutils release.
Install it with the following command:
Once installed, click ?retry? on your OUI screen and everything should be
taken care of! However, if this is a RAC system, don't forget to install
binutils on both nodes!
If you DID ignore the error and kept going with the patch, you?ll probably
find that ASM does not work. To fix this, you will have to install binutils,
relink all, and find a good working copy of $ORACLE_HOME/lib/libskgxp10.so
from another Oracle installation to replace the one on your patched system.
The moral of the story is, of course, to fix problems before continuing
Errors During CATUPGRD.SQL
While I?m at it, another problem I found was during the execution of the
CATUPGRD.SQL script that must be run after installing the Oracle software. I
received the following error:
SELECT version_script AS
file_name FROM DUAL
ERROR at line 1:
or function VERSION_SCRIPT is in an invalid state
Thankfully, this was an easy enough problem to fix. Simply change some
- alter system set plsql_code_type
string = INTERPRETED
- alter system set plsql_compiler_flags
string = INTERPRETED, NON_DEBUG
- Rerun ?/rdbms/admin/catupgrd.sql
Or, if you really want to use native PL/SQL compilation, just set your
plsql_native_library_dir and then rerun the script.
One Last Note
Make SURE you set your JAVA_POOL_SIZE and SHARED_POOL_SIZE to at least 150M
before running catupgrd.sql! If you do not have a large enough shared pool, you
will get errors during the install. You may be able to workaround these by
flushing the shared pool (alter system flush shared_pool), but you?re better off
doing it right the first time.
If you like Oracle tuning, see the book "Oracle
Tuning: The Definitive Reference", with 950 pages of tuning tips and
You can buy it direct from the publisher for 30%-off and get
instant access to the code depot of Oracle tuning scripts.