...

1. Check the job is running and not stuck in Rundeck.  It should rarely take more than 3 minutes.  If it's been running for over 10, it's almost certainly stuck.  Stop, allow to stop and then restart the Rundeck job and continue checking the below steps.
2. Check the Mantiki Database entity event tables to see if any events are in an error state ie have failed and no processing has occurred (SQL below).  Provided accounts have not manually adjusted for these entries, the state could be set back to pending here and when the extractor runs, it will try and process this entry again.
3. Check the Mantiki Database Dream Extractor temporary tables.  A status of 'Error' indicates that the attempt got so far as to be placed in the Mantiki temporary tables but has failed here.  You can set the corresponding entry to pending in the entity event tables but the attempt will probably fail due to a duplicate entry in the temporary table and you may need to remove a failed entry in the temporary table before setting the entity event to pending.
4. If you find errors above, it's unlikely that the entries will have reached the Dream Extractor Sql Server tables.  On taking some of the remedies above you'll want to check that the entry has appeared here thoughin the Sql Server tables.  Connection details in the main Dream Extractor guide page.  Also worth checking is that the tables contain recent data as if they don't, this is an indication that probably there is a problem (most likely one of the numbers above).

Any longer ago than two or three days since an incident and you should talk to Tim/Kris in IT in Preston and Finance in Preston for advice as to what to do next.  The entry may have been manually processed by Finance.

Useful SQL

Find transactions which haven't been processed - eg are either pending (probably legitimately waiting for processing) or are in an error state.

...

Find transactions that have been processed by the first half of the daemons ie are queued in the Mantiki Temporary tables for writing to the SQL Server Dream Extractor database but not reached a 'done' state - this may be due to errors.

select extract_customer_number, extract_shipment_created_on, extract_shipment_reference_number, record_status, record_status_comment from process_extract_dream_shipment where record_status != 'done'
UNION
select extract_customer_number, extract_refund_created_on, extract_credit_reference_number, record_status, record_status_comment from process_extract_dream_credit where record_status != 'done'
UNION
select extract_customer_number, extract_created_on, extract_payment_reference_number, record_status, record_status_comment from process_extract_dream_wbpayment_customer where record_status != 'done'
UNION
select extract_customer_number, extract_created_on, extract_payment_reference_number, record_status, record_status_comment from process_extract_dream_wbrefund_customer where record_status != 'done'
UNION
select extract_customer_number, extract_date, extract_account_type, record_status, record_status_comment from process_extract_dream_account_adjustment where record_status != 'done';

If you find your error in the above and the record_status_comment mentions a JDBC connectivity issue, then what you have is explained below - but basically Mantiki's failed to talk to the Preston database.  If you're within two or three days of the error happening then you can reset the record_status to NEW and the record will be found by the daemon and processed.   Find the id in the temporary table and make a query to update the rows.
The SQL will look like this: 
update
the table (will be one of process_extract_dream_shipment or process_extract_dream_credit or process_extract_dream_wbpayment_customer or process_extract_dream_wbrefund_customer or process_extract_dream_account_adjustment)
set record_status = 'NEW' where id in (             the id/s in the table           );

The transaction is marked as processed and I can see it in the temporary tables in Mantiki but it is not in Dream Extractor.  What's the problem?

...