Net8 Administrator's Guide
Release 8.1.5
A67440-01

Library
Product
Contents
Index

Prev Next

5
Considerations for Upgrades and Migration

This chapter describes coexistence of SQL*Net and Net8, migration and upgrades. Specific topics discussed are:

Net8 and SQL*Net Differences

When dealing with SQL*Net to Net8 migration, keep the following features in mind:

This Feature...   SQL*Net   Net8  

Multiple Protocol Support  

Multi-Protocol Interchange allows applications in TNS networks to communicate across different protocols.  

The Oracle Connection Manager has a multi-protocol support feature which allows client and database servers operating on different protocol stacks to communicate with each other.

Additional Information: See "Enabling Multi-Protocol Support".  

Configuration Tools  

SQL*Net provides:

  • SQL*Net Easy Configuration to create service names

  • Oracle Network Manager for complex configurations

 

Net8 provides:

  • Net8 Configuration Assistant for basic configuration of the listener, net service names, and naming methods.

  • Net8 Easy Config to create, modify, delete, or test net service names

  • Net8 Assistant for complex configurations and network administration

 

External Procedures  

n/a  

Support for external procedure, a function or procedure written in a third-generation language (3GL) that can be called from PL/SQL code.  

Though it is not required, migrating your network to Net8 is recommended for the following reasons:

The table below lists the networking features supported in each Oracle release.

Database Release   7.1.4   7.1.5   7.1.6   7.2.2   7.2.3   7.3.2   7.3.3   7.3.4   8.x  

SQL*Net  

2.1.4  

2.1.5  

2.1.6  

2.2.2  

2.2.3  

2.3.2  

2.3.3  

2.3.4  

n/a  

Oracle Names server  

1.0  

1.0  

1.0  

1.1  

2.0  

2.0.2  

2.0.3  

2.0.4  

8.x  

Oracle Advanced Networking Option  

n/a  

n/a  

n/a  

n/a  

n/a  

2.3.2  

2.3.3  

2.3.4  

8.0.x  

Oracle Advanced Security  

n/a  

n/a  

n/a  

n/a  

n/a  

n/a  

n/a  

n/a  

8.1.x  

Secure Network Services1  

1.0.1  

1.0.2  

1.0.3  

1.1  

2.0  

n/a  

n/a  

n/a  

n/a  

Net8  

n/a  

n/a  

n/a  

n/a  

n/a  

n/a  

n/a  

n/a  

8.x  
1 The functionality of Secure Network Services and SQL*Net/DCE are now included in the Oracle Advanced Networking Option and Oracle Advanced Security option.

Obsolete SQL*Net Parameters

The following SQL*Net parameter are no longer functional in Net8:

Parameter   File   Description  

COMMUNITY  

TNSNAMES.ORA  

The COMMUNITY parameter used to a required part of all network service addresses. Thus, it appears anywhere you might find an address (for example, local naming and listener configuration files).  

NAMES.DEFAULT_ZONE  

SQLNET.ORA  

The NAMES.DEFAULT_ZONE used to be included in profiles as slight variants of the NAMES.DEFAULTDOMAIN and NAMES.PREFERRED_SERVERS parameters.  

You may choose to delete these parameters or leave them. Though they are no longer required, they will not interfere with any network operations.

Client and Database Compatibility Issues

Consider the following client-to-database connection issues before you decide if upgrading or migrating is appropriate for you environment:

Oracle8i Client Release 8.1 Connection to Oracle8i Database Release 8.1

As Figure 5-1 depicts, an Oracle8i Client release 8.1 requires Net8 Client release 8.1, and an Oracle8i release 8.1 database requires Net8 Server release 8.1:

Figure 5-1 Oracle8i Client to Oracle8i Database


The Oracle8i Client must be configured with a service name, as described in "Configuring the Network with the Local Naming Method".

Oracle8i Release 8.0/Oracle7 Client Connection to Oracle8i Database Release 8.1

As Figure 5-2 depicts, an Oracle8i Client release 8.0 requires a compatible release of Net8 Client, an Oracle7 Client requires SQL*Net Client, and an Oracle8i database requires Net8 Server release 8.1.

