ORACLE NETWORK MANAGER 기본적인 사용방법

Question

제품 : SQL*NET
작성날짜 : 2002-04-12
ORACLE NETWORK MANAGER 기본적인 사용방법
========================================
I. TERMINOLOGY TO KNOW BEFORE USING THIS GUIDE
A. community - a set of nodes that use the same network protocol.
B. listener - a service that waits for incoming requests from client
and server nodes.
C. system identifier - (SID) name of the Oracle database instance,
which is usually the same as the database name
II. NETWORK CONFIGURATION STEPS
A. Develop a pictorial representation of the network.
B. Provide configuration data to Network Manager.
C. Save the network configuration data and generate the configuration files.
Step A. Develop a pictorial representation of the network.
The sample network is a single protocol TCP/IP network with two
databases. Each node has one listener.
Step B. Provide configuration data to Network Manager.
Network Manager requires information about the objects in the
network before it creates the configuration files. There is an
on-line walk-through which leads you through the creation of a
network definition from the beginning (specification of definitions)
to the end (generation of the configuration files). The walk-through
provides information in pop-up boxes before each step. During the
walk through, a series of object property sheets, which gather the
data about network objects, appear with values which you may need
to alter.
** Tasks **
1. Launch Network Manager and click OK to store the network definition
in a file. In the Open window click Cancel.
2. Choose New from the File pull-down menu to start a new network
definition. Use the on-line walk through and click OK in the Network
Description dialog box.
3. In the Community property sheet, enter TCP as the name of the
community and choose TCP/IP from the protocol list box. Close the
community property sheet by clicking OK.
4. a. To define a node, enter the node name, TCP_node1, in the Node
property sheet.
b. Specify UNIX as the type of operating system in the drop-down
list.
c. Click on the community folder tab. Add TCP.WORLD to the node
community list (Note:WORLD is a default suffix) and close the
node property sheet by clicking OK.
5. Click OK to close the Node property sheet. To create the node,
TCP_node2, repeat step 4 and specify the type to be OS/2.
6. Create a listener in the Listener property sheet, by entering
TCP_listener1 as the name and choosing TCP_node1 in the node
pull-down menu to indicate what node TCP_listener1 will listen to.
Select the addresses folder tab and click Create. This defines the
address of the listener. A service address property sheet appears
with the address information as default values. Click OK.
7. Click the database folder tab to define a database for the listener.
In the Database property sheet, click Create to specify information
about the Oracle database that will be included in the network.
Enter TCP_DB1 as the name of the database. Click TCP_node1 as the
node. Enter the SID: db1. In the Operating System Specific Details
field, enter the directory path of the Oracle executables, i.e.
/usr/oracle for Unix or c:\oraos2\ for OS/2. Click OK to close the
Database property sheet.
8. Click OK to close the listener property sheet. To create
TCP_listener2, repeat steps 6-7 and substitute TCP_node2, TCP_DB2,
and db2 for the node, database, and SID, respectively.
Note: The on-line walk-through automatically validates the network configuration.
Step C. Save the network configuration data and generate configuration files.
1. Save the network definition.
2. Click File System in the Export Network Definition dialog box and
click OK. Choose the directory and click OK. The network definition
is now complete and the configuration files are generated.
III. OTHER INFORMATION
A. About the configuration files
If the network definition is saved to the file system,
Network Manager creates two types of subdirectories within the
directory chosen to store the network definition.
These are: a node specific directory, which has the same name as the
node and contact configuration files for the service the node provides,
and a client profile directory, which has the same name as the client
community and contains configuration files for each client.
B. Hardware and Software Requirements
PC with 6Mb disk, IBM or 100% compatible with an 80386 processor
or higher one CD-ROM drive
MS-DOS Version 5.0 or later and Windows 3.1

Answer 1

Hi Steve,
1) PL/SQL API for Network Analysis is coming in Oracle 10g Release 2.
2) In Oracle 10g Release 1 it is a requirement to load the entire network. Loading the entire street network of new york city on my 1 Ghz laptop requires about 1 minute. In Oracle 10g Release 2 you can specify a predicate on the load network so you do not have to load the entire network.
3) Source code for elocation will be available as an Oracle 10g Release 2 feature (I'm not sure what the "name" of the feature is, but it is a bundling of geocoding and routing, and when combined with MapViewer is a complete "elocation in a box" type of feature.
Hope this helps.