DSXchange

The row merge does something completely different. The correct stage to use would be the modify stage, I am not sure if the default ":" concatenation operator can be used or if you need to call one of the builtin string functions. There is no reason not to use the Transform stage; the only stage tha...

I think if you make your output Oracle stage run in sequential mode, or just use a 1-node configuration, then the hint will not be used. I don't know why your DBAs should be so certain that this is the cause of your snapshot performance issue, though.

Somewhere in the job you are converting from a string to the database date column and the format is not correct, probably in the date derivation for the update link.

I do think that basic transformer does the work. when i try to capture the DBMSCODE out of Basic Transformer its giving 0 as output always But doesn't that mean that the BASIC transform doesn't work? If you intentionally force a database error (i.e. put a NULL value in a non-nullable field) do you ...

There are many ways to approach this "throttling" of resources; but none of them are builtin to the product One simple (but not necessarily 100% effective approach) is to add a call to a user-written before job routine in every PX job. This could easily be added to all by doing an export of the proj...

Hello premupdate, You probably cannot recitfy this. Was this job imported through a .dsx file? If so, then it was exported without sources and you can fix that with a re-export & import. If the job was built in the same project, then the data files for the job have most likely become corrupted. ...

I put together a very simple job that illustrates the error, so I think it is a bug. I've submitted it to IBM support and will post the results here.

I have a job that set the following two values where I am doing user-defined UPSERTs to Oracle tables: $APT_ORAUPSERT_COMMIT_ROW_INTERVAL=10000 $APT_ORAUPSERT_COMMIT_TIME_INTERVAL=10 It seems that these values are being ignored. I've tried running with just the time-based or row-based settings and i...

If it isn't a builtin, then you can create a user routine activity and call DSGetProjectInfo(DSJ.PROJECTNAME).

I do not think that the BASIC transform stage works the same way in a PX job, since in server jobs the transform stage takes care of reject handling; whereas in PX the database stage itself does that through an output link. This explains your problems and I don't think that there will be a way to do...

You are probably doing an ASCII (as opposed to a BINARY) ftp. If you file contains only text then this should be OK, as it will convert from your ASCII server to the mainframe's EBCDIC and it ought to be conserving the line length. You can try adding a "BINARY on" to your FTP commands and see if the...

Can you view the data as Ray asked, or try to execute the UNIX command "orchadmin ll {dataset}"? Any error messages?

The Ab Initio code looks like a direct interlude to the unix tr command; which you can use as a filter in the source sequential stage. The syntax of the DataStage CONVERT function is very different, you explicitly specify two strings, and each position value in one string is convert to the value in ...

If the source is the sequential file I would use a filter with a "tr" command, otherwise a CONVERT function will do the trick.

You asked a very general question, I gave a very general answer.

It seems you have a user-written routine in c++. You need to add this to the list in the manager, once that is done you will see the routine show up when you right-click in the transform stage in the designer.