4
Post-Installation

You must perform certain post-installation steps and configure Oracle8i after completing the Oracle Universal Installer session. This chapter describes the required steps, as well as some optional ones.

• Configuration Tasks to Perform as the root User

• Configuration Tasks to Perform as the oracle User

• Post-Installation for Oracle Products

• Oracle Configuration Assistants

• Accessing Installed Documentation

• De-installing Oracle Software

  Note: 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.

Configuration Tasks to Perform as the root User

Log in as the root user and perform the following tasks:

Create Additional UNIX Accounts

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.

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

SQL> SELECT username from dba_users;

You should delete accounts you do not need.

Verify Database File Security

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 recommended file modes and ownership are as follows:

• The oracle account should have read, write, and execute privileges all files and directories in an Oracle installation.

• The oinstall group should have read, write, and execute privileges on the oraInventory directory, but should not have write permissions on anything else.

• No user outside the 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.

Table 4-1 Access Permissions on Oracle Directories and Files

Automate Database Startup and Shutdown (Optional)

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

Automating Database Startup and Shutdown

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:

1. Edit the /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.

2. Create a file named dbora in the /etc/init.d directory (if it does not already exist).

3. Create entries similar to the following at the end of the 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.6
   
   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
   
   

4. Link dbora by entering:

   # ln -s /etc/init.d/dbora /etc/rc0.d/K10dbora
   # ln -s /etc/init.d/dbora /etc/rc2.d/S99dbora      
   

Configuration Tasks to Perform as the oracle User

Perform the following tasks as the oracle user.

Update UNIX Account Startup Files

Update the startup files of the oracle account and the UNIX accounts of Oracle users.

Set Environment Variables

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 

Table 4-2 Environment Variable Settings

JRE_Location, $ORACLE_HOME/jlib, 

$ORACLE_HOME/product/jlib

LD_LIBRARY_PATH

Required when using Oracle products that use shared libraries. Set
LD_LIBRARY_PATH to include $ORACLE_HOME/lib.

ORACLE_BASE

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

ORACLE_HOME

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

ORACLE_SID

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 different operating systems.

PATH

After installation of Oracle software, the search path should include all of the following:

• $ORACLE_HOME/bin, /bin, /usr/bin, and /usr/ccs/bin

• the local bin directory specified when the root.sh script was run, usually /usr/local/bin

  Note: If you require /usr/ucb in your search path, make sure it comes after /usr/ccs/bin in the search order.

CLASSPATH

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:$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.

TNS_ADMIN

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:

1. .tnsnames.ora file in the current user's home directory (Note the dot before the file name).

2. $TNS_ADMIN/tnsnames.ora

3. /var/opt/oracle/

4. $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.

TWO_TASK

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 Adminstator's Guide and the Oracle8i Administrator's Reference for Sun SPARC Solaris for more information about net service names.

Initialize the oraenv (coraenv) Script

You have the 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.

Single-Instance Machine

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 (coraenv) 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

Multiple-Instance Machine

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.

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

Update Other Oracle User Startup Files

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:

• for .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
  
  

• Settings for the ORACLE_BASE, ORACLE_HOME, and PATH environment variables as described in "Set Environment Variables".

Update the oratab File

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.

Apply Any Required Oracle Patches

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 2 (8.1.6) CD-ROM in the cd_rom_mount_point/patch directory. Review the README file included with each patch for installation instructions.

Set Initialization Parameters

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.

Modify initsid.ora Parameters

When you create a 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.

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)

Post-Installation for Oracle Products

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 "Accessing Installed 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:

• Net8

• Oracle Internet Directory

• Oracle Enterprise Manager

• Oracle Options

• Recovery Manager

• Multi-Threaded Server

• Oracle Parallel Server Management

• Oracle Precompilers (Pro*COBOL, Pro*C/C++, Pro*FORTRAN, SQL*Module Ada)

• Oracle Supported Protocols

