The following work should be done as root :

Some work needed to be done for organizational purposes on the machine first. This consisted of the following :

Setup the kernel environment by changing the following values in the mtune. (/etc/conf/cf.d/mtune). For an understanding of what these variables mean, look at the NCR Unix book for "Command Line Reference Manual - Volume 3" in Rich’s office. Note that these values are for a single instance only. For multiple instance installs, such as East Orange was, you may need to adjust these values.

• · SHMMAX to 2097152 0 (20 Mb)
• · SHMMIN to 1
• · SHMMNI to 250
• · SHMSEG to 10
• · SEMMNS to 200
• · SEMMNI to 70

Now rebuild the kernel by typing : "/etc/conf/bin/idbuild"

Finally reboot by typing :

• · cd /
• · shutdown -g0 -y -i6"

These are some other steps that I perform when setting up a Unix box. Some will be realized much after the install, and some much quicker. These next few are certainly not mandatory, but make life easier in the long run.

• · Create a directory called /usr/local/bin, which will hold local binary or executable files/scripts for local SCO machine.
• · Create a /home directory for users home directories.
• · Comment out roots /.profile entry which is asking for term type.
• · Modify /etc/default/login to include /usr/bin/X11 and /usr/local/bin in the default path.
• · Modify /etc/default/accounts to make the default home directory is /home
• · I also moved rich and edumet’s home directory’s from the original /usr directory to /home.
• · Link /var/mail to /var/spool/mail to keep consistency with NCR SVR4 style.
• · Change machine’s network nodename from edumet to sco. Did this by :

• 1. hostname sco.edumet.com
• 2. uname -S sco
• 3. and vi /etc/systemid and chaged to sco (Note that P20sysetup in /etc/rc2.d sets this up)
• 4. comment out the old entry in /etc/hosts for the old IP nubmer, as it will be found by the system before our new entry.

These steps are needed for the install of Oracle, so make sure to perform them.

• · Load SCO developer package from original SCO media. This is needed for the Oracle install. This package MUST be removed after delivery of the machine. The install is done by :

• 1. use "custom" at the command prompt OR startup the SCO software installer
• 2. choose "cdrom" from the source list
• 3. now choose the SCO developer system (ver 5.1.0Ac) package.
• 4. the licence info is :

• License Number : 2NC023137
• License Code : ftjvvful License
• Data : g0;k0;q1;md9xgmz

• · Load SCO patch "oss459a" from red floppy diskette appropriately marked. This is done by :

• 1. go into a unix window
• 2. extract the tar file on the diskette into a temp directory. I use /usr/local/os_patches.
• 3. use "custom" at the command prompt to startup the SCO software installer
• 4. choose "media images" from the source list.

• · Create "dba" group thru scoadmin facility
• · Create "oper" group thru scoadmin facility
• · Create "oracle" user thru scoadmin facility - member of dba group.
• · Find a home for oracle software - I chose /usr1/oracle
• · Find a name for the SID of the new database - I chose "sco7" for platform and version
• · Setup umask and ulimit, so that umask=022 and ulimit is large enough to allow files for install.
• · For orainst, we must setup the oracle environment specially like this :

• #####
• ##### Ulimit is measure in blocks, and this equates to 2gig which is
• ##### largest file size available in 32 bit.
• #####
• umask 022
• ulimit 4194303
• #####
• ##### The following lines added by Paul A. Luzzi on 12-10-97
• ##### Needed for oracle and oracle installer specifically.
• ##### ORACLE_HOME=/usr1/oracle
• ORACLE_BASE=/usr1/oracle
• ORACLE_DOC=/usr1/oracle/doc
• ORACLE_PATH=$ORACLE_HOME/bin:/bin:/usr/bin:/usr/lbin:/usr/local/bin
• ORACLE_SID=sco7
• ORACLE_TERM=386x
• ORA_CSM_MODE=line
• LD_LIBRARY_PATH=$ORACLE_HOME/lib:/usr/lib
• LOG=/tmp/rootpre.sh.log
• export ORACLE_HOME ORACLE_BASE ORACLE_DOC ORACLE_SID ORACLE_PATH ORACLE_TERM \ ORA_CSM_MODE LD_LIBRARY_PATH LOG
• unset SRCHOME
• unset TWOTASK

• · Mount CDRom using /cdrom/mount.readme command (if there are any problems, they will be reported)
• · Make sure you are logged in as root. · set ORACLE_HOME=/usr1/oracle
• · mkdir $ORACLE_HOME/orainst $ORACLE_HOME/bin
• · chown oracle $ORACLE_HOME/orainst $ORACLE_HOME/bin
• · chgrp dba $ORACLE_HOME/orainst $ORACLE_HOME/bin
• · chmod 775 $ORACLE_HOME/orainst $ORACLE_HOME/bin
• · cd /cdrom/orainst
• · ./rootpre.sh

