4
Post-Installation

Creating Additional UNIX Accounts

If necessary, create additional UNIX accounts. Users must be members of the OSDBA or OSOPER groups to connect to the database with administrator privileges.

Verifying Database File Security

If you configure Oracle9i database in a way similar to the United States NCSC C2 or European ITSEC E3 security evaluation configuration, then verify database file security to ensure the integrity of the Oracle software installation. This task is optional if security is not an issue.

To prevent unauthorized access to secure data, you must protect your files. The file privileges and recommended ownership are as follows:

• The oracle account should have read, write, and execute privileges for all files and directories in the Oracle9i installation.

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

• No user other than the oracle user or the ORAINVENTORY group should have write access on any files or directories in the Oracle9i installation.

Table 4-1 summarizes the directory and file permissions for different types of files.

Table 4-1 Access Permissions on Oracle Directories and Files

Changing Group Membership of the Apache User

After installing the Oracle9i database, the APACHE account access to the oraInventory directory needs to be removed in order to ensure database security. Perform the following tasks:

1. Create a new group to which no other group or user has access.

2. Assign ownership of this group to Apache.

3. Change the APACHE account primary Group Identifier (GID) from the one that has ownership of the oraInventory directory (typically ORAINVENTORY) to the new group name.

Automating Database Startup and Shutdown for HP, Linux and Solaris (Optional)

Oracle Corporation recommends that you configure your system to automatically start Oracle databases when your system starts up, and to shut down Oracle databases when your system shuts down. Automatic database startup and shutdown protects 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 the dbstart script automatically start up databases sid1, sid2, and sid3, and the dbshut script shut down only databases sid1 and sid2. You can, however, specify that the dbshut script shut down a set of databases while the dbstart script is not used at all. To do this, include a dbshut entry in the system shutdown file but omit the dbstart entry from the system startup files.

Perform the following tasks to set up the dbstart and dbshut scripts so that they are called at system startup. This process must be completed for every new database that you want to configure for automated startup and shutdown.

1. Edit the /var/opt/oracle/oratab file for Solaris and /etc/oratab file for HP and Linux.

   Database entries in the oratab file appears in the following format:

   ORACLE_SID:ORACLE_HOME:{Y|N}
   

   In the preceding command, Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database. For each database that you want to start up, find the ORACLE_SID entry identified by the sid in the first field. Change the last field for each to Y.

   For Oracle Real Application Clusters installation, this entry appears in the following format:

   DB_NAME:ORACLE_HOME:{Y|N}
   
   

   In the preceding command, DB_NAME is the cluster database name. Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database.

2. In the /etc/init.d directory, create a dbora script similar to the following, if it does 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/9.2.0.1.0
   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
   
   

3. Create symbolic links to the dbora script in the appropriate run-level script directories, as follows:

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

Automating Database Startup and Shutdown for AIX (Optional)

Oracle Corporation recommends that you configure your system to automatically start Oracle databases when your system starts up, and to shut down Oracle databases when your system shuts down. Automatic database startup and shutdown protects against improper shutdown of the database.

Automating Database Startup

Perform the following tasks to set up the dbstart and dbshut scripts so that they are called at system startup. This process must be completed for every new database that you want to configure for automated startup:

1. Edit the /etc/oratab file.

   Database entries in the oratab file appears in the following format:

   ORACLE_SID:ORACLE_HOME:{Y|N}
   
   

   In the preceding command, Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database.

   For Oracle Real Application Clusters installation, this entry appears in the following format:

   DB_NAME:ORACLE_HOME:{Y|N}
   
   

   In the preceding command, DB_NAME is the cluster database name. Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database.

2. For each database that you want to start up, find the ORACLE_SID entry identified by the sid in the first field. Change the last field for each to Y.

3. Add the dbstart script to the /etc/inittab file:

   # mkitab "oradb:2:wait:/bin/su oradb -c|/$ORACLE_HOMES/bin/dbstart"
   
   

   In the preceding command, oradb is the identifier of the oracle user for which you want to start the database.

Automating Database Shutdown

Automate database and system shutdown by creating a script, shut, to start dbshut and the system executable /etc/shutdown. Complete the following steps to create the script:

1. If you have not already done so, edit the database entries of your /etc/oratab file to enable dbstart and dbshut, as described in step 1 of the dbstart instructions.

