DECS connecting to Oracle says ORA-12640

HCL Domino Domino Forum
1

I have a Domino Server and an Oracle server on another box.When I use the LC API I can connect to the oracle with a script like this from the client:

Sub Initialize

Dim ss As New NotesSession

Dim lcss As New LCSession

Dim lcc As New LCConnection("oracle8")

Dim Result As LCFieldList

Dim fld As LCField



lcc.server = "server"

lcc.userid = "userid"

lcc.password = "password"

Call lcc.Connect

Set result = New LCFieldList(1)

Call lcc.Execute("select * from dual", result)

Set fld = result.GetField(1)

Call lcc.Fetch(result)

End Sub

But when I try to set up a DECS Connection in the table selection phase I get an ORA-12640 error (something with initializing the authentication interface but I’m not sure, the message is not in English)

I tried to connect through ODBC with the same results.

OK, to tell the truth when I run the script on the server I get the same error. And the client is on the same box as the server.

Anyone knows why?

TIA

2

Subject: RE: DECS connecting to Oracle says ORA-12640

There’s a reason that error messages include error numbers; it’s so that you can go into Google and search for the error number, finding useful information such as this:

http://searchoracle.techtarget.com/ateQuestionNResponse/0,289625,sid41_cid561060_tax294550,00.html

3

Subject: RE: DECS connecting to Oracle says ORA-12640

Thanks for the tip!The question really was that if there is an error then why it isn’t there in the client. Or if there is no error then why it is there on the server. All other things are the same since it’s the same box.

4

Subject: RE: DECS connecting to Oracle says ORA-12640

Not sure – maybe a path issue. What ID do you use to run Domino? Might it have different path definitions than your normal system logon?

5

Subject: RE: DECS connecting to Oracle says ORA-12640

The ID is different of course, but the paths for the system and the NT user look the same (except some visual basic paths)I have checked the ORA-12640 and the Internet said to comment the following line in the sql.ora:

SQLNET.AUTHENTICATION_SERVICES= (NTS)

Now both the server side script and DECS work.

Thanks for the tip again :slight_smile: And sorry for asking :frowning:

I still cannot see why it worked on the client. Maybe it’s the same reason as why the script ran on the client without the Uselsx “*lsxlc”