Release 1 (9.0.1)
Part Number A90191-02
 Home |
 Book List |
 Contents |
 Index |  Master Index |  Feedback |
| Oracle9i Database Migration Release 1 (9.0.1) Part Number A90191-02 |
|
This appendix describes coexistence, migration, and upgrade issues for Oracle Net Services. This appendix covers the following topics:
In an effort to streamline configuration decisions for the Internet, the following subsections describe the features and the configuration file that are no longer being supported:
If you are using Identix or SecurID authentication, provided by Oracle Advanced Security, Oracle Corporation recommends migrating to one of the following authentication methods:
Support for Novell Directory Services (NDS) as an authentication method and as an external naming method are no longer supported. If you are using NDS as an external naming method, Oracle Corporation recommends using directory naming instead.
Net8 OPEN, which provided an application program interface (API) that enabled programmers to develop both database and non-database applications, is no longer supported.
Parameters in the protocol.ora file have been merged into the sqlnet.ora file. These parameters enable you to configure access control to the database, as well as no delays in TCP/IP buffer flushing. These parameters include:
If you have a protocol.ora file in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows, Oracle Net Manager, when first started, will automatically merge its parameters into the sqlnet.ora file.
There may be operating system specific parameters in protocol.ora that are node specific. For this reason, Oracle Corporation recommends not sharing sqlnet.ora with other nodes after merging or adding these parameters.
Prespawned dedicated server processes are no longer supported. Instead, configure shared server (formerly named multi-threaded server) to improve scalability and system resource usage.
Protocol addresses using the SPX protocol must be replaced. Net8 provides support for the following network protocols:
Table F-1 describes the parameters no longer supported.
Table F-1 Unsupported Networking Parameters
|
See Also:
Oracle Net Services Reference Guide for further information about supported configuration parameters |
Table F-2 describes the control utility commands not supported in release 9.0.
Table F-2 Unsupported Network Control Utility Commands
|
See Also:
Oracle Net Services Reference Guide for further information about supported control utility commands |
Clients and database servers require compatible releases of Oracle Net Services or Net8. For example, an Oracle9i client requires an installation of Oracle Net Services, and an Oracle9i database requires an installation of Oracle Net Services with the Oracle Net Listener.
Consider the following client-to-database connection issues before you decide if migrating or upgrading is appropriate for your environment:
Connect descriptors, created for connections to an Oracle9i or an Oracle8i database, identify a database by its service name with the SERVICE_NAME parameter.
A connect descriptor to an Oracle9i or an Oracle8i database uses the parameter SERVICE_NAME, as shown in the following example:
sales=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=sales-sun1)(PORT=1521))
(CONNECT_DATA=
(SERVICE_NAME=sales.us.acme.com))
Connect descriptors that are currently configured with the SID parameter can remain. However, to take advantage of new features, such as client load balancing and connect-time failover, Oracle Corporation recommends replacing SID with SERVICE_NAME.
To modify a connect descriptor to use SERVICE_NAME, use the Oracle Net Manager's compatibility mode, as described in "Using the Oracle Net Manager to Handle Compatibility Issues".
|
See Also:
Oracle Net Services Administrator's Guide for information about database identification by |
Consider the following questions for an environment with Oracle release 8.0 clients connecting to an Oracle9i database:
No. You must rebuild or upgrade applications to work with Oracle Net libraries.
No. If a client needs to connect to a remote Oracle9i database, only Net8 Client release 8.0 needs to be configured on the client. However, new features of Oracle Net Services are not available to these clients.
No. The client requires an installation of Net8 Client release 8.0 in its Oracle home and the Oracle9i requires an installation of Oracle Net and Oracle Net Listener in its Oracle home.
A connect descriptor to an Oracle release 8.0 or Oracle7 database uses SID, as shown in the following example:
sales=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=sales-sun1)(PORT=1521))
(CONNECT_DATA=
(SID=sales))
In addition, the listener.ora file on the database server must be configured with the description of the SID for the Oracle release 8.0 database. In the following example, the listener is configured to listener for a database service called sales.us.acme.com that has a SID of sales:
SID_LIST_listener= (SID_LIST= (SID_DESC= (GLOBAL_DBNAME=sales.us.acme.com) (SID_NAME=sales)))
|
See Also:
Oracle Net Services Administrator's Guide for information about database identification by |
Consider the following questions for an environment with Oracle9i clients connecting to an Oracle release 8.0 database.
No. If a client needs to connect to a remote Oracle release 8.0 database, only Net8 Client of a compatible release needs to be configured on the client. The only limitation is that the new features available with Oracle Net Services are unavailable with this connection type.
Yes. The client requires an installation of Oracle Net in its Oracle home and the Oracle release 8.0 database requires an installation of Net8 Server in its Oracle home.
If you migrate or upgrade all or part of your network to Oracle9i, you should migrate or upgrade all the Oracle Names Servers in the region to version 9.
Yes.
Yes, if the connect descriptor was specified correctly when it was entered into Oracle Names.
|
Note: In future releases, Oracle Names will not be supported as a centralized naming method. Because no new enhancements are being added to Oracle Names, consider using directory naming or migrating an existing Oracle Names configuration to directory naming, as described in the Oracle Net Services Administrator's Guide. |
Because some parameters are enabled only for release 9.0.1 and release 8.1, Oracle Net Manager offers two options that permit you to set the proper parameters in the tnsnames.ora file for clients connecting to a release 9.0.1, release 8.1, and release 8.0database. These options are described in Table F-3.
| Oracle Net Manager Option | Description |
|---|---|
|
Use Options Compatible with Net8 8.0 Clients |
Enables you to configure multiple addresses parameters for a client.
If selected, enables the
If turned off, enables you to use the See Also: Oracle Net Services Administrator's Guide for information about configuring address list parameters |
|
Use Oracle8 Release 8.0 Compatible Identification |
Enables you to configure parameters specific to a database release in the If turned on, allows you to enter the SID of the Oracle release 8.0 or Oracle7 database.
If turned off, enables you to enter the Oracle9i or Oracle8i database 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 affected by whether this option is turned on or off. Some settings are only available for connections to an Oracle9i or Oracle8i database service. See Also: Oracle Net Services Administrator's Guide for information about configuring advanced connect data parameters |
To migrate from SQL*Net release 2.x to Oracle Net Services release 9.0.1 or upgrade from Net8 release 8.0 or 8.1, complete these tasks:
Step 1: Verify Service Name and Instance Name
Step 2: Perform Software Upgrade or Migration on the Server
Step 3: Perform Software Migration or Upgrade on the Client
If you want to identify a service and its instance in the tnsnames.ora file, ensure that the SERVICE_NAMES and INSTANCE_NAMES initialization parameters are set in the initialization parameter file.
| Parameter | Description |
|---|---|
|
|
Specifies one or more names for the database service to which this instance connects. You can specify multiple services names in order to distinguish among different uses of the same database. For example: SERVICE_NAMES = sales.us.acme.com, widgetsales.us.acme.com
If you do not qualify the names in this parameter with a domain, Oracle qualifies them with the value of the
Note: You can change the value of |
|
|
Specifies the unique name of this instance. Set the instance name to the value of the Oracle System Identifier (SID). |
To perform a software upgrade or migration on the database server, install the latest release of Oracle Net and Oracle Net Listener from the Oracle Universal Installer to receive the latest executables.
You are prompted to upgrade or migrate a database with the Oracle Data Migration Assistant if the Oracle Universal Installer detects an pre-release 9.0.1 database on your system. If you do not want to upgrade or migrate during the installation process, you can choose to install this assistant and use it later.
The Oracle Universal Installer automatically performs these tasks:
To perform a software migration or upgrade on the client, install the latest release of Net8 Client from the Oracle Universal Installer to receive the latest executables.
After the software is upgraded or migrated, it is not required to upgrade the configuration files unless you want to use the Oracle9i features. To take advantage of new features, review your configuration files:
Replace obsolete or renamed parameters.
Replace the SID parameter with the SERVICE_NAME parameter to connect to a release 8.1 or higher service, as in the following example.
sales=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=sales-sun1)(PORT=1521))
(CONNECT_DATA=
(SERVICE_NAME=sales.us.acme.com)))
If you have multiple addresses, you can configure client load balancing and connect-time failover features, as in the following example.
sales= (DESCRIPTION= (ADDRESS_LIST= (FAILOVER=on) (LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=tcp)(HOST=sales-sun1)(PORT=1521)(ADDRESS=(PROTOCOL=tcp)(HOST=sales-sun2)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=sales.us.acme.com)))
See Also:
- "Using the Oracle Net Manager to Handle Compatibility Issues" for information about configuring the service name and multiple address features.
- Oracle Net Services Administrator's Guide for information about multiple addresses
Because instance information is registered with the listener in release 9.0.1, it is no longer necessary to include the instance information with the SID_LIST_listener_name section of the listener.ora file.
However, Oracle Enterprise Manager still requires static information in the listener.ora file. 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_Table F-5 Service Settings in listener.oralistener_name= (SID_LIST= (SID_DESC= (GLOBAL_DBNAME=global_database_name) (ORACLE_HOME=oracle_home) (SID_NAME=sid)))
|
See Also:
Oracle Net Services Administrator's Guide for information about configuring service information and connect-time failover and Transparent Application Failover (TAF) |
|
Note: In future releases, Oracle Names will not be supported as a centralized naming method. Because no new enhancements are being added to Oracle Names, consider using directory naming or migrating an existing Oracle Names configuration to directory naming, as described in Oracle Net Services Administrator's Guide. The material presented here is primarily for reference to enable you to maintain your current Oracle Names environment. |
Oracle Names version 9 is backward compatible with Oracle Names versions 2 and 8. If you wish to take advantage of the new features provided with Oracle Names version 9, you must migrate all of your existing Names Servers in a region to version 9 by installing Oracle Names version 9 on every existing Oracle Names server node.
Migration issues to keep in mind are described in the following sections:
To migrate and transfer data from an existing Oracle Names server version 2 database to a version 9 region database, run the namesupg.sql script located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows platforms on the node where Oracle Network Manager stored your network definition.
In order to run the namesupg.sql script, two tables, NAMES_DOM and NAMES_DID must be created and populated using values from an existing names.ora file.
NAMES_DOM table needs a DOMAIN column with one row per domain specified by the NAMES.DOMAINS parameter in the names.ora file.
NAMES_DID table needs the ID which is defined in the NAME_P column in the NMO_INFORMATION table. The NAME_P column is the same as the DOCNAME specified by the NAMES.ADMIN_REGION parameter in the names.ora file.
To migrate data:
NAMES_DOM table as follows:
SQL> CONNECTuser/passwordSQL> CREATE TABLE NAMES_DOM (domain varchar(256));
NAMES.DOMAINS parameter in the names.ora file. For example, consider the following NAMES.DOMAIN parameter setting:
NAMES.DOMAINS=(DOMAIN_LIST=(DOMAIN=(NAME=)(MIN_TTL=86400))(DOMAIN=(NAME=com)(MIN_TTL=86400))(DOMAIN=(NAME=acme.com)(MIN_TTL=86400))
In this example, three rows for the root domain, acme subdomain, and com domain must be created as follows:
SQL> INSERT into NAMES_DOM values ('(root)'); SQL> INSERT into NAMES_DOM values ('acme'); SQL> INSERT into NAMES_DOM values ('acme.com');
NAMES_DID table as follows:
SQL> CREATE TABLE NAMES_DID (did number(10))
DOCNAME value under the NAMES.ADMIN_REGION parameter in the names.ora file. The DOCNAME represents the name associated with the region. In the following example, the DOCNAME is sbox.
NAMES.ADMIN_REGION= (REGION= (NAME=local_region.world) (TYPE=rosdb) (USERID=names) (PASSWORD=names) (description= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=tcp) (HOST=nineva) (PORT=1387))) (CONNECT_DATA=(SID=em))) (DOCNAME=sbox) (VERSION=34619392) # 2.1.4 (RETRY=60))
NMO_INFORMATION table for the ID associated with the DOCNAME and insert it into the NAMES.DOM table:
SQL> SELECT ID from NMO_INFORMATION where name_P=docname; SQL> INSERT into NAMES_DID select DID from NMO_INFORMATION where NAME_p='docname';
namesupg.sql script:
SQL> CONNECTuser/passwordSQL> @oracle_home/network/admin/namesupg.sql;
The procedure to migrate Oracle Names version 2 with the Dynamic Discovery Option is dependent upon whether or not you want Oracle Names version 8 to store information in a region database.
If you migrate to an Oracle Names version 8 from Oracle Names version 2 with the Dynamic Discovery Option, the new Oracle Names server should be able to obtain registered data from the old checkpoint files. If data is not registered, you can register objects by completing the procedures in the Oracle Net Services Administrator's Guide.
If you were previously running Oracle Names version 2 with the Dynamic Discovery Option, and you want to configure a region database as a repository for your Oracle Names information, you will need to:
tnsnames.ora file from Oracle Network Manager or run the following from the command line with a version 8 Oracle Names Control utility:
NAMESCTLNAMESCTL> DUMP_TNSNAMES
namesini.sql script located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows platforms on the computer where the database resides.
SQL> CONNECTuser/passwordSQL> @oracle_home/network/admin/namesini.sql;
NAMES.ADMIN_REGION parameter in every Oracle Names server configuration file (names.ora).
Oracle Net Services Administrator's Guide for information about creating an Oracle Names server.
See Also:
tnsnames.ora file into a version 9 Oracle Names server using either Oracle Net Manager or Oracle Names Control utility:
Oracle Names version 8 and higher do not support older configurations that use Resource Object Store (ROS) files (ROSFILES). ROSFILES must be migrated directly into Oracle Names database tables or first into a tnsnames.ora file and then into Oracle Names. The following sections cover both procedures:
To migrate ROSFILES to database tables:
SQL> CONNECT system/password SQL> CREATE USER user IDENTIFIED BY password DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp;
SQL> CONNECTusername/passwordSQL> @oracle_home\dbs\rosbild.sql; SQL> @oracle_home\dbs\nmcbild.sql; SQL> @oracle_home\dbs\rosgrnt.sql; SQL> @oracle_home\dbs\nmcgrnt.sql;
NAMES_DID and NAMES_DOM tables and run the namesupg.sql script, as described in "Migrating from Oracle Names Version 2 Using a Database".
To migrate ROSFILES to a tnsnames.ora file, and then import the tnsnames.ora file into Oracle Names:
tnsnames.ora file from ROSFILES:
tnsnames.ora file into the Oracle Names server using either Oracle Net Manager or Oracle Names Control utility:
In release 8.1, the region checkpoint file, ckpreg.ora, contained both topology and domain authoritative data. In release 9.0.1, this data has been split into two files. The topology checkpoint files, ckptop.ora, defines the domains in the administrative region and the Oracle Names servers authoritative for each domain. The domain checkpoint file, ckpdom.ora, contains the authoritative data for each domain.
These files are automatically generated if you are using a region database. If you are not using a region database and instead relying on the data in the checkpoint files, you can either disregard the checkpoint files and rely on Oracle Names servers running in the region or move data from the ckpreg.ora file to the ckptop.ora file.
To rely on data from other Oracle Names servers:
.sdns.ora file is in $ORACLE_HOME/network/names on UNIX operating systems or the sdns.ora file is in ORACLE_HOME\network\names on Windows.
This file contains the name and address of the first Oracle Names server. If it does not exist, discover the other Oracle Names server with the Oracle Net Manager's Command > Discover Oracle Names servers command or the Oracle Names Control utility's REORDER_NS command.
When an Oracle Names server starts, it finds another Oracle Names server and downloads the topology and domain data information from it.
To copy or move data from the ckpreg.ora file to the ckptop.ora file:
ckpreg.ora file to the ckptop.ora file. For example:
cd network/names mv ckpreg.ora ckptop.ora
When an Oracle Names server starts, it automatically generates the ckpdom.ora file.
The following checklist is provided to ensure proper migration to Oracle Names version 9.
|
 Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|