DSXchange

It is much the same in PX. We just don't use a hash file. On the incoming stream, we add a column called "dummy_key" and give it a value of "1". On the reference stream, we also add a column called "dummy_key" and give it a value of "1". A "Join" is ...

Our friends at Ascential Support wrote a cusom stage for us... the problem is that it "collects" the entire million rows before doing the range lookup. The rather inelegant solution we implemented was to join against all reference rows (I think it's called a cartesian product) and then hav...

Our PX job run via Designer fails with the same message: "...File too large". The ulimit shows: file(blocks) = unlimited Our Sysadmin questioned whether we "connect" to the userid using "su" or "su - ". If the former, then it will inherit the profile of the or...

Thanks, we're on the right track now. Your tip about the $APT_DISABLE_COMBINATION prompted me to check way back to where the job first reads from the database. And sure enough, the fields are not-null when read in from the DB. So it looks like Datastage has combined at least 18 stages, including Joi...

I cannot see any difference in nullability by checking the input and output links: all fields are nullable when looking at the Columns tab for both Input and Output. I hadn't thought of RCP, thanks for the tip. However, when I looked into it, RCP is disabled in Datastage Administrator, so I don't th...

Thanks.
By removing the Remove Duplicates stage, it uncovered another error.
Refer to the topic: Fatal error due to "differing nullability".

Thanks for the response Rich, but that's not the right track either.
The output link was also created from the same saved metadata, so all of the fields (and their nullability) are the same.
I have rebuilt the input links and output link just to be sure. The same error occurs.

Initially, I had a "key field not found in view-adapted input schema" message (Refer to the topic CDC Error ) When the problem stage was removed, I found another error, which may be the cause of the "key field not found". The new error is: main_program: When preparing operator: W...

Ascential supported confirmed that this intermittent problem would be fixed by upgrading our 7.1 software to 7.1r2. HTH.
- g

I received the same error in a Remove Duplicates stage, so it is not to do with mismatched columns in the CDC. Reiterating Karl's question: Has anyone experienced the error below? Does anyone know what is meant by "view-adapted input schema" in this case, and the major causes of this probl...

It is not that the jobs are so large that they need multiple developers, but that the development will be split into separate projects. With some jobs, since we are using PX, we may deliberately "combine" jobs into one large job to minimise the number of times the data lands to disk... but...

The actual structure is still being debated, but there may be multiple Datastage Projects, with some "common" jobs. If the common jobs are changed, then the changes will need to be consolidated before they are released to the production environment. But you are right; if we cannot easily c...

Can someone please expand on why ClearCase doesn't play nicely with .dsx files? We are about to install ClearCase to control things like unix scripts and java code, and would like to also use it for Datastage jobs (we are using Datastage PX, v7.1). We will need the ability to merge changes made by d...

I just got this using Parallel Extender v7.1, and am also puzzled.
So I thought I'd add a note, to make this topic "current".
praj, let me know if you've found a solution.
Thanks,
- g

It continues to be an occasional problem.

Does anyone have any thoughts on why this occurs, and what we can do to prevent it from happening?

Thanks,

- g