Installing ORACLE7 Server for A/UX (Version 7.0.12.2.0) Desktop
Victor Grigorieff
October 13, 1993 Apple A/UX 3.0.1
Updated 10/28/93 by Victor Grigorieff
This bulletin describes the steps required to install ORACLE7 Server for
A/UX. This document assumes that A/UX has been properly configured.
Bulletin #103947.028 describes in detail how to install A/UX 3.0.1
properly.
This bulletin only applies to the 7.0.12.2.0 Server release, as this
process will most likely change with the upcoming 7.0.15 release.
Related Bulletins:
#103947.028 - Setting up an AWS 95 Server for Oracle7 for A/UX
If any part of the pre-installation checklist is not clear,
or does not work, refer to this bulletin for assistance.
#104011.574 - Tips for administrating and supporting ORACLE7 for A/UX
This bulletin describes the techniques and tricks used to
setup and debug the UNIX and Oracle installations.
Pre-Installation Checklist
--------------------------
C Compiler You must install the C compiler for the install of Oracle to
complete. If you type the command 'which cc' at a UNIX
prompt, you should see '/bin/cc'. If you do not see this, you
must reinstall A/UX to install the C compiler.
Disk Space You must have 60 megabytes of space available to install the
ORACLE7 Server for A/UX with the sample database. You can use
the command 'df -B' to determine the amount of available space
on the currently mounted filesystems. I recommend installing
the Oracledatabase files on a separate filesystem from '/',
which contains the operating system.
TCP/IP If you intend to use SQL*Net TCP/IP, check the configuration
of the networking software. Type the command 'hostname' to
determine the name of your host, and then try to telnet to
that host. See Bulletin #104011.574 for more details on this.
AppleTalk If you intend to use AppleTalk check to see that the server
is connected properly to your network. Usually, the Workgroup
Server 95 is connected to an Ethernet network. If you are on
an Ethernet network, check to see that the Network Control
Panel has EtherTalk selected. Then, check the Chooser to se
if you can see other AppleTalk devices on the network such as
AppleShare file servers or LaserWriter printers.
Also, type the command:
ls -l /usr/lib/libat.a
If you do not see something like the following line, then you
need to reinstall A/UX, including the Network Server
capability:
-rw-r--r-- 1 bin bin 35774 Mar 23 1993 /usr/lib/libat.a
Installation
------------
Before installing Oracle7 Server for A/UX, log into the AWS 95 as the root
user. You must be root if you want to be able to install any SQL*Net
product.
To install ORACLE7 Server for A/UX, you run the "AUX Installer" program
from the folder called "Aux Installer" which is on the CD. The Installer
will ask you several questions along the way.
Destination You need to pick a folder to install the Oracle database
and utilities. This will later be known as the
ORACLE_HOME, which you will need to know.
*** Important: You may not install the Oracle database in any
*** directory whose path has a space in its name. This
*** means that you may not install in the '/ Shared Data'
*** directory.
Oracle owner This is the user who will own the Oracle installation. You
may pick an existing user, or let the Installer create a
new user for you. The default is to let the Installer
create a new user named 'oracle', which is fine.
DBA group This is the name of the group that will have the ability to
start and stop the database, and perform DBA-privileged
operations. The Installer will create a new group for you
if the group does not already exist. The default is to let
the Installer create a new group called 'dba'.
Software The ORACLE7 Server for A/UX is made up of several
components.
A/UX RDBMS and Utilities
A/UX Required Support Files Version 7.0
A/UX SQL*Net Version 1.0
I recommend installing all of the options with this
7.0.12.2.0 release. If you know you will never need either
SQL*Net AppleTalk or TCP/IP, you may choose to leave one of
them out, but you would not be saving a large amount of
disk space.
Procedural Option The Installer WILL NOT ask you if you are licensed
to use the Procedural Option. If you are in fact
licensed for this option, you may enable it by
running the script called CATPROC.SQL after
installing and creating the database. This process
is described in the Oracle7 Server Administrator's
Guide.
Distributed Option You will be asked if you are licensed to use the
Distributed Option. If you are licensed, you may
click yes.
If you click yes, several features will be enabled.
these include the ability to maintain snapshots and
snapshot logs (remote views of databases).
Note: The Distributed functionality will not work
unless the Procedural Option is enabled.
Seed Database You will be asked if you would like to create the seed
database in the folder where you are installing oracle.
There are good reasons to choose Yes or No, which are below:
Yes If you click yes, the Installer will start sqldba (the Oracle
database administration program), and run the script
createdb.sql, which was installed in the dbs directory of the
oracle home. The sample database will be named SAMP.
This is a quick way of having a working database that you can
use for learning and testing. The creation of this database
requires one click of the mouse.
You will be warned that creating the database will destroy any
other datbases in this location. If this is the first time
you have installed an Oracle database in that directory, do
not worry about this warning.
If you already have a database named SAMP in that directory,
choosing Yes will overwrite your old database by creating a
new one.
No You may choose not to create the seed database, because you
want to name the database something other than SAMP, or want
to use different parameters and sizes for your database.
You could manually create the database, following the
instructions in chapter 2 of the "ORACLE7 Server
Administrator's Guide". This is somewhat difficult if you have
never done it before.
Alternatively, you could make a copy of the createdb.sql
script, and edit that copy. If I have an edited copy of
createdb.sql called custom_createdb.sql, I could run that in
sqldba to build my database.
Once you have answered all of the questions, the Installer will install
the options you have selected, and create a seed database if you
requested that.
Post Installation Tasks
-----------------------
Once the installation is complete, you will need to go through a few more
steps to properly configure the Oracle database.
SQL*Net There are several files which need to be created/edited to
configure SQL*Net Version 1.
/etc/oratab You need to create a file called oratab in the /etc
directory. This file lists the instances (SID's)
available on the A/UX machine. This file is required
by both the TCP/IP and AppleTalk protocols of SQL*Net.
This file has one line per database on the machine.
Lines beginning with '#' are comments which are
ignored. Each line is made up of the format:
SID:ORACLE_HOME:STARTUP
Where: SID is the name of the database
ORACLE_HOME is where you installed the database
STARTUP is either Y or N, which indicates
whether the dbstart and dbshut
utilities should start or stop that
database.
The default /etc/oratab should have the line:
SAMP:/users/oracle:N
TCP/IP If you intend to use SQL*Net TCP/IP version 1, you must edit
several files, and startup the TCP/IP listener.
/etc/services You need to define a port number for SQL*Net
TCP/IP Version 1. By default, this is 1525. If
you use a different number for the orasrv port
number, you must configure the client machines to
use that same number. In most cases, you will be
fine if you add the following line:
orasrv 1525/tcp oracle # SQL*Net Version 1
/etc/hosts This file lists all the IP addresses and host
names for all machines that the A/UX server can
connect to using TCP/IP. If your own host is not
already listed in the file, add an entry with the
format
<IP address> <hostname> <aliasname>
An example would be:
139.185.81.95 squid.us.oracle.com squid
You may optionally list several other aliasnames
for each host, allowing you to call a host by
several different names.
tcpctl start This command starts the TCP/IP listener by running
the orasrv program.
This will start the orasrv process, which will
listen for client connections on the port defined
in the /etc/services file.
Client machines would then be able to connect
using the database connect string:
t:hostname:SAMP
hostname is the name of the server on the TCP/IP
network. SAMP is the name of the database.
AppleTalk If you wish to use SQL*Net AppleTalk version 1, you must
start the atksrv process. As the root user, type:
atksrv MyServer
This will start up an AppleTalk server named "MyServer".
Client machines will connect using the database connect
string:
at:MyServer:SAMP [,Appletalk_Zone]
You would only need to specify the AppleTalk Zone if the
client machine is in a different zone than the server.
Starting the atksrv process in this fashion will tie up that
window until you stop the listener by hitting control-C.
You may run the atksrv process in the background by adding
the ampersand (&) character after the command. You could
then kill that process with the command "kill %", provided
the atksrv process was the only background process of that
window. Please see Bulletin 104011.57 for more information
on running the atksrv process in the background.
Oracle user If the A/UX Installer created the oracle user, there will be
no .login file in the oracle user's home directory. If this
is the case, log in as the oracle user, and issue the
command:
cp /usr/lib/skel/std.login ~/.login
You will need to edit the .login file which is in the oracle
user's home directory (by default /users/oracle). Add the
following lines to the end of the file:
setenv ORACLE_HOME /users/oracle
setenv ORACLE_SID SAMP
setenv PATH "/users/oracle/bin:/bin:/usr/bin:/usr/ucb:
/mac/bin:/etc:/usr/etc:/usr/local/bin"
The examples above assume that Oracle was installed in
/users/oracle and that the name of the SID is SAMP. If you
have a different oracle home or a different name of the SID,
you will need to use different values in the examples above.
*** Once you have edited the oracle user's .login file, you must
*** log out, and log in again as oracle before the changes will
*** take effect.
Post-Installation Checklist
---------------------------
Verify that database is running by using the ps command as shown here:
ps -ef | grep dbwr
root 10355 10242 2 07:39:46 pb 0:00 grep dbwr
oracle 4196 1 0 Sep 2 ? 0:02 ora_dbwr_SAMP
Look at the right-most column in this output. If you see the process
named "ora_dbwr_SAMP", then the SAMP database is running.
Verify that the TCP/IP listener process is running by using the command
tcpctl status
tcputl: Status summary follows
Server is running:
Started : 21-SEP-93 10:01:29
Last connection : 30-SEP-93 14:39:49
Total connections : 300
Total rejections : 6
Active subprocesses : 3
ORACLE SIDs : S7F,SAMP
Default SID : (null)
Logging mode is ENABLED.
DBA logins are DISABLED.
OPS$ logins are ENABLED.
OPS$ROOT logins are DISABLED.
Orasrv is detached from the terminal.
Break mode = IN BAND.
Debug level = 1
No timeout (on orasrv handshaking).
Length of listen queue = 10
Orasrv logfile = /u2/7012f/tcp/log/orasrv.log
Orasrv mapfile = /etc/oratab
In the above example you see the string "Server is running", which is the
sign that TCP/IP is up and running.
Verify that the AppleTalk listener is running by using the command:
ps -ef | grep atksrv
root 22675 22662 0 14:57:02 q2 0:00 atksrv Squid
root 22676 22662 1 14:57:28 q2 0:00 grep atksrv
Look at the right-most column in this output. If you see the process
called "atksrv Servername", then the AppleTalk listener is running.
Verify that you can connect to the database using sqldba.
sqldba
SQL*DBA: Release 7.0.12.2.0 - Production on Thu Sep 30 15:00:11 1993
Copyright (c) Oracle Corporation 1979, 1993. All rights reserved.
ORACLE7 Server Release 7.0.12.2.0 - Production
With the procedural and distributed options
PL/SQL Release 2.0.14.0.1 - Production
SQLDBA> connect scott/tiger
Connected.
In this output, I connected as scott/tiger, and was successful. At this
point you know that the database is running, and is accepting connections.
If you are still having problems with debugging/verifying the installation,
refer to bulletin 104011.574 - Tips for administrating and supporting
ORACLE7 for A/UX.