October 26, 2006 at 7:48 am
What if you log errors to sql (sysdtslog90 table), then you could retrieve the data based on the executionid and include in your email... Good Luck!
October 26, 2006 at 11:48 am
I am logging errors to sysdtslog90. Unfortunately, it won't be able to help. Below is the contents of the table containing the error. Notice that there are 3 different executionid's.
In this example I want to report FACT_AssignmentServiceTimes as the failing package. But I have no way of finding package type sources in this table. Even if there was a way to only consider package type objects, I no way of knowing which package contains the offending task. The executionid for the offending package is different than that of the starting package.
| source | executionid | |
| Update Assignment Current Keys | 70BFC971-B8A2-447F-9BDE-40E93AD8EA4E | <==offending step |
| FACT_AssignmentServiceTimes | 70BFC971-B8A2-447F-9BDE-40E93AD8EA4E | <== 3rd package in chain. Has the offending step |
| Load Assignment Service Time Fact | 70BFC971-B8A2-447F-9BDE-40E93AD8EA4E | |
| CTL_FactTableLoad | 70BFC971-B8A2-447F-9BDE-40E93AD8EA4E | |
| Update Assignment Current Keys | 2A166CFA-3262-47AE-A312-E53D74181E4B | |
| FACT_AssignmentServiceTimes | 2A166CFA-3262-47AE-A312-E53D74181E4B | |
| Load Assignment Service Time Fact | AE0F3FE7-AC11-45C5-8E6D-580D575B438D | |
| CTL_FactTableLoad | AE0F3FE7-AC11-45C5-8E6D-580D575B438D | <== 2nd package in chain |
| Load Fact Tables | AE0F3FE7-AC11-45C5-8E6D-580D575B438D | |
| Load Data Warehouse and Update Config Info | AE0F3FE7-AC11-45C5-8E6D-580D575B438D | |
| For each active not running application | AE0F3FE7-AC11-45C5-8E6D-580D575B438D | |
| CTL_DataWarehouseLoad | AE0F3FE7-AC11-45C5-8E6D-580D575B438D | <==starting package |
Viewing 2 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply