Re: Windows 3.11 and Oracle 7

u4imcehb_at_apollo.wes.army.mil (Ernest Boswell) writes:

>Terry Collins (terry_at_ms1.ucs.ualberta.ca) wrote:
>: If anyone out there can help me with this problem it would be much appretiated. When using
>: Oraccle's data browser to connect to a oracle database on a Novell server I am getting a error message
>: that reads
 

>: BRW-15387: Login Failed
>: ORA-06468 NETSPX SPX get local target failed.

     If you are using Windows for Workgroups 3.11 and amking use of
     Microsoft's protected mode netware driver, there are some 
     paramters you have to set in the Network Setup program.
     One is for the number of open IPX sockets and the other is
     for the number of connections.  I set both to 32 and this seems
     to work OK.  I received this same error before I made the adjustment.

> ORA-06468: NETSPX: SPX get local target error
 

> Cause: SPX cannot locate the destination on the network
 

> Action: Reboot the server, reload the SQL*Net driver, and retry the
> operation. If error recurs, contact your DBA.
 

> This is from the Oracle7 Server For Netware Installation and User's Guide,
> Appendix C - Error Messages and Codes. Can't help you beyond that,
> because I just finished installing the software, and when I tried the
>ORALOAD command, the server crashed. Anybody got any ideas why?
> (NOTE: Netware 3.11)

     If you are using Netware 3.11 right out of the box, then you
     have to use the updated NLMs which come with Oracle 7. If you
     installed it correctly, there should be a subdirectory under
      ORACLE7 called NLM.  In it you will find some updated NLMs for
     SPX and some others. 
    
     In the O7 installation guide, they tell you exactly which
     ones to use including the dates of each file.  

     My advice is to copy the Original NLMs from the SYSTEM directory
      to a safe place.  Then copy in the NLMs which come with O7 into
     SYSTEM.
  
     Also, the ORALOAD command is simply a "batch" file (.NCF) which runs under
     Netware.  Take a look at this file and you'll see three separate
     commands.  Try executing each command separately to see which one
     bombs first.  i.e. if the first one crashes and burns then
     you have a version problem with the NLMs.  If the CORE.NLM
     crashes, then it could be a memory problem, etc.

     Naturally there are about 100 combinations of all of the above
     which could be causing it   :)

     If you like, I can supply you with my AUTOEXEC.NCF to compare.

>Thanks in advance
 

>--
>Harry Boswell u4imcehb_at_apollo.wes.army.mil
>Computer Scientist
>Information Technology Laboratory
>U.S. Army Corps of Engineers
 

>"select std_disclaimer from opinions_not_shared_by_employer"

Rich Holowczak
Rutgers University
holowcza_at_andromeda.rutgers.edu Received on Mon Mar 14 1994 - 22:08:42 CET