Release 3 (8.1.7) for Sun SPARC Solaris
Part Number A85471-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Installation Guide Release 3 (8.1.7) for Sun SPARC Solaris Part Number A85471-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.
This chapter describes basic configuration only. The more sophisticated configuration and tuning typically required for production systems is described in the Oracle8i Administrator's Reference for Sun SPARC Solaris and in product administration and tuning guides.
Note:
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 Oracle8i 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 must be protected 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, "Access Permissions on Oracle Directories and Files", 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). Be sure to 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
After installing Oracle8i, the Apache account access to oraInventory needs to be removed in order to protect database security. Perform the following tasks:
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 "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 the root.sh script was run, 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/rt.jar:$ORACLE_HOME/jlib/<product jar file>:$ORACLE_HOME/product/jlib/<product jar file>
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 Sun SPARC Solaris 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.
The Oracle8i release, which this manual accompanies, includes patches that must be applied to Oracle8i or other products. Patches can be found on the Oracle8i Release 3 (8.1.7) CD-ROM in the cd_rom_mount_point/patch directory. Review the README file included with each patch for installation instructions.
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 may 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)
Perform the product-specific steps as necessary for your installation. Not all products require post-installation setup.
To review online documentation before you configure your Oracle products, see "De-installing Oracle Software". It is not necessary to read product documentation before completing the configuration tasks in this manual, but more sophisticated tuning requires information in the product documentation.
The following products have post-installation steps:
Oracle servers configured with Multi-Threaded Server require a higher setting for the initialization parameter SHARED_POOL_SIZE or a custom configuration that uses LARGE_POOL_SIZE. If you installed your server with Oracle Universal Installer, the value of SHARED_POOL_SIZE is set for you automatically by Oracle Database Configuration Assistant. However, if you created a database manually you should raise SHARED_POOL_SIZE in the initsid.ora file. Typically, you should add 1 KB for each anticipated concurrent user.
Basic configuration of Net8 is done by Net8 Configuration Assistant when it is invoked by Oracle Universal Installer during installation of Net8. For an explanation of how Net8 Configuration Assistant configures your installation, see "Understanding Net8 Configuration". For information on running Net8 Configuration Assistant as a stand-alone tool, see "Net8 Configuration Assistant".
Verify and complete your initial configuration with the following steps:
root and reserve a port for the Net8 listener by making the following entry in the /etc/services file:
listener_name 1521/tcp #Net8 listener
$ lsnrctl status [listener_name]
The listener_name field is required if the listener has a name other than the default, listener.
If the listener is not running, start it with the following command:
$ lsnrctl start listener_name
$ sqlplus username/password@net_service_name
If you can successfully connect to the server with SQL*Plus, you have established network connectivity over TCP/IP.
The following Oracle configuration assistants are described in this section:
These configuration assistants are usually run during an installation session, but can also be run in a stand-alone mode. Like Oracle Universal Installer, each of these assistants can also be run non-interactively using a response file. See "Non-Interactive ("Silent") Installation and Configuration" for information on using response files with the product assistants.
When the Net8 Server or Net8 Client is installed, the Net8 Configuration Assistant is automatically launched by Oracle Universal Installer.
If you create a database using the Oracle Database Configuration Assistant during or after installation, it will automatically update the Net8 configuration with any configuration information necessary for the new database. Oracle Database Configuration Assistant either registers the database in a supported directory service so that clients can use the directory to connect to the database, or it will create an entry in the local naming file (tnsnames.ora) that can then be distributed to client machines to connect to the database.
If you choose to do a separate Oracle8i Client installation, the Net8 Configuration Assistant will automatically create a profile that is consistent with any selections you made during the installation. The Installer will automatically run the Net8 Configuration Assistant to set up a net service name in the Local Naming file found in the $ORACLE_HOME/network/admin directory of the client installation.
After installation is complete, more detailed configuration can be accomplished using the Net8 Configuration Assistant with the following command:
$ netasst
|
See Also:
See "Understanding Net8 Configuration" for a description of how Net8 Configuration Assistant configures your installation. For information on the use and configuration of Net8, see the Net8 Administrator's Guide. |
If you have installed Oracle8i to use with an existing database from a prior software release, and you did not choose to upgrade the database during the installation, you need to upgrade or migrate the database before mounting it.
|
See Also:
The process of migrating a database exceeds the scope of this manual. See Oracle8i Migration for detailed instructions and information. |
Oracle Database Configuration Assistant can create a default or customized database or it can be used to configure an existing database to use Oracle options. The assistant can create the database or present a collection of shell and SQL scripts which you can inspect, modify, and run at a later time. See "Identifying Your Database Environment" for information on the types of databases that you can install using Oracle Database Configuration Assistant.
Start Oracle Database Configuration Assistant with the following command:
$ dbassist
For help with the Oracle Database Configuration Assistant, use the -help or -h command line parameters with dbassist.
$ dbassist -help
Oracle Corporation recommends running the UTLRP.SQL script after creating, upgrading, or migrating a database. This script recompiles all PL/SQL modules that may be in an INVALID state, including packages, procedures, types, and so on. This step is optional, but recommended so that the cost of recompilation is incurred during the installation rather than in the future.
$ SQLPLUS
SYS account:
SQL> CONNECT SYS/PASSWORDAS SYSDBA
where PASSWORD is CHANGE_ON_INSTALL by default, unless it was changed after installation.
SQL> STARTUP
Run the UTLRP.SQL script:
SQL> @ORACLE_BASE/ORACLE_HOME/RDBMS/ADMIN/UTLRP.SQL
Oracle Enterprise Manager Configuration Assistant is a tool that enables you to create, configure, drop, or upgrade the Oracle Enterprise Manager repository.
|
See Also:
For detailed information about the Oracle Enterprise Manager Configuration Assistant, see the Oracle Enterprise Manager Configuration Guide. |
If you installed Oracle Enterprise Manager Server through the Oracle8i Management Infrastructure, Custom installation, or Custom Management Infrastructure types, Oracle Enterprise Manager Configuration Assistant will automatically start at the end of the installation to guide you through repository configuration. If you installed Oracle Enterprise Manager through any other installation type, Oracle Enterprise Manager Configuration Assistant will not start automatically at the end of the installation.
Manually start Oracle Enterprise Manager Configuration Assistant after installation if a repository needs to be created configured, upgraded, or dropped.For information on running Oracle Enterprise Manager Configuration Assistant as a stand-alone tool, see "Oracle Enterprise Manager Configuration Assistant".
Carry out the following task after installation:
If you install additional Oracle Options after the initial installation, use Oracle Database Configuration Assistant to configure your database for the options you install.
dbassist, which is located at:
$ORACLE_HOME/bin/dbassist
Execute privileges will be granted to PUBLIC for all of the options and packages.
If you intend to install Oracle interMedia Text after your initial installation, ensure you have at least 10 MB of disk space for the data dictionary.
For interMedia Text, include $ORACLE_HOME/ctx/lib in the LD_LIBRARY_PATH environment variable.
Your database must include tablespaces specific to interMedia Text data. Verify that tablespaces exist to serve as default and temporary tablespaces for Oracle interMedia Text. Oracle interMedia Text uses the DRSYS tablespace for its default and temporary tablespaces. If tablespaces for Oracle interMedia Text do not exist or you do not want to use the DRSYS tablespace, create additional tablespaces before proceeding.
root user and add a line similar to the following in the /etc/init.d/dbora system startup file:
su - oracle -c "opsd log=/tmp/opsd.log"
The above entry is optional. The default entry is:
/tmp/opsdlog
$ORACLE_HOME/bin/lsnodes -n
$ORACLE_HOME/ops/opsname.conf, and install a copy to each node.
This file contains parameters describing the configuration of Oracle Parallel Server instances and related services.
All precompiler configuration files are located in the following location:
$ORACLE_HOME/precomp/admin
The configuration file pcscfg.cfg must be customized for your environment before using Pro*C/C++. This file is installed without content and may be configured with any text editor according to your site-specific requirements.
The configuration file pcbcfg.cfg is installed without content and may be configured with any test editor according to your site-specific requirements.
The configuration file is pccfor.cfg. This file is installed without content and may be configured with any text editor according to your site-specific requirements.
.
The configuration file is pmscfg.cfg. This file is installed without content and may be configured with any text editor according to your site-specific requirements.
|
See Also:
See the SQL*Module for Ada Programmer's Guide for information on how to configure this file. |
Perform the following steps after installing any protocol:
|
Note:
This procedure fails if the TNS_ADMIN environment variable is not set or if |
root user and add a line similar to the following in the /etc/init.d/dbora system startup file:
su - oracle -c "lsnrctl start"
tnsnames.ora file). See "Configuration Environment Variables" for information on setting environment variables.
$ lsnrctl start
$ lsnrctl status
oracle user, start SQL*Plus, to test the connection:
$ sqlplus username/password@service_name
Recovery Manager is an automated recovery utility that is installed as part of Oracle8i. It stores information in a recovery catalog in a separate Oracle8i database. This second Oracle8i database should be installed on a separate machine to provide maximum fault resistance.
To create a recovery catalog, perform the following steps:
If you do not to write a custom script to create the database, create a typical, preconfigured database with Oracle Database Configuration Assistant. The default database is adequate for the recovery catalog.
RECOVERY_CATALOG_OWNER.
RECOVERY_CATALOG_OWNER, run the createCatalog command at the Oracle Recovery Manager prompt.
Once the Secure Socket Layer is installed, you must run Net8 Configuration Assistant to properly configure it for your system.
This section describes the user names and passwords included in the starter database. The SYS, SYSTEM, and DBSNMP user names and INTERNAL alias passwords in the following table are automatically included in all databases created by Oracle Database Configuration Assistant.
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, although you had the opportunity to change it. 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 are used to 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:
A complete de-installation of Oracle software requires you to remove any installed databases with the Oracle Database Configuration Assistant and de-configure Net8 with the Net8 Configuration Assistant. Both assistants must be run before you use the Installer to completely de-install Oracle software. The Oracle Internet Directory Control Utility and Oracle Internet Directory Monitor must be stopped before de-installation of Oracle Internet Directory. In addition, before beginning de-installation, the Apache account primary GID must be changed to the group that owns oraInventory. A partial de-installation of Oracle software does not necessarily require you to run either Oracle Database Configuration Assistant or Net8 Configuration Assistant.
$ dbassist
Because you can only delete one database at a time, you must repeat these steps for each database that you want to delete.
After you have run Oracle Database Configuration Assistant, run the Net8 Configuration Assistant in de-install mode by invoking it at the command line with the /deinst parameter:
$ netca /deinst
To deinstall Oracle Internet Directory Services:
$ 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 © 1996-2000, Oracle Corporation. All Rights Reserved. |
|