Focal Point
Error Message - FOC1400 [SOLVED]

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/2197072276

August 20, 2014, 04:45 PM
Corky
Error Message - FOC1400 [SOLVED]
Anyone know what would cause this error? Been reading the boards searching for it, but haven't found anything that really explained it yet.

(FOC1400) SQLCODE IS -901 (HEX: FFFFFC7B)
: [58004] [IBM][CLI Driver][DB2/AIX64] SQL0901N The SQL statement failed
: because of a non-severe system error. Subsequent SQL statements can be p
: rocessed. (Reason "Too many columns or record length exceeded.".) SQLS
: TATE=58004
L (FOC1405) SQL PREPARE ERROR.
(FOC1400) SQLCODE IS 1400 (HEX: 00000578)
: SQLCODE IS -901 (HEX: FFFFFC7B)
L (FOC1406) SQL OPEN CURSOR ERROR. : WCCLM

This message has been edited. Last edited by: Corky,
August 20, 2014, 04:50 PM
Francis Mariani
quote:
Too many columns or record length exceeded

Doesn't this comment make sense?


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
August 21, 2014, 08:08 PM
StuBouyer
FOC1400 errors are errors that WebFOCUS gets back from the SQL data adapter - in this case DB2.

To find the root of the issue you need to read the next few lines and search on the SQL error codes returned from the database.

A quick google on the SQLSTATE=58004 and "Too many columns or record length exceeded" returned this from IBM

http://www-01.ibm.com/support/....wss?uid=swg1IC98761

Are you using DB2 10.1 by any chance? You might need to apply a fix.

Otherwise your record set being returned is too big for DB2 to process.

Cheers

Stu


WebFOCUS 8.2.03 (8.2.06 in testing)
August 26, 2014, 05:29 PM
Corky
quote:
Originally posted by Francis Mariani:
quote:
Too many columns or record length exceeded

Doesn't this comment make sense?

Not really, because it wasn't very much data.

What I ended up doing was moving one of my WHERE statements in the first hold to another part of the program.

So essentially when I tried pulling even more data in the first hold (by eliminating one of the WHERE statements) the program worked.

It wasn't much different from any other programs I've written, so I have no idea.