Release 2.1.1 for UNIX
Part Number A88797-01
 Library |
 Contents |
 Index |
| Oracle Internet Directory Installation Guide Release 2.1.1 for UNIX Part Number A88797-01 |
|
After completing the Oracle Universal Installer session, you must perform certain post-installation steps and configure Oracle8i. This chapter describes the required steps, as well as some optional ones.
Oracle Corporation recommends that you change the password for user names immediately after installation.
To change a password:
$ sqlplus
Enter user-name:username/password
SQL> ALTER USERUSERNAMEIDENTIFIED BYPASSWORD;
Log in as the root user and perform the following tasks:
If necessary, create additional UNIX accounts with a system administration utility such as admintool or useradd. Each DBA user on the system must be a member of the OSDBA group.
If you configure Oracle Internet Directory in a way similar to a United States NCSC C2 or European ITSEC E3 security evaluation configuration, verify database file security to ensure the integrity of the Oracle software installation. This task is optional if security is not an issue.
Many files require protection to prevent unauthorized access to secure data. The file privileges and recommended ownership are as follows:
oracle account should have read, write, and execute privileges for all files and directories in an Oracle installation.
oinstall group should have read, write, and execute privileges on the oraInventory directory, but should not have write permissions on anything else.
oracle account or the oinstall group should have write access on any files or directories in an Oracle installation.
Table 4-1 summarizes the directory and file permissions for different types of files.
You can configure your system to automatically start Oracle databases when your system starts up and to shut down Oracle databases when your system shuts down. Automating database startup is optional, but automatic shutdown is recommended because it guards against improper shutdown of the database.
The dbstart and dbshut scripts are located in the $ORACLE_HOME/bin directory and can be used to automate database startup and shutdown.
The dbstart and dbshut scripts reference the same entries in the oratab file, so the scripts must apply to the same set of databases. For example, you cannot have dbstart automatically start up databases sid1, sid2, and sid3, and dbshut shut down only databases sid1 and sid2. You can, however, specify that dbshut shut down a set of databases while dbstart is not used at all. To do this, include the dbshut entry in the shutdown file but omit the dbstart entry from the system startup files.
This process must be completed for every new database that you want to configure for automated startup and shutdown. Perform the following tasks to set up the dbstart and dbshut scripts so that they are called at system startup:
/var/opt/oracle/oratab file.
Database entries in the oratab file appear in the following format:
ORACLE_SID:ORACLE_HOME:{Y|N}
where Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database. Find the entries for all the databases that you want to start up. They are identified by the sid in the first field. Change the last field for each to Y.
dbora in the /etc/init.d directory (if it does not already exist).
dbora file (if they do not already exist). Make sure that you give the full path of the dbstart utility.
#!/bin/sh # Set ORA_HOME to be equivalent to the ORACLE_HOME
# from which you wish to execute dbstart and
# dbshut
# set ORA_OWNER to the user id of the owner of the
# Oracle database in ORA_HOME
ORA_HOME=/u01/app/oracle/product/8.1.7
ORA_OWNER=oracle
if [! -f $ORA_HOME/bin/dbstart]
then
echo "Oracle startup: cannot start"
exit
fi
case "$1" in
'start')
# Start the Oracle databases: # The following command assumes that the oracle login will not prompt the
# user for any values
su - $ORA_OWNER -c $ORA_HOME/bin/dbstart &
;;
'stop')
# Stop the Oracle databases: # The following command assumes that the oracle login will not prompt the
# user for any values
su - $ORA_OWNER -c $ORA_HOME/bin/dbshut &
;;
esac
dbora by entering:
# ln -s /etc/init.d/dbora /etc/rc0.d/K10dbora # ln -s /etc/init.d/dbora /etc/rc2.d/S99dbora
Perform the following tasks as the oracle user:
Update the startup files of the oracle account and the UNIX accounts of Oracle users.
Set the following environment variables in the .profile or .login file of the oracle account before using Oracle8i products. Table 4-2, "Environment Variable Settings" shows the recommended settings. The settings that you use here should correspond to the settings you used during installation as described in "Task 2: Set Environment Variables". The syntax for setting environment variables is as follows.
For the Bourne or Korn shell:
variable_name=value; export variable_name
For the C shell:
setenv variable_name value
| Environment Variable | Recommended Setting |
|---|---|
|
Set it to include |
|
|
|
|
|
|
|
|
If you do not remember the value you entered when you were prompted by the Oracle Universal Installer, you can find it listed in the Installer log file located in
The |
|
|
Make sure the new |
|
|
CLASSPATH must include the following:
Note: |
|
|
Set it to the location of the Net8 configuration files. This variable only needs to be set if Net8 configuration files are not located in one of the default locations. |
|
|
Set TWO_TASK to the Net8 connect string alias defined in |
Required when using Oracle products that use shared libraries. Set
LD_LIBRARY_PATH to include $ORACLE_HOME/lib.
Specifies the directory at the top of the Oracle software and administrative file structure. The OFA-recommended value is:
software_mount_point/app/oracle.
For example:
/u01/app/oracle
Specifies the directory containing the Oracle software for a given release. The Optimal Flexible Architecture recommended value is:
$ORACLE_BASE/product/release.
For example:
/u01/app/oracle/product/8.1.7.
Specifies the Oracle System Identifier (SID) which is the name of the Oracle Server instance. Because the sid is incorporated into many file names, Oracle Corporation recommends restricting it to no more than four characters to avoid filename problems on different operating systems.
After installation of Oracle software, the search path should include all of the following:
$ORACLE_HOME/bin, /bin, /usr/bin, and /usr/ccs/bin
bin directory specified when you ran the root.sh script, usually /usr/local/bin
The CLASSPATH variable is used for Java functionality. CLASSPATH is different for various products. Refer to your product documentation for more information. In addition to any pre-existing settings, CLASSPATH must include the following JRE location(s):
$ORACLE_HOME/JRE/lib:$ORACLE_HOME/jlib:$ORACLE_HOME/product/jlib
The variable product indicates any product directory in the ORACLE_HOME, such as rdbms or network, where a JRE or file required for Java functionality are located.
To place the Net8 configuration files in a location other than the default locations (/var/opt/oracle or $ORACLE_HOME/network/admin), set the
TNS_ADMIN environment variable to the directory where Net8 configuration files are located. For example, if tnsnames.ora resides in the /tns directory, set
TNS_ADMIN to /tns.
Oracle products will look for the tnsnames.ora file in the following order:
.tnsnames.ora file in the current user's home directory (Note the dot before the file name).
$TNS_ADMIN/tnsnames.ora
/var/opt/oracle/
$ORACLE_HOME/network/admin/
Check that a tnsnames.ora file exists in one of these locations; otherwise, you may be unable to connect to a database through Net8 using local naming.
If you have a Client/Server configuration, you can set TWO_TASK to the net service name of the database where client software will connect by default. When TWO_TASK is set, you do not have to specify the net service name of the database to connect to it with Oracle client software. See the Net8 Administrator's Guide and the Oracle8i Administrator's Reference for your platform for more information about net service names.
You have the option of using the oraenv script to set a common environment for oracle users. Follow the instructions below for a single-instance or multiple-instance configuration for the oraenv script.
On a single-instance machine, set the environment variable ORACLE_SID in the .profile or .login file of the oracle account followed by these commands to initialize the oraenv file at login.
For the Bourne or Korn shell:
ORAENV_ASK=NO
. /usr/local/bin/oraenv
For the C shell:
set ORAENV_ASK = NO
source /usr/local/bin/coraenv
unset ORAENV_ASK
On a multiple-instance machine, include a list of instance names and the commands necessary to initialize the oraenv file at the end of the startup file of the oracle account.
For the Bourne or Korn shell:
#!/usr/bin/sh echo "The SIDs on this machine are:" cat /var/opt/oracle/oratab | awk -F: '{print $1}' | grep -v "#" ORAENV_ASK="YES" . /usr/local/bin/oraenv
For the C shell:
#!/usr/bin/csh echo "The SIDs on this machine are:" cat /var/opt/oracle/oratab | awk -F: '{print $1}' | grep -v "#" set ORAENV_ASK="YES" source /usr/local/bin/coraenv
To create the same environment for all oracle accounts, update each user startup file to include the following line at the end of the startup file:
.profile files used by the Bourne or Korn shells:
. /usr/local/bin/oraenv
for .login files used by the C shell:
source /usr/local/bin/coraenv
If you have created a database manually instead of using Oracle Database Configuration Assistant, you must ensure the system configuration is reflected in the /var/opt/oracle/oratab file.
Add an entry for each Server instance on the system in the following format:
ORACLE_SID:ORACLE_HOME:{Y|N}
where Y or N indicates whether you want to activate the dbstart and dbshut scripts. Oracle Database Configuration Assistant automatically adds an entry for each database it creates.
You can change initialization parameters to configure and tune your system for optimal performance. The default initsid.ora file shipped with the distribution is located in the $ORACLE_BASE/admin/sid/pfile directory. A template init.ora file is also in $ORACLE_HOME/dbs. The file contains settings for small, medium, and large databases, with the settings for medium and large databases commented out. The size settings are relative to each other, but do not represent an empirical size of the database.
When you create a typical startup database using Oracle Database Configuration Assistant, your initsid.ora parameters are automatically set. You can manually modify the initialization parameters in the initsid.ora with a UNIX text editor. Activate the modified initsid.ora file by shutting down and restarting the database.
Do not use symbolic character representations such as question marks (?) for ORACLE_HOME in parameter files, as they might lead to startup errors.
To bring rollback segments online automatically with database startup, you must uncomment the rollback_segments in the initsid.ora file.
For example, change:
#rollback_segments = (r0, r1, r2, r3)
to:
rollback_segments = (r0, r1, r2, r3)
Carry out the following task after installation:
Run cryptupgrd.sh immediately after installation. The script can be found in $ORACLE_HOME/ldap/bin.
The Oracle8i database is identified by its global database name, which consists of the database name and network domain in which the database is located. The global database name uniquely distinguishes a database from any other database in the same network domain. You create a global database name when prompted in the Database Identification window during Oracle8i database installation. The global database name takes the form:
database_name.database_domain
For example:
sales.us.acme.com
The DB_NAME parameter (value sales) and DB_DOMAIN name parameter (value us.acme.com) combine to create the global database name value assigned to the SERVICE_NAMES parameter (value sales.us.acme.com) in the init.ora file.
The System Identifier (SID) identifies a specific Oracle8i instance that references the database. The SID uniquely distinguishes a database from any other database on the same computer. Multiple Oracle homes enable you to have multiple, active Oracle databases on a single computer. Each database requires a unique SID and database name.
The SID name is taken from the value you entered for the database name in the Database Identification window. The SID can be up to 64 alphanumeric characters in length.
For example, if the SID and database name for an Oracle database are ORCL, each database file is located in the $ORACLE_BASE/oradata/ORCL directory and the initialization parameter file is located in the $ORACLE_BASE/admin/ORCL/pfile directory. The directory ORCL is named after the DB_NAME parameter value.
An Oracle8i database is divided into smaller logical areas of space known as tablespaces. Each tablespace corresponds to one or more physical datafiles. Datafiles contain the contents of logical database structures such as tables and indexes. A datafile can be associated with only one tablespace and database.
The tablespaces in the Oracle8i database contain the following types of datafiles located in the $ORACLE_BASE/oradata/<db_name> directory:
The starter database contains one database initialization parameter file located in the $ORACLE_BASE/admin/<db_name>/pfile directory:
The starter database contains three redo log files located in the $ORACLE_BASE/oradata/<db_name> directory:
The starter database contains three control files located in the $ORACLE_BASE/oradata/<db_name> directory:
|
See Also:
Oracle8i Administrator's Guide for information on setting this initialization parameter value. |
Rollback segments record the old values of data changed by each transaction (whether or not committed). Every database contains one or more rollback segments, which are portions of the database that record the actions of transactions in the event that a transaction is rolled back. Rollback segments provide read consistency to roll back transactions and to recover the database.
The starter database contains the following rollback segments:
The data dictionary is a protected collection of tables and views containing reference information about the database, its structures, and its users. The data stored in the dictionary includes the following:
To deinstall Oracle Internet Directory:
$ oidctl connect=<net_service_name> server=oidldapd instance=<server_instance_number> stop
where <net_service_name> is the network connection to the Oracle Internet Directory server and <server_instance_number> is the instance number. This number appears in the Server List tab of Oracle Directory Manager.
$ oidmon stop
|
 Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|