DSXchange

What is the version of your source database. Not sure you can turn it off through datastage....

.i.e with RCP it will dependon your source database system, and how it interprets the meta data...

I am interested in knowing myself how to turn it off if one can....

arvind

I see it is working but pardon my question

Just trying to understand what the @FM system variable really does..

The help document and the parellel developers guide do not seem to have much on it

Is it setting the field delimiter...?


Arvind

Can you paste the snapshot of the column definition as defined in your oracle stage

Kapil Here are a few more thoughts I have done queries against oracle all the time where the column could have a null value. The data stage jobs will work just fine if the meta data matches. In that for example say your query is select col1 from table1 If col1 can have null make sure the meta data i...

Please boot me if this is a hijacking of the topic... but on a related to note, i would like to clarify that if In using the oracle stages in parellel jobs, if one is using the LOAD TRUNCATE method, i.e any of the LOAD methods, there is no way to specify the commit size... , The $APT environment var...

I have seen this error when working with oracle source tables. If your metadata is as follows COL1 decimal (38,10) TEST varchar 20 And For example if you have a query which is as follows SELECT COL1 ,NULL TEST FROM TABLE; where you want to set the test column to null,( though many will question why ...

The aggregator stage in the parellel engine does not work with the date and char datatype as far as i know. It works well with decimals and numbers only... I have had that same issue as well, where i was trying to get the max date for a given record set.. In our environment folks have used the sort ...

The job reads from data tables representing SAP data and does a few basic transforms to get the dwids from the dimension and builds the fact table.


arvind

The "broken pipe" situation happened at different stages in the job and it "DOES NOT" necessarily happen consistently after some row count. The problme is there is not consistent pattern to when it will occur. I am breaking down the parellel job into multiple small jobs and using...

I get this error after running my parellel job. The job runs for a few hours before it gets this error. Is this related to memory limitation reached or some kind of resource limits reached Are there any solutions in general or is this more of a job tunning aspect that needs to evaluated on a case by...