Another listener, iiop problem

Question

Hi All,
If anyone can help, any assistance is greatly appreciated!!!!!
Oracle support has been completely useless and unresponsive regarding these issues. I have 2 open TARs that have gone nowhere in the last 1 1/2 weeks.
I am struggling with the listener and making an iiop connection to the database from my client.
config:
client - NT4 w/ 8.1.6 client
db1 - Redhat 6.2 w/ 8.1.6
db2 - NT4 w/ 8.1.6
I have been trying to get an IIOP connection to both databases using the sess_sh command. On both boxes I can connect and create an ORB session locally.
On the NT db, when I run sess_sh from the client, I successfully connect only if I bypass the listener and connect to the dispatcher port. If I try and connect using listener port I get "cannot connect to service sess_iiop". A port scan of the NT box lists the IIOP port as unknown. Listener.ora:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 2481))
(PROTOCOL_STACK =
(PRESENTATION = GIOP)
(SESSION = RAW)
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1521))
On the Linux box, when I run sess_sh using both the listener and bypassing the listener, using the dispatcher port, it crashes and I get a CORBA error ("NO_IMPLEMENT = MAYBE", whatever that is supposed to mean). The services command in lsnrctl tells me that I made a connection, but I cannot create an ORB session.
How am I supposed to evaluate Oracle software when I cannot get it running and support is non-existant? I am on the verge of dumping Oracle products and implementing a Microsoft solution, simply because I can get Microsoft products to work and then start to work around Microsoft's other (and many) short comings.
Thanks in advance for any responses.
null

Answer 1

Some people have hit problems when their NT client machine is configured to only use TCP shortnames (ie machinename, but no
domain info). This is a problem as the listener always uses the long machine names (ie including full domain info). The losing TCP implementation never figures out that the short and long names are for the same machine, and thinks it cant find the required
machine. In either case, by simply editing the host file on your NT machine to have both shortname and longname associated with
the same IP number, it should work fine. Typically, your hosts file is at c:\winnt\system32\drivers\etc\hosts and should contain:
ip-number machinename machinename.yourdomain.com
Try doing the above & let me know if it helps