DSBrowser1.DSLink1: DSD.BCIGetNext call to SQLFetch failed.
SQL statement:SELECT TG_TERRITORY.ADDR1, TG_TERRITORY.ADDR2, TG_TERRITORY.TERRITORY, TG_TERRITORY.NAME, TG_TERRITORY.ADDRESS, TG_TERRITORY.CITY, TG_TERRITORY.STATE, TG_TERRITORY.ZIP_CODE, TG_TERRITORY.PHONE_NO, TG_TERRITORY.SPARE, TG_TERRITORY.W_SHOP, TG_TERRITORY.PROFIT_CENTER_NO, TG_TERRITORY.AREA, TG_TERRITORY.LI_NO, TG_TERRITORY.POST_CODE, TG_TERRITORY.SPARE_A, TG_TERRITORY.OPEN_CALLS, TG_TERRITORY.SPARE_B, TG_TERRITORY.LI_NO_A, TG_TERRITORY.PRODUCT_TYPE, TG_TERRITORY.BRAND FROM TG_TERRITORY
SQLSTATE=S1000, DBMS.CODE=930122
[Ardent][SQL Client][UNIVERSE]UniVerse/SQL: Row length exceeds buffer size.
Please Help --- What is causing this error?
Need more information! release level? operating system?
*************************************************************
Rick Schirm
Application Performart Ltd.
Vice President of Engineering
mailto:rick.schirm@performart.com
web: www.performart.com
phone: 817.291.6177
*************************************************************
-----Original Message-----
From: Roosa, Mike [mailto:Mike.Roosa@getronics.com]
Sent: Thursday, August 31, 2000 8:27 AM
To: informix-datastage@oliver.com
Subject: Please Help --- What is causing this error?
DSBrowser1.DSLink1: DSD.BCIGetNext call to SQLFetch failed.
SQL statement:SELECT TG_TERRITORY.ADDR1, TG_TERRITORY.ADDR2, TG_TERRITORY.TERRITORY, TG_TERRITORY.NAME, TG_TERRITORY.ADDRESS, TG_TERRITORY.CITY, TG_TERRITORY.STATE, TG_TERRITORY.ZIP_CODE, TG_TERRITORY.PHONE_NO, TG_TERRITORY.SPARE, TG_TERRITORY.W_SHOP, TG_TERRITORY.PROFIT_CENTER_NO, TG_TERRITORY.AREA, TG_TERRITORY.LI_NO, TG_TERRITORY.POST_CODE, TG_TERRITORY.SPARE_A, TG_TERRITORY.OPEN_CALLS, TG_TERRITORY.SPARE_B, TG_TERRITORY.LI_NO_A, TG_TERRITORY.PRODUCT_TYPE, TG_TERRITORY.BRAND FROM TG_TERRITORY
SQLSTATE=S1000, DBMS.CODE=930122
[Ardent][SQL Client][UNIVERSE]UniVerse/SQL: Row length exceeds buffer size.
*************************************************************
Rick Schirm
Application Performart Ltd.
Vice President of Engineering
mailto:rick.schirm@performart.com
web: www.performart.com
phone: 817.291.6177
*************************************************************
-----Original Message-----
From: Roosa, Mike [mailto:Mike.Roosa@getronics.com]
Sent: Thursday, August 31, 2000 8:27 AM
To: informix-datastage@oliver.com
Subject: Please Help --- What is causing this error?
DSBrowser1.DSLink1: DSD.BCIGetNext call to SQLFetch failed.
SQL statement:SELECT TG_TERRITORY.ADDR1, TG_TERRITORY.ADDR2, TG_TERRITORY.TERRITORY, TG_TERRITORY.NAME, TG_TERRITORY.ADDRESS, TG_TERRITORY.CITY, TG_TERRITORY.STATE, TG_TERRITORY.ZIP_CODE, TG_TERRITORY.PHONE_NO, TG_TERRITORY.SPARE, TG_TERRITORY.W_SHOP, TG_TERRITORY.PROFIT_CENTER_NO, TG_TERRITORY.AREA, TG_TERRITORY.LI_NO, TG_TERRITORY.POST_CODE, TG_TERRITORY.SPARE_A, TG_TERRITORY.OPEN_CALLS, TG_TERRITORY.SPARE_B, TG_TERRITORY.LI_NO_A, TG_TERRITORY.PRODUCT_TYPE, TG_TERRITORY.BRAND FROM TG_TERRITORY
SQLSTATE=S1000, DBMS.CODE=930122
[Ardent][SQL Client][UNIVERSE]UniVerse/SQL: Row length exceeds buffer size.
First guess is that youre running into a limit on the length of a row (in
characters) in a result set.
By default this limit is 8192. Are some of your VarChar fields very long, or contain many multi-values? You can set a larger limit in the uvodbc.config file in the project directory. For example: MAXFETCHBUFF = 16384 will allow 16KB per row. Note that the space either side of the "=" is required.
> ----------
> From: Roosa, Mike[SMTP:Mike.Roosa@getronics.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 31 August 2000 21:26
> To: informix-datastage@oliver.com
> Subject: Please Help --- What is causing this error?
>
> DSBrowser1.DSLink1: DSD.BCIGetNext call to SQLFetch failed. SQL
> statement:SELECT TG_TERRITORY.ADDR1, TG_TERRITORY.ADDR2,
> TG_TERRITORY.TERRITORY, TG_TERRITORY.NAME, TG_TERRITORY.ADDRESS,
> TG_TERRITORY.CITY, TG_TERRITORY.STATE, TG_TERRITORY.ZIP_CODE,
> TG_TERRITORY.PHONE_NO, TG_TERRITORY.SPARE, TG_TERRITORY.W_SHOP,
> TG_TERRITORY.PROFIT_CENTER_NO, TG_TERRITORY.AREA, TG_TERRITORY.LI_NO,
> TG_TERRITORY.POST_CODE, TG_TERRITORY.SPARE_A, TG_TERRITORY.OPEN_CALLS,
> TG_TERRITORY.SPARE_B, TG_TERRITORY.LI_NO_A, TG_TERRITORY.PRODUCT_TYPE,
> TG_TERRITORY.BRAND FROM TG_TERRITORY SQLSTATE=S1000, DBMS.CODE=930122
> [Ardent][SQL Client][UNIVERSE]UniVerse/SQL: Row length exceeds buffer
> size.
>
characters) in a result set.
By default this limit is 8192. Are some of your VarChar fields very long, or contain many multi-values? You can set a larger limit in the uvodbc.config file in the project directory. For example: MAXFETCHBUFF = 16384 will allow 16KB per row. Note that the space either side of the "=" is required.
> ----------
> From: Roosa, Mike[SMTP:Mike.Roosa@getronics.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 31 August 2000 21:26
> To: informix-datastage@oliver.com
> Subject: Please Help --- What is causing this error?
>
> DSBrowser1.DSLink1: DSD.BCIGetNext call to SQLFetch failed. SQL
> statement:SELECT TG_TERRITORY.ADDR1, TG_TERRITORY.ADDR2,
> TG_TERRITORY.TERRITORY, TG_TERRITORY.NAME, TG_TERRITORY.ADDRESS,
> TG_TERRITORY.CITY, TG_TERRITORY.STATE, TG_TERRITORY.ZIP_CODE,
> TG_TERRITORY.PHONE_NO, TG_TERRITORY.SPARE, TG_TERRITORY.W_SHOP,
> TG_TERRITORY.PROFIT_CENTER_NO, TG_TERRITORY.AREA, TG_TERRITORY.LI_NO,
> TG_TERRITORY.POST_CODE, TG_TERRITORY.SPARE_A, TG_TERRITORY.OPEN_CALLS,
> TG_TERRITORY.SPARE_B, TG_TERRITORY.LI_NO_A, TG_TERRITORY.PRODUCT_TYPE,
> TG_TERRITORY.BRAND FROM TG_TERRITORY SQLSTATE=S1000, DBMS.CODE=930122
> [Ardent][SQL Client][UNIVERSE]UniVerse/SQL: Row length exceeds buffer
> size.
>