|
|
This appendix gives detailed instructions for installing Oracle Enterprise Server software Version 7.3.4 on Solaris 2.5.1 to be used as the relational database management system (RDBMS) component of the Cisco Access Manager (CAM). Oracle Enterprise Server software Version 7.3.4 is the recommended release.
The following topics are covered:
Before you can install Oracle 7.3.4, you must perform the following steps:
1. "Tune the Kernel for Shared Memory"
2. "Verify Your Server Has the Solaris Packages Needed by Oracle7"
3. "Create a dba Group in the /etc/group File"
4. "Create the Oracle UNIX Administration Account"
5. "Create the /usr/localbin Directory"
To prepare for Oracle installation, you must tune the kernel so that it can use shared memory. You can refer to the etc_system.example.
Step 1 Log in as the root user.
Step 2 Use a text editor such as vi to edit the /etc/system file, adding the following statements to the end of it:
Step 3 Save the /etc/system file.
When using forceload, you must specify a filename which includes a directory. The forceload statements cause the specified modules to be loaded at boot time, that is, prior to mounting the root file system rather than at first reference. (Loading a module does not mean that the module will be installed.) If you do not include the forceload statements as indicated, the shared memory parameters might not be set after reboot.
Step 4 Reboot the system.
If you are following along with the Oracle installation guide, it might tell you to install patches at this point. Do not install any patches. Solaris 2.5.1 does not require them.
Confirm the kernel parameter settings by entering the following command:
# ./usr/sbin/sysdef
To install Oracle 7.3.4, the following Solaris 2.x packages must already be installed on the server:
To install these packages:
Step 1 Determine if the above-listed Solaris 2.x packages are installed. As the root user, enter the following command:
Solaris lists a description of each of the installed packages.
Step 2 Use /usr/sbin/pkgadd to install any of the above packages that are not already installed. Refer to your Solaris installation documentation for full instructions.
For example, to add the SUNWarc package from the Solaris 2.5.x CD-ROM, enter the following commands:
As the root user, create a group called dba. We recommend you do this by editing the /etc/group file using the Solaris Admintool, but you can also edit the /etc/group file manually.
If you are running the X Window System (OpenWindows or CDE), you can also use the Admintool graphical user interface (GUI) to create the dba group as follows:
Step 1 Start the Admintool by entering the following command:
Step 2 Choose Browse>Groups, and then Edit>Add.
Step 3 Under Group Name, enter dba. (The Group ID field will be automatically filled with a valid Group ID value.)
Step 4 Click OK.
To manually add the group dba:
Step 1 Check to make sure the 101 group ID (GID) is unassigned by entering the grep command on the /etc/group file:
If you do not receive any output, you can use 101. If you receive output, 101 is in use. In the later case, repeat this step using other group IDs until you find an available one.
Step 2 To manually edit the file, append the following command to the /etc/group file:
This can also be done by entering the following command:
where GID is the group ID (GID) that is assigned to the group. (If 101 is already assigned to another group, use a different, unassigned number.)
As the root user, create a user account named oracle. Although this user account could be named something other than oracle, we recommend that you name the account oracle for consistency with other Oracle installations. You can create the Oracle account using the Admintool or manually.
To create the oracle account, you must have the following information:
If you are running the X Windows System (OpenWindows or CDE), you should use the Admintool to create the Oracle account as follows:
Step 1 If the Admintool is not already running, start the Admintool by entering the following command:
Step 2 If you are not in the Admintool: Users screen, select Browse>Users.
Step 3 Select Edit>Add. The Admintool: Modify Users screen appears. (See Figure A-1.)
Step 4 Fill out the form as follows:
(a) Under User Name, type oracle.
(b) Under Primary Group, type dba.
(c) Select Create Home Dir.
(d) Under path, type mntpoint/oracle/product/7.3.4.
where mntpoint is the mount point for the Oracle installation that you have determined has at least 4.0 GB of available disk space.
(e) Click OK.

