DSXchange

Hi Shawn, the problem is that the source column is alpha-decimal but some subtrings are decimal and can be packed. That is why, I think, datastage does not convert anything because source is char(200). The problem still persists : I tried to create my own routine (oconv (xxx, MP) ) but without succ...

Hi, Thanks for your quick answer! I will try to be a bit clearer : a field is packed on our AS400 and when we try to get the content of this field via Datastage - ODBC Stage into a column type "char" , we can not read this data, we only obtain some pipes '||||', the numeric are packed and...

Unfortunatly no one has any idea whats going on here and I have run out of time. I am reverting to the old job with collectors and partitioners. We have just upgraded to vers 7 so I am hopeing that that will help keep this job running smothly. Thanx for all of you guys imput. Jim Jim, In my opinion...

The odd thing is that it worked perfectly finr is 6. Go figure

Oh !! :( . I didn't know about that. I wish there is a place where we can go the submitted Trouble tickets for every version so that we will not spend too much time on them before we realise that it is bug in the system, or is does on already exist ? I spent several days chasing this one down. I th...

Here is a gross pictorial view. TransformLink1-700rows->Link Collector-->Oracle Stage TransformLink2- 2rows--> To be more specific, why does every field in every row contain zeros after passing through the collector? So this happens in Oracle also? We have seen the same issue in SQL Server and have...

When compiling a server job, the error message is "Link Collector stage does not support in-process active-to-active inputs or outputs". The Link Collecter has two output links from the same transformer and an input link to one Oracle stage. I don't have a clue what this error message is ...

Do an archive search for Upgrade and you will see a few threads on the upgrade to version 7. No real issues to worry about, a pretty easy upgrade. A good idea to export your projects first. Thre our of the four upgrade we did went without a hitch. The one that failed required a messy delete of the ...

The OLEDB stage and the SQL Server bulk load stage do not pass pass back the error from the server and will pass back these unusable messages. This problem has been reported to Ascential and there is a case for it. I have found that the best way to find out what is happening is to run the SQL Server...

Nope not sophisticated enough to use shared containers yet. :) and maybe we will get our support aggrement signed with Ascential so that i can upgrade!!!! :) thanx for the help Jim Jim, Do yourself a favor and use a shared container, it will eliminate tons of work that you are doing in replicating ...

I have a job that uses a the partitioner/collector to speed up processing a large sequincial file. It has three partitions for the file. This job worked fine in the past untill I added extra data clensing to it. Now the only way that i can get the job to run with out posting an error "timeout ...

Actually I hate to admit that I actually read this one but "Data Warehousing for Dummies" is pretty good.

Yes, Control-M by default treats any exit code besides 0 as an error. There are options in Control-M where you can define what exit codes are treated as errors.

We have one also and just by chance we also call it an ODS. We use it to normalize the dimensional data before loading it into the data warehouse.

chulett wrote:Unfortunately, all of the wire drivers seem to be marked as "[not Tru64]" in the server readme. So, as noted, I assume you'd need to purchase them for the Alpha platform from the vendor.

I just went to the Data Direct site and it looks like DataDirect does not even support Tru64.