https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52810#M14528 Hi. I've used proc append + force + nowarn and it was only partly successful. It supressed most of the warnings except for the data type mismatch (i.e. col1 in BASE has different lengths with that of DATA). Is there a way to suppress this too? Is it documented somewhere why this type of warning is not being suppressed? Thu, 03 Mar 2011 17:22:14 GMT omBoy 2011-03-03T17:22:14Z https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52805#M14523 HI all, <BR /> <BR /> I have problems with appending a SAS Data set to an oracle table. <BR /> Connection to the Oracle-database via the LIBNAME-statement works fine, also the table definition in ORACLE fits with the format definition of my SAS-table at first view. But when I execute a PROC CONTENTS statement on the ORACLE table the column definitions are not the same as in the ORACLE definition (e.g. character 40 in SAS instead of character 30 in ORACLE and so on). <BR /> So I always receive warnings in response to my PROC APPEND statement because of different lengths on BASE and DATA files, though the definitions look OK as I mentioned above. <BR /> <BR /> Does anybody know how to solve this problem? <BR /> <BR /> Thanks in advance,<BR /> Chris Mon, 20 Dec 2010 14:18:47 GMT https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52805#M14523 deleted_user 2010-12-20T14:18:47Z https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52806#M14524 have you tried the force option? Thu, 23 Dec 2010 00:30:11 GMT https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52806#M14524 Reeza 2010-12-23T00:30:11Z https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52807#M14525 Hi<BR /> <BR /> From what you describe it's not the format but the length of the character variables which are different. So PROC APPEND is kind of right to issue a truncation warning.<BR /> <BR /> The best solution would be to define the lengths in your SAS data set according to the ones in the ORACLE table.<BR /> <BR /> If this is not possible and you're sure that the columns lengths in ORACLE are sufficient then you could use PROC APPEND NOWARN; to suppress the warnings. Not pretty - but it should work.<BR /> <BR /> HTH<BR /> Patrick Thu, 23 Dec 2010 09:45:13 GMT https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52807#M14525 Patrick 2010-12-23T09:45:13Z https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52808#M14526 Hi.Patrick.<BR /> Long time no see your posting.<BR /> Happy Holidays!<BR /> <BR /> <BR /> Ksharp Fri, 24 Dec 2010 07:04:53 GMT https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52808#M14526 Ksharp 2010-12-24T07:04:53Z https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52809#M14527 Hi Ksharp<BR /> Yes, real life projects kept me too busy.<BR /> Merry Chrismas and happy New Year to you.<BR /> Cheers<BR /> Patrick Fri, 24 Dec 2010 11:30:15 GMT https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52809#M14527 Patrick 2010-12-24T11:30:15Z https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52810#M14528 Hi. I've used proc append + force + nowarn and it was only partly successful. It supressed most of the warnings except for the data type mismatch (i.e. col1 in BASE has different lengths with that of DATA). Is there a way to suppress this too? Is it documented somewhere why this type of warning is not being suppressed? Thu, 03 Mar 2011 17:22:14 GMT https://communities.sas.com/t5/SAS-Procedures/Need-help-for-PROC-APPEND/m-p/52810#M14528 omBoy 2011-03-03T17:22:14Z