Figure 5-2 Oracle8i Client release 8.0/Oracle7 Client to Oracle8i Database


While is not necessary to replace the Oracle System Identifier (SID) of the database with its service name, Oracle recommends doing so to take advantage of new functionality. For example: 

net_service_name=
(description= 
  (address=...)
  (address=...)
  )
  (connect_data=
   (service_name=sales.com)===
  )

This effect may be accomplished by replacing SID=SID with SERVICE_NAME=SERVICE_NAME with the Net8 Assistant's compatibility mode. See "Using the Net8 Assistant to Handle Compatibility Issues".

Consider the following questions for an environment with Oracle7 clients connecting to an Oracle8i release 8.1 database:

Oracle8i Client Release 8.1 Connection to Oracle8i Database Release 8.0/Oracle7 Database

As depicted in Figure 5-3:

Figure 5-3 Oracle8i Client to Oracle8i Release 8.0/Oracle7 Database


The release 8.1 clients must be configured with the SID of the database. For example, the TNSNAMES.ORA would have the following effect: 

net_service_name=
(description= 
  (address=...)
  (address=...)
  )
  (connect_data=
   (sid=sales)
  )

This effect may be accomplished with the Net8 Assistant's compatibility mode. See "Using Release 8.0/7.x Features and Connecting To a Release 8.0/7.x Service".

Additionally, the LISTENER.ORA on the database server must still be configured with the description of the SID, as described in "Configuring a Listener with Service Information".

Consider the following questions for an environment with Oracle8i clients release 8.1 connecting to an Oracle7 database.

Oracle Names

If you are migrate or upgrade all or part of your network to Net8, you should migrate or upgrade all the Oracle Names Servers in the region to version 8.

Using the Net8 Assistant to Handle Compatibility Issues

Because some parameters are enabled only for release 8.1, the Net8 Assistant offers two options that permit you set the proper parameters in the TNSNAMES.ORA file for Net8 release 8.1 clients or Net8 release 8.0/SQL*Net release 2.x clients:

Net8 Assistant option   Description  

Use Options Compatible with Net8 8.0 Clients  

Allows you to enable or disable release 8.1 options for multiple addresses.

If turned ON, allows you to only select the Oracle Connection Manager parameter, SOURCE_ROUTE, for pre-release 8.1 client connections.

If turned OFF, allows you to enable or disable SOURCE_ROUTE, LOAD_BALANCE and FAILOVER parameters for release 8.1 client connections.

Additional Information: See "Configuring Multiple Address Options".  

Use Oracle8i Release 8.0 Compatible Identification  

Allows you to enable or disable release 8.1 advanced options for the CONNECT_DATA section of the TNSNAMES.ORA.

If turned ON, allows you to enter the SID of the pre-release 8.1 database.

If turned OFF, allows you to enter the release 8.1 service name (SERVICE_NAME).

Note: The Advanced Service Options dialog box, which is visible when the Advanced button in the Service Identification group is chosen, is also impacted by whether this option is turned ON or OFF. Some settings are only available for connections to a release 8.1 service.

Additional Information: See "Configuring Advanced Connection Attributes for a Net Service Name".  

Using Release 8.1 Features and Connecting To a Release 8.1 Service

If using older configuration files prior to release 8.1, the TNSNAMES.ORA may be modified to take advantage of new features or to connect to a release 8.1 service. These changes can be made manually to the TNSNAMES.ORA file or with the Net8 Assistant.

To configure old configuration files for release 8.1 features, use either the Net8 Assistant:

  1. Start the Net8 Assistant:

    • On UNIX, run netasst at $ORACLE_HOME/bin.

    • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

  2. Double-click on the Net Service Names folder in the directory tree.

  3. Select a net service name for which you want the compatibility mode to apply.

  4. If multiple addresses are configured for the selected net service name, you may configure client load balancing, connect-time failover and Oracle Connection Manager options:

    1. Click the Advanced button in the Address Configuration group.

      The Address List Options dialog box appears:


    2. Ensure Use Options Compatible with Net8 8.0 Clients is turned OFF.

    3. Select any of the address list options, then click OK.

      See "Configuring Multiple Address Options" for further information about the options.

  5. Connect to a release 8.1 service:


    1. Ensure Use Oracle8i Release 8.0 Compatible Identification is turned OFF in the Service Identification group box.

    2. Enter the name of the service to which you want to connect in the Service Name field.

      The service name is typically the global database name, a name comprised of the database name and domain name, entered during installation or database creation.

      For further information about the service name value, see:

      - "Setting Service Names and Instance Names" and "Step 1: Verify Service Name and Instance Name" to set the service name

      - "Configuring Advanced Connection Attributes for a Net Service Name" for more information about optional connection settings

  6. Choose Save Network Configuration from the File menu.

  7. Choose Exit from the File menu.

    The Net8 Assistant application exits.

