Debugging in Ascential

jpr196 · Post by **jpr196** » Tue Dec 12, 2006 4:17 pm

Hi everyone,

I was wondering if there are any ways to view more detailed information about an aborted job than using director and looking at the log file. For some of our delivered mappings that fail, all we get is a job aborted message and nothing else to really indicate what the problem might be. I was hoping to gather some more information about the job if there are means to doing this.

Thanks in advance for the help.

DSguru2B · Post by **DSguru2B** » Tue Dec 12, 2006 4:29 pm

Yes this website.

Jokes apart, what exact message were you referring too. I doubt any error message that the DSEngine can produce, has not been discussed here. Usually there are surrounding warning messages that aid in understanding the fatal message.

jpr196 · Post by **jpr196** » Tue Dec 12, 2006 4:56 pm

DSguru2B wrote:Yes this website.
Jokes apart, what exact message were you referring too. I doubt any error message that the DSEngine can produce, has not been discussed here. Usually there are surrounding warn ...

Ha...yeah you're right...This would be the first place i'd come if I had some kind of warning or error to run with. However, the only warning in the log is an abnormal termination of the DRS Target Stage and then a warning saying the job aborted. Anyway, the more detailed log information is just something I was wondering about to make our lives here a bit easier. No big deal, thanks though.

chulett · Post by **chulett** » Tue Dec 12, 2006 5:12 pm

Have you tried Resetting (not recompiling) the job via the Director? Sometimes that will get you a 'From previous run...' log message and it can have additional (as in helpful) information.

I_Server_Whale · Post by **I_Server_Whale** » Tue Dec 12, 2006 5:18 pm

jpr196 wrote: However, the only warning in the log is an abnormal termination of the DRS Target Stage and then a warning saying the job aborted.

Since you are writing into a Database, does the job terminate after loading a few records?
Or does it fail doing nothing?

If you could provide more design/behavior info on your job, then may be more mysteries can be unearthed.

Whale.

jpr196 · Post by **jpr196** » Wed Dec 13, 2006 8:37 am

chulett wrote:Have you tried Resetting (not recompiling) the job via the Director? Sometimes that will get you a 'From previous run...' log message and it can have additional (as in helpful) information.

Hi, yes I tried to reset the job in director but it didn't give me anymore information. Also, the job appears to load successfully until the ipc before the target table. Then it fails when trying to load the target table, so I don't believe any rows are being populated.

DSguru2B · Post by **DSguru2B** » Wed Dec 13, 2006 8:59 am

what is your job design. What if you replace the IPC stage with sequential file stage or just get rid of the IPC stage?

jpr196 · Post by **jpr196** » Wed Dec 13, 2006 9:59 am

Hey, Thanks for the help guys. Can't say we really found the error, but it was something to do with the target table's metadata. When we reimported the table structure, the job ran fine.

I_Server_Whale · Post by **I_Server_Whale** » Wed Dec 13, 2006 1:11 pm

Ahah, Good! Since the problem is resolved. It would be nice to mark the topic as resolved.