F
Migration and Coexistence Issues

This appendix describes migration and coexistence issues for SQL*Net Version 2.x and Net8. Specific topics discussed are:

• Migration and Coexistence Overview
• Installation Considerations for Net8
• Migration Issues
• Coexistence Issues

Migration and Coexistence Overview

When installing Oracle Networking Products, you have these installation decisions to make:

Installation Decision	Description
New Installation	Install Net8 on a system containing no previous Oracle Networking Products (SQL*Net).
Coexistence	Install Net8 into the same Oracle home as your SQL*Net Version 2.x.
Migration	Migrate from SQL*Net Version 2.x to Net8. Migration involves installing Net8 and de-installing SQL*Net Version 2.x.

.

Coexistence and Migration Considerations

Consider the following issues before you decide which of the above procedures is most suitable for your requirements.

• Why should I use Net8?

  Net8 offers new features that are not available on SQL*Net Version 2.x. However, you should not migrate your network to Net8 until your client applications migrate to Oracle8 database. Coexistence is probably the best solution at this time.

• Do I need to migrate SQL*Net V2.x clients to Net8 to connect to a remote Oracle8 database?

  No. SQL*Net V2.x clients can connect to the Oracle8 server, which uses a Net8 listener, without further configuration. Net8 is backwards compatible with SQL*Net Version 2.x. The only limitation is that the network features available with Net8 will be unavailable with that connection. The figure below gives an example of this network configuration.

  

• Do I have to install Net8 Client on SQL*Net Version 2.x clients to connect to a local Oracle8 database?

  Yes. If the SQL*Net Version 2.x client needs to connect to a local Oracle8 database, the client needs SQL*Net Client Version 2.x, Net8 Client, and Net8 Server on the computer. Note that Net8 Client and Net8 Server are already installed during the installation of Oracle8 Enterprise Edition.

  You also need to create a service name using SQL*Net Easy Configuration or Oracle Network Manager in the SQL*Net Client Version 2.x TNSNAMES.ORA file. Ensure you specify this service name in the connect string when connecting to the Oracle8 database. Note that the Bequeath protocol adapter is not supported when connecting from an Oracle7 client to an Oracle8 database. The figure below gives an example of this network configuration.

  

• Do I need to install SQL*Net Client Version 2.x on Net8 clients to connect to a remote Oracle7 database?

  No. If a Net8 client needs to connect to a remote Oracle7 database, the client only needs to be configured with Net8 Client. TheNet8 client can connect to the Oracle7 database that uses a SQL*Net Version 2.x listener without further configuration. SQL*Net Version 2.x is upwards compatible with Net8. The only limitation is that the new network features available with Net8 are unavailable with this connection type.

  

• Do I have to install SQL*Net Server Version 2.x on Net8 clients to connect to a local Oracle7 database?

  Yes. If the Net8 client needs to connect to a local Oracle7 database, you need to install both SQL*Net Server Version 2.x and Net8 Client on the computer. Note that the Net8 client uses the Bequeath protocol adapter by default to connect to an Oracle7 database. The figure below gives an example of this network configuration.

  

Installation Considerations for Net8

Advanced Networking Option (ANO)

Net8 and ANO have some DLLs that share the same name but not the same functionality. Therefore, do not install Net8 after installing ANO. If you do, ANO will not work because some DLLs will be overwritten.

Migration Issues

SQL*Net Version 2.x clients should migrate to Net8 only when their client applications migrate to Oracle8. Until client applications upgrade to Oracle8, clients using SQL*Net Version 2.x can connect to Oracle8 servers.

SQL*Net Version 2.x can coexist with Net8 on the same machine in the same Oracle home directory.

WARNING: For co-existence of Net8 and SQL*Net Version 2.x, you must install Net8 into the same Oracle home directory as SQL*Net Version 2.x. Installing Net8 into a different Oracle home directory will disable the products located in the old Oracle home directory.

Directory Structure Differences

Configuration files in Net8 are contained in the directory:

ORACLE_HOME\NET80\ADMIN

Configuration files in SQL*Net Version 2.x are contained in the directory:

ORACLE_HOME\NETWORK\ADMIN

Installation Process

If you are migrating from SQL*Net Version 2.x to Net8, Oracle Installer automatically performs these tasks:

1. Configuration files are copied from ORACLE_HOME\NETWORK\ADMIN and saved into ORACLE_HOME\NET80\ADMIN.
2. SQL*Net Version 2.x listener is stopped. The startup type is changed from Automatic to Manual (Windows NT Control Panel).
3. Net8 listener is setup as Automatic startup and is started.

   Note: You can select the Migration installation option while installing the Oracle8 server.

File Names Differences

In Net8, executables (.EXE files) and dynamic link libraries (.DLL files) are contained in the directory:

ORACLE_HOME\BIN

File names in Net8 typically have an 80 appended to the corresponding name in SQL*Net Version 2.x. This suffix prevents conflict with SQL*Net Version 2.x files.

Service Names

Net8 service names differ from SQL*Net Version 2.x service names:

Net8 Component	SQL*Net V2 Name	Net8 Name
Listener	TNSListener	OracleTNSListener80
Oracle Names	NamesListener	OracleNames80
Oracle Connection Manager	(not available)	OracleCMAdminService80 OracleCMANService80
Client Cache Daemon	(not available)	OracleClientCache80

Coexistence Issues

SQL*Net Version 2.x clients should migrate to Net8 only when their client applications migrate to Oracle8. Until client applications upgrade to Oracle8, clients using SQL*Net Version 2.x can connect to Oracle8 servers.

SQL*Net Version 2.x can coexist with Net8 on the same machine in the same Oracle home directory.

WARNING: For co-existence of Net8 and SQL*Net Version 2.x, you must install Net8 into the same Oracle home directory as SQL*Net Version 2.x. Installing Net8 into a different Oracle home directory will disable the products located in the old Oracle home directory.

The Installation Process

If you are not migrating, and you are installing Net8 onto the same machine where SQL*Net Version 2.x exists, Oracle Installer automatically performs these tasks to enable coexistence:

1. Configuration files are copied from ORACLE_HOME\NETWORK\ADMIN and saved into ORACLE_HOME\NET80\ADMIN.
2. The Net8 listener is setup as Manual startup. The listener is not started (Windows NT Control Panel).

To use the Version 8 listener, you may need to change your network configuration on either the SQL*Net Version 2.x or Net8 configurations to prevent conflict. For example, you may need to change:

• Port number on a TCP/IP network
• Service name on an SPX network
• Pipe name on a Named Pipes network
• KEY for IPC connection

You may also need to start the Net8 listener, and change the status to Automatic startup, depending upon your network needs. If you make changes to the listener, you must make changes to client configuration files to ensure that clients can connect to the listener.

SQL*Net Version 2.x will use configuration files from ORACLE_HOME\NETWORK\ADMIN, while Net8 will use files from ORACLE_HOME\NET80\ADMIN by default. If you want both SQL*Net and Net8 to use configuration files from the same directory, set the registry variable TNS_ADMIN.

Additional Information: See Appendix A, "Modifying Configurations" for more information.

---