2. As root, create the shut shell script:

   # cd /etc
   cat > shut << EOF
   ? su oracle_owner -c /usr/oracle/bin/dbshut
   ? /etc/shutdown $* \
   ? [Ctrl-D]
   # chmod u+x shut
   
   

3. Execute the following command to run the shut script and shut down the database:

   # /etc/shut -h now
   
   

This closes Oracle databases and shuts down the system with the specified options.

Automating Database Startup and Shutdown for Tru64 (Optional)

This process must be completed for every new database that you want to configure for automated startup and shutdown. Perform the following tasks to start up and shut down listeners and set up the dbstart and dbshut scripts so that they are called at system startup:

1. Log in as root user.

2. Edit the /etc/oratab file.

   Database entries in the /etc/oratab file appear in the following format:

   ORACLE_SID:ORACLE_HOME:{Y|N}
   
   

   In the preceding command, Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database.

   For Oracle Real Application Clusters installation, this entry appears in the following format:

   DB_NAME:ORACLE_HOME:{Y|N}
   
   

   In the preceding command, DB_NAME is the cluster database name. Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database.

3. For each database that you want to start up, find the ORACLE_SID entry identified by the sid in the first field. Change the last field for each to Y.

4. Change directory to /sbin/init.d.

5. Create a file named oracle, and use chmod to set the privileges to 750.

   
   

   Note: This script assumes that a password is not set for the listener. If a password is set, the listener will not be stopped. The ORACLE_HOME and ORACLE variables are examples. Use information as appropriate for your installation.

   
   

6. Add the following contents to the /sbin/init.d/oracle file:

   #!/bin/sh
   #
   # change the value of ORACLE_HOME to be correct for your
   # installation
   ORACLE_HOME=/opt/oracle/product/9.2.0.1.0
   PATH=${PATH}:$ORACLE_HOME/bin
   HOST='hostname'
   #
   # change the value of ORACLE to the login name of the
   # oracle owner at your site
   #
   ORACLE=oracle
   export ORACLE_HOME PATH
   #
   if [ ! "$2" = "ORA_DB" ] ; then
       rsh $HOST -l $ORACLE /sbin/init.d/oracle $1 ORA_DB
       exit
   fi
   #
   LOG=$ORACLE_HOME/startup.log
   touch $LOG
   chmod a+r $LOG
   #
   
   case $1 in
   'start')
           echo "$0: starting up" >> $LOG
           date >> $LOG
           # Start Oracle Net
           if [ -f $ORACLE_HOME/bin/tnslsnr ] ;
           then
                   echo "starting Oracle Net listener"
                   $ORACLE_HOME/bin/lsnrctl start >> $LOG 2>&1 &
           fi
           echo "starting Oracle databases"
           $ORACLE_HOME/bin/dbstart >> $LOG 2>&1
           ;;
   'stop')
           echo "$0: shutting down" >> $LOG
           date >> $LOG
           # Stop Oracle Net
           if [ -f $ORACLE_HOME/bin/tnslsnr ] ;
           then
                   echo "stopping Oracle Net listener"
                   $ORACLE_HOME/bin/lsnrctl stop >> $LOG 2>&1
           fi
           echo "stopping Oracle databases"
           $ORACLE_HOME/bin/dbshut >> $LOG 2>&1
           ;;
   *)
           echo "usage: $0 {start|stop}"
           exit
           ;;
   esac
   #
   exit
   

7. Change the .rhosts file in the oracle user login home directory to allow root login access to the account.

   your_host_name root
   
   

8. Link files into the startup and shutdown directories by using the 'ln -s' command.

   # ln -s /sbin/init.d/oracle /sbin/rc3.d/S99oracle
   # ln -s /sbin/init.d/oracle /sbin/rc0.d/K01oracle
   
   

   This file automatically starts and stops Oracle9i when the system is started or stopped.

Updating UNIX Account Startup Files

Update the startup files of the oracle user and the UNIX accounts of oracle users.

Setting Environment Variables

Set the following environment variables in the.profile or.login file of the oracle user before using Oracle9i products. The settings that you use here should correspond to the settings 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 describes the Environment Variable Settings.

Table 4-2 Environment Variable Settings

$ORACLE_BASE/product/release

ORACLE_BASE variable is:
/u01/app/oracle, then the ORACLE_HOME variable would be:
/u01/app/oracle/product/9.2.0.1.0

$ORACLE_HOME/jlib/<product jar file>:
$ORACLE_HOME/product/jlib/product_jar_file 

Initializing the oraenv Script

