DSXchange

This issue has been identified as a VAS issue where few connections are failing. The user id on old server was a local id where as on new server it is an Active Directory id.

Thank you.

All, We are trying to migrate from an old server hosting the UDB database to a new one. Jobs are using DB2 connectors. The same jobs were working perfectly when the old server was the norm. -Every time there is more than one connection/stage referring to the new server in the same job(even both read...

This is done by Datastage in background. I dont think we can edit the query.

Here is some more info :

The DBA has informed us that the Metastage process query is holding a lock on the table when job runs. Any idea what this is about?

Query holding lock :

select Computer, SoftwareProduct, DataStore, DataSchema from MetaStage_Loc_Info

Hi, I need help on this error faced while accessing DB2 using a ODBC connection : ODBC_Connector_41,0: [IIS-CONN-ODBC-000013] ODBC Info: SQLSTATE = HY000: Native Error Code = 1,210: Msg = [IBM(DataDirect OEM)][ODBC DB2 Wire Protocol driver]Abnormal end unit of work condition occurred. ODBC_Connector...

Figured it out. The DB2 connector stage, which is my source for data, is also the source of this issue.

Note, it does not do this for every value in the column:!: Very selective!

I used ODBC connector in its placed and now I am good to go!

Thanks.

Got the error: A decimal field, both sides same precision. On one side it is " 00004.032898" and other side " 00004.032899" The thing is : The source value is : 4.032900 Datastage it converting it to other side " 00004.032899" :( Any reason why datastage is reading 4.03...

I have run the change capture stage in sequential and my before and after have only one record. Also, I have one key only

Even converted all char fields to varchar and tried.

Hi, I have a CDC job which is triggering an update when there is no change at all. I have made sure that I am comparing apples to apples and even trim for ascii nulls for char fields. Checked the forum, closest match : http://www.dsxchange.com/viewtopic.php?t=133411&highlight=change+capture+stag...

Hi, I'm reading from a partitioned table (3 nodes) on a newly created DSN on DS and writing data to another table on another database. When i enable show instances in Director Monitor, I see three nodes for target, but only one on source. Am I missing something? I cannot get the detailed pdf for DB2...

Its a simple tab delimited file read and write to FTP stage.

I did use a workaround of converting the date to VARCHAR 10 in target. But just wanted to know why its doing that because some other similar job which runs fine with date.

I know this is coming late and someone might have done it some way too...But this is what I managed : - Use a Sequencer; - Pass you IN list as a comma separated string : (in Parm file : filedname=ABC,CED,MNO ); - In the command stage, put this complete line: echo #fieldname# |sed -e 's/^/?/g' |sed -...

2010-12-31 was converted to 15760
This records :
"2010-12-319331A904A1A9MIS256560111402008-11-05....."

looked like this when transferred :

"157069331A904A1A9MIS25656011140149201492092830155561555923..."

Use Trim(String,"-")

This will reduce all multiple occurrences of dashes in string to one.

Any idea why the FTP PX stage would convert dates to a number format on transfer? The file on the source side is generated in Datastage and a view on UNIX shows the date formats to be correct. Any help will be appreciated.

No special FTP parameters specified.

Thanks.