I ran across an interesting error in using SSIS to pull data from an Oracle database that I am posting screenshots for both the error and the fix; it's quite simple, but could cause some problems for anyone if they are either not aware nor know how to resolve the warning (it shows as just a warning and will allow you to continue building and using the package, but you will be exposed to issues down the road if not resolved here).
Here is a screenshot of the error, in this example, my datasource for my OLE DB Source in my Data Flow task in SSIS is an Oracle database:
To resolve this issue, go to the properties window for the OLE DB Source data flow object and set "AlwaysUseDefaultCodePage" to True.
Why does this happen? SSIS cannot read the character set used by the Oracle database and thus gives you this warning. In most cases in your U.S. based projects, you will be fine assumming 1252 which is the Western Alphabet character set -- if this is not the case, then you will need to determine what character set the source database is using and be sure to set your values appropriately. Here is an Oracle script you can execute against the database to try and determine this value (not guaranteed to work against all versions of Oracle): select * from sys.props$ where name = 'NLS_CHARACTERSET'
Tags: ssis,
oracle
Categories: SQL Server |
SSIS