Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cc22
Starting Member
1 Post |
 Posted - 2015-02-25 : 12:59:55
|
| I am trying to import a data source table from our AS400 system and keep getting this error that prevents the remainder of the table from being uploaded with the import wizard. Are there specific characters that SQL is not accepting? Or is there a way to bypass the character?- Copying to [dbo].[Test_Table] (Error)MessagesError 0xc020901c: Data Flow Task 1: There was an error with Source - Query.Outputs[OLE DB Source Output].Columns[LDESC1] on Source - Query.Outputs[OLE DB Source Output]. The column status returned was: "Text was truncated or one or more characters had no match in the target code page.". (SQL Server Import and Export Wizard) Error 0xc020902a: Data Flow Task 1: The "Source - Query.Outputs[OLE DB Source Output].Columns[LDESC1]" failed because truncation occurred, and the truncation row disposition on "Source - Query.Outputs[OLE DB Source Output].Columns[LDESC1]" specifies failure on truncation. A truncation error occurred on the specified object of the specified component. (SQL Server Import and Export Wizard) Error 0xc0047038: Data Flow Task 1: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on Source - Query returned error code 0xC020902A. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. (SQL Server Import and Export Wizard) |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2015-02-25 : 14:54:47
|
| I encountered the truncate error yesterday actually. I couldn't figure out why the column in question was throwing that error since the source data was only 20 characters, and the destination column was varchar(50). It turns out that the package's source column was set to length=6 (not sure why), which I found in the advanced editor. I couldn't modify the value from the advanced editor page since it was grayed out, so instead I modified the xml (view code on the dtsx file).Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2015-02-25 : 14:55:15
|
| Oh I just realized you are using the wizard. To do what I mentioned, you'll need to save the package and then modify it.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
unmatched character in import