DSXchange

Dear All, I have installed Datastage 8.7 in Solaris platform. During installation Service tier and Engine Tier is installed in one host and metadata repository is pointed to other host and its oracle. Installation is successful and I am able to connect to admin console "protocol://host:port/ibm...

Hi, I need some clarifications on DVD's available at DSXchange Learning Center 1) I have ordered a Category C DVD and selected shipping method as download. But after confirming my order, I was not prompter with download link. Will I get them in mail? or how does it work 2) I wish to purchase all Cat...

Hi All, I need some clarification on Shared Tables. I have imported the table definition into Datastage using Oracle Connector import wizard. Then in IA, I completed the Column Analysis of all the tables that I have imported in datastage. (I haven't re-imported the metadata. I used the same metadata...

kwwilliams wrote:Both of the Oracle stages have their preserve partitioning set to Clear?

Yes. Both of the stages has preserve partition set to clear and still the warning message exists!

Your Oracle stage is sequential and you have the Preserve Partitioning set to Default which is Propogate. The lookup stage is running on four nodes and is partitioning your data despite the fact that you have the Oracle stage set to Propogagte the partitioning. Set the preserve partitioning to clea...

I have replace Oracle Enterprise stage to Oracle connector stage which don't have preserve partition flag. Even with it, the warning message exist. If it is surely not the correct behavior, I can raise it with IBM. I have access to IBM support. Please advise.

Many Thanks
MSR

Setting Preserve Partitioning to Clear in the Oracle stages is the cause of this warning. Change it to Default. Thanks for your input. I have set them to default. But still the warning exists. Either we clear it or default it, the warning message exists. (I have double checked it. Compiled the job ...

Hi All, I have searched the forum and did maximum possible thing from my understanding to solve the issue. But I couldn't. Please have a look. We have the following warning message in the lookup stage ReferAttributes: When checking operator: Operator of type "APT_LUTProcessOp": will partit...

Hi All, Need a suggestion on making the meta data changes to the code. The site is a data migration project and we had a new version of the target. Some of the fields in the target application has changed and in all case the length is increased. For example the manufacture code is increased from var...

Hi Ray,

Did you got the beta version to test. Is it available for IBM customers?

Regards
MSR

:!: I've removed your code tagged example data due to concerns over exposing PHI/PII in the forums here. Please feel free to edit your post and replace your previous examples with something more appropriate - redacted / masked or completely made up values for example - for things like name, phone n...

I have done a quick test on look up and Merge stage. It also exhibits the same kind of behavior. Please find the metadata below record ( EMPLOYEE_ID:decimal[6,0]; FIRST_NAME:nullable string[max=20]; LAST_NAME:string[max=25]; EMAIL:string[max=25]; PHONE_NUMBER:nullable string[max=20]; HIRE_DATE:times...

Hi, The joiner stage is dumping a junk values on the rows that test due to left or right outer joins. <removed by Moderator> If you can have a look at the first and last record, it is evident that datastage is generating zero on some numeric field (in case of last record for employee id it was zeros...

AndW, The issue is intermittent. I couldn't able to reproduce it. IBM has asked me to provide them the job export of the job and after run. i.e., before and after snapshot of the jobs and parameters in dsx. We haven't started using connectors heavily in our jobs. The issue appeared in the couple of ...

We logged a PMR with IBM. Will update on any response