C.1 Listener Addresses

Team-Fly    

 
Oracle Net8 Configuration and Troubleshooting
By Jonathan  Gennick , Hugo Toledo
Table of Contents
Appendix C.  The listener.ora File


The addresses that a listener monitors are specified in listener.ora in a long entry that is typically referred to as the listener address section . You will have one listener address section for each listener that you define. The listener name is used to tag the section, and underneath the name will fall one or more nested parameters.

Listener Address

The listener address section (or entry) defines a listener and the network addresses that it monitors. If you're running Release 8.1 or higher, the listener address entry may take one of the following forms (the first form is the preferred form):

  listener_name  =    (DESCRIPTION_LIST=       (DESCRIPTION =  address_description  )       [(DESCRIPTION =  address_description  )]       ...    )  listener_name  =    (DESCRIPTION =  address_description  )  address_description  := (ADDRESS =  address_data  )                           [(PROTOCOL_STACK=                              (PRESENTATION = {TTCGIOP})                              (SESSION = {NSRAW})                            )]                        )  address_data  (TCP/IP) :=     (PROTOCOL = TCP)(HOST = {  hostname   ip_address  })(PORT =  port_number  )  address_data  (IPC) :=     (PROTOCOL = IPC)(KEY =  key_name  )  address_data  (SPX) :=     (PROTOCOL = SPX)(SERVICE =  spx_service_name  )  address_data  (Named Pipes) :=    (PROTOCOL = NMP)(SERVER =  server_name  )(PIPE =  pipe_name  ) 

The DESCRIPTION and DESCRIPTION_LIST keywords were introduced in Release 8.1. If you're running a release prior to 8.1, then use the following form with an ADDRESS_LIST keyword:

  listener_name  =    (ADDRESS_LIST=       (ADDRESS =  address_data  )       [(ADDRESS =  address_data  )       ...]    ) 

Parameters

listener_name

The name that you want to give the listener.

DESCRIPTION_LIST

Encloses one or more DESCRIPTION entries. Use this when you want an Oracle8 i listener to listen on more than one network address.

DESCRIPTION

Encloses an ADDRESS entry together with its related PROTOCOL entry.

address_description

Describes an address in terms of both the network protocol supported (TCP/IP, SPX, etc.) and the presentation and session layers being used.

ADDRESS

Defines one address on which a Net8 listener listens.

address_data

The protocol-specific address data required to identify a listener address.

PROTOCOL_STACK

Specifies the presentation and session layers to support on an address.

PRESENTATION={TTC GIOP}

Specifies the presentation layer to support. Use TTC (Two-Task Common) for traditional Oracle connections. Use GIOP (General Inter-Orb Protocol) for CORBA connections from Java clients . Your SESSION setting must correspond to your PRESENTATION setting.

SESSION={NS RAW}

Specifies the session layer to support. Use NS (Network Session) if you specified TTC for the presentation layer. Use RAW if you specified GIOP for the presentation layer.

PRESENTATION and SESSION are not independent of each other. If your presentation is TTC, your session layer must be NS. If your presentation is GIOP, then your session layer must be RAW. Those are the only two valid combinations.

ADDRESS_LIST

Encloses a list of one or more ADDRESS entries. Prior to the release of Oracle8 i , the PROTOCOL_STACK entry did not exist. All you needed in order to define a listener was a list of one or more ADDRESS entries. That list was enclosed by the ADDRESS_LIST entry. This obsolete form is still supported for backward compatibility.

host_name

The TCP/IP hostname of your server.

ip_address

The TCP/IP address of your server.

port_number

The TCP/IP port number that you want the Net8 listener to monitor. If you're not sure which port to use, try 1521. That's the default port assigned when you install Oracle to begin with.

key_name

An IPC key name. This can be any alphanumeric name that you like. Programs making an IPC connection to the database must then use a net service name that references this same key in its definition.

spx_service_name

An arbitrary name that you choose. This must correspond to the SPX service name in a net service name definition in order for a client to connect.

server_name

The name of your server.

pipe_name

The name of the pipe over which you want to communicate. This can be any name you choose, but it must correspond to the pipe name in a net service name definition in order for a connection to take place.

Examples

 PRODLISTENER =   (DESCRIPTION_LIST =     (DESCRIPTION =       (ADDRESS = (PROTOCOL = TCP)(HOST = donna.gennick.org)(PORT = 1521))       (PROTOCOL_STACK =         (PRESENTATION = TTC)         (SESSION = NS)       )     )     (DESCRIPTION =       (ADDRESS = (PROTOCOL = IPC)(KEY = PNPKEY))       (PROTOCOL_STACK =         (PRESENTATION = TTC)         (SESSION = NS)       )     )   ) 

Team-Fly    
Top


Oracle Net8 Configuration and Troubleshooting
Oracle Net8 Configuration and Troubleshooting
ISBN: 1565927532
EAN: 2147483647
Year: 2000
Pages: 120

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net