DSXchange

Thanks for the replies.

The lookup stage is a case sensitive.

Last_Update_Date and Last_UpDate_Date was having letter case difference, hence the records were not flowing to the target.

Thanks,

Hi Guys, Please need your help to fix the lookup issue. The job design DataSet | v ODBC connector -> Lookup -> DataSet (SQL server) Lookup Reference is Entire partitioned, and input is hash partioned by a columnname Field1. The join/lookup key is primary.Field1= reference.col1. Both the below output...

Thanks for reply. Dyanmic PLSQL is used in the 1st job, Its a implicit conversion here. In the 2nd job, trying to do explicit conversion to get the orignal value, with the below code. if IsNull(Value_Id) then SetNull() else AsInteger(NullToEmpty(Value_Id)) Tried with AsDouble and Asfloat, here the v...

Thanks for reply.

If I don't use as ASInteger, Iam getting the values as below from 1st job target table.

1.12267e+007
1.54196e+007

I need to convert this.

Dynamic PLSQL, is which parameters are explicitly identified.

Thanks,

Thanks for reply. My mistake. The job design is as follows 1st Job (pivot job) ODBC Connector -> Transformation -> Oracle Connector 2nd Job Oracle Connector -> Transformer -> CDC -> Target (Oracle) In the first job, we have used dynamic SQL to insert into the database, hence cannot use DecimalToStri...

Thanks for the replies.

1st Job (pivot job)
ODBC Connector -> Transformation -> DataSet

2nd Job
Dataset -> Transformer -> CDC -> Target (Oracle)

@Sanjay Have you tried the conversion function, any specific function I need to try.

Value_Id datatype is Varchar in Oracle.

Thanks,

Hi Guys, Please need your help, source column and target columns values are getting mismatched. In the 1st job, source column i.e Value_Id(datatype Integer) is getting mapped to Varchar. In the 2nd job, for the same column Iam using the below logic to format it again. if IsNull(Value_Id) then SetNul...

Hi, Iam trying to do the implementation of Pivot with the help of Sort stage. EmployeeID ArchiveID Empno FieldName DataValue Version DateCreated 11 81 111 First_name RAM 1 2013-05-31 05:33:32.710 22 92 111 First_name RAM 1 2013-04-16 10:06:32.710 33 71 111 First_name RAM 1 2013-05-31 07:40:51.663 Ne...

Thanks for the input.

Will change the partitioning of the jobs to SAME.

Thanks,
Naveen

Thanks for the reply. Hash partitioning in copy stage because based on 2 fields, records would be distributed. Is there any issue with this. Reg. the duplicate, I have checked, there are no columns like this, my mistake. I will re-phrase my scenerio. Job 1. SQL Server -> Copy -> DataSet Job 2. DataS...

Hi, Have 1 doubt, can anyone please clarify. Suppose I have 5 columns A,B,C,D,E. I got 2 jobs Job 1. SQL Server -> Copy -> DataSet Job 2. DataSet -> Column_Generator -> Oracle. A,B are PK columns in source(SQL Server) and column A is Pk column in Target Table(Oracle). In the copy stage, done Hash pa...

Thanks for the replies, will try out and let you know.

Thanks for the reply. My mistake, 1node.apt is RAP Twonode.apt { node "node1" { fastname "RAP" pools "" resource disk "/apps/IBM/dataset1" {pools ""} resource scratchdisk "/apps/IBM/scratch" {pools ""} } node "node2" { f...

Hi, Please need your help to resolve the below issue. Job Design ODBC Connector(SQL server) -> Copy Stage -> DataSet. The job is running fine in the 2 node environment. But when I run the job in 1 node, its getting failed with the below error. Parallel job reports failure (code 139) Below are the 2 ...

Thanks for the reply.

In the Oracle connector, update query was not correct, have corrected it and re-run the job. Its working fine now.

Thanks,