Q
Problem solve Get help with specific problems with your technologies, process and projects.

Clients can't connect after registering Oracle server at domain

We use Oracle8i 8.1.7.00. The Oracle server (fix IP 192.168.0.2) is embedded in the domain DOM_MIC. The clients are embedded the domain ADS_MIC. That all works fine. Now, when I register the Oracle server (fix IP 192.168.0.2) at the domain ADS_MIC, the clients cannot connect to the Oracle server database again.

Fatal NI connect error 12640, connecting to:

(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleorc1)(A RGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=( SID=orc1)(CID=(PROGRAM=D:oracleora81binoradim.exe)(HOST=ORACLE)(USER=SYS TEM))))

VERSION INFORMATION: TNS for 32-bit Windows: Version 8.1.7.0.0 - Production Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 8.1.7.0.0 - Production Time: 17-MAI-2004 16:49:38, Tracing not turned on.

TNS error struct:
nr err code: 0 ns main err code: 12640
TNS-12640: Berechtigungs-Adapter konnte nicht initialisiert werden
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0

I'm a little rusty on my German, but I looked up the error in English and it is: 12640, 00000, "Authentication adapter initialization failed"

*Cause: The function specified in the authentication table entry for the service failed. *Action: Enable tracing to determine the exact error.

The other suspicious thing about the information you gave (which looks like it's from a sqlnet.log) is that it was generated by the oradim.exe utility. I'm not sure what's running the oradim.exe utility on your system -- that's usually only used for startup, shutdown, and maintenance activities. If your instance is no longer starting up, then I'd investigate that separately -- that's different than a connectivity issue. If the instance starts fine, but users cannot connect, then you should investigate the error that the users are seeing (which may be the same error, but may not be).

I'd suspect that with this type of error, some parameters that may be set in the sqlnet.ora file on the server or the client could be to blame. Particularly, the SQLNET.AUTHENTICATION_SERVICES parameter should be investigated. If you are using standard username/password authentication as the only authentication mechanism, then you can remove this parameter from your sqlnet.ora file or set it to (NONE). That will likely clear up your error.

Dig Deeper on Oracle database design and architecture

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close