Using Release 8.0/7.x Features and Connecting To a Release 8.0/7.x Service

If configuring a client to connect to a release 8.0 or release 7.x service, the TNSNAMES.ORA must be configured with the SID of database.

To configure release 8.0 features, use either the Net8 Assistant or manually modify the TNSNAMES.ORA file:

  1. Start the Net8 Assistant:

    • On UNIX, run netasst at $ORACLE_HOME/bin.

    • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

  2. Double-click on the Net Service Names folder in the directory tree.

  3. Select a net service name for which you want the compatibility mode to apply.

  4. If multiple addresses are configured for the selected net service name, you may configure Oracle Connection Manager:

    1. Click the Advanced in the Address Configuration group.

      The Address List Options dialog box appears:


    2. Ensure Use Options Compatible with Net8 8.0 Clients is turned ON.

    3. Select Use each address in order until destination reached. The Try each address, in order, until one succeeds option turns the source route option OFF. The other options are connect-time failover and client load balancing options that are not available for pre-release 8.1 clients.

      See "Configuring the Client for Oracle Connection Manager Features" for further information about configuring Oracle Connection Manager.

  5. Connect to a release 8.0 or release 7.x service:


    1. Ensure Use Oracle8i Release 8.0 Compatible Identification is turned ON.

    2. Enter the name of the SID to which you want to connect in the SID field.

  6. Choose Save Network Configuration from the File menu.

  7. Choose Exit from the File menu.

    The Net8 Assistant application exits.

Migrating and Upgrading Considerations

When installing Net8, you have these installation decisions to make:

Installation Decision   Description  

Install into another Oracle home  

Install release 8.1.5 in a different Oracle home on the same server.  

Migrate  

Migrating is the process of moving from SQL*Net release 2.x to Net8. Migration involves installing Net8 and de-installing SQL*Net release 2.x.  

Upgrade  

Upgrading is the process of transforming one release to another release of the same database version. For example, transforming an Net8 release 8.0.5 to an Oracle8i database release 8.1.5 is upgrading the database system.  

Note:

It is not possible to install release 8.1.5 products into an existing Oracle home.  

Upgrading and Migrating to Net8 Release 8.1

To upgrade from Net8 release 8.0 to Net8 release 8.1 or migrate from SQL*Net release 2.x to Net8 release 8.1, follow these tasks:

Step 1: Verify Service Name and Instance Name

Step 2: Perform Software Upgrade or Migration on the Server

Step 3: Perform Software Upgrade or Migration on the Client

Step 4: Perform Functional Upgrade and Migration

Step 1: Verify Service Name and Instance Name

If you want to take advantage of the Net8 release 8.1 feature to identify a service and its instance in the TNSNAMES.ORA file, ensure the SERVICE_NAMES and INSTANCE_NAMES parameters are set in the database initialization file (INITSID.ORA).

Parameter   Description  

SERVICE_NAMES  

One or more comma separated strings that represent the names of the services on the network. One of the services should be set to the global database name, a name comprised of the database name (DB_NAME) and domain name (DB_DOMAIN).  

INSTANCE_NAME  

A string value representing the name of instance and is used to uniquely identify a specific instance when multiple instances share common services names. INSTANCE_NAME should not be confused with the SID, which actually uniquely identifies the instances shared memory on a host.

The INSTANCE_NAME should be set to the value of the SID.  

Step 2: Perform Software Upgrade or Migration on the Server

Note:

You cannot install release 8.1.5 into an Oracle home that was created using an earlier release of Oracle8i database and you cannot install releases of the Oracle8i database prior to release 8.1.5 into an Oracle home that was created by release 8.1.5.  

