DSXchange

I've not used LDAP so cannot help you there. If you don't click on the "share User registry" and enter the UNIX userid and password (correctly), then add a user and also assign the roles to that user then you should be able to login (if other things are wrong the error message will reflect...

The main effect is that your database rollback space will need to be large enough to contain the whole transaction. If it isn't the job will abort.

I have seen "artefacts" before as well but can't recall the cause. I think at the time a "force compile" from the designer somehow worked for us.

Did you do Administration -> Domain Management -> DataStage Credentials, select and open that up and enter the default DataStage and Qualitystage credentials?

Just as in the first post, this has nothing to do with rcp. You will need to define a transformation (either in a transform or modify stage) where you tell the job how to convert your timestamp to a date.

That looks like the 8.1 version where the data is in the XMETA and not in hashed files. I think that it won't work at any version prior to 8.1

I submitted an eCase for this problem about a year ago but don't have the case number available at the moment. I seem to recall this having come up here at DSXchange a couple of weeks ago and I have a vague feeling that someone mentioned that it might be fixed at 8.1 but "vague" and "...

The question sounds very much like an interview question. Perhaps it was the way it the question was formulated. Also, once you actually implement a sequential file stage in a test job the answer becomes evident.
Would it be possible to ask the question in a different way?

If by "pipelines" you mean "nodes" then there is no hard limit but the ones imposed by the capacity of the system you are working on. If you have a 2 CPU system with little physical memory then a configuration file with 128 nodes is going to cause the job to abort due to lack of ...

Karthik, could you explain for us at a high level what you want to do; perhaps there is a better approach to use. I, for one, don't understand your wishes and therefore gave up on adding to the thread. You have a routine that processes one file and returns one value. Then you asked about multiple fi...

That parameter doesn't have to do with NLS; if your uvconfig has no NLS entries then any character conversion is not being done by DataStage. Read your Oracle and write to a text file, then look at the value in the text file (not with View Data in DataStage) to see if has been altered. What is your ...

It is the userid that is being used that caused the error, and in your case the real error occurred before the ODBC error; perhaps the user didn't have enough access to those files required for an ODBC connection (odbc.ini for example).

What about "head -c 1 MyTextFile" to get just the first character of the file? You can use to remove the last line from a file.

I have seen issues with concurrently running multi-instantiated jobs that occur sporadically. The cause was that there were auto-purge settings enabled for the jobs in question. If you do have auto-purge enabled then try turning it off to see if that might be causing your problems.