Hi Chris, I checked the attached console log, but it is hard to imagine the reason of the problem. Did you check the worker logs? It looks that some exceptions occured in workers, but the query master didn't recognize them. If you can, would you share worker logs? It will help to find the problem.
Thanks, Jihoon 2014-08-24 16:17 GMT+09:00 Christian Schwabe <[email protected]>: > Hello guys > > i started following query last night and this morning have seen that still > ran the query with the fact that has the display of procent not changed and > only ran on time. So I have to start again this morning reproduce the query > to the error. The result you see in the table below: > Running QueriesQueryIdQuery MasterStartedProgressTimeStatussqlKill Query > q_1408862421753_0001 > <http://christians-mbp.fritz.box:28080/querydetail.jsp?queryId=q_1408862421753_0001> > christians-mbp.fritz.box2014-08-24 08:46:3345%15 mins, 48 > secQUERY_RUNNINGINSERT > INTO TMP_DFKKKO_DFKKOP select pos.validthru, pos.mandt, pos.opbel, > pos.opupk, pos.opupz, pos.bukrs, pos.augrs, pos.abwkt, pos.hvorg, > pos.tvorg, pos.kofiz, pos.hkont, pos.mwskz, pos.mwszkz, pos.xanza, > pos.stakz, pos.astkz, pos.opsta, pos.infoz, pos.inkps, pos.betrh, > pos.studt, ko.fikey, ko.blart, ko.herkf, ko.stbel, ko.storb, ko.ernam, > ko.cpudt, ko.cputm, ko.bldat, ko.budat from dfkkop_hist pos left join > dfkkopw_hist wdh on ( pos.validthru = wdh.validthru and pos.mandt = > wdh.mandt and pos.opbel = wdh.opbel and pos.whgrp = wdh.whgrp ) inner join > dfkkko_hist ko on ( pos.validthru = ko.validthru and pos.mandt = ko.mandt > and pos.opbel = ko.opbel ) > > Second Screenshot: > Running QueriesQueryIdQuery MasterStartedProgressTimeStatussqlKill Query > q_1408862421753_0001 > <http://christians-mbp.fritz.box:28080/querydetail.jsp?queryId=q_1408862421753_0001> > christians-mbp.fritz.box2014-08-24 08:46:3343%23 mins, 21 > secQUERY_RUNNINGINSERT > INTO TMP_DFKKKO_DFKKOP select pos.validthru, pos.mandt, pos.opbel, > pos.opupk, pos.opupz, pos.bukrs, pos.augrs, pos.abwkt, pos.hvorg, > pos.tvorg, pos.kofiz, pos.hkont, pos.mwskz, pos.mwszkz, pos.xanza, > pos.stakz, pos.astkz, pos.opsta, pos.infoz, pos.inkps, pos.betrh, > pos.studt, ko.fikey, ko.blart, ko.herkf, ko.stbel, ko.storb, ko.ernam, > ko.cpudt, ko.cputm, ko.bldat, ko.budat from dfkkop_hist pos left join > dfkkopw_hist wdh on ( pos.validthru = wdh.validthru and pos.mandt = > wdh.mandt and pos.opbel = wdh.opbel and pos.whgrp = wdh.whgrp ) inner join > dfkkko_hist ko on ( pos.validthru = ko.validthru and pos.mandt = ko.mandt > and pos.opbel = ko.opbel ) > > Third Screenshot: > > Finished QueriesQueryIdQuery MasterStartedFinishedTimeStatussql > q_1408862421753_0001 > <http://christians-mbp.fritz.box:28080/querydetail.jsp?queryId=q_1408862421753_0001> > christians-mbp.fritz.box2014-08-24 08:46:33--QUERY_RUNNINGINSERT INTO > TMP_DFKKKO_DFKKOP select pos.validthru, pos.mandt, pos.opbel, pos.opupk, > pos.opupz, pos.bukrs, pos.augrs, pos.abwkt, pos.hvorg, pos.tvorg, > pos.kofiz, pos.hkont, pos.mwskz, pos.mwszkz, pos.xanza, pos.stakz, > pos.astkz, pos.opsta, pos.infoz, pos.inkps, pos.betrh, pos.studt, ko.fikey, > ko.blart, ko.herkf, ko.stbel, ko.storb, ko.ernam, ko.cpudt, ko.cputm, > ko.bldat, ko.budat from dfkkop_hist pos left join dfkkopw_hist wdh on ( > pos.validthru = wdh.validthru and pos.mandt = wdh.mandt and pos.opbel = > wdh.opbel and pos.whgrp = wdh.whgrp ) inner join dfkkko_hist ko on ( > pos.validthru = ko.validthru and pos.mandt = ko.mandt and pos.opbel = > ko.opbel ) > > As you can see, the query is still running but there is no image data and > progress more. > > I attached a log in which you can see the output in the console. Striking > here is the display of the percentage jumps sometimes and not further > altered towards the end and remains constant. > The data size of the tables to which I JOINS by lead is for dfkkop_hist > 5,83GB, dfkkopw_hist 2,47GB and dfkkko_hist 2.35 GB. As I write this, the > description of the query is still running. > I know these are large amounts of data, but I would have expected which > thus constitutes the colloquial no problem. Can you imagine why it comes > here to this problem? > > > > > Best regards, > Chris > >
