cc/td/doc/product/access/ap/apm
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Oracle Installation Guidelines

Oracle Installation Guidelines

This appendix gives detailed instructions for installing Oracle Enterprise Server software version  7.3.3 on Solaris 2.5.x to be used as the relational database management system (RDBMS) component of the Cisco  AccessPath Manager (APM). APM will run with either Oracle Enterprise Server software version 7.3.2.2 or 7.3.3. We recommend using version 7.3.3, and the installation procedure for 7.3.3 is the one described in this appendix.

Note You must install Oracle before you install APM. Also, make sure you place Oracle on a file system with a minimum of 4.0  GB of free disk space.
Note This document only provides basic guidelines for installing Oracle for use with APM. For a full description of Oracle installation, and to be sure you have the most recent documentation, refer to the documentation that came with your Oracle software or refer to the Oracle Corporation web site at http://www.oracle.com.

Installing the Oracle Server consists of the following steps:

    1. "Pre-Installation Procedures"

    2. "Installing the Oracle Server Software"

    3. "Post-Installation Procedure"

    4. "Performing a Workaround for Oracle dbstart and dbshut"

    5. "Starting Oracle Automatically (Optional)"

    6. "Shutting Down Oracle and Netscape FastTrack Server Automatically (Optional)"

Pre-Installation Procedures

Before you can install Oracle 7.3.3, 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 /opt/bin Directory"

    6. "Set the Oracle User Environment Variables"

    7. "Reserve a Port for the SQL*Net Version 2 Listener"

Tune the Kernel for Shared Memory

To prepare for Oracle installation, you must tune the kernel so that it can use shared memory.

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:

Save the /etc/system file.

Step 3 Reboot the system.

Note You must reboot your system after you have added these lines to /etc/system, otherwise, the installation program will not be able to complete.

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 does not require them.

Verify Your Server Has the Solaris Packages Needed by Oracle7

To install Oracle 7.3.3, 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 will list 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, type the following commands:

Create a dba Group in the /etc/group File

As the root user, create a group called dba. We recommend that you do this by editing the /etc/group file using the Solaris Admintool, but you can also edit the /etc/group file manually.

Using the Admintool to Edit the /etc/group File

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, 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.

Manually Editing the /etc/group File

To manually add the group dba:

Step 1 Check to make sure the 101 group ID (GID) is unassigned by using 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 executing 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.)

Create the Oracle UNIX Administration Account

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:

To decide this, you will need to know which partition has enough available space for the Oracle installation. Use the command df -k for information on free disk space. The partition you install Oracle onto should have 4.0 GB of available disk space.
Open the /etc/passwd file. The third field of each line is the UID. The UID you assign to the oracle user must be unique. We recommend that you increment the highest of all of the UIDs by one.

Using the Admintool to Create the Oracle Account

If you are running the X Window 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:


Figure A-1: Creating the Oracle User with the Admintool


Manually Creating the Oracle User

To create the oracle user manually:

Step 1 Use vi or another text editor to editing the /etc/passwd file. Append the following line to it.

where:

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.3, where mntpoint is the Oracle installation mount point.

This is the same directory that you will be installing the Oracle software into, which will also be known as ORACLE_HOME. Your home directory should be the same as ORACLE_HOME so that when you log in as the oracle user, you will be placed into the directory structure that you will need access to.

To create ORACLE_HOME, execute 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, execute the following command:

You will be prompted for the new password and then asked to re-enter it to verify you have entered it correctly. Do not forget the oracle user password.

Create the /opt/bin Directory

As the root user, create the /opt/bin directory. Execute the following command:

% mkdir /opt/bin

Set the Oracle User Environment Variables

To set environment variables for the oracle user, follow these steps:

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.

Caution It is important that you set the APM_DBPATH variable in  .cshrc file to be the same as your input variable at installation time. If the settings are different, APM may experience problems communicating with the Oracle Server during system boot. The above example is the default installation.

Step 4 Use the source command to add the environment variables to your current environment:

You may 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.

Reserve a Port for the SQL*Net Version 2 Listener

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."


 Installing the Oracle Server Software

 
 To install the Oracle Server software, follow the steps in this section. 



Note The examples and screen captures in this procedure assume that you are not running the X Window System, however, we have provided additional instructions for installations while using the X Window System.




Step 1	 Insert the Oracle 7.3.3 CD-ROM into the system's local CD-ROM drive. 



Step 2	 Optionally, as the oracle user, you can check the environment settings using the env command:




Step 3	 Change directories to the Oracle installation directory on the CD-ROM:




Step 4	 Issue the orainst command:



The Install Type screen appears. (See Figure A-2.)





Figure A-2: Install Type Screen

 



Step 5	 Select Default Install and press Return. The Installation Activity Choice screen appears. (See Figure A-3.)



Figure A-3: Installation Activity Choice Screen

 



Step 6	 Select the default option, Install, Upgrade, or De-Install Software. The Installation Options screen appears. (See Figure A-4.)



Figure A-4: Installation Options Screen

 



Step 7	 Select the second option, Install New Product - Do Not Create DB Objects. The Environmental Variables screen appears. (See Figure A-5.)



Figure A-5: Environmental Variables Screen

 



Step 8	 Make sure that:



 Press Return. The Relink All Executables screen appears. (See Figure A-6.)



Figure A-6: Relink All Executables Screen

 



Step 9	 Select No and press Return. It is not necessary to re-link the executables. The Summary of Installation Options screen appears. (See Figure A-7.)