• answer Y to install from cdrom
• answer N to install icons on ODT
• answer oracle to name of software owner
• answer dba to group of software owner
• answer Y to create above files/settings
• answer N to install thru floppy drive

• · upon exit, copy /usr/lbin/oraenv to /usr1/oracle/bin
• · Now exit out and login as oracle

The following work should be done as oracle :

· cd /cdrom/orainst

· I always use a ksh for this with an xterm (this is just personal preference) :

• exec ksh -o vi
• xterm -sb -sl 10000 -fn 6x13 &

· Run the oracle installer by typing : ./orainst from the /cdrom/orainst directory

· ./orainst (options are as follows)

• Choose custom install
• Install new product - create DB objects
• /usr1 for top mounting point
• Accept 7.3.3 (we will change later)
• Change/make sure that ORACLE_BASE=/usr1/oracle
• Change/make sure that ORACLE_HOME=/usr1/oracle
• Accept defaults for all log files
• Select "YES" as we have already run the rootpre.sh
• Choose install from cd-rom
• Accept SID name from our pre-set environment
• Select America/English since we wont need all languages
• Select "YES" to relink all executables (this will be automatically selected later anyway)
• (Write down the location of the postinstall script - s/b /usr1/oracle/orainst/root.sh)

• Products to install are :

• 1. Oracle Intelligent Agent 7.3.3.0.0
• 2. Oracle Online Text Viewer 1.0.1.0.0
• 3. Oracle Server Manager (motif) 2.3.3.0.0
• 4. Oracle Unix Installer 4.0.1.0.0
• 5. Oracle 7 Server RDBMS 7.3.3.0.0
• 6. Oracle 7 XA Library 7.3.3.0.0
• 7. PL/SQL v2 2.3.3.0.0
• 8. SQL*Net v2 2.3.3.0.0
• 9. SQL*Plus 3.3.3.0.0
• 10. TCP/IP Protocol Adapter v2 2.3.3.0.0

• Totals are 21 Mb in 10 products.

• Select Install from the button between the two windows. (This will actually launch some dependency checks and eventually the installer itself.

• Click on "OK" to accept the message about the ulimit. That is "OK" because we already set it.
• "dba" will be unix group name for dba’s.
• select "oper" for OSOPER group
• Choose filesystem type for database (Very Important !!!!)
• Distribute the control files over 3 mount points : /usr3, /usr5, and /usr7
• Character set is US7ASCII
• Select system password of "******" and confirm
• Select sys password of "******" and confirm
• choose "YES" to change/set the internal password
• Select "******" for internal password and confirm
• choose 10 concurrent dba users
• select "******" for tns password and confirm
• select "NO" to configure MTS listener
• select "YES" to create control files as named.
• Select "OK" to options on size of files.
• Select "NO" to accept defaults for tablespace sizes and locations.
• Use /usr1 for system tablespace
• Select "YES" to accept all of these choices
• select "YES" to load SQL*Plus help facility
• select "NO" to load SQL*Plus demo tables
• select "OK" to /usr/lib for libXt.a and libX11.a if asked

That will begin the installation !

At one point in the install, you will be required to open up another window and login to server manager. To do this do the following :

• · Click on Unix for another xterm/scoterm window, or use <CTRL><ALT><F3> to go to other screen.
• · You should already be the oracle user, but do verify by typing "id" and confirming.
• · Type svrmgrl to startup server manager in line mode.
• · Type shutdown to shutdown database in a normal fashion
• · upon completion, exit out of server manager.
• · Click on "YES" to continue if prompted.
• · After a bit, you may see an error message (pupbld.sql) which will have something to do with the fact that the installer could not successfully insert or do something in the database, and this is because the database is currently not running. Repeat the above procedure, only choose startup instead of shutdown this time.
• · Please not that you should let the system sit and "soak" for about 5-10 minutes during the error message period.
• · Click on "YES" to continue if prompted.

This should take you straight thru to completion. Any errors at all will require out of the ordinary troubleshooting and are therefore not covered in this manual.

At this point, the installation should basically be complete. You will need to take care of a few other post install steps. They follow.

The following work should be done as root (again) :

• Unmount the cdrom by typing "umount /cdrom" if you get device busy, make sure you are not in that directory and try again.
• Remove the Oracle 7 server cd and insert the Oracle 7 Online documentation cd.
• Type : "/cdrom/mount.readme" to mount it, and just hit enter for the question asked.

The following work should be done as oracle (again) :

• Make sure to be logged in as "oracle" at this point.
• Start local installer by typing "orainst" from /usr1/oracle/orainst. This will launch the local version, and not the cdrom version.
• Choose custom install
• accept defaults until you get to "install doc only" and select it.
• Accept defaults for all other values until you get to the point of choosing a home for documentation.
• We have already setup the $ORACLE_DOC variable, so the default should be fine for that.
• For the install from device, choose "/cdrom/DOC" (*** note that the doc MUST be in upper case ***)
• Select all products.
• upon completion, in a unix shell window, type the two links as defined on page 4-17 on the install book :

• ln -s $ORACLE_HOME/orainst/doc/platform $ORACLE_HOME/doc/platform
• ln -s $ORACLE_HOME/orainst/doc/generic $ORACLE_HOME/doc/generic

• copy the crindex.sh from the /usr1/oracle/orainst to $ORACLE_HOME/doc
• run the crindex.sh as : ./crindex.sh $ORACLE_HOME/doc

The following work should be done as root (again) :

• run the root.sh scripts located in the /usr1/oracle/orainst directory.
• Vi /etc/conf/sdevice.d/sleeper and change the "N" to a "Y".
• run /etc/conf/bin/idbuild to rebuild the kernel.
• Reboot the machine, by typing "cd / ; shutdown -g0 -y -i6"

• Modify the /usr1/oracle/dbs/initsco7.ora file by addding the line "use_post_wait_driver = TRUE"
• vi /etc/conf/cf.d/mtune again and this time set :

• · NAIOREQ to 512
• · NAIOBUF to 512
• · NAIOREQPP to 512

• Now type mkdev aio. If there is already one installed, just exit.
• Rebuild the kernel again by typing : "/etc/conf/bin/idbuild"
• Modify the initsco7.ora file again, this time adding "async_write = TRUE"
• Shutdown and reboot the machine again by typing : "cd / ; shutdown -g0 -y -i6"

• Now go and add any users to the system that need to be dba users. They must be members of the "dba" group by default, on adding. Setup /etc/rc0.d and /etc/rc2.d for shutdown and startup scripts of the database respectively. There are examples located on the yellow diskette.

The following work should be done as oracle (again) :

• Edit $ORACLE_HOME/dbs/initsco7.ora (Note that the choice for a "medium" sized database only works for single installed instance - multiple instances on the same machine, will initially have to be "small" instead of "medium") :

• set "open_cursors" to 200
• change all sections from small to medium (again - only for single instance install)
• and set the compatible parameter.
• The global names parameter should remain false for the database links to work properly.
• Below is a subsection of the file :

• #####
• ##### Added by Paul A. Luzzi on 12-15-1997
• ##### as per oracle's instructions on 5-3 of install book.
• #####
• use_post_wait_driver = TRUE
• async_write = TRUE
• open_cursors = 200
• # tuning parameters
• db_files = 20
• # db_file_multiblock_read_count = 8 # SMALL
• db_file_multiblock_read_count = 16 # MEDIUM
• # db_file_multiblock_read_count = 32 # LARGE
• . . . . . .
• compatible = 7.3.0.0
• global_names = FALSE

• Now stop and restart the database to make sure that these changes dont cause any problems, before going any further. Use server manager in line mode to do this :

• svrmgrl SVRMGR> connect internal
• Connected. SRVMGR> shutdown immediate;
• Statement processed.
• SVRMGR> startup;
• SVRMGR> Connected to an idle instance.
• SVRMGR> ORACLE instance started.
• Total System Global Area 8163284 bytes
• Fixed Size 41876 bytes
• Variable Size 6962240 bytes
• Database Buffers 1126400 bytes
• Redo Buffers 32768 bytes
• Database mounted.
• Database opened.
• SVRMGR> Server Manager complete.

• Once that looks ok, we will turn on archiving. To do this:

• First, we need to add/change 3 new lines in the initsco7.ora file. The directory chosen in the log_archive_dest reflects the ORACLE_SID of the instance, so be sure to either change this for each instance in a multiple instance install, or make it an environment variable. They are :

• log_archive_start = true # if you want automatic archiving
• log_archive_dest = /usr1/oracle/dbs/arc/sco7/arc_
• log_archive_format = _%S.arc

• Now, stop the database

• svrmgrl
• SVRMGR> connect internal
• Connected. SRVMGR> shutdown immediate;
• Statement processed.
• Then restart the database in mount mode (Note that by not issuing a PFILE parameter, "init${ORACLE_SID}.ora" is assumed:

• SVRMGR> startup mount
• ORACLE instance started.
• Total System Global Area 8163284 bytes
• Fixed Size 41876 bytes
• Variable Size 6962240 bytes
• Database Buffers 1126400 bytes
• Redo Buffers 32768 bytes
• Database mounted. SVRMGR>

• Now start the archive process :

• SVRMGR> alter database archivelog;
• Statement processed.

• Now check to see if it is in fact running :

• SVRMGR> archive log list;
• Database log mode Archive Mode
• Automatic archival Enabled
• Archive destination /usr1/oracle/dbs/arc/arc_
• Oldest online log sequence 82
• Next log sequence to archive 84
• Current log sequence 84
• SVRMGR>

• Now open the database for use by all :

• SVRMGR> alter database open;
• Statement processed.
• · Setup the login ability as a dba, from a networked terminal now, by editing the configsco7.ora file in the same directory as the initsco7.ora file resides. Add the following line as the last line in the file :

• remote_login_passwordfile = exclusive

• · Now stop and restart the database. You should already know how to do that.

• · Now we need to setup the listener and naming files for the database. There are samples included on the orange diskette. Use these for now, as we have not yet installed the network manager. You will have to tar these two files into the /etc directory, and give them permissions of 755 with owner/group of oracle/dba. If they need to be edited for the database name, do so now.

• · We now need to make a link from the /etc/oratab file to /var/opt/oracle/oratab - (This is so that the dbsnmp listener will startup, and we can use Oracle Enterprise Manager).

• · Copy /etc/tnsnames.ora to $ORACLE_HOME/network/admin. Do the same copy for /etc/listener.ora.

• · Now finally we should be able to startup the listener. We do so by typing (as oracle) :

• lsnrctl start (for the database listener daemon - regular connections)
• lsnrctl dbsnmp_start (for the Oracle Enterprise Manager listener daemon)

• · Now we should be able to connect in from a client side sqlplus or server manager if available.

• · Create tablespace EDUMET, for storage of all of our products. Use either server manager (GUI Windows version if still operational, or Server Manager in line mode). Choose to create a new tablespace, and use a datafile of ‘/usr?/oradata/sco7/???.dbf’. If using OEM or some other graphical utility, choose to autoextend if the option exists.

• · If you couldnt autoextend above, then modify the tablespaces/datafiles for USERS and EDUMET, to make them autoextend now. Below is one example. You will need to change the names of the datafiles, and tablespaces. Do this by bringing up a unix window as oracle and using server manager in line mode :

• svrmgrl
• SVRMGR> connect internal
• Connected.
• SRVMGR> alter tablespace edumet offline;
• Statement processed.
• SVRMGR> alter database datafile ‘/usr5/oradata/sco7/edumet_1.dbf’ autoextend on;
• Statement processed.
• SVRMGR> alter tablespace edumet online;

• ·Do the same thing for any other tablespaces that you need this option.

• · Now we should go and create two roles in the database. "developer_dba" and "developer_nondba". Note that this is for the office. Remote sites will not need the developer role.

• The developer_dba will have all available options with grant ability, and the developer_nondba will just have connect and resource, with no grant options.

The following steps were performed for the install of the Office machine. The client sites will not need this stuff. So it is provided strictly for reading purposes.

• · Create a user called "edumet" in the system using a default tablespace of "edumet" that we just created.

• · Create an export from the "test3" sid, the existing sid we are migrating from, by logging in as oracle, and doing the following :

• exp (to launch the oracle export utility) enter username and password of ******/****** (note that edumet must have export_database role) create a file called /tmp/edumet.exp Select 2 for users yes to export grants yes to export table data no to compress extents users are edumet only since we dont want to carry over any old crap

• · Now ftp that new export file over from "edu-met" to "sco" .

• · Import it into the sco7 database now. To import it, we basically do the opposite.

• imp (to launch the oracle import utility) enter username/password of ******/****** (note that the edumet user must have import_database role) filename is /tmp/edumet.exp (or whatever you ftp’d it as/to) Make sure to ignore errors durring creation, but accept defaults for all the rest when you get to "import whole file ?" - answer Yes

• · Now add the following users to the database:

• username and password : kevin role : developer_dba + sys.sysdba & sys.sysoper both with admin
• username and password : munish role : developer_dba + sys.sysdba & sys.sysoper both with admin
• username and password : chris role : developer_nondba
• username and password : ricardo role : developer_nondba
• username and password : john role : developer_dba + sys.sysdba & sys.sysoper both with admin
• username and password : paul role : developer_dba + sys.sysdba & sys.sysoper both with admin
• username and password : dan role : developer_nondba

• · Lastly, I always make a symbolic link for the oracle instance init files and alert logs into the $ORACLE_HOME/db_mgmt directory for easy viewing. Below are examples of how to do so for the sco7 database sid.

• ln -s /usr1/oracle/admin/sco7/pfile/initsco7_o.ora /usr1/oracle/db_mgmt/initsco7.ora
• ln -s /usr1/oracle/admin/sco7/pfile/configsco7.ora /usr1/oracle/db_mgmt/configsco7.ora
• ln -s /usr1/oracle/admin/sco7/bdump/alert_sco7.ora /usr1/oracle/db_mgmt/alert_sco7.ora