Very Computer

I just installed Oracle Server Enterprise Edition 8.1.7 on a Windows 2000
Server. The installation was fine, the database is up and running.

Then I wanted to use Enterprise Manager. It needs Management Server, so I
created a new Repository with the Configuration Assistant. I told the
Assistant to create a new user for the Repository, so the user's access
rights should be ok.

However, when starting the Management Server the following is given:

oemctrl fr Windows NT: Version 2.2.0.0.0
Copyright (c) 1998, 2000, Oracle Corporation.  Alle Rechte vorbehalten.
Oracle Management Server wird hochgefahren... [main][2001-10-15:8:38:54:514]
VdbSession.processError: errorCode >12640<
 [main][2001-10-15:8:38:54:514] VdbSession.processError: errorMsg

Quote:>ORA-12640: Inititalisierung des Berechtigungsprfungsadapters misslungen

< [main][2001-10-15:8:38:54:514] VdbSession.processError: database
connection error
VXA-2018 :
Anmeldung bei OMS-Registrierungsdienst nicht
m?glichoracle.sysman.vxn.VxnBootstrapException:
 at oracle.sysman.vxa.VxaAppServer.startServices(VxaAppServer.java:1353)
 at oracle.sysman.vxa.VxaAppServer.main(VxaAppServer.java:2547)
Fehler beim Hochfahren von Oracle Management Server.

Translating the important messages into English would result in

 - initializing the "adapter for testing the access rights" failed
 - logon to the OMS registration service not possible
 - error when booting the Oracle Management Server

Does anybody have a clue on what might be wrong?

Michael G. Schneider

Obviously this is a well know feature (bug). After a successfull
installation of Oracle 8.1.7 you have to change

   SQLNET.AUTHENTICATION_SERVICE=(NTS)

to

   SQLNET.AUTHENTICATION_SERVICE=()

in sqlnet.ora. Since I changed that, the Management Server starts fine.

It's a very tough job to create an out-of-the-box-installation. Until now I
have never been able to just doubleclick SETUP.exe and have a running Oracle
Database. But I am just a developer and not an Oracle DBA.

Michael G. Schneider

Quote:> Obviously this is a well know feature (bug). After a successfull
> installation of Oracle 8.1.7 you have to change

>    SQLNET.AUTHENTICATION_SERVICE=(NTS)

> to

>    SQLNET.AUTHENTICATION_SERVICE=()

> in sqlnet.ora. Since I changed that, the Management Server starts fine.

> It's a very tough job to create an out-of-the-box-installation. Until now
I
> have never been able to just doubleclick SETUP.exe and have a running
Oracle
> Database. But I am just a developer and not an Oracle DBA.

The only difference is the true DBA thinks that having to consider carefully
what you are doing and change all the defaults is rather a good idea.

--
Niall Litchfield
Oracle DBA
Audit Commission UK

Quote:> The only difference is the true DBA thinks that having to consider
carefully
> what you are doing and change all the defaults is rather a good idea.

True developers try to concentrate on what they are good at - developing
software. They appreciate if a software is installed just by clicking on
SETUP.exe. Maybe the software doesn't get optimally installed. Maybe
somebody who has time and ambition to play around with the settings will
create a better running system. But it is very important, that a software
starts running correctly right from the beginning.

Of course, I would never install an Oracle Database on a production system.
This is only for my own developing efforts. And here a
out-of-the-box-installation would be perfect.

Michael G. Schneider