| Fatal NI connect error 12638, connecting to: [message #622825] |
Sun, 31 August 2014 09:08  |
|
|
Hi
Recently we have changed our Oracle Database 11g (Enterprise Edition Release 11.2.0.3.0 on Windows Server 2008 Enterprise Edition) to a new server. Accordingly we have modified the configuration settings of the applications (third party) to point to the new database. The application services were started and all options were seems to be working fine. But one of the application is showing system exception error and closes the connection. This is occurring regularly. Then we used to restart that application service and then start the application itself which allows user to work for some time.
The alert log shows the following error:
Sat Aug 30 15:45:17 2014
***********************************************************************
Fatal NI connect error 12638, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - Production
Time: 30-AUG-2014 15:45:17
Tracing not turned on.
Tns error struct:
ns main err code: 12638
TNS-12638: Credential retrieval failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (2368) as a result of ORA-609
Sat Aug 30 15:45:27 2014
***********************************************************************
Fatal NI connect error 12638, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - Production
Time: 30-AUG-2014 15:45:27
Tracing not turned on.
Tns error struct:
ns main err code: 12638
TNS-12638: Credential retrieval failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (3520) as a result of ORA-609
The sqlnet.log, also shows continuously the same above mentioned error. We contacted the application (third party) support, they advised setting SQLNET.EXPIRE_TIME parameter to 1 may resolve the issue.
No my point is, if we set the above parameter in SQLNET.ORA file, do we need to restart the instance?
Can we RELOAD the listener without disturbing/affecting the users connected to that instance as restarting the database needs downtime, which is difficult as operations are running round the clock 24x7?
Could anyone out there help me out to resolve this.
Thanks & Regards
|
|
|
|
|
|
|
|
|
|
| Re: Fatal NI connect error 12638, connecting to: [message #622999 is a reply to message #622857] |
Wed, 03 September 2014 04:06  |
|
|
Thanks a lot for you kind help in resolving the issue. Anyway, the problem was with the Application (third party) we are using.
Those people asked us to change some parameters in the application itself and it worked. Users are able to connect/work without
any interruption now.
Once again thank you very much.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
