DSXchange

The Transformer is used to assign some constant values to few fields and for CurrentTimestamp() and DSJobName. There are no transformations/surrogate key generate. Only the source has CLOB fields - which might cause the memory issue? But not sure how to handle it. Btw, the job runs fine if only 10 r...

Yup, did that, it shows data and Connection is successful.

Here are the warnings: odbc__STAGE_QC_TEST__Ld,0: from /usr/lib/hpux64/libc.so.1 odbc__STAGE_QC_TEST__Ld,0: #1 0xc000000000560d70:0 in __nanosleep2+0xd0 () from /usr/lib/hpux64/libc.so.1 odbc__STAGE_QC_TEST__Ld,0: #2 0xc00000000040aa10:0 in sleep+0x3f0 () from /usr/lib/hpux64/libc.so.1 odbc__STAGE_Q...

Hi, We have few jobs which reads SQL Server table and loads another SQL Server table. The source and target tables are in different databases. Job Design: ODBCStage_Sourcetable ->Transformer ->ODBCStage_Targettable ODBC Target stage - WriteMode: Insert; Table Action: Append; Generate SQL : Yes The s...

Mostly the job does abort when the SP fails due to primary key violation. There haven't been any other errors which made the SP fail and hence the datastage job didn't fail too.

We haven't changed anything in the job.

This issue seems to be resolved for now.

We made the foll changes:

1. used hash partion
2. defined keys on the target table
3. changed Transaction and array size from 2000 to 500

Thanks!

The job successfully updates when run on single node.

There are no duplicates in the source data, we verified that.
The job is run on 2 nodes.

Hi, I have a job which updates and inserts a table [Update if record exists else insert]. This table has no primary keys defined on it. This job worked fine in lower environments with fewer records (few hundreds), but failed in production with deadlock error on update statement, where the volume was...

Hi, I have a parallel job in V 8.7. The design has a row generator, generating 1 dummy row followed by Stored Procedure stage. The DB is MSSQL Server Procedure type - Transform No parameters are being passed to SP and no values are returned from the SP. However even when the SP fails, the Datastage ...

The account actually got locked, and once password was reset, the job ran successfully.
However we think it is because the password contained special chars like "#"

So running the job in Grid is causing this?
How can I prevent it?

Hi, The "view data" option in ODBC Connector stage of Datastage Designer connects and shows data, but the job aborts with the below error The connector could not establish a connection to data source <DSN_name> using user <user_id> I have checked the values passed to the db connection para...

Thanks for your replies. Guess I will have to de dup the After dataset so it has just 1 record.

Hi, I have a job comparing 2 datasets - before and after and supposed to capture the edits and inserts. The after dataset has 2 records with same key column and the before dataset has 1 record with the key column. Before ds: K1,1,a After ds: K1,1,a K1,2,b Expected Result; K1,1,a,no change K1,2,b,edi...