Can Connect Directly to Shared Server Dispatcher Port, Why ?

(Doc ID 461857.1)

Last updated on AUGUST 25, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 11.1.0.6 [Release 9.2 to 11.1]
Information in this document applies to any platform.
Information in this document applies to any platform.

Goal

By changing the net service name port in the address, to the shared server dispatcher port, connections can connect directly to a shared server dispatcher.

Tnsnames.ora

HAL =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = myhost)(PORT = 61628))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = orcl10.oracle.com)
    )
  )

Listener services

lsnrctl services listener10g 

LSNRCTL for Solaris: Version 10.1.0.5.0 - Production on 09-OCT-2007 09:44:15 

Copyright (c) 1991, 2004, Oracle.  All rights reserved. 

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC0))) 
Services Summary... 
Service "PLSExtProc" has 1 instance(s). 
  Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service... 
    Handler(s): 
      "DEDICATED" established:0 refused:0 
         LOCAL SERVER 
Service "orcl10.oracle.com" has 1 instance(s). 
  Instance "orcl10", status READY, has 3 handler(s) for this service... 
    Handler(s): 
      "DEDICATED" established:0 refused:0 state:ready 
         LOCAL SERVER 
      "D000" established:0 refused:0 current:0 max:972 state:ready 
         DISPATCHER <machine: myhost, pid: 18713> 
         (ADDRESS=(PROTOCOL=tcp)(HOST=myhost.oracle.com)(PORT=61628))



Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms