DSXchange

The functions you use are expanded inline and will result in a large c++ program - I'm not sure how the location of the logic in the transform stage (whether as a stage variable, constraint or derivation) will make a difference, but it might. The number of identical userids working in parallel shoul...

Ignore the PEEK output. If you copy the data from Oracle through DataStage to Oracle you will have an identical string.

I wonder if you haven't hit the system file table limit, referring to

[ENFILE] File table overflow

.

The parameter and location where this system limit is set depends upon which flavor of UNIX you are using.

Rajee - the important part of Ray's post is visible to you.

At the site I am currently at we have seen similar issues, but we peak at 40 minutes compilation time. The root issue does seem to be network transfer rates between the UNIX server and the PC on which the compilation is being done. Some of the job compile is done via Java on the client side and I th...

As mentioned before, DataStage will not convert data unless either explicitly told to do so or if an implicit NLS conversion is taking place. As you don't have NLS installed then you should just pass the data through without any conversions.

What is your job default date format (check in the designer, under the tab "Job Defaults")? I am not sure what you actually want to do - put in "1900-01-01" when the value is NULL? Use a "NullToValue(In.Column,StringToDate("1900-01-01","%dddd-%mm-%dd"))" derivation.

Ann_nalinee - it would be helpful for future "search"ers to add the problem and resolution to your post.

The first name is in my signature and the last name is Wussing.

bharatmajeti wrote:...The file identified as '/work/temp/dataset.ds' is not an ORCHESTRATE Data Set descriptor.

Start with fixing that error. Which process created it? What kind of a file is it?

You can access it through the main page, but here is the link

This should work with ODBC - What does the SQL command look like if you use auto-generated commands?

you are getting the warning because your date format given does not match your default date format. I thought your project default might be yyyy/mm/dd and therefore the suggestion.
The "null field value" applies when write to a sequential file, not when you write to a table.

There are also free, public domain packages that do similar things. I used Google to get a list.

Message handlers apply to PX jobs, not server jobs (which include job sequences). You cannot deprecate or suppress warnings that way, you need to get rid of the cause in the job.