You can use the oraenv script to set a common environment for Oracle software users.

ORAENV_ASK=NO
. /usr/local/bin/oraenv

set ORAENV_ASK = NO
source /usr/local/bin/coraenv
unset ORAENV_ASK

#!/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

#!/bin/sh
echo "The SIDs on this machine are:"
cat /etc/oratab | awk -F: '{print $1}' | grep -v "#"
ORAENV_ASK="YES"
. /usr/local/bin/oraenv

#!/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

#!/usr/bin/csh
echo "The SIDs on this machine are:"
cat /etc/oratab | awk -F: '{print $1}' | grep -v "#"
set ORAENV_ASK="YES"
source /usr/local/bin/coraenv

ORACLE_SID:ORACLE_HOME:{Y|N}

DB_NAME:ORACLE_HOME:{Y|N}

Backing Up the root.sh Script

Oracle Corporation recommends that you back up the root.sh script after a successful product installation. If you install another product category later into the same Oracle home directory, then the Oracle Universal Installer replaces the contents of the existing root.sh script during the installation. If after a later installation you require information from the original root.sh script, then you can recover it from the backed up root.sh file.

For example, if you install Oracle9i Management Infrastructure into the same Oracle home directory as a successful Oracle9i Server installation, then the Oracle Universal Installer replaces the contents of the existing root.sh script during the installation. Backing up the root.sh file after each product installation insures that you have all root.sh files available for reference if necessary.

Setting Initialization Parameters

When you create a typical startup database using Database Configuration Assistant, the initsid.ora parameters are automatically set. Change initialization parameters to configure and tune the system for optimal performance. The default initsid.ora file is located in the $ORACLE_BASE/admin/sid/pfile directory. A template init.ora file is also in the $ORACLE_HOME/dbs directory. The file contains settings for small, medium, and large databases, with the settings for medium and large databases commented out in the file. The size settings are relative to each other, but do not represent an empirical size of the database.

Manually modify the initialization parameters in the initsid.ora file with a UNIX text editor. To activate the modified initsid.ora file, shut down and restart the database.

Oracle Corporation recommends that you do not use symbolic character representations such as question marks (?) for the ORACLE_HOME environment variable in parameter files, as they might lead to startup errors.

To bring rollback segments online automatically with database startup, uncomment the rollback_segments command in the initsid.ora file.

For example, change:

# rollback_segments = (r0, r1, r2, r3)

to:

rollback_segments = (r0, r1, r2, r3)

Configuring Shared Server Parameters

Oracle servers configured with Shared Server require a higher setting for the SHARED_POOL_SIZE initialization parameter, or a custom configuration that uses the LARGE_POOL_SIZE initialization parameter. If you installed your server with Oracle Universal Installer, then the value of the SHARED_POOL_SIZE parameter is set automatically by Database Configuration Assistant. However, if you created a database manually, increase the SHARED_POOL_SIZE parameter in the initsid.ora file. Typically, you should add 1 KB for each concurrent user.

Post-Upgrade Tasks for Oracle Internet Directory

Perform the following post-upgrade tasks for Oracle Internet Directory:

• Job Queue Processes Parameter in init.ora file

• Default Subscriber Configuration

Set the Job Queue Process parameter in the init.ora file of the database to the following values:

• For single-node, set the parameter to at least 1.

• For multi-node, set the parameter to (Number of nodes - 1)

Perform the following tasks for single-node and multi-node upgrades.

The following information needs to be added to the root Oracle Context in the entry identified by the following DN "cn=Common, cn=Products, %RootOracleContextDN%". By default, the RootOracleContextDN is "cn=OracleContext". Table 4-5 lists the attributes in the Root Oracle Context.

Table 4-5 Attributes in the Root Oracle Context

The following information needs to be added in the subscriber-specific Oracle Context in the entry identified by the following DN "cn=Common, cn=Products, cn=oracleContext, <subscriber DN>." Table 4-6 lists the attributes in the Default Subscriber Oracle Context.

Table 4-6 Attributes in the Default Subscriber Oracle Context

If the password policy exists in the earlier version of Oracle Internet Directory (located under the DN "cn=pwdpolicyentry, cn=Oracle Internet Directory"), then this policy will be applied to both the Root Oracle Context and the default Subscriber Oracle Context. The original DN containing the policy "cn=pwdpolicyentry, cn=Oracle Internet Directory" will be removed from the earlier version. Otherwise, the default password policy is set up as part of the Subscriber Oracle Context creation. By default, the password policy for the default subscriber is set to the following values:

