Re: The black art of SQL*Net

Jim Richards (aka Mr Grumpy) wrote:  

> I an in the second category. I have a solaris box, oracle 7.3.2 and a win95
> box. I have sql*net v2 ... all the files appear correct, and look nice.
>
> Does anyone have any of the "ah ha" experiences in getting it going that
> they would like to share?
>

  I've not made it through an installation yet without having to throw   myself on Oracle Support's mercy. What I've found out so far applies   to HP-UX and I'm not sure how much is applicable to Sun, but here goes:

> As far as I get when in developer/2000 I enter the connect string of
> devl (the instance name, or SID for the purists) I get the two errors
> PDE-PUP004 which means oracle7 had an error and ORA-12154 and if I use
> the connect string of t:bismark:devl i get the same pup error but
> ORA-6105.
>
  The 12154 error generally a problem with the service name according to   the SQL*Net Administrator's Guide 2.0. The first time that I had this   problem, the environment variable, TNS_ADMIN, was not pointing to   $ORACLE_HOME/network/admin. Also, the files in the TNS_ADMIN directory
  may not be correct. Check TNSNAMES.ora.

  If you used netman to set up your files, be careful. The install manual
  for HP-UX recommended 1525 for the oracle server's port number in the   /etc/services file, but netman defaulted to 1526. Other than that problem,
  netman is a good configuration tool. When you use it, it will create the
  TNSNAMES.ORA, SQLNET.ORA and LISTENER.ORA for you in at least two directories.
  One for the server and one for the client. Copy the client directory to
  the $ORACLE_HOME/network/admin on the client. Most of the setup is the
  same on the client. At least it was for me when I connect four HP-UX boxes
  to a NOVELL server and had a disc-less PC running Windows 3.1. Once again
  since this is not the same set up the rules may differ.

  The only other thing that I know of is the connect string. Under HP-UX,
  your connect string would be for version 1 of SQLNET. The version 2   connect string should be in the form of hostname.world (if you let netman
  do your naming).

  You can check the status of the listener with lsnrctl status. This should
  show you that the listner is alive and well. It also show the port number
  that you are listening on.

  Finally, check $TWO_TASK. It should have the same form as the connect string.  

  I hope this helps.

-allan hicks Received on Thu May 30 1996 - 00:00:00 CEST