How to prevent rulerunner from creating record on Engine DB, taskstats table?
Hi all,
I am having mvscan as part of my rulerunner workflow to ensure that my workflow is fully automated. However, it keeps inserting record for the scan action even when there is no document found in the import folder. My guess is because the mvscan rule keeps listening to my import folder.
Is there any way to prevent this from happening? Thank you in advance!
Best regards, Aaron Chia
There shouldn't be any "new" record created if the import folder is indeed empty. So, my first guess is that the import folder is not completely empty because it is on a Windows server and has one of those Thumbs.db which is hidden by default. So, please confirm if it's the case and do a little research to turn it off.
If it's not the case, you'd need to provide some logs.
My second guess is that you didn't set or have the folder for images to be saved after import or rulerunner doesn't have proper access to it.
To prove or disprove this, we need to see logs and/or your batch's xml.
Hi @yanglo,
Thank you for the prompt reply. To provide more background, the new record is actually inserted into "taskstats" table, not the "tmbatch" table.
Also, for my mvscan rule, I have set the types of files to ingest to only tiff,tif,jpeg,jpg,pdf,png,bmp,jpg. Thus, to ingest Thumbs.db is not possible.
I have attached a sample of the DB record below.
Thank you once again!
Best regards, Aaron Chia
So, both of my guesses are off the target. :(
Now that you've clarified the case, I'm not sure if it's best for a PMR. I think that, if your batches are moving forward in the job/workflow, I'd not worry about this "issue". But first, I'd find out if each of these records in taskstats table should mean or match anything in your respective batches.
Have a look at bottom of this article: http://www-01.ibm.com/support/docview.wss?uid=swg21575411
It states:
Tasks run by Rulerunner / Rulerunner Quattro or other clients Inserts cannot be prevented with these clients, but a trigger can be created within SQL or Oracle to immediately delete the entry. For the above example, the trigger might look like the following:
Create Trigger on taskstats
AFTER insert AS
BEGIN
Delete from taskstats where new.ts_TaskName='VScan' AND new.ts_Status='pending'
END
/////////////////////////////////////////////////////
I hope this helps.
Peace,
Ed Lee