Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Windows and Oracle v8.04

3 views
Skip to first unread message

Brandy

unread,
Jun 21, 1999, 3:00:00 AM6/21/99
to
I am unable to load Oracle v8.04 for NT onto a Windows 2000 Beta 3 OS.

I get an error
rdbms80.vrf(664): OS_ERROR while getting service status portmap

Any ideas what might cause the problem?

Thanks,


Jonathan Gennick

unread,
Jun 22, 1999, 3:00:00 AM6/22/99
to

Microsoft?

Seriously, there's no reason to expect that what you are
doing will work. As I recall, Windows 98 broke some Oracle
client software (and Personal Oracle too) that used to work
under Windows 95. It's reasonable to assume that Oracle will
have to create a new release just for Win 2k.

Jonathan

_____________________________________________________
jona...@gennick.com
http://gennick.com
Brighten the Corner Where You Are


Billy Verreynne

unread,
Jun 22, 1999, 3:00:00 AM6/22/99
to
Brandy wrote in message <7km3m7$pbr$1...@remarQ.com>...

>I am unable to load Oracle v8.04 for NT onto a Windows 2000 Beta 3 OS.
>
>I get an error
> rdbms80.vrf(664): OS_ERROR while getting service status portmap
>
>Any ideas what might cause the problem?


Hey, I'm always prepared to thumb suck! :-) This seems to be a NT specific
problem and not a problem/bug with Oracle.

The "service status" bit may refer to an error Oracle received trying to use
the NT Service Manager API calls - these are used for registering, starting
up, pausing and shutting down NT services.

The "portmap" bit may refer to Oracle not being able to bind a TCP port (but
why would the Oracle db engine want to bind a port?). The two of them
together.. got me confused...

Anything useful in the event log? A service is suppose to report errors in
the event log. If a service is not properly registered, you will find "funny
messages" in the event log (the message number is the only part that exist
in the event log - the actual message is contained in the service EXE or
associated DLL. If the registration process fail, the event viewer does not
know where to look up the error message code which then result in a "funny
message").

You can also try and disable all other non-essential services like FTP, IIS
etc. and see if that makes any difference.

regards,
Billy


0 new messages