Hello, > There should be not differences between Linux/Windows and > 7.4/7.5. Are we talking about a Unicode-environment? Do all > columns have the same codetype (ASCII/UNICODE)? What does the > tabledefinitions (columnname, datatype, codetype, length) > look like for table contract?
Initially we used UNICODE. After switching to ASCII, the statements did fit. Close (very vew bytes left), but it worked. The difference was UNICODE on Linux vs. ASCII on Windows. > There is no way to adjust the limit. While it's solved for now, I have this feeling that this will hurt us some time again. We'll see. Thank you for your valuable hint. Matthias > -----Original Message----- > From: Zabach, Elke [mailto:[EMAIL PROTECTED] > Sent: Monday, April 26, 2004 3:42 PM > To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED] > Subject: RE: DB Error -2003 "Output columns too long" - > Differences between Versions? > > > Matthias G�rtner wrote: > > > > Hello, > > > > Both statements below can be executed under Windows MaxDB > 7.5 without > > problems. With Linux and SAP DB 7.4 a database exception occurs > > (-2003, "Output columns too long", JDBC). > > > > There seems to be an internal limit. > > Is there a way to adjust this limit? > > Why is there a difference between Linux and Windows or > 7.4./7.5? What > > do you suggest to circumvent this? > > > > There should be not differences between Linux/Windows and > 7.4/7.5. Are we talking about a Unicode-environment? Do all > columns have the same codetype (ASCII/UNICODE)? What does the > tabledefinitions (columnname, datatype, codetype, length) > look like for table contract? > > There is no way to adjust the limit. > > Elke > SAP Labs Berlin > > > Regards, > > Matthias > > > > > > > > SELECT > contract.scn,contract.carrieraccessstatus,contract.containerTy > > pes,contract.r > > emarks,contract.carrierstatus,contract.template,contract.durat > > ionTo,contract > > .originRegion,contract.vip1IsPerc,contract.clientName,contract > > .vip2IsPerc,co > > ntract.fac120,contract.destinationRegion,contract.mqc20teu,con > > tract.isClient > > Contract,contract.vip2onVip1,contract.email,contract.fac1IsPer > > c,contract.vip > > 220,contract.carrierId,contract.fac140,contract.vipInfo,contra > > ct.dateOfIssue > > ,contract.vip120,contract.emailCc,contract.durationFrom,contra > > ct.comGrouping > > ,contract.activatestatus,contract.mqc40teu,contract.currency,c > > ontract.isActi > > ve,contract.emailBcc,contract.demurrage,contract.vip240,contra > > ct.clientcontr > > acttype,contract.issuedBy,contract.detention,contract.contract > > owner,contract > > .vip140 FROM contract WHERE scn='?' > > > > select > t.scn,t.carrieraccessstatus,t.containertypes,t.remarks,t.carri > > erstatus,t.tem > > plate,t.durationto, > > t.originregion,t.vip1isperc,t.clientname,t.vip2isperc,t.fac120 > > ,t.destination > > region,t.mqc20teu,t.isclientcontract, > > t.vip2onvip1,t.email,t.fac1isperc,t.vip220,t.carrierid,t.fac14 > > 0,t.vipinfo,t. > > dateofissue,t.vip120,t.emailcc,t.durationfrom, > > t.comgrouping,t.activatestatus,t.mqc40teu,t.currency,t.isactiv > > e,t.emailbcc,t > > .demurrage,t.vip240,t.clientcontracttype, > > t.issuedby,t.detention,t.contractowner,t.vip140 from contract > > as t where > > scn='?' > > > > com.sap.dbtech.jdbc.exceptions.DatabaseException: [-2003] (at > > 637): Output > > columns too long > > at > > com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPa > > cket.java:69) > > at > > com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSa > > pDB.java:768) > > at > > > com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:434) > > at > > com.sap.dbtech.jdbc.CallableStatementSapDB.sendCommand(Callabl > > eStatementSapD > > B.java:1498) > > at > > com.sap.dbtech.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:725) > > at > > com.sap.dbtech.jdbc.CallableStatementSapDB.doParse(CallableSta > > tementSapDB.ja > > va:224) > > at > > com.sap.dbtech.jdbc.CallableStatementSapDB.constructor(Callabl > > eStatementSapD > > B.java:175) > > at > > com.sap.dbtech.jdbc.CallableStatementSapDB.<init>(CallableStat > > ementSapDB.jav > > a:79) > > at > > com.sap.dbtech.jdbc.ConnectionSapDB.prepareStatement(Connectio > > nSapDB.java:66 > > 0) > > > > > > > > -- > > MaxDB Discussion Mailing List > > For list archives: http://lists.mysql.com/maxdb > > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/maxdb?> [EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
