Unable to read rdbms_server_dn from init.ora

[sadia]

hi,
i saw the same error message posted before but could not find the answer.
I'm getting the following error when trying to start oracle.


Dump file D:\TOPSSDB\Trace\ORA02148.TRC
Tue Oct 15 16:25:44 2002
ORACLE V8.1.6.0.0 - Production vsnsta=0
vsnsql=e vsnxtr=3
Windows 2000 Version 5.0 Service Pack 3, RC 3.51, CPU type 586
Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
Windows 2000 Version 5.0 Service Pack 3, RC 3.51, CPU type 586
Instance name: tps

Redo thread mounted by this instance: 1

Oracle process number: 8

Windows thread id: 2148, image: ORACLE.EXE


*** SESSION ID:(7.79) 2002-10-15 16:25:44.375
Unable to read rdbms_server_dn from init.ora.

[Christian Gebhardt]

Hi
I have found two postings on oracle-metalink. I hope this will help you:

RDBMS Version: 816 EE

Unable to read rdbms_server_dn

I am getting this error though not too frequently.

What should I do to avoid this. Also provide me some info on this.

Regards
--------------------------------------------------------------------------------
From: Oracle, Helen Schoone 16-Jan-02 19:02
Subject: Re : Unable to read rdbms_server_dn


Hi. This error would be related to bug 1393786 where when sqlnet.auth...=(NTS) and logging in as a user identified externally, and it fails, such as due to invalid username/password, etc., we are attempting to perform a global authentication of the user, thus leading to the generation of this trace file with this cryptic message. The bug is fixed in Oracle9i and included in the 8.1.7.3 patchset release.

I hope this helps.

Regards,
Helen
Oracle Support Services
_________________________________________________________________________________

RDBMS Version: 8.1.7

Unable to read rdbms_server_dn from init.ora.

What are the valid vaues and their meaning for ent_domain_name? I tried search this parameter but with no luck. We are getting the same error in the trace file since we upgraded to 8.1.7 from 8.1.5. In one of the threads, it was suggested by Oracle analyst this is related to bug 1393786 and has something to do with user authentication and it's fixed in 9i. Is the fix backported? We have os_authent_prefix = "" and SQLNET.AUTHENTICATION_SERVICES= (NTS). How do I get rid of this error and how do I find out who's entering the wrong userid/password? Any help is greatly appreciated!

--------------------------------------------------------------------------------

From: Oracle, Rowena Serna 31-Aug-01 04:55
Subject: Re : Unable to read rdbms_server_dn from init.ora.

It is fixed in oracle9.
As far as finding out who's entering incorrect password, you could
audit.
For example:
AUDIT CONNECT BY SCOTT WHENEVER NOT SUCCESSFUL ;
should log an entry to audit tables if scott doesn't successfully login.

It has not been backported.

Regards,
Rowena Serna
Oracle Corporation

[John Palmer]

Hi,

Oracle is objecting to the setting that you've got for the initialisation parameter 'dbms_server_dn'.

Check the setting in inittms.ora.

Regards,
John