New answers tagged odbc
I had a similar problem, the fix was a linked table refresh. Access was not aware that the precision had changed in my Oracle table and kept giving me the 'precision too small' error.
There are technically two windows for ODBC Data Sources in Windows. The 64 bit window pops up when navigating to Control Panel > Administrative Tools > ODBC. That connection for NETEZZA_I2B2_ETL worked. However, the 32 bit dialog also had this data source. But the connection failed there. So after I fixed the connection, Informatica worked, and it ...
I had a key in this registry path that was not pointing to anything. So I removed it. HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI (this is the 64 bit window that pops up) Realize that there is also a 32 bit window for ODBC that exists for this registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI C:\Windows\SysWOW64\odbcad32.exe (Yes, ...
I know this was asked a while ago, but maybe someone else will stumble across this answer and not spend the multiple hours that I've been bashing my head against this. Turns out that you need to use the SQL_WVARCHAR type for Variables. The following is my evidence, showing the SQL_WVARCHAR works. OLEDB command from SQL Profiler: exec sp_executesql N'exec ...
Top 50 recent answers are included