You can perform a non-interactive (or "silent") installation of Oracle8i
products and patches by supplying the Oracle Universal Installer with a response file. The
Installer uses the variables and values contained in this text file to provide answers to
some or all of the Installer's user prompts. If you include responses for all of the
Installer's prompts in the response file, you can run a silent installation that displays
no graphical output.
You will need to edit the response file to suit your environment.
- Unpack the patch (e.g. p1746764_8171_SOLARIS.zip)
tar xvf 8171b_solaris_32_patchset.tar
In this case, two subdirectories response and stage are
created. Go to the response directory and edit the response file (e.g. 8171b.rsp)
Note, that you must enter the values in double quotas ( " " ). Here is
an example for a response file, where only the edited parameters are shown.
The complete response file can be found here.
Make sure, that no Processes belonging to the user Oracle still
connect sys/... as sysdba
ps -ef | grep "oracle"
kill -9 xxx
To perform a completely silent installation or configuration session,
use the -silent parameter. In silent mode, the DISPLAY environment variable must still be
./runInstaller -silent -responseFile /app/response/8171b.rsp
The success or failure of the installation is logged in the
silentInstall.log file. If an Oracle Inventory exists on your system, then the
silentInstall.log file is created there. Otherwise, it is created in the
oraInventory_location/logs/ directory. The detailed results of the non-interactive
installation session are found in the
tail -f installActions.log
tail -f oraInstall.err
tail -f oraInstall.out
The installation of Oracle 8i Patch Set was successful.
- Postmigration (Start Oracle in RESTRICTED MODE)
SELECT 'REVOKE restricted session FROM '
|| username || ';' FROM dba_users
WHERE username NOT IN ('SYS','SYSTEM');
ALTER SYSTEM ENABLE RESTRICTED SESSION;
Run the postmigration scripts
You may execute additional scripts, e.g.
# Run all sql scripts for replication
# Collect I/O per table (actually object) statistics by
# statistical sampling
# This package creates a table into which references to
# the chained rows for an IOT (Index-Only-Table) can be
# placed using the ANALYZE command.
# Wrap Package which creates IOTs (Index-Only-Table)
# This package allows you to display the sizes of objects
# in the shared pool, and mark them for keeping or
# unkeeping in order to reduce memory fragmentation.
# Creates the default table for storing the output
# of the ANALYZE LIST CHAINED ROWS command
# Creates the EXCEPTION table
# Grant public access to all views used by TKPROF
# with verbose=y option
# Create table PLAN_TABLE that is used by the EXPLAIN PLAN
# statement. The explain statement requires the presence
# of this table in order to store the descriptions of
# the row sources.
# Create performance tuning views
# Create v7 style export/import views against the v8 RDBMS
# so that EXP/IMP v7 can be used to read out data in a
# v8 RDBMS. These views are necessary if you want to export
# from Oracle8 and import in an Oracle7 database.
# Create views of oracle locks
# Print out the lock wait-for graph in a tree
# structured fashion
# Creates the default table for storing the output of the
# analyze validate command on a partitioned table
# PL/SQL Package of utility routines for raw datatypes
# Contains the PL/SQL interface to the cryptographic
# This package provides a built-in random number
# generator. It is faster than generators written in PL/SQL
# because it calls Oracle's internal random number
# DBMS package specification for Oracle8 Large Object
# This package provides routines for operations on BLOB
# and CLOB datatypes.
# Procedures for instrumenting database applications
# DBMS_APPLICATION_INFO package spec.
# Run obfuscation toolkit script.
# Create Heterogeneous Services data dictionary
# Stored procedures for Oracle Trace server
# Oracle8i Profiler for PL/SQL
# Profilers are helpful tools to investigate programs and
# identify slow program parts and bottle necks. Furthermore
# you can determine which procedure, function or any other
# code part is executed how many times. To be able to use
# the DBMS_PROFILER package you have to install once for
# your database the following packages. Do this as user SYS
The utlrp.sql script recompiles all existing PL/SQL modules
that were previously in an INVALID state, such as packages, procedures, types, etc.
These actions are optional; however, they ensure that the cost of recompilation is
incurred during installation rather than in the future
Now, you can shutdown and restart the database again
ALTER SYSTEM DISABLE RESTRICTED SESSION;
To determine whether Java has previously been loaded into the
invoke SQL*Plus (sqlplus), connect as internal and run the following:
SQL> describe dbms_java
If the result is:
ORA-04043: object dbms_java does not exist
then java has not previously been loaded in the database. If the result
is a long package description, then java has previously been loaded in the database.
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):
If you will perform the first installation of Oracle products on a system
with Oracle Universal Installer running in silent mode, you must manually create the
oraInst.loc file. this file specifies the directory where the installer creates the
inventory of Oracle products installed on the system.
To create the oraInst.loc file, Log in as the root user
If it does not already exist on your system, you must create the
# mkdir /var/opt/oracle
Change to the /var/opt/oracle directory.
# cd /var/opt/oracle
Using a text editor, create a file called oraInst.loc with the following
two lines of content:
Set inventory_loc to ORACLE_BASE/oraInventory.
Include, but do not set, inst_group= on the second line.