To create the oracle user manually:
Step 1 Use vi or another text editor to add the following line to the /etc/passwd file:
where UID is the User ID you have determined and uniquely assigned to the Oracle account and mntpoint is the mount point for the Oracle installation that you have determined has at least 4.0 GB of available disk space.
Step 2 Edit the /etc/shadow file. Append the following line:
Step 3 Create the Oracle user's home directory. Your home directory would be /mntpoint/oracle/product/7.3.4, where mntpoint is the Oracle installation mount point. This is the same directory into which you will be installing the Oracle software, which will also be known as ORACLE_HOME. Your home directory should be the same as ORACLE_HOME so when you log in as the Oracle user, you will be placed into the directory structure to which you will need access.
To create ORACLE_HOME, enter the following commands:
where mntpoint is the mount point for the Oracle installation.
The chown command changes the owner of Oracle directory to oracle user. The chgrp command changes the group of oracle directory to dba.
Step 4 Set the oracle user password. As the root user, enter the following command:
You are prompted for the new password and asked to re-enter it to verify you have entered it correctly. Do not forget the Oracle user password.
As the root user, create the /opt/bin directory. Enter the following command:
% mkdir /usr/localbin
Or, you can also create the /usr/localbin directory. Enter the following command:
% mkdir /opt/bin
To set environment variables for the oracle user:
Step 1 Log in as the oracle user.
Step 2 Copy .cshrc to .cshrc.save.
Step 3 Using vi or another text editor, add the following statements to the .cshrc file.
where mntpoint is the mount point for the Oracle installation.
Step 4 Enter the source command to add the environment variables to your current environment:
You might receive an error message that says the /opt/bin/coraenv file is not found. This error will be resolved when you have finished installing Oracle and run the root.sh script.
As the root user, add the following line to the /etc/services file:
listener 1521/tcp # Oracle Listener process
This completes the pre-installation procedures. Continue with the next section, "Installing the Oracle Server Software."
To install the Oracle Server software, follow the steps in this section. Be sure to log in as the Oracle user you created earlier.
Step 1 Insert the Oracle 7.3.4 CD-ROM into the system's local CD-ROM drive.
Step 2 Optionally, as the Oracle user, you can check the environment settings by entering the env command:
Step 3 Change directories to the Oracle installation directory on the CD-ROM:
Step 4 Enter the orainst command:

Step 5 Select Default Install and press Return.
The Installation Activity Choice screen appears:

Step 6 Select the default option, Install, Upgrade, or De-Install Software.
The Installation Options screen appears:

Step 7 Select the second option, Install New Product - Do Not Create DB Objects.
The Environmental Variables screen appears:

Step 8 Make sure that:
Step 9 Press Return.
The Relink All Executables screen appears:

Step 10 Select No and press Return. It is not necessary to re-link the executables.
The Summary of Installation Options screen appears:

Step 11 Check to make sure that all of the Oracle file locations are correct. If they are, select OK and press Return.
The Software Asset Manager screen appears:

Step 12 Select the following components:
*If you are installing CAM client software on your machine only, you need to install only SQL*Plus and SQL*Net.
Step 13 When all of the items listed above are marked for installation, press Return or click Install.
The DBA Group screen appears, but does not apply to the client.

Step 14 Select dba and press Return.
The OSOPER Group screen appears, but does not apply to the client.

Step 15 With dba selected as the OSOPER group, press Return.
The Shared Library Installation screen appears:

Step 16 Select OK and press Return.
After between 25 and 40 minutes, the Installer Actions Completed screen appears:

Step 17 Press Return.
The Software Asset Manager screen appears. Press Tab until Exit is highlighted, and then press Return twice. This completes the Oracle Server software installation. Proceed to "Post-Installation Procedure."
As root user, run the root.sh script. Enter the following commands:
# setenv ORACLE_HOME /mntpoint/oracle/product/7.3.4
# setenv ORACLE_SID CAMDB
# cd $ORACLE_HOME/orainst
# /usr/bin/sh ./root.sh
where mntpoint is the mount point for the Oracle installation which you have determined has at least 4.0 GB of available disk space.
This completes the post-installation procedure. Resolve any issue with the Oracle dbstart and dbshut scripts.
For additional documentation, refer to the Oracle Corporation Web site at http://www.oracle.com.
We recommend that you set up Oracle to start automatically. If you set up the UNIX system in /etc/rd2.d for the automatic start up script, and /etc/rd0.d for the automatic shutdown script, when UNIX system reboots, the Oracle server will be shut down orderly and start up automatically.
Refer to the README.database that is included in the CSCOcamdb package.
To set up Oracle and the Netscape FastTrack Server to be shut down automatically when the CAM server shuts down, refer to the README.database that is included in the CSCOcamdb package.
The K80CSCOapm file should look like this example when you are done. (This example assumes you want to shut down the Oracle processes at system shutdown.)
This completes the procedure for shutting down Oracle automatically at system shutdown.
For additional documentation, refer to the Oracle Corporation Web site at http://www.oracle.com.
|
|