Question Re: Data Services General error;274 inserted value too large for column in Technology Q&A

Data Services General error;274 inserted value too large for column

Former Member — Tue, 05 Dec 2017 05:57:38 GMT

I get this error (below) when copying data from HANA data base to another HANA data base. The work around is to extend the column in the target.

My question is why is this happening as I am moving data from HANA to HANA ?

I think the issue is to do with unicode charcater in a field eg 1/4 ..is a special unicode character.

I think this is a bug as DS imports a column definition a varchar(32) but the target must be manually changed to varchar(40).

Is there some settings in DS or the target database.?

In my case when moving from a erp_table via odbc to a new HANA table in another database, I seen this when moving from various HANA data bases generally ERP or CRM hana tables -> to new blank hana database even using the older ftp or scp. still gets this error.

Is this a bug , is there a setting that can be chaneg rather that constantky increasing teh column when someone puts in a chinese chracter etc..

ODBC data source <XXX.XXX.XXX.au> error message for operation <SQLExecute>: <[SAP AG][LIBODBCHDB SO][HDBODBC]
                                                            

General error;274 inserted value too large for column

Re: Data Services General error;274 inserted value too large for column

former_member187605 — Thu, 07 Dec 2017 14:51:24 GMT

No bug at all.

Use NVARCHAR data type instead of VARCHAR. And all your unicode issues will mysteriously disappear.

Re: Data Services General error;274 inserted value too large for column

Former Member — Thu, 12 Apr 2018 04:10:43 GMT

Hi Thanks Again, you have helped me so many time in the past but didn't know!

I couldn't change the column defintions to nvarchar in either source or destination.data flows , however there on the destination template table , double click on the table , and options table , hidden at the bottom , is an

option Use NVARCHAR fro VARCHAR columns in support databases., turning this to yes fix the problem and then turning back to no broke it.

was having this problem from maxdb to hana..in this case.as well.

thanks once again.