Skip to Content
0
Former Member
Oct 17, 2011 at 12:02 AM

Data Services 4.0 error when running job - not updating repository table

174 Views

Hi All,

I am hoping someone might have come across this error before.

When running a data services job, from within Data Services Designer, when trying to re-run the same job, I get the following error messages:

9332 2572 DBS-070300 17/10/2011 10:38:39 AM |Data flow DF_XXXX_Data_DW1Date

9332 2572 DBS-070300 17/10/2011 10:38:39 AM SQL submitted to Oracle Server <BO3> resulted in error <ORA-00001: unique constraint (DS3_ADMIN.SYS_C005632) violated

9332 2572 DBS-070300 17/10/2011 10:38:39 AM >. The SQL submitted is <INSERT INTO AL_BW_REQUEST (REQUESTID,TYPE,VALUE,DF_NAME,CREATION_TIME) VALUES (

9332 2572 DBS-070300 17/10/2011 10:38:39 AM 'REQU_4NIVIZ1G9S5B7LUY0HHP65ZJU', 3 , '29', 'DF_XXXX_Data_DW1Date', to_date('2011.10.17 10:38:39', 'yyyy.mm.dd

9332 2572 DBS-070300 17/10/2011 10:38:39 AM hh24:mi:ss') )>.

9332 2572 REP-100109 17/10/2011 10:38:39 AM |Data flow DF_XXXX_Data_DW1Date

9332 2572 REP-100109 17/10/2011 10:38:39 AM Cannot save <RequestID info> into the repository. Additional database information: <SQL submitted to Oracle Server <BO3>

9332 2572 REP-100109 17/10/2011 10:38:39 AM resulted in error <ORA-00001: unique constraint (DS3_ADMIN.SYS_C005632) violated

When I go and look into the Data Services repository AL_BW_REQUEST table, the first time the job is run, all five fields in this table populate with data successfully. When re-running the job, on 3 out of the five fields within this table are populated but the VALUE and DF_NAME field are not populated, hence causing the primary key violation.

Here is the data below from the AL_BW_REQUEST table:

REQUESTID TYPE VALUE DF_NAME CREATION_TIME

REQU_4NIVIZ1G9S5B7LUY0HHP65ZJU 3 10/17/2011 10:38:38 AM

REQU_4NJ503RVIFD3VLBJJEKBJ3OE2 3 10/17/2011 10:33:37 AM

REQU_4NJ4ZHSP9F93L3OAUDV6RHCMY 3 10/17/2011 10:32:31 AM

REQU_4NIV1NKP9645E394E7H12Q796 3 10/17/2011 9:53:53 AM

REQU_4NEYFNI2U68MBJOEWFJWVWWU2 3 24 DF_XXXX_Data_DW1Date 10/17/2011 9:47:58 AM

If I truncate this table and re-run the DS job, it will not populate the VALUE and DF_NAME fields.

Does anyone know what could be causing this? The target source is BW.

Seems like a bug to me.

Thanks,

Ainsley