Release 8.1.5 for Sun SPARC Solaris
A67457-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Installation Guide Release 8.1.5 for Sun SPARC Solaris A67457-01 |
|
You must perform certain post-installation steps and configure Oracle8i after completing the OUI session. This chapter describes the required steps, as well as some optional ones.
root User
Log in as the root user and perform the following tasks:
root.sh Script
The OUI creates the root.sh script in the ORACLE_HOME directory and prompts you to run the root.sh script. Log in as the root user and run the script to set the necessary file permissions for Oracle products, and perform other root-related configuration activities:
# cd $ORACLE_HOME # ./root.sh
If you have installed Oracle Parallel server, you must run the root.sh script on every node in the cluster.
The root.sh script prompts you to confirm the environment before it performs any actions. If you need to reset the environment for any reason, terminate the root.sh script. If you terminate the script, you must re-run it; you do not need to run the OUI again. Select the [OK] button on the OUI screen after root.sh runs successfully to continue the installation.
Depending on the products you installed, messages are displayed to inform you of the progress of root.sh. You might also be prompted for user names and be given additional instructions.
You will be asked by the root.sh script to specify the local bin directory. If this directory does not already exist, root.sh creates it for you.
If necessary, create additional UNIX accounts with your system administration utility (useradd). Each DBA on the system must have an account in the OSDBA group.
Sites using Oracle8i configured in a way similar to a United States NCSC C2 or European ITSEC E3 security evaluation configuration must perform this task to ensure the integrity of the Oracle software installation. This task is optional if security is not an issue.
Query the data dictionary view using SQL*Plus to list the accounts in the default database. Accounts in the database are based upon the products chosen in the OUI.
sql> SELECT username from dba_users;
You should delete accounts you do not need.
Many files must be protected to prevent unauthorized access to secure data. The recommended file modes and ownership are as follows:
oracle account should own all common system files and installation files.
Table 4-1 summarizes the directory and file permissions for different types of files. Note that these permissions are the default values and should not be changed.
Automating database startup is optional, but automatic shutdown is recommended, because it guards against improper shutdown of the database.
The dbshut and dbstart 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.
|
See Also:
Check the documentation for the |
This process must be completed for every new database that you want to have automated startup and shutdown. 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.
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.5
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
oracle User
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 shows the OUI's default values (which you might have modified). 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
|
Note:
You should not define environment variables with names that are identical to those used for Oracle processes, for example: |
The classpath is used for Java functionality. CLASSPATH is different for various products. Refer to your product documentation for more information.
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 OFA-recommended value is $ORACLE_BASE/product/release. For example: /u01/app/oracle/product/8.1.5.
Specifies the Oracle system identifier, or sid, which is the name of the Oracle Server instance. Because the sid is incorporated into many filenames, Oracle Corporation recommends restricting it to no more than four characters to avoid filename problems on heterogeneous systems.
Verify that the search path includes all of the following:
$ORACLE_HOME/bin, /bin, /usr/bin, and /usr/ccs/bin
bin directory, /usr/local/bin, created automatically by the OUI
|
Note:
If you require |
| Environment Variable | Default Setting |
|---|---|
|
LD_LIBRARY_PATH |
There is no default setting for LD_LIBRARY_PATH. Set it to include |
|
ORACLE_BASE |
|
|
ORACLE_HOME |
|
|
ORACLE_SID |
There is no default setting for ORACLE_SID. If you do not remember the value you entered, you can find it listed in the OUI log file. |
|
PATH |
There is no default setting for PATH. Make sure the new |
|
CLASSPATH |
There is no default setting, and CLASSPATH must include the following:
Note: |
oraenv (coraenv) Script
You have option of using the oraenv or coraenv scripts to set a common environment for oracle users. Follow the instructions below for a single-instance or multiple-instance configuration for the oraenv script, or the coraenv script if you are running the C shell.
On a single-instance machine, include the following commands to initialize the oraenv (coraenv) file at the end of the .profile or .login file of the oracle account.
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 (coraenv) file at the end of the startup file of the oracle account. The value of ORACLE_SID you defined before the OUI session is the default instance name.
For the Bourne or Korn shell:
#!/bin/sh SIDLIST=`awk -F: '/^[^#]/{printf "%s",$1} '/var/opt/oracle/oratab`
echo "SIDs on this machine are $SIDLIST"
ORAENV_ASK=
. /usr/local/bin/oraenv
For the C shell:
set sidlist=`awk -F: '/^[^#]/{printf"%s",$1} '/var/opt/oracle/oratab`
echo "SIDs on this machine are $sidlist"
unset ORAENV_ASK sidlist
source /usr/local/bin/coraenv
To create the same environment for all Oracle users, update each user startup file to include:
ORACLE_HOME/bin in the PATH statement
. /usr/local/bin/oraenv
(or source /usr/local/bin/coraenv for C shell users)
oratab File
If you have created a database manually instead of using the Database Configuration Assistant (DBCA), 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. The DBCA 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 Product CD-ROM in the /cd_rom_mount_point/patch directory. Review the README file included with each patch for installation instructions.
The default initsid.ora file shipped with the distribution is located in the $ORACLE_BASE/admin/sid/pfile directory. A template initsid.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.
initsid.ora Parameters
When you create a database using DBCA 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.
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)
|
See Also:
Oracle8i Administer's Reference for Sun SPARC Solaris for information on |
Perform the product-specific steps as necessary for your installation. Not all products require post-installation setup.
To access online documentation before you configure your Oracle installation, see the instructions for accessing that documentation. 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:
If you intend to install Oracle interMedia Text, ensure you have at least 10 MB of disk space for the data dictionary.
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.
dbassist, which is located at:
$ORACLE_HOME/bin/dbassist
Execute privileges will be granted to PUBLIC for all of the options and packages.
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.
|
Note: Recovery Manager can also be used in a restricted mode without a recovery catalog, if the installation and maintenance of a second Oracle8i database is impractical. |
Perform the following steps if you want to create a recovery catalog:
If you choose not to write a custom script to create the database, create the default database with the OUI. The default database is adequate for the recovery catalog.
createCatalog command at the Recovery Manger prompt.
Servers configured with MTS require a higher setting for the initialization parameter SHARED_POOL_SIZE or a custom configuration that uses LARGE_POOL_SIZE. The value of SHARED_POOL_SIZE will be set for you automatically by the Oracle Database Configuration Assistant if you installed your server with the OUI. 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. See Oracle8i Tuning for further information on configuring MTS.
root user and add a line similar to the following in the system startup file:
su - oracle -c "opsd log=/tmp/opsd.log"
The above entry is optional, the default is:
/tmp/opsdlog
On Sun SPARC Solaris, the startup file is /etc/init.d/dbora.
$ORACLE_HOME/opsm/utl/getnodelist -a"
$ORACLE_HOME/ops/opsname.conf, and install on each node. This file contains parameters describing the configuration of OPS instances and related services.
|
See Also:
For more information, refer to the Oracle Parallel Server Management Configuration Guide for UNIX. To view this document, point your browser to |
The configuration file pcscfg.cfg in $ORACLE_HOME/precomp/admin 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. See your SPARCworks/workshop C compiler documentation to determine how to configure this file.
|
See Also:
The Programmer's Guide to the Pro*C/C++ Precompiler for further information on configuring the |
The configuration file is pcbcfg.cfg. For This file is installed without content and may be configured with any text editor according to your site- specific requirements. See your Micro Focus COBOL documentation to determine how to configure this file.
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. See you FORTRAN77 documentation to determine how to configure this file.
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 your Sun Ada 2.1 documentation to determine how to configure this file.
Configuring a complete Oracle network is beyond the scope of this manual, and is covered in detail in the Net8 Administrator's Guide. When the Net8 Server or Net8 Client is installed, the Net8 Configuration Assistant is automatically launched to complete initial configuration of Net8 as follows:
sqlnet.ora and a listener called listener with a listening endpoint that is consistent with any protocol support selections you made. In most cases, this results in listening on protocol TCP/IP using port number 1521. In all but the most complicated environments this will be the only listener you will ever need to configure. The listener will be started automatically by the Net8 Configuration Assistant. If you wish to check the status of the listener following installation you can do so by using the command:
$ lsnrctl status
If the listener is not running, start it up:
$ lsnrctl start listener
root and reserve a port for the Net8 listener by making the following entry in the /etc/services file:
listener 1521/tcp #Net8 listener
If you create a database using the Database Configuration Assistant during or after installation, it will automatically update the listener configuration with any necessary configuration information for this new database. This file can then be distributed to any client machines to connect to the Oracle8i database.
If you choose to do a separate Oracle8i client install, the Net8 Configuration Assistant will automatically create a profile that is consistent with any selections you made during install. The OUI will automatically run the Net8 Easy Configuration wizard which assists you in configuring a net service name in the Local Naming file located in the $ORACLE_HOME/network/admin directory of your client installation.
After installation is complete more detailed configuration can be accomplished using the Net8 Assistant by executing:
$ netasst
Net8 Easy Configuration is also available by executing:
$ netec
For information on the use and configuration of Net8 please refer to the Net8 Administrator's Guide.
tnsnames.ora file, append its contents to existing tnsnames.ora files in the $ORACLE_HOME/network/admin directories of client machines.
$ sqlplus username/password@service_name
At this point you have established network connectivity over TCP/IP. For more advanced network configuration, refer to the Net8 Administrator's Guide.
Legato Storage Manager installation through the OUI is done via the root.sh script as described in "Run the root.sh Script" .
root.sh has completed the LSM installation, verify that all the required packages were installed:
# pkginfo | grep -i LSM application ORCLclnt LSM (Backup/Recover) Client system ORCLdrvr LSM (Backup/Recover) Device Drivers application ORCLman LSM (Backup/Recover) Man Pages application ORCLnode LSM (Backup/Recover) Storage Node application ORCLserv LSM (Backup/Recover) Server
Legato Storage Manager (LSM) provides a means to integrate SAP R/3 and Oracle8 backup and recovery initiated from SAPDBA along with the SAP br-tools (brbackup, brarchive, and brrestore) with the LSM server to perform archive, backup, and recover operations.
On the Oracle software CD-ROM, the directory containing the LSM software has a subdirectory named SAP with the following files for SAP R/3 on Oracle:
backint - SAP API that integrates SAP R/3 backup and recovery with third-party utilities
init.utl - Parameter file that specifies the variables used by backint during backup, recover, and archive operations
README - Text file that describes the SAP R/3 files and where to install them
You can follow these steps to set up and configure LSM with SAP R/3 on Oracle:
/usr/sbin, in the PATH environment variable for the Oracle user, oraoracle_sid.
SAP in the LSM directory on the Oracle CD-ROM, copy the backint program file into the directory where the SAP br-tools reside.
SAP in the LSM directory on the Oracle CD-ROM, copy the file init.utl into the directory where you installed LSM, /usr/sbin.
backint program by setting the backup_dev_type parameter in the SAP initialization file, initoracle_sid.sap. In initoracle_sid.sap, set the parameter as follows:
backup_dev_type = util_file
initoracle_sid.utl for backint-specific parameters by setting the util_par_file parameter in the SAP initialization file, initoracle_sid.sap.
In initoracle_sid.sap, set the parameter as follows:
util_par_file = ?/dbs/initoracle_sid.utl
The session report, backintoracle_sid.log, is created after the first backup session using SAP R/3 integrated with LSM. The report, typically located in the directory /nsr/logs, is appended to after each backup, recover, or archive.
Oracle Names Server is installed automatically with Net8. If you want to configure your network to use Oracle Names Server, do the following:
sqlnet.ora and names.ora.
/etc/hosts file of all network nodes.
$ namesctl startup
$ namesctl status
Perform the following steps after installing any protocol:
root user and add a line similar to the following in the system startup file:
su - oracle -c "lsnrctl start"
On Sun SPARC Solaris, the startup file is /etc/init.d/dbora.
tnsnames.ora file).
$ lsnrctl start
$ lsnrctl status
oracle user, start SQL*Plus, to test the connection:
$ sqlplus username/password@service_name
Start the ntisbsdm executable before starting the Net8 listener:
$ ntspxctl ntspxctl> startup
Command output confirms the status of the executable.
Once the Secure Socket Layer (SSL) is installed, you must run Net8 Configuration Assistant to properly configure it for your system.
You can install documentation in HTML and PDF (Adobe Portable Document Format, which requires Acrobat Reader) formats. Solaris-specific documentation files are installed from the Oracle8i CD-ROM. Generic documentation files are installed from the Online Generic Documentation CD-ROM. The location of the documentation files is determined according to the following rules:
$ORACLE_BASE/doc directory.
$ORACLE_HOME/doc directory.
To access the documentation, point your browser to either index.htm or products.htm (the latter does not a require a frames-enabled browser). You can print the PDF files, if you prefer paper documentation.
You can also access documentation directly from the CD-ROM.
|
See Also:
Information on accessing documentation directly from CD-ROM is contained in the CD-ROM insert. |
Information Navigator is a Java-based search and navigation utility provided on the Oracle Documentation CD-ROM. If you are using a Java-enabled browser, Information Navigator is launched automatically when you open the index.htm file. Information Navigator can be used with Oracle documentation, whether you are reading from CD-ROM or from installed files.
|
 Copyright © 1999 Oracle Corporation. All Rights Reserved. |
|