DSXchange

We faced the same issue and the resolution was in Excel. As the data had been in some point of time in numeric format in the column Excel refused to make it text. The workaround was to create a new column, make it as text, then copy data from old column to Notepad and finally copy the data back to n...

Hi, I faced the same issue the other day and after some testing found out that at least one way to reproduce the issue is to use "View data"-functionality before saving the job with a new connector stage. So basically when you add a new connector stage and use parameters in it you should s...

Hi, IBM did fix numerous bugs in version 8 concerning Oracle OCI stage and one aspect especially affected with those fixes was date-conversions. I actually stumbled myself into a similar problem and the fix was quite straight forward even though quite annoying: As the actual data type in the Oracle ...

As I tumbled myself recently into this same problem I'll post my solution here. In AS400 data can be stored in CHAR() FOR BIT DATA -format that requires translation before it is shown correctly in DataStage. In order to make the translation you must tell the odbc-driver which character set is used i...

Are you setting any WHERE-constraints in your select statement? FastExport cannot handle selects that use unique key constraint that would only return one row. This is set from the Teradata's side not by Datastage.

Janne

Hi everybody, just to post the cause of the problem: Anti virus software Yes, I know it should be obvious to check this out first but we had done the same exercise couple of months ago with same kind of mysterious problems. The end result back then was not to include project folder in the virus scan...

Now we get similar error stating problems with DS_JOBOBJECTS. I'm starting to think that our project is about to crash... Maybe I'll try to create a new project and move jobs there.

Thanks for replies,

Janne

Hi ArndW and thanks for the response. I was also thinking the problem must be with DS_STAGETYPES as this is always referred to in error messages. I ran DS.REINDEX and it went smoothly - no warnings and all three indices with build status Not Reqd. And worst of all - the problem didn't go anywhere (w...

I have a job where I load five hashed files from five Oracle tables. There are ten to twenty of these jobs. Lately I have stated to experience problems with these jobs failing with following error messages. I tried to reindex DS_STAGETYPES as I though it might have something to do with that but that...

Check that you are NLS-enabled and the folder stage is set to read UTF-8 if the xml file is defined to be utf-8 encoded. Other way to do it is to set the FileName as input column for the xml stage (In folder stage remember to set the Fully qualified -property to Yes). Then in the xml stage set the i...

It should be there. I just checked my DS 7.1. On the bottom left corner... Precious: At least I haven't managed to put the passthrough columns in the begining of the output columns. I think it is the way row splitter works that it first splits the column specified and only after it runs out of data ...

Hi Kirti,

try moving the pass through columns to the end of the output column definitions and in the Output/Format-page check "Missing columns action" to be None. That should work.


Cheers,

Janne
Finland

PS. The sun has been seen here too

What you have bumped into is the underlying heavily typed parallel engine. The aggregator operator is coded so that it will output its results as dfloat. Now that you have explicitly stated that you want it as integer the engine will do a default conversion from dfloat to integer. This kind of conve...

Hi Rubu, Your JobMonApp has stopped for some reason. You can start it by running "./jobmoninit start" from /dsadm/Ascential/DataStage/PXEngine/java -directory. You might need to set the environment by running ". ./dsenv" before this. If you have 7.5 version you should get in touc...

Hi NEO, I came across the same problem recently and I found out that routines just pass the parameter values as they are. I found two ways to get around that: 1. Use encrypted string as input to the routine. This can be found for example from the Director log or when scheduling a job. I.e. if you se...