• The user passwords expire in 60 days (pwdmaxage=5184000)

• The account is locked out after 10 successive failed login attempts (pwdlockout=1 and pwdmaxfailure=10)

• Password syntax checking is enabled and the minimum length of user passwords is five (pwdchecksyntax=1 and pwdminlength=5)

• User passwords must contain at least one numeric character (orclpwdalphanumeric=1).

Configuring Oracle Net Services

Basic configuration of Oracle Net Services is done by Oracle Net Configuration Assistant when it is started by Oracle Universal Installer during installation.

Verify and complete your initial configuration with the following steps:

1. Log in as root and reserve a port for the Oracle Net listener by making the following entry in the /etc/services file of each Oracle Net Services node on the network:

   listener_name 1521/tcp                   #Oracle Net listener
   
   

   In the preceding command, 1521 is the default port number. If you chose a different port when you configured the Oracle Net listener, specify that port in the /etc/services file.

2. Check the status of the listener following the installation by using the following 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 by using 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.

Configuring Oracle Messaging Gateway

Perform the following post-installation tasks before running the Oracle Messaging Gateway.

• Load Database Objects into the Database

• Modify listener.ora file for External Procedure for Linux, Solaris 32-bit, and Tru64

• Modify listener.ora file for External Procedure for AIX, HP, and Solaris 64-bit

• Modify tnsnames.ora file for External Procedure

• Modify mgw.ora file for External Procedure

• Create Users

• Installation Verification for Oracle Messaging Gateway

CREATE USER <admin_user> IDENTIFED BY <admin_password>;
GRANT CONNECT, RESOURCE to <admin_user>;
GRANT MGW_ADMINISTRATOR_ROLE to <admin_user>;

CREATE USER <agent_user> IDENTIFED BY <agent_password>;
GRANT CONNECT, RESOURCE to <agent_user>;
GRANT MGW_AGENT_ROLE to <agent_user>;

connect <admin_user>/<admin_password>
exec dbms_mgwadm.db_connect_info('<agent_user>','<agent_password>',  '<agent_database>');

