In 22.214.171.124, we have a job that has 3 assets - Buffer Table, Insert Trigger, & Update Trigger. We had stopped the job last Friday. The Buffer table has not refreshed since then.
How can we get the Buffer table to pull everything since last Friday? Thanks.
Please let me know your thoughts.
This topic has been locked.
4 replies Latest Post - 2010-10-26T22:22:35Z by SystemAdmin
Pinned topic Refreshing Buffer Table
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2010-10-26T22:22:35Z at 2010-10-26T22:22:35Z by SystemAdmin
Refreshing Buffer Table2010-10-26T17:15:47Z in response to SystemAdminStopping the Job should not affect the Buffer table as records are put into that table via the insert and update triggers. The job takes records out to process them.
If you are not getting records added to the buffer table you need to check the triggers, if they are not getting removed you need to ensure the job works, and then turn it back on.
If you have turned it back on, and you are not getting queued records pulled from the buffer table, you need to check the assets section and ensure that the name and location of the buffer table is correct. For instance; we store those buffer tables in a seperate but linked db so we always need to update the assests section with the fully qualified name: Database.schema.table.
Thanks Mark2010-10-26T17:40:17Z in response to SystemAdminThanks Mark. I appreciate your response.
As you correctly said, the triggers were missing. But, now the main challenge is to pull all the records into the buffer table.
How to populate the IH_FLAG field? What about IH_PK? IH_OPERATION_NAME will be "INSERT"?
After few struggles, I figured the IH_PK is primary key, IH_FLAG will be NULL and IH_OPERATION_NAME = 'INSERT"
but, when the job ran, the error was
An exception occurred while processing the inbound job: Exception while getting min and max id from buffer table
RE: min and max ids2010-10-26T21:23:26Z in response to SystemAdminSajid,
The min and max error is sometimes a permission issue. Did you ensure the account that you are using has access to the control table? It sounds like you went through some intense database changes.
If the account your using has permissions, sometimes it's the appliance itself that has problems, and a restart corrects.
Hi David2010-10-26T22:22:35Z in response to SystemAdminHi David,
First of all, thank you very much for the response to my post (& also to other posts). You valuable comments are appreciated.
Permissions were okay. Mahesh from Cast Iron support suggested that I undeploy/load the missing data into the buffer table/start the job (in order). This worked. Thanks Mahesh.
Yes, we had a deployment which wiped out the triggers...
Restart was my last alternative but could not try it as customers were actively using the appliance with their real time jobs.