DSXchange

fork() failed, Resource temporarily unavailable This is a UNIX message and there are many detailed explanations available through Google of what the fork() mechanism is and how important it is to UNIX systems. If a process cannot duplicate (i.e. fork()) itself then it is usually indicative of a res...

Do a "reset" of the job and see what the "from previous run..." entry in the log file states.

G.K.K wrote:...
Excmd_file.$CommandOutput:"<1>"

is wrong. Use "Excmd_file.$CommandOutput<1>"

by now your Oracle user is probably locked out and needs to be reset by the DBA. But please post the complete error message in any case.

Could you post the complete and unedited error message? Did you login to Oracle from "sqlplus" on the UNIX client? Did you add the ORACLE_ environment variables to the dsenv file?

That limit is set in the executable and can be modified (with ldedit on AIX) but I am sure that there are drawbacks to doing so, otherwise the limit would be set higher in all jobs.

Here is a tip to reduce the size of your lookup, perhaps then it will fit into the 512Mb block limit = remove the length specifications for VarChar fields.

Here is a tip to reduce the size of your lookup, perhaps then it will fit into the 512Mb block limit = remove the length specifications for VarChar fields.

In your job, you can only declare the type of "k_ftch" as String,Encrypted,Integer,Float,Pathname,List,Date and Time. We are looking for one of these as an answer to the first questions.
The second question is what actual value are you passing to "k_ftch".

Kamal, tell us WHAT datatype you defined this parameter as, and WHAT value you are trying to pass to that parameter, then you will get an answer.

You should write a loop in a job sequence to expand that wildcard and call the routine within the loop.

When you read from Oracle into DataStage you need to specify the correct NLS map - the one Oracle is actually using. The same needs to be done when writing to your target. If either one of these settings is not done correctly then it is possible that characters don't get mapped the way you expect. W...

No, no work around from me, since I believe that the site is valuable and that membership pays to keep it running.

The DataStage "View Data" facility has caused more perceived NLS problems than any other part of the tool - it is not capable of correctly displaying NLS data and shouldn't be used to see if NLS is working or not. Did you "view data" to see the character or use another tools?

The list of users is no longer easy to retrieve on the IIS server in hashed files or other objects. It is stored somewhere in the depths of Websphere and I wouldn't know how to access that list from the program level.