4 Postinstallation Tasks

4.1.1 Running Database Configuration Assistant in Interactive Mode

To start Database Configuration Assistant in interactive mode, perform the following:

1. Set up the X Window environment by using the following DCL command:

   SET DISPLAY/CREATE/TRANSPORT=TCPIP/NODE=workstation_name or IP_address
   
   

2. Set default to the [BIN] directory in the Oracle home directory, and then enter the following command to start DBCA:

   $ @disk:[oracle_home_directory]ORAUSER
   $ SET DEFAULT ORA_ROOT:[BIN]
   $ DBCA
   
   

   Note:

   Click Finish to go to the last screen. This accepts the default answers to the questions on the other screens. However, if DBCA determines that the default answers to one or more screens do not apply, the DBCA will not display the last screen.

   Database Configuration Assistant graphical user interface (GUI) is displayed.

4.1.2 Using Database Configuration Assistant Response Files

An alternative to creating an argument file to pass command-line options to Database Configuration Assistant is to use a response file. A sample response file (DBCA.RSP) is provided in the ORA_ROOT:[ASSISTANTS.DBCA.LOGS] directory. Make a copy of this file and customize it as necessary. Follow the instructions that are contained in comments. The value that is specified for the CREATE_TYPE field determines which of the other sections are applicable. Each field has a comment header block with the following entries: Name, Datatype, Description, Valid values, Default value, and Mandatory (Yes/No) descriptions.

For example:

#_____________________________________________________________________________
# Name          : CREATE_TYPE
# Datatype      : String
# Description   : Type of database creation
# Valid values  : "createDatabase" \ "createTemplateFromDB" \ 
#                 "createCloneTemplate"
# Default value : None
# Mandatory     : Yes
#_____________________________________________________________________________
CREATE_TYPE = "createDatabase"

All mandatory values must be provided, but only for the applicable sections as indicated by the CREATE_TYPE value. After customizing the response file, start Database Configuration Assistant and pass the name of the response file at the command line as follows:

$ DBCA –SILENT –RESPONSEFILE full_response_file_name

4.1.3 Database Configuration Assistant Unsupported Options

The following Database Configuration Assistant options are not supported with this release:

• OLAP

• UltraSearch

• Sales History Demonstration

4.2.1 Downloading and Installing Patches

Check the OracleMetaLink Web site for required patches for the installation. To download required patches:

1. Use a Web browser to view the OracleMetaLink Web site at

   https://metalink.oracle.com

2. Log on to OracleMetalink.

   Note:

   If you are not an OracleMetaLink registered user, click Register for MetaLink! and follow the registration instructions.

3. On the main OracleMetaLink screen, click Patches.

4. Select Simple Search.

5. Specify the following information, then click Go:

   • In the Search By field, select Product or Family, then specify the RDBMS Server.

   • In the Release field, specify the current release number.

   • In the Patch Type field, specify Patchset/Minipack.

   • In the Platform or Language field, select the platform.

4.2.2 Configuring Oracle Products

Many Oracle products and options must be configured before you use them for the first time. Before using individual Oracle products or options, refer to the appropriate manual in the product documentation library.

4.2.3 Setting the NLS_LANG Environment Variable

NLS_LANG is a logical name that specifies the locale behavior for Oracle software. This variable sets the language and territory used by the client application and the database server. It also sets the character set for the client, which is the character set for data entered or displayed by an Oracle client program, such as SQL*Plus.

4.7.1 Configuring Oracle Net Services

If you have a previous release of Oracle software installed on this system, you may want to copy information from the Oracle Net Services TNSNAMES.ORA and LISTENER.ORA configuration files from the previous release to the corresponding files for the new release.These files should have a record format of stream_lf. If you copy a TNSNAMES.ORA or a LISTENER.ORA file from an earlier version, use the following command to convert the files:

$ CONVERT/FDL=SYS$INPUT filename
 filename
 RECORD
 CARRIAGE_CONTROL carriage_return
 FORMAT stream_LF ^Z

Modifying the listener.ora File

If you are upgrading from a previous release of Oracle Database, Oracle recommends that you use the current release of Oracle Net Services listener instead of the listener from the previous release.

To use the listener from the current release, you may need to copy static service information from the LISTENER.ORA file from the previous release to the version of that file used by the new release.

Modifying the tnsnames.ora File

Unless you use a central TNSNAMES.ORA file, copy Oracle Net Services service names and connect descriptors from the previous release TNSNAMES.ORA file to the version of that file used by the new release.

If necessary, you can also add connection information for additional database instances to the new file.

4.7.2 Configuring Oracle Label Security

If you install Oracle Label Security, you must configure it in a database before you use it. You can configure Oracle Label Security in two ways, with or without Oracle Internet Directory integration. If you configure Oracle Label Security without Oracle Internet Directory integration, you cannot configure it to use Oracle Internet Directory at a later stage.

4.7.3 Installing Oracle Text Supplied Knowledge Bases

An Oracle Text knowledge base is a hierarchical tree of concepts used for theme indexing, ABOUT queries, and deriving themes for document services. If you plan to use any of these Oracle Text features, you can install two supplied knowledge bases (English and French) from the Oracle Database 10ginstallation media.

4.7.4 Configuring Oracle Messaging Gateway

To configure Oracle Messaging Gateway, refer to the section about Messaging Gateway in Oracle Streams Advanced Queuing User's Guide and Reference. When following the instructions listed in that manual, refer to this section for additional instructions about configuring the LISTENER.ORA, TNSNAMES.ORA, and MGW.ORA files.

Modifying the LISTENER.ORA File for External Procedures

To modify the ORACLE_HOME:[NETWORK.ADMIN]LISTENER.ORA file for external procedures:

1. Back up the LISTENER.ORA file.

2. Ensure that the default IPC protocol address for external procedures is set as follows:

   (ADDRESS = (PROTOCOL=IPC)(KEY=EXTPROC))
   
   

3. Add static service information for a service called mgwextproc by adding the following lines to the SID_LIST parameter for the listener in the LISTENER.ORA file:

   (SID_DESC =
       (SID_NAME = mgwextproc)
       (ORACLE_HOME = oracle_home)
       (PROGRAM = extproc)
     )
   
   

   For example, set the SID_LIST parameter as follows:

   SID_LIST_LISTENER =
     (SID_LIST =
       (SID_DESC =
         (SID_NAME = PLSExtProc)
         (ORACLE_HOME = somedisk:[oracle.product.10_1_0.db_1])
         (PROGRAM = extproc)
       )
       (SID_DESC =
         (SID_NAME = mgwextproc)
           (ORACLE_HOME = somedisk:[oracle.product.10_1_0.db_1])
           (PROGRAM = extproc)
       )
     )
   
   

   In this example:

   • ORACLE_HOME is the path of the Oracle home directory.

   • extproc is the external procedure agent executable file.

Modifying the TNSNAMES.ORA File for External Procedures

To modify the ORACLE_HOME:[NETWORK.ADMIN]TNSNAMES.ORA file for external procedures:

1. Back up the TNSNAMES.ORA file.

2. In the TNSNAMES.ORA file, add a connect descriptor with the net service name MGW_AGENT as follows:

   MGW_AGENT = 
   (DESCRIPTION= 
      (ADDRESS_LIST= (ADDRESS= (PROTOCOL=IPC)(KEY=EXTPROC))) 
      (CONNECT_DATA= (SID=mgwextproc) (PRESENTATION=RO)))
   
   

   In this example:

   • The value specified for the KEY parameter must match the value specified for that parameter in the IPC protocol address in the LISTENER.ORA file.

   • The value of the SID parameter must match the service name in the LISTENER.ORA file that you specified for the Oracle Messaging Gateway external procedure agent in the previous section (mgwextproc).

Setting Up the MGW.ORA Initialization File

To modify the ORA_ROOT:[MGW.ADMIN]MGW.ORA file for external procedures, define the CLASSPATH logical name. A sample MGW.ORA file can be found in the ORA_ROOT:[MGW.ADMIN]SAMPLE_MGW.ORA directory.

You must include the classes in Table 4-1 and any additional classes required for Oracle Messaging Gateway to access non-Oracle messaging systems, such as WebSphere MQ or TIBCO Rendezvous classes.

4.7.5 Oracle Precompilers

The following sections describe references and configuration files that are associated with Oracle precompilers.

Pro*C/C++

For the Pro*C/C++ precompiler, the configuration file is ORA_ROOT:[PRECOMP.ADMIN]PCSCFG.CFGS. This file installs without content. Use any text editor to customize it to the site requirements. For more information about configuring the pcscfg.cfg file, refer to Pro*C/C++ Programmer's Guide

Pro*COBOL

For the Pro*COBOL precompiler, the configuration file is PCBCFG.CFG. This file installs without content. Use any text editor to customize it to the site requirements. For more information about configuring the pcbcfg.cfg file, refer to Pro*COBOL Programmer's Guide.

Pro*FORTRAN

For the Pro*FORTRAN precompiler, the configuration file is PCCFOR.CFG. This file installs without content. Use any text editor to customize it to the site requirements. For more information about configuring the pccfor.cfg file, refer to Pro*FORTRAN Supplement to the Oracle Precompilers Guide.