Thanks Elke, is there something like a faq for database updates? the databse is very large and it is used in a production webapplication. So I have to plan an update very carefully. Do you think I should wait for the next release?
bye Daniel ----- Original Nachricht ---- Von: "Zabach, Elke" <[EMAIL PROTECTED]> An: [EMAIL PROTECTED],[email protected] Datum: 14.01.2005 12:01 Betreff: AW: com.sap.dbtech.jdbc.exceptions.DatabaseException: [-1103]: Too complicated SQL statement > [EMAIL PROTECTED] wrote: > > > > Hi, > > > > what do you think about the following error? > > Is there a way to get around this behaviour? > > Version: 'X32/LINUX 7.5.0 Build 005-121-054-885' > > > > bye > > > > Daniel > > > > ERROR 2005-01-14 09:26:47,030 > > com.callisto.inreport.Report.processReport(Report.java:216) java error > > while inserting reportResult: null > > com.sap.dbtech.jdbc.exceptions.DatabaseException: [-1103]: Too > complicated > > SQL statement > > at > > > it may help to increase installation parameter _MAXTASK_STACK. > If this does not help, please provide the command resulting in that > error, the definitions of the used table(s), views, dbprocs, trigger, > functions, referential constraints (if any) and a vtrace according to > http://sapdb.2scale.net/moin.cgi/VTrace > > BTW: Why don't you use a newer version of 7.5.00 than that of Oct 2003? > > Elke > SAP Labs Berlin > > > > com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java: > 71 > > ) > > at > > > com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:8 > 29 > > ) > > at > > com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:488) > > at > > com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:376) > > at > > > com.sap.dbtech.jdbc.CallableStatementSapDB.execute(CallableStatementSapD > B. > > java:415) > > at > > > com.sap.dbtech.jdbc.CallableStatementSapDB.execute(CallableStatementSapD > B. > > java:299) > > at > > > com.sap.dbtech.jdbc.CallableStatementSapDB.executeQuery(CallableStatemen > tS > > apDB.java:707) > > at > > > org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(Delegat > in > > gPreparedStatement.java:179) > > at com.callisto.inreport.Report.processReport(Report.java:167) > > at > > > com.callisto.inreport.openoffice.DocumentThread.processJobDatabase(Docum > en > > tThread.java:289) > > at > > > com.callisto.inreport.openoffice.DocumentThread.processJobDatabase(Docum > en > > tThread.java:213) > > at > > > com.callisto.inreport.openoffice.DocumentThread.acceptJob(DocumentThread > .j > > ava:112) > > at > > > com.callisto.inreport.servlet.ReportProcessorServlet.processQueue(Report > Pr > > ocessorServlet.java:306) > > at > > > com.callisto.inreport.servlet.ReportProcessorServlet$Supervisor.execute( > Re > > portProcessorServlet.java:352) > > at > > > com.callisto.inreport.servlet.InReportTimerTask.run(InReportTimerTask.ja > va > > :57) > > at java.util.TimerThread.mainLoop(Timer.java:432) > > at java.util.TimerThread.run(Timer.java:382) > > > > -- > > 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/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