connect <admin_user>/<admin_password>;
exec dbms_mgwadm.db_connect_info ('<agent_user>', '<agent_password>', '<agent_database>';

Running Oracle Configuration Assistants As Standalone Tools

Configuration Assistants are usually run during an installation session, but can also be run in stand-alone mode. As with Oracle Universal Installer, each of these assistants can also be run non-interactively using a response file. The following Oracle configuration assistants are described in this section:

• Using Oracle Net Configuration Assistant

• Using Database Upgrade Assistant

• Using Database Configuration Assistant

• Configuring New or Upgraded Databases

• Using Oracle Enterprise Manager Configuration Assistant

  
  

  See Also: "Non-Interactive Installation and Configuration" for more information on using response files with the product assistants.

  
  

$ netca

$ dbua

$ dbua -help

$ dbca

$ dbca -help

Configuring the Database for Additional Oracle Products

If you install additional Oracle products after the initial installation, use the Database Configuration Assistant to configure your database for the new products. The database must be running.

1. Start up the Database Configuration Assistant by using the dbca command located in the $ORACLE_HOME/bin/ directory:

   $ dbca
   
   

2. Select Configure Database option in a database.

3. Select the appropriate database SID from the list of those detected by the Database Configuration Assistant.

4. Choose the products you wish to enable from the list and click Finish.

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

Configuring Oracle Real Application Clusters

The following sections contain post-installation instructions for Oracle Real Application Clusters:

• Managing Oracle Real Application Clusters

• Re-installing Oracle Real Application Clusters

• Inspecting Oracle Real Application Clusters Configuration for Linux

su - oracle -c $ORACLE_HOME/bin/gsd

Configuring Oracle Label Security

If Oracle9i software is already installed and a database is created, then verify that the COMPATIBLE initialization parameter is set to 9.2.0.1.0 or higher.

Configuring Oracle Precompilers

All precompiler configuration files are located in the
$ORACLE_HOME/precomp/admin directory. Table 4-7 describes the Oracle Precompilers.

Table 4-7 Oracle Precompilers

pcscfg.cfg

pcbcfg.cfg

pcccob.cfg

pccfor.cfg

pmscfg.cfg

Configuring Oracle Workflow

You must perform a number of configuration procedures for Oracle Workflow. These include the following:

• Edit the init.ora parameter file

• Install and configure a web server

• Verify your base URL

• Set up the Oracle Workflow Monitor and HTML help

  
  

  See Also: Oracle Workflow Server Installation Notes, Oracle Workflow Client Installation Notes, and Oracle Workflow Guide for more information on these procedures.

  
  

Creating a Recovery Catalog for Recovery Manager

Recovery Manager is an automated recovery utility that is installed as part of Oracle9i database. It stores information in a recovery catalog in a separate Oracle9i database. This second Oracle9i database should be installed on a separate computer to provide maximum fault resistance.

To create a recovery catalog, perform the following steps:

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

   Create a typical, preconfigured database with 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 user, run the createCatalog command at the Oracle Recovery Manager prompt.

   
   

   See Also: Oracle9i Database Backup and Recovery Guide for more information on Recovery Manager.

   
   

Configuring Secure Sockets Layer

After Secure Sockets Layer is installed, run Oracle Net Configuration Assistant to configure it properly for your system.

Unlocking and Resetting User Passwords

Passwords for all Oracle system administration roles and privileges except SYS, SYSTEM and SCOTT are expired upon installation. You are required to unlock user names and reset passwords for all other administrative user names before using them. You can do this through Database Configuration Assistant.

Reviewing User Names and Passwords

All databases created by Database Configuration Assistant include the SYS, SYSTEM, and DBSNMP user names and passwords. In addition, Oracle Corporation provides several other administrative users. Unlock users and reset passwords before using these administrative accounts.

Table 4-8 describes the default user names and passwords.

Table 4-8 Default User Names and Passwords

Identifying Databases

The Oracle9i software identifies a database by its global database name. A global database name consists of the database name and network domain. The global database name uniquely distinguishes a database from any other database in the same network domain. Enter a global database name when prompted in the Database Identification window during Oracle9i database installation.

sales.us.acme.com

In the preceding example, sales is the name of the database. The database name portion is a string of no more than 8 characters that can contain alphanumeric, and additional characters. The database name is also assigned to the DB_NAME parameter in the init.ora file.

us.acme.com is the network domain in which the database is located. Together, the database name and the network domain make the global database name unique. The domain portion is a string of no more than 128 characters that can contain alpha, numeric, period (.), and additional characters. The domain name is also assigned to the DB_DOMAIN parameter in the init.ora file.

The DB_NAME parameter and the DB_DOMAIN name parameter combine to create the global database name value assigned to the SERVICE_NAMES parameter in the init.ora file.

The System Identifier (SID) identifies a specific Oracle9i database instance. The SID uniquely distinguishes a database from any other database on the same computer. Multiple Oracle home directories enable you to have multiple, active Oracle databases on a single computer. Each database requires a unique SID and database name.

The SID name comes from the value entered for the SID prefix in the Database Identification window. The SID can be up to 8 alphanumeric characters in length.

For example, if the SID and database name for an Oracle database are ORCL, each database file is in the $ORACLE_BASE/oradata/ORCL directory and the initialization parameter file is in the $ORACLE_BASE/admin/ORCL/pfile directory. The ORCL directory is named after the DB_NAME parameter value.

Tablespaces and Data Files

An Oracle9i database is divided into smaller logical areas of space known as tablespaces. Each tablespace corresponds to one or more physical data files. Data files contain the contents of logical database structures such as tables and indexes. You can associate each data file with only one tablespace and database.

Table 4-9 describes the tablespaces in the Oracle9i database located in the $ORACLE_BASE/oradata/db_name directory.

Table 4-9 Tablespaces and Data Files

Locating the Initialization Parameter File

The starter database contains the init.ora database initialization parameter file. It is a text file that contains a list of preconfigured instance configuration parameters. The file is located in the $ORACLE_BASE/admin/db_name/pfile directory, and must exist for an instance to start. No edits are required to this file in order to use the starter database.

Locating Redo Log Files

The starter database and the custom database each contain three redo log files located in the $ORACLE_BASE/oradata/db_name directory. Table 4-10 describes the redo log files.

Table 4-10 Redo Log files

Locating Control Files

The starter database contains three control files. These files are located in the $ORACLE_BASE/oradata/db_name directory. The files control01.ctl, control02.ctl, and control03.ctl are automatically included in the Custom database. Oracle Corporation recommends that you keep at least three control files (on separate physical drives) for each database and set the CONTROL_FILES initialization parameter to list each control file. Table 4-11 describes the database control files.

Table 4-11 Database Control Files

Using Rollback Segments

Rollback segments record the old values of data changed by each transaction whether or not the transaction has been committed. Every database contains one or more rollback segments. Use rollback segments to provide read consistency, roll back transactions, and recover the database. Table 4-12 describes the rollback segments of the starter database.

Table 4-12 Rollback Segments

Using the Data Dictionary

The data dictionary is a protected collection of tables and views containing reference information on the database, its structure, and its users. The data stored in the dictionary includes the following:

• Names of the Oracle database users

• Privileges and roles granted to each user

• Names and definitions of schema objects including tables, views, snapshots, indexes, clusters, synonyms, sequences, procedures, functions, and packages

• Integrity constraints

• Space allocation for database objects

• Auditing information, such as who accessed or updated various objects

  
  

  See Also: Oracle9i Database Concepts and Oracle9i Database Reference for more information on data dictionary.

  
  

Removing an Oracle Database with Database Configuration Assistant

1. Start the Database Configuration Assistant by using the dbca command located in the $ORACLE_HOME/bin/ directory:

   $ dbca
   
   

2. The Welcome window appears. Click Next.

3. Select Delete a Database from Operations window.

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 window that appears.

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 the Database Configuration Assistant, run the Oracle Net Configuration Assistant in remove mode by starting the assistant from the command line with the /deinst parameter:

$ netca /deinst

Removing Oracle Internet Directory

To remove Oracle Internet Directory Services:

1. Stop the Oracle Internet Directory Server by using the following command:

   $ oidctl connect=net_service_name server=oidldapd \instance=server_instance_number stop

   In the preceding command, net_service_name parameter is the network connection to the Oracle9i Database Server which stores the directory data and server_instance_number is the instance number which appears in the Server List tab of Oracle Directory Manager.

2. Stop the Oracle Internet Directory Monitor by using the following command:

   $ oidmon connect=net_service_name stop

   Follow the procedures in "Removing an Oracle Database with Database Configuration Assistant" to remove the Oracle9i database configured with Oracle Internet Directory.

   
   

   See Also: Oracle Internet Directory Administrator's Reference for more information on removing Oracle Internet Directory.

   
   

Changing the APACHE Account GID for Removal

1. Log in as root user.

2. Change the APACHE account primary GID group to the group that has ownership of the oraInventory directory. Typically, this is the ORAINVENTORY group.

3. Log out as root user.

Removing Oracle Label Security

Perform the following steps to remove Oracle Label Security. Do not perform a DROP USER CASCADE on the LBACSYS account to remove Oracle Label Security.

1. Connect as SYSDBA.

2. Execute the $ORACLE_HOME/lbac/admin/droplbasys.sql script to delete the LBACSYS account.

3. Use the Oracle Universal Installer to remove Oracle Label Security.

Removing Oracle Messaging Gateway

Perform the following steps to remove Oracle Messaging Gateway.

1. Shut down the Oracle Messaging Gateway.

2. Remove any user-created queues whose payload is a Oracle Messaging Gateway canonical type. (For example, MGW_BASIC_MSG_T)

3. Log in to SQL*Plus as user SYS as SYSDBA.

4. Run the catnomgw.sql script, located in the $ORACLE_HOME/mgw/admin directory.

5. Run Oracle Universal Installer to uninstall Oracle Messaging Gateway.

6. Use the backup copies of listener.ora and tnsnames.ora to return the files to their previous state.

Removing Oracle Software with Oracle Universal Installer

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

2. Click on the Deinstall Products button on the Welcome window or the Installed Products... button available on any Installer window. The Inventory window appears, listing the installed products.

3. In the Inventory window, select any product(s) to remove.

4. Click on the Remove button.

Cleaning Up After a Failed Installation

If an installation fails, you must remove files that the Installer created during the attempted installation. Perform the following steps to remove the files:

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

2. Click on the Deinstall Products button on the Welcome window or the Installed Products... button available on any Installer window. The Inventory window appears, listing installed products.

3. In the Inventory window, select any product(s) to remove.

4. Click on the Remove button.

To complete the cleanup, you must manually remove the Oracle home directory. This is necessary because the Oracle Universal Installer might copy files to your system but fail to register them during the unsuccessful installation. This step is not necessary if removal deletes all files from the Oracle home directory.