1. If necessary, modify the
Oracle Net configuration files (tnsnames.ora, listener.ora, and sqlnet.ora) found in $TNS_ADMIN (if you specified that variable) or $ORACLE_HOME/network/admin (typically the primary default location).
2. Log in as oracle9
and at a UNIX prompt, reload (or start, if not already running) the listener by
typing lsnrctl reload (or lsnrctl
start) to register the instance with
the listener. The value "test" (or the name you used for the seed database)
should appear in the output (part of a sample output is shown below).
Service "test" has 1 instance(s).
Instance "test", status READY, has 1 handler(s) for this service...
At this point, you should be
able to start a SQL*Plus session. Verify that you can connect as sysdba. At a
UNIX prompt, enter
# sqlplus /nolog
SQL> connect / as sysdba
Connecting as sysdba
is how you need to connect to the database when performing startup and shutdown
because Oracle9i no longer supports the use of Server Manager (the svrmgrl
utility found in earlier releases of Oracle). See Troubleshooting Tips
if you cannot connect as sysdba.
Once you are satisfied you can
connect to the seed database locally and across your network (by testing a
connection to the server from a remote client), you can shutdown the instance
and delete the database files to recover the disk space. You can also delete
the control files and redo log files.
3. If you do not need the
Apache web server, stop the Apache server by executing
# $ORACLE_HOME/Apache/Apache/bin/apachectl stop
Solaris OS Patches
If you are using a version
of Solaris 8 that does not have Sun kernel patch 108528-15 or higher, or if
your company requires the latest Solaris OS patch as a matter of policy, follow
the steps in this section. The output from uname -a will show the
patch level of 108528.
$ uname -a
SunOS stecal 5.8 Generic_108528-15 sun4u sparc SUNW,Ultra-5_10
Sun recommends you download
and install a Sun recommended patch cluster for Solaris 8 ("Solaris 8
Recommended Patch Cluster") and have patch 108528-15 (or higher) installed
as part of the cluster (see http://sunsolve.sun.com).
Download the patch cluster for Solaris 8 (not "8 x86") and unzip the
files. The files can be unzipped anywhere on the file system where your UNIX
user root has access. The install script that comes with the
cluster will place the patches in their proper locations. You need
approximately 75.5MB of disk space for the download (as of Dec 4, 2002).
After unzipping the download
in the <patch cluster
directory>, at a UNIX prompt as root
run the install cluster script.
# cd <patch cluster directory>
By default, a message
warning the user to check for minimum disk space allowance will appear and
allow the user to abort if inadequate space exists. The progress of the script
will be displayed on your terminal. It should look something like:
Patch cluster install script for <cluster name>
Determining if sufficient save space exists...
Sufficient save space exists, continuing...
Installing patches located in <patch cluster directory>
To confirm that patch
108528-17 (where -17 is the latest patch version) was installed, execute showrev -p | grep 108528-17 at a UNIX
prompt. If the patch does not appear, check the install log at
There may be two patches in
the cluster that do not install (110723-03 and 109951-01), but their absence
does not matter. If you experience problems while installing patches, contact
your UNIX systems administrator for assistance.
When the install cluster
process is finished, reboot the system. You will also need to reboot the
system after kernel parameters have been changed, and you can wait until then
Problem: GUI-based tools such as Database Configuration Assistant
fail to run ($ORACLE_HOME/JRE/bin/jre not found message appears when using the OUI)
Description: A Java component (oracle.swd.jre) did not install
Solution: Continue the installation without running the
Database Configuration Assistant or Oracle Net Configuration Assistant. Exit
the installation process when everything else is finished. Re-insert CD #1 and
wait for the Oracle Universal Installer: Welcome window to appear. Open a
separate shell window, login as oracle9, and issue the following commands at the UNIX
# mkdir $ORACLE_HOME/JRE
# cd /tmp/OraInstall/jre
# cp -r * $ORACLE_HOME/JRE
Confirm the bin
and lib directories were created in $ORACLE_HOME/JRE. The /tmp/OraInstall directory is automatically created and deleted during
the installation process. Re-starting the OUI creates the necessary files you
can copy to $ORACLE_HOME/JRE. As oracle9 at a UNIX prompt, you can type dbca
and netca to start the two assistants and run them outside of
the installation process. dbca and netca are found in $ORACLE_HOME/bin.
Problem: You cannot connect as sysdba, and receive ERROR ORA-01031: insufficient privileges
Description: Your user privileges need to be adjusted. On a
local machine, connect / as
sysdba will work in virtually all cases
as this command string replaces connect
internal, which Oracle9i does not
support. You should be able to perform a connect
system/manager as sysdba on the server (do not include the @<net service name>
part of the string). You may encounter the ORA-01031 error if you use connect system/manager@<net service
Solution: Refer to the following items for information on how
to resolve this error:
- Doc Id 50508.1 on MetaLink,
- Doc Id 50507.1 on MetaLink, or
- Oracle9i Database Administrator's
Guide, Release 2 (9.2), dated March 2002 (Oracle Part No. A96521-01), starting
on page 1-13 (PDF version) in the section titled, "Database Administrator
See All Articles by Columnist Steve Callan