Oracle-L: Re: Where is TCP/IP adapter for DECNET ?. (was ORA 12500)

From: As WE see ourselves, So do WE become !!! 02-Jan-1996 1621 +0800 <ravi_at_QCAV01.ENET.DEC.COM>
Date: Tue, 2 Jan 1996 06:07:21 EST
Message-Id: <9601021128.AA15728@alice.jcc.com>

>>>>Subj: Where is TCP/IP adapter for DECNet? (was ORA-12500)

>>>>Env: VMS 6.1, Oracle 7.0.16

>>>>Actually, I've just discovered that my 7.0.16 installation doesn't have
>>>>TCP/IP adapter v2. It hasn't been installed. I've tried building the thing,
>>>>but only options are: WIN/TCP and Multinet. No DecNet. Oracle support is
>>>>baffled as well. We tried to fool the build procedure by entering 'D'. But
>>>>Oracle is no fool. It rejected our request. So folks, what needs to be done
>>>>to get TCP/IP Adapter v2 for VMS?

>>>>TIA,
>>>>Leng.

Leng,

I have installed Oracle 7.0.16 on OVMS VAX 6.1 with SQL*NET 2. I have UCX or DEC TCP/IP ver 3.0 running on my machine.

During the ORACLE installation , selecting the NETCONFIG product you can reconfigure for DEC TCP/IP. For me the option presented was as follows.

>>>Version 2 TCP/IP driver (Win TCP, MULTINET, DEC TCP/IP) W/M/D/N ? <<<<

Wherein I selected 'D', which is for DEC TCP/IP.

Everything went well, except that my listener process starts and stops within seconds !!!.

Just in case it helps , I am enclosing my LISTENER.ora and extract of README.

Regards
Ravi

The LISTENER.ORA file generated by the Config Tool on the VMS platform needs to be modified as follows after configuring the listener using the Edit Listeners screen:

locate the ORACLE_HOME entry for each SID
replace it with a PROGRAM entry as shown in the following examples

On VMS, the server process is not specified by just a location, but by a specific program using the PROGRAM keyword, usually a .COM file defined during installation. This is the program that the listener runs when passing control to a server process. Additionally a location for output can be specified using the OUT parameter.

When editing LISTENER.ORA, be careful that the parentheses match up. Too many open or closed parentheses will cause the listener to fail. Many editors can count them for you.

Restriction: When entering the network name for the node, the Config Tool with SQL*Net 2.0.13.0 will not be able to generate any files with the network name format "xx.xxx" ie "good.com".

###########

# FILENAME: listener.ora
# TIME....: 90-12-27 06:01:24
# NETWORK.: SISHIR
# NODE....: SISHIR
# SERVICE.: LISTENER
###########

LISTENER =
(ADDRESS_LIST =

        (ADDRESS=
          (PROTOCOL=IPC)
          (KEY= SISHIR)
        )
        (ADDRESS=
          (PROTOCOL=IPC)
          (KEY= TISCO)
        )
        (ADDRESS =
          (PROTOCOL = TCP)
          (PORT = 1521)
        )

  )
SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =

      (SID_NAME = TISCO)
      (PROGRAM='DKA100:[TISCO.NETCONFIG]ORASRV2.COM')

)
)

STARTUP_WAIT_TIME_LISTENER = i
CONNECT_TIMEOUT_LISTENER =i
LOG_DIRECTORY_LISTENER = ora_network:
LOG_FILE_LISTENER = sqllog

TRACE_LEVEL_LISTENER = ADMIN
TRACE_DIRECTORY_LISTENER=dka100:[TISCO.NETWORK.TRACE]
TRACE_FILE_LISTENER=sishir

Received on Tue Jan 02 1996 - 06:28:38 CST