I found this knowledge base answer to fixing a stuck extraction....
If an extraction is stuck in Editing, Counting or Scheduled status and you are sure that the extraction's status should be Open, the suggestion below should allow you to reset the status of the extraction to be Open. 1) Locate the extraction number that is stuck by noting the value in the "Extr No" column in Extractions. 2) Open a Query window in Enterprise Manager and switch to the impresario_cci database. 3) Issue the following statement, replacing ### with the extraction_no to be reset: Update t_ka_header set status = 'O' where ka_no = ### (If there are multiple extractions that need to be reset, note all of the extraction numbers and issue the following statement, replacing the # signs with these extraction numbers): Update t_ka_header set status = 'O' where ka_no in (#, ##, ###) You may want to try this in your test environment first to make sure you update the approriate extractions. Once everything appears to be in order, replicate this procedure in the live system."
Yet when I queried select * from t_ka_header where ka_no = 1512 I got "Msg 208, Level 16, State 1, Line 1Invalid object name 't_ka_header'".
I then searched the tables and found only 't_ka_response'. Has the naming convention of this table changed? Am I mentally challenged and or not had enough caffeine today?
Does anyone know what causes extractions to get stuck in the 'counting' status to begin with? I have run a number of extractions in the past few days and all are frozen in counting.
Thanks,
Chuck Buchanan
Chuck,
Are these extractions using any custom List Builder elements?
--Gawain
No.
One extraction was as simple as one segment with just a single performance date. No matter what the criteria, all extractions are getting stuck in the counting status.
I've seen this happen in the past on more of a one-time-only basis, but not with all extractions one after another.