Re: TNSLSNR crashes on Windows XP

"Benjamin Day" <benday_at_benday.com> wrote in message news:ee5a61b3.0302021858.3b1fb7e5_at_posting.google.com...
> > There shouldn't be any issues at all, provided (1) you're using the PRO
> > version of XP, and not the Home one (2) you're using 9.2 and not 9.0.1
(3)
> > you have adequate RAM and (4) it's a 'clean' machine
>
> WinXP Pro: check.
> Oracle 9.2: check.
> RAM: check. (512MB)
> Clean machine: reasonably clean. I definitely didn't do the install
> of oracle first but the machine is only a week old and doesn't have
> any games only office and developer tools.
>
>
> > I think number 4 is the real killer. Now, I've got 9i currently running
on
> > XP, that also has MS Office, WinDVD, VMware, Nero, Civilization III, and
> > Lord knows what else installed. But I installed Oracle first.
>
> I did the install of 9.2 on my win2k server box and it went through
> without a hitch....it had tons of stuff installed by the time I got
> around to installing oracle.
>
> While I agree that installing oracle first might minimize the freaky
> error factor, my installation of XP Pro is pretty standard and I have
> a hard time thinking that oracle should only install/work on a
> completely fresh box.

That wasn't what I was saying. Merely that installation *tends* to be trouble-free in such circumstances, and it helps to eliminate any unknowns.

>
> By the point that I'm getting this TNSLSNR.EXE crash, oracle itself is
> pretty much all set up. If you think about it, since TNSLSNR starts
> running, it is completely installed and actually listening...the crash
> always happens when I attempt to connect.
>

It's completely installed alright. On a box with problems.

> What does oracle do differently when omit the host name from the
> "connect" command? ("connect scott/tiger" works but "connect
> scott/tiger_at_laptop" causes the crash.)

It by-passes the Listener and names resolution methods, and makes a direct connection using ICP.

>
> Does anyone have any guesses as to what the underlying problem(s)
> could be?

Best we have a look at your listener.ora, your sqlnet.ora and your tnsnames.ora. But since your original error indicates a problem in the oranttcp DLL, then it could be a corrupt install, a permissions problem, bad RAM or anything else. Which is why I'd re-install Windows, re-install Oracle and see if the problem is repeatable.

Regards
HJR
> Thanks in advance.
> -Ben
>
Received on Mon Feb 03 2003 - 14:21:02 CST