4 Oracle Database Postinstallation Tasks

4.3.1 Configuring Oracle Administration Assistant for Windows

Oracle Administration Assistant for Windows requires the Microsoft Management Console and HTML Help 1.2 or higher to run. Microsoft Management Console (MMC) version 2.0 ships with Windows 2003. Oracle recommends the latest MMC version available.

http://www.microsoft.com/

4.3.2 Installing Natively Compiled Java Libraries for Oracle JVM and Oracle interMedia

If you plan to use Oracle Java Virtual Machine (JVM) or Oracle interMedia, Oracle strongly recommends that you install the natively compiled Java libraries (NCOMPs) used by those components from the Oracle Database Companion CD. These libraries are required to improve the performance of the components on your platform.

4.3.3 Running Oracle Cluster Synchronization Services (CSS) from a Different Oracle Home

To reconfigure Oracle Cluster Synchronization Services (CSS) to run from a different Oracle home, enter the following at the command prompt:

localconfig reset [destination_Oracle_home]

where destination_Oracle_home is required if you run this command from the Oracle home where the CSS service is currently configured.

4.3.4 Configuring Oracle Counters for Windows Performance Monitor

Before using Oracle Counters for Windows Performance Monitor to view Oracle-specific counters, you must specify the SYSTEM password using Operfcfg.exe located in the ORACLE_BASE\ORACLE_HOME\bin directory.

To set the system password, enter the following:

c:\> ORACLE_BASE\ORACLE_HOME\bin\operfcfg.exe -U SYSTEM -P password -D TNS_Alias_for_database 

4.3.5 Configuring Oracle Label Security

If you installed Oracle Label Security, you must configure it in a database before you use it. You can configure Oracle Label Security 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.3.6 Configuring Oracle Net Services

If you have a previous release of Oracle software installed on this system, you can copy information from the Oracle Net tnsnames.ora and listener.ora configuration files from the previous release to the corresponding files for the new release.

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

For any database instances earlier than release 8.0.3, add static service information to the listener.ora file. Oracle Database releases later than release 8.0.3 do not require static service information.

Modifying the tnsnames.ora File

Unless you are using a central tnsnames.ora file, copy Oracle Net 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.3.7 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 Companion CD.

4.3.8 Configuring or Reinstalling Oracle XML DB

Refer to Oracle XML DB Developer's Guide for more information about the following tasks:

• Reinstalling Oracle XML DB

• Configuring or customizing the Oracle XML DB tablespace

• Configuring FTP, HTTP/WebDAV port numbers

4.3.9 Configuring PL/SQL External Procedures

Configuring PL/SQL depends on the network configuration files used. In nearly all cases, configuration is automatic. However, if you are using pre-8.0.3 tnsnames.ora and listener.ora files with your 10g release 2 (10.2) database, you need to manually configure them.

4.3.10 Configuring Shared Server Support

Configuring shared server support depends on how support was installed. If you installed Oracle Database through the Enterprise Edition, Standard Edition, or Personal Edition installation types, then shared support was not configured. If you created your database through Oracle Database Configuration Assistant, then you were offered a choice of shared or dedicated server support.

4.3.11 Setting Credentials for the Job System to Work with Enterprise Manager

Windows systems require that you set the correct credentials for the Jobs system to work properly in Enterprise Manager. By default, the Management Agent service is installed as a LocalSystem user. When submitting jobs, such as stopping or starting the database, the user submitting the job must have the Log on as a batch job privilege enabled.

Perform the following steps to establish that privilege for any operating system user who needs to submit an Enterprise Manager job.

1. Start the Local Security Policy tool: From the Start menu, Administrative Tools, then Local Security Policy.

2. Under the Security Settings list, expand the list to Local Policies.

3. Under Local Policies, double-click User Rights Assignment.

4. Under Policy, search for the Log on as a batch job policy.

   If the Management Agent service is installed as any other user (that is, not LocalSystem), then, in addition to granting the Log on as a batch job privilege, you must grant the "Windows service" user the following three privileges:

   • Act as part of the operating system

   • Adjust memory quotas for a process

   • Replace a process level token

5. With each policy, perform the following steps:

   1. Double-click the policy name.

   2. In the Properties dialog box, click Add User or Group.

   3. In the Select Users or Groups dialog box, enter the name of the user (for example, jsmith, administrator, and so on.)

   4. Click Check Names to check that you've entered the name correctly.

   5. Click OK.

6. Click OK to exit the Properties dialog box, then exit Local Security Settings and Administrative Tools.

7. Restart your computer.

If a user exists both locally and at the domain level, Windows gives the local user precedence. To use the domain user, qualify the username with the domain name. For example, to use the user joe in the ACCOUNTS domain specify the username as ACCOUNTS\joe.

4.3.12 Configuring Oracle Database to Communicate with Automatic Storage Management

On Windows, Oracle Database installations that use Automatic Storage Management must use Windows native authentication. By default, Windows native authentication is enabled. To ensure that it is, check the sqlnet.ora file, by default located in ORACLE_BASE\ORACLE_HOME\network\admin, and make sure that it has NTS enabled. For example:

sqlnet.authentication_services=(NTS)

4.3.13 Configuring Databases to Use Oracle Enterprise Manager Database Control

You have the option to configure Oracle Enterprise Manager Database Control automatically when creating a new database using Database Control Assistant. This lets you administer your entire database using Enterprise Manager Database Control

4.3.14 Using Oracle9i Language and Definition Files with Oracle Database 10g Release 2 (10.2)

You can use Oracle9i database language and territory definition files with Oracle Database 10g release 2 (10.2).

To enable this functionality:

1. Run the cr9idata.pl script, by default located in ORACLE_BASE\ORACLE_HOME\nls\data\old.

   Alternatively, before you install Oracle Database, you can run the Oracle Universal Installer setup command with the b_cr9idata variable set to true, as follows:

   setup.exe oracle.rsf.nlsrtl_rsf:b_cr9idata=true
   
   

2. Set the ORA_NLS10 environment variable to point to the directory where you installed the new language and territory definition files, which by default are in ORACLE_BASE\ORACLE_HOME\nls\data.

3. Restart Oracle Database.

4.3.15 Installing Oracle Database Components from the Companion CD

The Oracle Database Companion CD contains additional database-related components that you can install. Whether you need to install these components depends on which Oracle Database components or features that you plan to use. If you plan to use the following components or features, Oracle strongly recommends that you install the components from the Companion CD:

• JPublisher

• Oracle Database Examples (formerly Oracle Demos)

• Oracle JVM

• Oracle interMedia

• Oracle Text Supplied Knowledge Bases

• Oracle Ultra Search

• Oracle HTTP Server

• Oracle HTML DB

• Oracle Workflow server and middle-tier components