Hi all - looking to complete an extraction and I am running into a behavior that I'm not sure if it is intended. As you can see, one SS shows successful extraction of tables labeled 800 and up. However, when an earlier tabled primed for extraction fails to run (labeled 100-800), the previously shown passing tables fail. Any ideas on what is going on here?
Question
Do errors propagate during extraction?
+5
+14Hi, it says on the error that Metadata has been changes, meaning the current table schema mismatch with the new data. You can resolved this by doing a FULL load or if it is not an option then you can go to extraction settings and select Option B. Included metadata changes.
+5Hi Rio,
Thanks for the quick reply. That makes sense to solve metadata issues, but my main question was to understand why a failed extraction of one table causes the rest of the queued extractions to fail. Do you have any insight on why that happens?
+14Hi, sure, it depends on the data extracted, if the rest of the queued table extract is dependent on the failed extract then the rest will also fail. This is like when the header table fails, so is its Line Item table.
HTH
+5Hi, sure, it depends on the data extracted, if the rest of the queued table extract is dependent on the failed extract then the rest will also fail. This is like when the header table fails, so is its Line Item table.
HTH
Is there a method to view the dependencies on a given table? These tables in question do not execute a join on each other or anything.
+14Is there a method to view the dependencies on a given table? These tables in question do not execute a join on each other or anything.
Can you provide what data connection or system in question ?
+5Is there a method to view the dependencies on a given table? These tables in question do not execute a join on each other or anything.
We are using a JDBC connection to a DB2 database.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.