MOS Note: 2757734.1 – Windows: While Connect to Database Getting ORA-12638 After Applying Jan 2021 WINDBBP 19.10.I would like to ask you to open SRs and check with Oracle Support for further guidance as I don’t have the chance to test with all the different client options and possibilities. Further Questions?Īs many of you commented already, I have not more information about this issue – and especially no further advice. Then everything should work as it has been worked before. You will need to set this in your client-side sqlnet.ora: SQLNET.NO_NTLM=FALSE So NO_NTLM=TRUE is now the standard from 19.10.0 on for Windows systems. Add an Input tool to the canvas and select Data Sources. After installing the driver you can then select it from a list of drivers available in the Alteryx tool you are using to connect to the database. Access to it has been disabled by default due to a security fix. To connect via OLEDB, first, install the OLEDB driver on your machine. NTLM is the Windows Networks LAN Manager authentication service. and might have an invalid value as far as Oracle is concerned. Or it happens simply when you try to connect from the client using sqlplus you’d do a SQLnet trace, you would spot this message: NO_NTLM set, not local conn, not actively falling back to NTLM even if server might not support kerberos. Using 32-bit Oracle with 64-bit FME may produce the following error in the FME Workspace. When you have SQLNET.AUTHENTICATION_SERVICES=NTS in your sqlnet.ora, then you may see now ORA-12638: Credential retrieval failed when you for instance select over a database link. after installing 32-bit Oracle client software on a 64-bit Windows. This is an issue which happens on MS Windows only. There is no control over this path name at install time because the SQL Server. So at first, thanks to Ernst and Marcus for bringing this to my attention. Photo by Fanny Rascle on Unsplash What has been changed?
0 kommentar(er)