Figure A-7: Summary of Installation Options Screen

 



Step 10	 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. (See Figure A-8.)



Figure A-8: Software Asset Manager Screen

 



Step 11	 Select the following components: 




 When all of the items listed above are marked for installation, press Return or click Install. The DBA Group screen appears. (See Figure A-9.)




Figure A-9: DBA Group Screen

 



Step 12	 Select dba and press Return. The OSOPER Group screen appears. (See Figure A-10.)




Figure A-10: OSOPER Group Screen

 



Step 13	 With dba selected as the OSOPER group, press Return. The Shared Library Installation screen will appear. (See Figure A-11.)



Figure A-11: Shared Library Installation Screen

 



Step 14	 Select OK and press Return. After between 25 and 40 minutes, the Installer Actions Completed screen will appear. (See Figure A-12.)



Figure A-12: Installer Actions Completed Screen

 



Step 15	 Press Return. The Software Asset Manager screen will appear. Press Tab until Exit is highlighted, then press Return twice. 


 This completes the Oracle Server software installation. Continue with the next section, "Post-Installation Procedure."


 Post-Installation Procedure

 
 As root user, run the root.sh script. Enter the following commands:


# setenv ORACLE_HOME mntpoint/oracle/product/7.3.3

# setenv ORACLE_SID APMDB

# cd $ORACLE_HOME/orainst

# /usr/bin/sh  ./root.sh



 where mntpoint is the mount point for the Oracle installation that you have determined has at least 4.0 GB of available disk space.



Note You may see a message that says, "Please raise the Oracle owner's ulimit as per the IUG." You can ignore this message; it will not affect the usability of the oracle account or APM.



 This completes the post-installation procedure. To resolve an issue with the Oracle dbstart and dbshut scripts, continue with "Performing a Workaround for Oracle dbstart and dbshut." 


 For additional documentation, refer to the Oracle Corporation web site at http://www.oracle.com. 


 Performing a Workaround for Oracle dbstart and dbshut

 
 The dbstart and dbshut scripts provided with Oracle Server Software version 7.3.2 and 7.3.3 reference SQL*DBA, which has been replaced by Server Manager. To correct for this, perform the following steps (Oracle reference number 307228). 



Note If you install Oracle 7.3.2.2, be sure to install the patches as well as this bug fix.




Step 1	 Use vi or another text editor to create a script that will replace SQL*DBA: 




Step 2	 Save this script as $ORACLE_HOME/bin/sqldba.



Step 3	 Use the chmod command to add execute permission:




Note Simply creating a link to SQL*DBA will not work. dbstart and dbshut will check for SQL*DBA in the version string. 



 This completes the fix of the Oracle dbstart and dbshut scripts. Additional information on this and other Oracle issues is available on the web at http://www.oracle.com/support/. 


 Two other procedures are provided in this document:



 For additional documentation, refer to the Oracle Corporation web site at http://www.oracle.com. 


 Starting Oracle Automatically (Optional)

 
 To set up Oracle to start automatically under Sun Solaris:



Step 1	 Make sure the /var/opt/oracle/oratab entry for APMDB in the Oracle oratab file ends with a capital Y. This tells the dbstart script that to automatically start the Oracle APM database at system boot time. 



Step 2	 As the root user, use vi or another text editor to create a script in the /etc/rc2.d directory called S80CSCOapm_oracle. This file should contain the following text:



 where mntpoint is the mount point for the Oracle installation.



Step 3	 If you want to use SQL*Net to make your database available for use as a remote database, add the following line to your S89CSCOapm_oracle file:



 where mntpoint is the mount point for the Oracle installation.



Step 4	 Ensure that the oracle user's  .cshrc file does not have the ORAENV_ASK variable set to YES. 


 If this variable is set to YES, Oracle will be required to interactively confirm environment variable settings; interactive confirmations are not possible at boot time. Your machine will not start Oracle automatically at boot time if the ORAENV_ASK variable is set to YES.


 This completes the procedure for starting Oracle automatically at boot time. 


 For additional documentation, refer to the Oracle Corporation web site at http://www.oracle.com. 


 Shutting Down Oracle and Netscape FastTrack Server Automatically (Optional)

 
 To set up Oracle and the Netscape FastTrack Server to be shut down automatically when the APM server shuts down:



Step 1	 As the root user, use vi or another text editor to create a script named K80CSCOapm in the /etc/rc0.d directory. This file should contain the following text:



 where apm_server_name is the name you have assigned to your APM server.



Step 2	 If you want the Netscape FastTrack Admin program and the FastTrack Server to shut down automatically when the APM server shuts down, add the following lines to your K80CSCOapm file:




Step 3	 If you want Oracle to shut down automatically when the APM server shuts down, add the following lines to your K80CSCOapm file:



 where apm_server_name is the name you have assigned to your APM server.



Step 4	 End the K80CSCOapm file with exit 0.


 Example


 The K80CSCOapm file should look like this example when you are done. (This example assumes you will want to shut down both the Oracle and the Netscape processes at system shutdown.)



 where apm_server_name is the name you have assigned to your APM server.


 This completes the procedure for shutting down Oracle and Netscape automatically at system shutdown. 


 For additional documentation, refer to the Oracle Corporation web site at http://www.oracle.com. 







hometocprevnextglossaryfeedbacksearchhelp




Copyright 1989-1998 
 © 
Cisco Systems Inc.