Follow-up on your open support ticket

Hi Nikhil, A quick follow-up on the ticket you have open with us. We have been through the load history on our side and the source that stopped loading last failed at the same step each night. It looks as though something changed on the source before our job picked it up, but I would rather you confirm than have me guess from here. Two things would help me close this off: - Can you confirm whether anything changed in that source recently, a table, a column or a permission? - Which role is the brain's service account using to read it? Once I have those I can tell you whether this is a fix on our side or yours, and I will keep the ticket open until a full nightly refresh has completed cleanly. Thanks, Olivia Support Engineer, BG-Demo

Olivia, I checked the load history as well. That's a schema change: a column was renamed upstream and the object the job reads was recreated. The service role was never granted on the new object, so the job fails at read. I have fixed the grants in the test schema and the load runs there. Production I will do on Monday. I am not changing it on a Friday, and I won't confirm it works in production until I have tested it there. If your side has a mapping that references the old column name, that will need updating too. Can you check? Nikhil

Hi Nikhil, Thanks, that is clear and Monday is fine with us. I have checked and our connector mapping does reference the old column name. I have prepared the change so it is ready to go as soon as you tell me the grants are in place in production. I would rather not apply it before then, so the job does not fail again overnight. On Monday, drop me a line when you are done and I will re-run the load by hand, then watch the nightly refresh the following morning. If it completes before 07:00 as it should, I will close the ticket and note the cause on it for your records. Have a good weekend. Kind regards, Olivia Support Engineer, BG-Demo