• Legato Storage Manager

Net8

Configuring a complete Oracle network is beyond the scope of this manual and is covered in detail in the Net8 Administrator's Guide.

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:

1. Log in as 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
   
   

   Note: 1521 is the default port. If you chose a different port when you configured the Net8 listener, specify that port in the /etc/services file.

2. Check the status of the listener following installation by using the command:

   $ 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
   
   

3. Install and configure Oracle client software on a remote system, if necessary, then start SQL*Plus to test the connection to the server.

   $ 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. For more advanced network configuration, refer to the Net8 Administrator's Guide.

Oracle Internet Directory

To complete installation of Oracle Internet Directory, you must perform the following tasks.

Start the Directory Server

See the Oracle Internet Directory Administrator's Guide for instructions on starting Oracle Internet Directory.

Configure Security

When you first install Oracle Internet Directory, the default configuration grants to all users complete access to the directory. One of the first things you will want to do is to establish and implement an access control policy to ensure that each user receives the appropriate authorization.

Also, in the process of loading directory entries, you are also creating a hierarchy of directory entries. You must establish the following:

• Permissions to load entries into this hierarchy

• Directory access to clients who need read, modify, and write access to the entries

Before attempting to add directory entries, see the chapters on SSL and managing directory access control in the Oracle Internet Directory Administrator's Guide for a detailed explanation of security options and instructions for setting up security.

Oracle Enterprise Manager

If you installed Oracle Enterprise Manager through the Oracle Management Server or Custom installation types of the Oracle8i Management Infrastructure category, 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 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".

There are further post-installation steps for Oracle Enterprise Manager that exceed the scope of this manual and are discussed in detail in the Oracle Enterprise Manager Configuration Guide.

Oracle Options

Oracle interMedia

For interMedia Text, include $ORACLE_HOME/ctx/lib in the LD_LIBRARY_PATH environment variable.

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.

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.

Configuring the Database for Oracle Options

If you install additional Oracle Options after the initial installation, use Oracle Database Configuration Assistant to configure your database for the options you install.

1. Start up the Oracle Database Configuration Assistant by executing dbassist, which is located at:

   $ORACLE_HOME/bin/dbassist
   
   

2. Select [Modify Database].

3. Select the appropriate database SID from the list of those detected by the Oracle Database Configuration Assistant. The database that you want to modify must already be running.

4. Choose the options you wish to enable from the list and click the [Finish] button.

Execute privileges will be granted to PUBLIC for all of the options and packages.

Recovery Manager

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:

1. Install Oracle8i on a separate machine from any other Oracle8i system and create a database for the recovery catalog.

   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.

2. Create a user in the recovery catalog database to be the
   RECOVERY_CATALOG_OWNER.

3. As the RECOVERY_CATALOG_OWNER, run the createCatalog command at the Oracle Recovery Manager prompt.

   See Also: For more detail on Recovery Manager, see the Oracle8i Backup and Recovery Guide.

Multi-Threaded Server

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. See Oracle8i Designing and Tuning for Performance for further information on configuring Multi-Threaded Server.

Oracle Parallel Server Management

1. To start the Oracle Parallel Server Communication Daemon automatically when the machine is rebooted, log in as the 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 entry is:

   /tmp/opsdlog
   
   

   On Sun SPARC Solaris, the startup file is /etc/init.d/dbora.

   Note: The following two steps are not necessary if Oracle Database Configuration Assistant was used to create the database

2. Determine the node numbers for all nodes of the cluster, by entering:

   $ORACLE_HOME/bin/lsnodes -n
   
   

3. Create the Oracle Parallel Server configuration file,
   $ORACLE_HOME/ops/opsname.conf, and install a copy on each node. This file contains parameters describing the configuration of Oracle Parallel Server instances and related services.

   See Also: The Oracle Parallel Server Setup and Configuration Guide.

Oracle Precompilers

Pro*C/C++

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 the Pro*C/C++ Programmer's Guide for information on how to configure this file.