To perform a software upgrade or migration on the database server:

Install the latest release of Net8 Server from the Oracle Universal Installer to receive the latest executables.

If Net8 Sever is installed with the Oracle8i database, you are prompted to upgrade a database with the Oracle Data Migration Assistant if the Oracle Universal Installer detects a release 8.0 database on your system. If you do not want to upgrade during the installation process, you can choose to install this assistant and use it later.

The Oracle Universal Installer automatically performs these tasks:

Step 3: Perform Software Upgrade or Migration on the Client

To perform a software upgrade or migration on the client

Install the latest release of Net8 Client from the Oracle Universal Installer to receive the latest executables.

Step 4: Perform Functional Upgrade and Migration

After the software is upgraded and migration, it is not required to upgrade the configuration files unless you want to use the new release 8.1 features. To take advantage of new features:

For this configuration file...   Perform the following...  

SQLNET.ORA on clients and server  

Remove AUTOMATIC_IPC, the parameter to force session to use IPC, as it will be ignored.  

TNSNAMES.ORA  

Replace SID with the SERVICE_NAME parameter to connect to a release 8.1 service. 

net_service_name=
(description= 
  (address=...)
  (address=...)
  )
  (connect_data=(service_name=sales.com))

The SERVICE_NAME is typically the global database name, a name comprised of the database name and domain name, entered during installation or database creation.

Additional Information: See:

 

 

Enable client load balancing and/or connect-time failover.

Additional Information: See:

 

LISTENER.ORA  

Because instance information is registered with the listener in release 8.1, it is no longer necessary to include the instance information with the SID_LIST_listener_name section of the LISTENER.ORA file.

However, many management tools, including Oracle Enterprise Manager, still require this information for release 8.1.5. If you are using Oracle Enterprise Manager to manage database objects, the LISTENER.ORA file must be configured with information about the database in the following manner: 

sid_list_listener_name=
  (sid_list=
     (sid_desc=
        (global_dbname=global_database_name)
        (oracle_home=oracle_home)
        (sid_name=sid)
     )
  )

Implementing connect-time failover does not allow use of static service configuration parameters in the LISTENER.ORA file. However, static configuration is required for Oracle8i release 8.0 or Oracle7 databases and Oracle Enterprise Manager. For further information about statically configuring the listener, see "Configuring a Listener with Service Information".

See the Oracle8i Parallel Server Setup and Configuration Guide for additional configuration instructions on setting up connect-time failover for Oracle Parallel Server in an Oracle Enterprise Manager environment.

Additional Information: See "Configuring a Listener with Service Information"  

See the next section, "Additional Considerations for Oracle Connection Manager and Oracle Names", for additional Oracle Connection Manager and Oracle Names migration issues.

Additional Considerations for Oracle Connection Manager and Oracle Names

If you are currently using Oracle Multi-Protocol Interchange or Oracle Names, review the following topics:

Using Oracle Connection Manager Release 8.1

The Oracle Connection Manager's administrative process, CMADMIN, is used by the CMCTL control utility to execute administrative commands.

In release 8.1, new configurations require a protocol address for CMADMIN. By default this address is: 

cman_admin=
 (address=
  (protocol=tcp)
  (host= host)
  (port=1830)
 )

Oracle Connection Manager release 8.1 is backwards compatible with release 8.0. This implies that:

Using Oracle Connection Manager Instead of Oracle Multi-Protocol Interchange

If you have migrated your clients to Net8, and you still require multi-protocol support, you will need to install Oracle Connection Manager, and route your sessions through it. Oracle Multiprotocol Interchange is no longer supported past SQL*Net release 2.3.

To ensure proper functioning of Oracle Connection Manager, verify that you have deleted the following files on those nodes:

Other migration considerations are specific to your network configuration.

See "Enabling Multi-Protocol Support", for further information about multi-protocol support.

Using Oracle Names Version 8

Oracle Names version 8 is backward compatible with SQL*Net version 2. This implies that clients running on SQL*Net version 2 can access Oracle Names servers using Oracle Names version 8 to connect to an Oracle8i database.

