Capturing the error in a file or table
Moderators: chulett, rschirm, roy
Capturing the error in a file or table
Hi,
How can i write the error we are getting in the director log into a file or table,
eg: am having a job which reads from source and inserts into a table, when some oracle error like (datatype invalid or inserted record too large) happens i want this particular error message to be captured in a file or table,
Hw it can be achieved,
Thanks in advance,
Senthil MP
How can i write the error we are getting in the director log into a file or table,
eg: am having a job which reads from source and inserts into a table, when some oracle error like (datatype invalid or inserted record too large) happens i want this particular error message to be captured in a file or table,
Hw it can be achieved,
Thanks in advance,
Senthil MP
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Where are you doing this from, and what have you tried?
I neglected, earlier, to mention that Director has a Print option under the Project menu, and that the print dialog has a Print to File choice available. This may do it for you.
I neglected, earlier, to mention that Director has a Print option under the Project menu, and that the print dialog has a Print to File choice available. This may do it for you.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Am trying to do in the Datastage Designer, My aim is as follows:
Step 1) Read data from oracle source and transform it with one to one mapping and write to the target. IF any datatype mismatch or field length more than expected the entire rows will be rejected by giving a warning in director.
Step 2) I will be collecting those records rejected through outputlink.REJECTED and writing into a file/table. This all work fine.
Now what i want to do is, also attach a field with already existing field of rejection links say 'Warning Field' and this should have the particular warning message from the log.
For eg. if a record is rejected due to the warning 'Inserted value too large for column,row rejected' then this warning message should be entered in the Warning Field to the reject link along with other rejected record field
if the target table is havign Field1 with varchar2(3) and the data for this particular field from source is 'DATAST' then it will be rejected with the above said warning, now the file/table which collects the reject records should have Fiedl1 - DATAST Warning Field - Inserted Value too large for column,row rejected
This is what am trying to achieve, to be short we trying to do Bad Records Handling mechanism
Step 1) Read data from oracle source and transform it with one to one mapping and write to the target. IF any datatype mismatch or field length more than expected the entire rows will be rejected by giving a warning in director.
Step 2) I will be collecting those records rejected through outputlink.REJECTED and writing into a file/table. This all work fine.
Now what i want to do is, also attach a field with already existing field of rejection links say 'Warning Field' and this should have the particular warning message from the log.
For eg. if a record is rejected due to the warning 'Inserted value too large for column,row rejected' then this warning message should be entered in the Warning Field to the reject link along with other rejected record field
if the target table is havign Field1 with varchar2(3) and the data for this particular field from source is 'DATAST' then it will be rejected with the above said warning, now the file/table which collects the reject records should have Fiedl1 - DATAST Warning Field - Inserted Value too large for column,row rejected
This is what am trying to achieve, to be short we trying to do Bad Records Handling mechanism
-
- Participant
- Posts: 597
- Joined: Fri Apr 29, 2005 6:19 am
- Location: Singapore
-
- Participant
- Posts: 597
- Joined: Fri Apr 29, 2005 6:19 am
- Location: Singapore
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 597
- Joined: Fri Apr 29, 2005 6:19 am
- Location: Singapore