Pro*COBOL

The configuration file pcbcfg.cfg is installed without content and may be configured with any text editor according to your site-specific requirements. See the Pro*COBOL Programmer's Guide for information on how to configure this file.

Pro*FORTRAN

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.

SQL*Module Ada

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 the SQL*Module for Ada Programmer's Guide for information on how to configure this file.

Oracle Supported Protocols

All Supported Protocols

Perform the following steps after installing any protocol:

1. Verify that you have created and installed the necessary configuration files for the network.

2. To start the listener automatically when the machine is rebooted, log in as the 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.

3. If you have a client/server configuration, you must set the TWO_TASK environment variable on the clients to point to the server. Set the TWO_TASK environment variable on the client machines to the service name for the server (available from the tnsnames.ora file). See "Set Environment Variables" for information on setting environment variables.

4. Start the listener on the server:

   $ lsnrctl start
   
   

5. Check the listener process:

   $ lsnrctl status
   
   

6. As the oracle user, start SQL*Plus, to test the connection:

   $ sqlplus username/password@service_name
   

SPX/IPX

Before starting the Net8 listener, start the ntisbsdm executable:

$ ntspxctl
ntspxctl> startup

The command's output confirms the status of the executable.

Configuring the Secure Socket Layer

Once the Secure Socket Layer is installed, you must run Net8 Configuration Assistant to properly configure it for your system.

Legato Storage Manager

You can install Legato Storage Manager with the Installer by running the root.sh script as described in "Run the root.sh Script". Instructions for manually installing Legato Storage Manager from the Oracle8i CD-ROM are described in "Installing Legato Storage Manager Manually".

1. After the LSM installation has completed, 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
   
   

2. Configure the driver software to provide support for Legato Storage Manager to back up data to the SCSI storage devices attached to the system. For more information, refer to the Legato Storage Manager Administrator's Guide.

Integrating SAP R/3 with Legato Storage Manager

To perform archive, backup, and recover operations, Legato Storage Manager provides a means to integrate SAP R/3 and Oracle8i backup and recovery. The backup and recovery is initiated from SAPDBA along with the SAP br-tools (brbackup, brarchive, and brrestore) with the LSM server.

On the Oracle8i software CD-ROM, the directory containing the Legato Storage Manager 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.

To set up and configure Legato Storage Manager with SAP R/3 on your system, perform the following tasks:

1. With SAP R/3 already installed, install Legato Storage Manager on your system. Follow the installation instructions in "Installing Legato Storage Manager Manually".

2. Include the pathname of the directory containing the Legato Storage Manager executables (/usr/sbin) in the PATH environment variable for the oracle user.

3. Configure a client resource for the Oracle8i server in Legato Storage Manager, according to the instructions in Chapter 2 of the Legato Storage Manager Administrator's Guide, which is included on the Oracle Online Generic Documentation CD-ROM.

4. From the subdirectory named SAP in the Legato Storage Manager directory on the Oracle8i CD-ROM, copy the backint program file into the directory where the SAP br-tools reside.

5. From the subdirectory named SAP in the Legato Storage Manager directory on the Oracle8i CD-ROM, copy the file init.utl into the directory where you installed LSM, /usr/sbin.

6. Instruct the SAP Database Administration program to use the backint program by setting the backup_dev_type parameter in the SAP initialization file, initsid.sap. In initsid.sap, set the parameter as follows:

   backup_dev_type = util_file

7. Instruct the SAP Database Administration program to use the file initsid.utl for backint-specific parameters by setting the
   util_par_file parameter in the SAP initialization file, initsid.sap.

   In initsid.sap, set the parameter as follows:

   util_par_file = ?/dbs/initsid.utl
   
   

The session report, backintsid.log, is created after the first backup session using SAP R/3 integrated with Legato Storage Manager. The report, typically located in the directory /nsr/logs, is appended to after each backup, recover, or archive.