If you wish to take advantage of the new features provided with Oracle Names version 8, you must migrate all of your existing Names Servers in a region to version 8 by installing Oracle Names version 8 on every existing Names Server node.

Migration issues to keep in mind include:

Migrating from Oracle Names Version 2 Using a Database

To migrate and transfer data from an existing Oracle Names server database to a version 8 database, run the NAMESUPG.SQL script located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows NT on the node where Oracle Network Manager stored your network definition: 

sql> CONNECT user/password
sql> @oracle_home/network/admin/namesupg.sql;

Migrating from Oracle Names Version 2 Using the Dynamic Discovery Option

The procedure to migrate Oracle Names version 2 with the Dynamic Discovery Option is dependent upon whether nor not you want Oracle Names version 8 to store information in a region database.

Non-Region Database Migration

If you migrate to a Oracle Names version 8 from Oracle Names version 2 with the Dynamic Discovery Option, the new Oracle Names server should be able obtain registered data from the old checkpoint files. If for some reason data is not registered, you can register objects, following the procedures in "Step 5: Configure the Listener" to configure the listener properly with the USE_PLUG_AND_PLAY parameter and "Step 6: Register Data with the Oracle Names Server" to register objects.

Region Database Migration

If you were previously running Oracle Names version 2 using the Dynamic Discovery Option, and you want to configure a database as a repository for your Oracle Names information, you will need to:

  1. Write the information stored in the Oracle Names version 2 local administrative region to a TNSNAMES.ORA file. From the command line, enter: 

    namesctl
namesctl> dump_tnsnames
  2. Run the NAMESINI.SQL script located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows NT on the Oracle Names Server node where you want the database to reside: 

    sql> CONNECT user/password
sql> @oracle_home/network/admin/namesini.sql;
  3. Load the TNSNAMES.ORA file into a version 8 Oracle Names server using either the Net8 Assistant or the NAMESCTL control utility:

    Use the Net8 Assistant...   Use the control utility NAMESCTL...  
    1. Start Net8 Assistant.

      -On UNIX, run netasst at $ORACLE_HOME/bin.

      -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

    2. Double-click on the Oracle Names server folder.

    3. Select the Oracle Names server.

    4. Select Manage Data from the drop-down list box.

    5. Select Load.

    6. Enter the path and file name of the Oracle Network Manager-generated TNSNAMES.ORA file in the File field.

    7. Select Execute.

    8. Select Save Network Configuration from the File menu.

    9. Select Exit from the File menu to exit the Net8 Assistant application.

     

    From the command line, enter: 

    namesctl
namesctl> load_tnsnames file_name
     

  4. Use the Net8 Assistant to configure a NAMES.ADMIN_REGION parameter in every Oracle Names server configuration file (NAMES.ORA). See "Step 3: Create an Oracle Names Server".

  5. Reload Oracle Names server information into at least one Oracle Names server by issuing a NAMESCTL REORDER_NS command on one of the Oracle Names server node. See "Step 4: Configure Clients and Database Servers To Use Oracle Names Servers".

Migrating from ROSFILES to Oracle Names Tables in a Database

Oracle Names version 8 does not support older configurations that use Resource Object Store (ROS) files (ROSFILES). ROSFILES must be migrated directly into Oracle Names database tables or first intoTNSNAMES.ORA files and then into Oracle Names.

ROSFILES to Database Tables

To migrate ROSFILES to database tables:

  1. Create a database user account for Oracle Network Manager: 

    sql> CONNECT system/password
sql> CREATE USER user
    identified by password
    default tablespace users
    temporary tablespace temp;
  2. Grant SYSDBA privileges to the user: 

    sql> GRANT sysdba to username identified by password;
  3. To build the necessary tables, the scripts described below must be run against the server. Typically, these scripts are run on the Oracle Network Manager node. 

    sql> CONNECT user/password
