Start the database (if necessary): SQL> STARTUP

4. Run the utlrp.sql script, which by default is located in ORACLE_ HOME\rdbms\admin\utlrp.sql. For example:

SQL> @?\rdbms\admin\utlrp.sql

5.3 Configuring the Secure Sockets Layer

Oracle highly recommends you configure and use a Secure Sockets Layer (SSL) to ensure that passwords and other sensitive data are not transmitted in clear text in HTTP requests.

Note: There should be no other data definition language (DDL) statements running on the database while the script is running, and packages STANDARD and DBMS_STANDARD must be valid.

See Also:

■ "Using SSL" and "Enabling SSL" in Oracle Database Security Guide for more information about configuring and using SSL

■ "SSL Usage Issues" in Oracle Database Security Guide for more information about SSL usage issues

Configuring Oracle Components

5.4 Postinstallation Tasks for Oracle SQL Developer

See the following sections in Oracle SQL Developer Installation Guide for recommended postinstallation tasks for SQL Developer:

■ Migrating User Settings from a Previous Release ■ Migrating Information from Previous Releases ■ Location of User-Related Information

5.5 Configuring Oracle Components

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.

This section contains these topics: ■ Direct NFS Client

■ Configuring Oracle Messaging Gateway

■ Configuring Oracle Administration Assistant for Windows ■ Configuring Oracle Counters for Windows Performance Monitor ■ Configuring Oracle Label Security

■ Configuring Oracle Database Vault ■ Configuring Oracle Net Services

■ Installing Oracle Text Supplied Knowledge Bases ■ Installing the Oracle Text Filtering Component ■ Configuring or Reinstalling Oracle XML DB ■ Configuring PL/SQL External Procedures ■ Configuring Shared Server Support

■ Setting Credentials for the Job System to Work with Oracle Enterprise Manager ■ Configuring Oracle Database to Communicate with Oracle Automatic Storage

Management

■ Configuring Databases to Use Oracle Enterprise Manager Database Control ■ Installing Oracle Database Examples

See Also:

■ Chapter 4, "Configuration Tasks When Installing from the Database" in Oracle Application Express Installation Guide ■ "Post-installation Database Configuration" section in Oracle

Configuration Manager Installation and Administration Guide for information about postinstallation tasks for Oracle Configuration Manager

Note: You need only perform postinstallation tasks for components that you intend to use.

Configuring Oracle Components

5.5.1 Direct NFS Client

With Oracle Database 11g, you can store data files on a supported NFS system. You can configure Oracle Database to access NFS V3 servers directly using an Oracle internal Direct NFS Client. If Oracle Database cannot open an NFS server using Direct NFS Client, then an informational message is logged into the Oracle alert and trace files indicating that Direct NFS Client could not be established.

Management of Oracle data files created with Direct NFS Client should be done according to the guidelines specified in Oracle Database Administrator's Guide. The Oracle files resident on the NFS server that are served by the Direct NFS Client can also be accessed through a third party NFS Client. The volume must be mounted through CIFS or kernel NFS to enable regular windows utilities and commands, such as copy, and so on, access the database files in the remote location. Volumes mounted through CIFS cannot be used for database file storage without configuring Direct NFS Client. The atomic write requirements required for database access are not guaranteed by CIFS protocol. Consequently, CIFS can only be used for operating system level commands, such as copy, move, and so on.

Some NFS file servers require NFS clients to connect using reserved ports. If your filer is running with reserved port checking, then you must disable it for Direct NFS Client to operate. To disable reserved port checking, consult your NFS file server

documentation.

Direct NFS Client can consume upto four network paths defined for an NFS server. The Direct NFS Client performs load balancing across all specified paths. If a specified path fails, then Direct NFS Client reissues I/O commands over any remaining paths. Direct NFS Client requires an NFS server supporting NFS read/write buffers of at least 16384 bytes.

Direct NFS Client issues writes at wtmax granularity to the NFS server. Direct NFS Client does not serve an NFS server with a wtmax less than 16384. Oracle recommends that you use the value 32768.

Use the following views for Direct NFS Client management:

■ v$dnfs_servers: Shows a table of servers accessed using Direct NFS Client. ■ v$dnfs_files: Shows a table of files currently open using Direct NFS Client.

■ v$dnfs_channels: Shows a table of open network paths (or channels) to servers for which Direct NFS Client is providing files.

■ v$dnfs_stats: Shows a table of performance statistics for Direct NFS Client. For NFS servers that restrict port range, you can use the insecure option to enable clients other than root to connect to the NFS server. Alternatively, you can disable Direct NFS Client as described in "Disable Direct NFS Client".

The following sections elaborate on enabling, disabling, checking the buffer size for a Direct NFS Client:

■ Enable Direct NFS Client ■ Disable Direct NFS Client

Note: Use NFS servers supported for Oracle Database. See the My Oracle Support website for support information:

Configuring Oracle Components

5.5.1.1 Enable Direct NFS Client

To enable Direct NFS Client, a new Oracle specific file oranfstab can be added to ORACLE_HOME\dbs. When oranfstab is placed in ORACLE_HOME\dbs, its entries are specific to a single database.

Direct NFS Client looks for the mount point entries in ORACLE_HOME\dbs\oranfstab. It uses the first matched entry as the mount point.

Complete the following procedure to enable Direct NFS Client:

1. Create an oranfstab file with the following attributes for each NFS server to be