Connect Error 12640
Vincenzo Messages: 6Registered: July 2004 Junior Member I have following problem with start oracle services: Fatal NI connect error 12640, connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oraclefleetdb)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=fleetdb)(CID=(PROGRAM=D:oracleora81binoradim.exe)(HOST=OPEN_FLEET)(USER=SYSTEM)))) 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: 22-JUL-2004 11:43:01 Tracing not turned on. Tns error struct: nr err code: 0 ns main err code: 12640 TNS-12640: Authentication adapter initialization failed ns secondary err code: 0 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 I perform update Windows NT to Windows 2000 Server. If I try to start oracle services manually then it works but not work on startup PC. excused my English I hope you can help me. Report message to a moderator Re: ORA-12640 [message #67434 is a reply to message #67433] Fri, 23 July 2004 04:29 Mahesh Rajendran Messages: 10671Registered: March 2002 Location: oracleDocoVille Senior MemberAccount Moderator are u sure u are using BEQ protocol instead of TCP/IP? Report message to a moderator Re: ORA-12640 [message #67436 is a reply to message #67434] Mon, 26 July 2004 05:21 Vincenzo Messages: 6Registered: July 2004 Junior Member I have resolved the problem changing string "SQLNET.AUTHENTICATION_SERVICES= (NTS)" within the file sqlnet.ora in SQLNET.AUTHENTICATION_SERVICES= (NONE). Now the oracle startup is good and the database is running, but when i using the 'DBA Studio' tool I do not succeed to connect to me like sysdba... before the modification i connect like: (system/manager like Normal user) (system/manager like sysdba user) Me it seems that BEQ protocol is used for the client connection and not for database startup... but I dont are sure of this. However I believe to use the Tcp/Ip protocol... how I can verify it? Report message to a moderator Previous Topic: Calling Transact SQL stored procedure via Transparent Gateway Next Topic: credential retrievel fa
Problem(Abstract) Reports that are published with IWR 7 Version 2 connect to Oracle 8.1.7. When trying to launch a report in Upfront the following error message is displayed: Text: Logon error while connecting the database The report works correctly if it is launched in Impromptu http://www.orafaq.com/forum/t/24255/ or with ImpServer.exe in the server. Resolving the problem The iwr.log file contained the following: Oracle Error ORA-12640. 12640, 00000, "Authentication adapter initialization failed" // *Cause: The function specified in the authentication table entry for the service failed. // *Action: Enable tracing http://www.ibm.com/support/docview.wss?uid=swg21354868 to determine the exact error. The solution is to modify the parameter SQLNET.AUTHENTICATION_SERVICES in the file sqlnet.ora Edit the file sqlnet.ora in a text editor such as Notepad, and change SQLNET.AUTHENTICATION_SERVICES=(NTS) to SQLNET.AUTHENTICATION_SERVICES=(NONE) Cross reference information Segment Product Component Platform Version Edition Business Analytics Cognos Series 7 PowerPrompt Business Analytics Cognos Series 7 Upfront Historical Number 1003188 Document information More support for: Cognos Series 7 Impromptu Web Reports Software version: Impromptu Web Reports 7.0, Impromptu Web Reports 7.1, Impromptu Web Reports 7.3, PowerPrompt 7.1, Upfront 7.3 Operating system(s): Platform Independent, Solaris, Windows Reference #: 1354868 Modified date: 2014-09-12 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
SAP on OracleWhere is this place located?All Places SAP on Oracle 22 Replies Latest reply: Sep 24, 2007 3:26 PM by Admin Admin Tweet error ORA-12640 Admin Admin Sep 14, 2007 12:36 PM Currently Being Moderated While I was https://scn.sap.com/thread/560292 instaling java-addin - database instance, system didn't start.In logs I've got following information. Thu Sep 13 13:58:50 2007C *** ERROR => OCI-call 'OCIServerAttach' failed with rc=12640 [dboci.c 4313]C *** ERROR => CONNECT failed https://davidalejomarcos.wordpress.com/2011/01/18/removing-fatal-ni-connect-error-xxxx-from-your-alert-log/ with sql error '12640' [dbsloci.c 11044]C Try to connect with default passwordC Connecting as SAPBSD/
have a script to monitor the alert.log file for any ORA-xxxx errors. With 11g we found out many entries in regards of: Fatal NI connect error The problem: alert.log file has many entries for Fatal NI connect error. Examples: *********************************************************************** Fatal NI connect error 12514, connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxx)(PORT=nnn))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=sss)(CID=(PROGRAM=oracle)(HOST=xxx)(USER=oracle)))) VERSION INFORMATION: TNS for Linux: Version 11.2.0.2.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production Time: 17-JAN-2011 10:20:45 Tracing not turned on. Tns error struct: ns main err code: 12564 TNS-12564: TNS:connection refused ns secondary err code: 0 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 Error 12514 received logging on to the standby Mon Jan 17 10:21:45 2011 *********************************************************************** or *********************************************************************** Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.2.0 - Production Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production Time: 18-JAN-2011 15:13:08 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12560 nt main err code: 505 TNS-00505: Operation timed out nt secondary err code: 110 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=xx.xx.x.xx)(PORT=nnnn)) Tue Jan 18 15:40:20 2011 The solution: We will have an entry on the alert.log file every time a client connection of any kind fails to complete or is aborted. One way to minimize the impact is by using the parameter SQLNET.INBOUND_CONNECT_TIMEOUT (default to 60 seconds on 10gR2 and 11g) but, sometimes, this value is not adequate. Oracle also