sql> @oracle_home\dbs\rosbild.sql;
sql> @oracle_home\dbs\nmcbild.sql;
sql> @oracle_home\dbs\rosgrnt.sql;
sql> @oracle_home\dbs\nmcgrnt.sql;

    Script   Description  

    ROSBILD.SQL  

    Builds tables for use by the ROS.  

    NMCBILD.SQL  

    Builds tables for use by the Oracle Network Manager Objects (NMO) components.  

    ROSGRNT.SQL  

    Grants access to the users who will access the common tables. You will be prompted for the user name. Use the same user name that was used when you set up the Oracle Network Manager account.  

    NMCGRNT.SQL  

    Grants access to the users who will access the Oracle Network Manager tables.  

  4. From the Oracle Network Manager, save the ROSFILES to a database:

    1. Choose Save As from the File menu.

    2. Select Database in the Save Network Definition dialog box, then click OK.

    3. Enter the database user name/password created in step 1 and a net service name for the database in the Connect dialog box. Click OK.

    4. Select or enter the name of the network you wish to save in the Save Network Definition dialog box.

    5. Choose Exit from the File menu to exit the Oracle Network Manager.

  5. On the server, upgrade the database file by running the NAMESUPG.SQL script located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows NT: 

    sql> CONNECT user/password
sql> @oracle_home/network/admin/namesupg.sql;
ROSFILES to TNSNAMES.ORA File

To migrate ROSFILES to a TNSNAMES.ORA file, and then import the TNSNAMES.ORA file into Oracle Names:

  1. Create a TNSNAMES.ORA file:

    1. From the Oracle Network Manager, choose Preferences from the Special menu.

    2. Ensure Oracle Names is not selected in the Preferences dialog box.

    3. Choose Generate from the File menu to update the network definition and create a TNSNAMES.ORA file.

    4. Choose Exit from the File menu to exit the Oracle Network Manager.

  2. Load the TNSNAMES.ORA into the Oracle Names server using either the Net8 Assistant or the NAMESCTL control utility:

    Use the Net8 Assistant...   Use the control utility NAMESCTL...  
    1. Start Net8 Assistant.

      -On UNIX, run netasst at $ORACLE_HOME/bin.

      -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

    2. Double-click on the Oracle Names server folder.

    3. Select the Oracle Names server.

    4. Select Manage Data from the drop-down list box.

    5. Select Load.

    6. Enter the path and file name of the Oracle Network Manager-generated TNSNAMES.ORA file in the File field.

    7. Select Execute.

    8. Select Save Network Configuration from the File menu.

    9. Select Exit from the File menu to exit the Net8 Assistant application.

     

    From the command line, enter: 

    namesctl
namesctl> load_tnsnames file_name
     

See also the following documentation:

Checklist for Ensuring Proper Migration to Oracle Names Version 8

The following checklist is provided to ensure proper migration to Oracle Names version 8.

Migrate all Oracle Names servers in each region to the same version 8.

If you were previously running Oracle Names version 2, and you want to update your database as a repository for your Oracle Names information, you will need to run the NAMESUPG.SQL script located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin\names on Windows NT on the node where the network definition is stored.

If you were previously running Oracle Names version 2 using the Dynamic Discovery Option, and you want to configure a database as a repository for your Oracle Names information, you will need to:

  1. Run the NAMESINI.SQL script located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin\names on Windows NT on the node where you wish to install the database. 

    sql> CONNECT user/password
sql> @oracle_home/network/admin/names/namesini.sql;
  2. Use the Net8 Assistant to configure a NAMES.ADMIN_REGION parameter in every Names Server configuration file. For more information about the NAMES.ADMIN_REGION parameter, see Appendix C, "Configuration Parameters".

Set up at least two Oracle Names servers in each region to provide for fault tolerance.

Clients contact Oracle Names server through a preferred Oracle Names server list, well-known Oracle Names server, or generated list obtained through discovered, as described in "Differences Between Versions of Oracle Names" and "Understanding Discovery".

If you would like to use the version 8 generated list of Oracle Names servers, .SDNS.ORA on UNIX and SDNS.ORA on Windows platforms, follow "Step 4: Configure Clients and Database Servers To Use Oracle Names Servers"

After the file is created, delete the NAMES.PREFERRED_SERVERS parameter in the SQLNET.ORA file. Any Oracle Names servers specified in the NAMES.PREFERRED_SERVERS parameter will override the results of the discovery process.


Prev
Next
Oracle
Copyright © 1999 Oracle Corporation.
All Rights Reserved.

Library
Product
Contents
Index