DSXchange

I think you should see if the error remains after rebooting. It probably will go the way of the dodo bird.

Generally that statement about caching is correct, but in your job design the file won't be loaded to memory until the cached writes complete, so keeping the write cache will speed up and not hurt this particular job.

Ray,

I tried that before posting, since I had a vague memory that I had done this before but no routines showed up in my list, this is at 7.5. Are you using V8?

Those ulimit values look good. Are you using the same dataset in 2 or more lookups in your job?

try "ls -al /Fld1/Dataset1.ds" from unix. If ther permissions are OK, you can also try a "orchadmin ll /Fld1/Dataset1.ds" at unix to see if all the partfiles are accessible.

Currently neither the export nor import allow single routines to be selected.

This is the equivalent of saying "I have a red light on my car's dashboard. What do I need to do?".

Try a reset of the job and seeing what the "from previous run" entry in the log states.

No, you will need to use 2 transformers to do this.

Can you add a call in your before-job to issue a "ulimit -a" and see what the actual runtime values are?

Are you sure the link is called "DSLink", not "DSLink1"?

My thought is that if the error occurs during a write statement it is probably due to bad data (a null in the key, for example) otherwise the pseudocode statement will help pinpoint the cause.

Nick - let us see what is happening at line 250 of your DSD.WriteLog program and that might give a hint as to the cause. a) Enter TCL or the command line execution in the Administrator. b) "LIST VOC DSD.WriteLog F2 F3" to get the program name and file name for this routine. c) "VLIST DSD.BP {Basic P...

What did Ray's suggestion return? If the file is corrupt it would give you an error message. If the file is broken then restarting DataStage won't do a thing.

Ray - are you sure? I tried to convert that raw type into something useable and failed - I'll look into the column import stage now.

I don't know if sql server can do a "Convert(datetime ,'20071005')", that would explain your problem.