DSXchange

I encounter the similar problem, i don't remeber exactly, but it is related to the final delimiter only, try using different type of final delimiter, probably setting the final delimiter value to 'none' wolve the problem My job was actually working fine until a few days back. Then when I was testin...

Hi, Both exactly the same job, one in SIT and another in Development project. Reading the same file. SIT gives the problem and Development wont. Will the rerun of the SIT job work. :roll: Regards kumar Kumar - Can you please let me know if you fond what was the issue. I have the same problem now.

kris007 wrote:[Well I can delete using UNIX rm command but if the file happens to be a dataset then I would only be deleting teh configuration file and that leaves the real data file hanging somewhere using up the space.

The real data files are created in your resource directory.

sanjay wrote:
I want Trap oracle error message in file . I am using oracle enterprise Stage . I am getting sqlcode in reject link but i also want actual oracle error message

Did you use generated SQL or user-defined SQL.

ray.wurlod wrote:Do you have a rejects-handling output link from the Oracle Enterprise stage?

Yes, to a peek stage

That's right. You set it up for a generated upsert and that gives you a generate insert and update statement. You copy your insert statement into the clipboard. You switch it to user-defined update and then paste the insert statement into the entry screen and modify it to suit. This works if there ...

There is no problem with the diskspace, both scratch and resource. TransUpsert is a Transformer stage.

When I replace Sybase OC stages with copy stage or dataset it works fine.

The job reads from a DataSet and based on a constaint writes to one of the 9 Sybase Tables. I am using Sybase OC stage. Job runs fine when the source data set has about 100,000 rows. But aborts with the below errors when ran using a dataset with 470,000 rows. TransUpsert,1: Unable to wait for job to...

I don't think its possible with the global exception handler. You will have to explicitly handle the errors and continue to the next job. i.e. on the job activity trigger expression type = Unconditional, you will need to handle the exception using a routine or execute command activity and then conti...

Don't forget to check the "Automatically hanle activities that fail" option in the General job properties when using a Exception handler.

I don't think you can parameterize the job name in job activity. The other approach is to develop a routine to call the job. Routine takes the job name and job parameters as parameters. Call the routine in the sequence using routine activity with job name as parameter.

My personal experience is Parallel jobs may perform better but they take longer to develop. There are several bugs & the issues just keep coming. Server Edition is much stable. Still we decided to stick with Parallel jobs.

But it should still 'work' as in capture rejected rows. How are you defining the 'reject' link - check the option, via a constraint, both, what? And when you use those 'combo' update actions, never expect the first action to generate any rejects, that failure is what drives the firing of the second...

Which stage are you using for sourcing data. If its a sequential file stage then in the properties tab ->Options -> you can set Reject Mode = Output and rediret these records through a reject link, and perhpas write to a sequential file. You can only get the orginal row data but not the error message.

DSguru2B wrote:What link are you providing in the linkname.REJECTED. That linkname should be the one going into the database.

Yes, I am using the linkname that is going to the Sybase OC stage.