DSXchange

Hi,
Welcome Aboard :D !!!
Try with '\t'.

Check if different values are passed to parameters while at run time, if parameterized.
You might have got the view data from source, check the same sanity check in target (Insert statement).

Hi Vivek,
If resolved, could you post the step that you did to overcome this warning. It will be useful for future searchers.

Are you sure all the input stream to the funnel stage have exactly the same metadata?
Check if you have RCP enabled, if so disable it.

dsclient_xpsp2. Search for this.

Oh.. ok, the discussion is for the next method. The usage of filter is coupled with Sort stage. And hence there is no need to use of stage variable as well.

You log shows that, input stage EXPIDENTIAL_CALC consumed 13822 records. But BPBB_CABLE_RAW_CLEAN_csv Output produced 55334 records. Though its an virtual dataset, are you letting it to an test sequential file or something. Since the error came up after 13822th record, check the next comming records...

Ray, The job is scheduled on Sunday. So I guess current date should also work.

Hi Yashwin, Ray has already provided a solution. You can get the access by subscribing to Premium content. And so you can help DsXchange to help to help you. An alternate solution, use it in the after job subroutine. mv Emp Emp`date +%m%d%y`.txt. Where the job will write the file with filename as Emp.

What is the design of the job? Are you doing some kind of Pivot or something?
Check the memory usage and the temp space usage during the job run.
Are you performing any Decimal to Integer conversion?
Try to restrict the flow till 13822 records and check if the jobs completes sucessfully.

Select Yearweek from TIME_DIM where Year_Month = to_char(SYSDATE,'YYYYMM')
Will give you all the Yearweek for the current month. And finding the min will give the first week of the month.
But Iam not sure, how could you do a outer join based on Year_Month on tab1 and Year_Week in tab2.

As far as I understand, its the stage next to the Linkcollecter, hence the target stage.

Then you may need to check for all the fields, whether it has been converted correctly. Do you get any other error or warning which points out any field name. And its you who mentioned in you sample ":6" field as the converting to date.

Merly - Its time to mark the topic as resolved.

As mentioned, if Ultramundane also getting the same effect, it could be a bug. But once I face similar kind of issue with CFF stage and reported to support, but later we found that the place where we looking for the input value is modified when it is actually given to Datastage. If possible try to c...