DSXchange

I am also facing same issue. I am trying to import the jobs from one server to another in DS 9.1. But while importing I get this error. Has anyone found a resolution for this?

Hi,

We are also facing the same issue. I have exported the dsx without executables and tried the proxy heap size change also. Still same issue persists. Did anyone was able to find any solution for this?

Thanks

Check whether column FACULTY_OWN has no spelling mistake, if you have put in manually anywhere before and after shared container. Remaining errors might have been caused due to this warning.

You can utilize some of the existing information if not all. For e.g. create a shell script to query the database table and pass parmeters like Source table/Tgt table, source query, insert/update query to datastage job.

My job design is as follows:- rowgen -> teradata api stage Here rowgen stage is acting as a dummy stage which sends just 1 record which is not used anywhere. All the data processing takes place via a SQL which is written in API stage. Something like Insert Into tab1 (col1,col2,col3....) Select col1,...

Hi, I have few jobs which use Teradata API stage with User Defined SQL method in Insert write mode. I am loading my target table by selecting records from source table and applying few joins/formatting. My job gets completed successfully but in Director log, the number of records inserted/updated/de...

Try Pivot stage. You need to add 1 column with a constant value and then use pivot enterprise stage. This would not get you the column names though.

I guess, for Change capture stage, there should be unique keys in both before and after data. In my opinion DS won't do a row position by position comparison.

@ArndW
I am using sort option in the partitioning tab of Remove Duplicate stage itself. I am not much clear about the pros and cons of using stable sort, but will try and post back results

If you meant the datatypes of key columns then it is integer and date.

The NLS settings are same for both ASCII_ASCL. And the selection of records to retain keeps on changing every time I run the jobs with same source data. Is there any change in the hash algorithm between the 2 versions.

Hi All, I am facing a unique issue while migrating 8.1 version jobs to 8.7 version. Couple of jobs that have remove duplicate stage with hash partition are displaying difference in results when i compare 8.1 output with 8.7 Scenario is like this:- i/p colA,colB,colC,colD A,B,C,1 A,B,D,2 B,C,D,1 keys...

Thanks chulett. I will try setting this variable and let you know the results.

Hi, found the solution, we need to pass escape charcters also as part of the parameter value so

#WHERE_CLS#=where (cast(dt_yr as date FORMAT \'yyyy\') < 12)


so that single qoutes are treated as a character while execution

Hi, I have a datastage job which has a teradata connector stage as target that issues a delete statement to purge the data from the tables. Table name and where clause is parameterized so that the same job can be utilized for multiple purges. The issue that I am facing is when I have single quotes i...