Oracle Configuration Assistants

The following Oracle configuration assistants are described in this section:

• Net8 Configuration Assistant

• Oracle Data Migration Assistant

• Oracle Database Configuration Assistant

• Oracle Enterprise Manager Configuration Assistant

These configuration assistants are usually run during and 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 Installation and Configuration" for information on using response files with the product assistants.

Net8 Configuration Assistant

When the Net8 Server or Net8 Client is installed, the Net8 Configuration Assistant is automatically launched by Oracle Universal Installer. See "Understanding Net8 Configuration" for a description of how Net8 Configuration Assistant configures your installation.

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 install, the Net8 Configuration Assistant will automatically create a profile that is consistent with any selections you made during install. 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 your client installation.

After installation is complete, more detailed configuration can be accomplished using the Net8 Configuration Assistant with the following command:

$ netasst

For information on the use and configuration of Net8, see the Net8 Administrator's Guide.

Oracle Data Migration Assistant

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, upgrade or migrate the database prior to mounting it using Oracle8i.

You can start Oracle Data Migration Assistant with the following command:

$ odma

The process of migrating a database exceeds the scope of this manual. See Oracle8i Migration for detailed instructions and information.

Oracle Database Configuration Assistant

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 output a collection of shell scripts and SQL script 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.

You can start Oracle Database Configuration Assistant with the following command:

$ dbassist

For help invoking Oracle Database Configuration Assistant, use the -help or -h command line parameters with dbassist.

Oracle Enterprise Manager Configuration Assistant

Oracle Enterprise Manager Configuration Assistant is a tool that enables you to create, configure, drop, or upgrade the Oracle Enterprise Manager repository.

You can start Oracle Enterprise Manager Configuration Assistant with the following command:

$ emca

For detailed information about the Oracle Enterprise Manager Configuration Assistant, see the Oracle Enterprise Manager Configuration Guide.

Accessing Installed Documentation

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:

• If ORACLE_DOC is defined in the environment, the files are installed in that directory.

• If ORACLE_DOC is not defined but ORACLE_BASE is defined, the files are installed under the $ORACLE_BASE/doc directory.

• If neither ORACLE_DOC nor ORACLE_BASE are defined in the environment, the files are installed under the $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). If you prefer paper documentation, you can print the PDF files.

You can also access documentation directly from the CD-ROM as described in "Accessing Online Documentation".

Oracle Information Navigator

Oracle Information Navigator is a Java-based search and navigation utility provided with Oracle online documentation. If you are using a Java-enabled browser, Information Navigator is launched automatically when you open the index.htm file at the top level of the CD-ROM. Information Navigator can be used with Oracle documentation, whether you are reading from the CD-ROM or from installed files.

De-installing Oracle Software

If you are completely de-installing Oracle software from your system, then you must de-configure Net8 with the Net8 Configuration Assistant and remove any installed databases with the Oracle Database Configuration Assistant. Both assistants must be run before you use the Installer to completely de-install Oracle software. A partial de-installation of Oracle software does not necessarily require you to run either Oracle Database Configuration Assistant or Net8 Configuration Assistant.

To de-install an Oracle database with Oracle Database Configuration Assistant:

1. Start the Oracle Database Configuration Assistant

   $ dbassist
   
   

2. From the initial screen, select "Delete a Database."

3. Click Next.

4. Select the instance for the database that you want to delete.

5. Click Finish. Verify that you want to delete the database in the windows that appear.

Because you can only delete one database at a time, you must run Oracle Database Configuration Assistant and 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 de-install Oracle software using Oracle Universal Installer:

1. Start the Installer as described in "Using Oracle Universal Installer".

2. Click the [De-install Products] button on the "Welcome" dialog box or the [Installed Products...] button available on any Installer screen. The "Inventory" dialog box appears, listing installed products.

3. In the "Inventory" dialog box, select any product(s) to be de-installed, then click the [Remove] button.