DSXchange

Hi Jayaram, Perform the lookup based on your 4 key fields and read all of the fields (Source and Lookup) into your job. Concatenate all the fields from your source record together into a stage variable (remembering to handle NULLS on each field). Then use the crc32 or checksum function on your conca...

You can change the settings for how often your job logs are purged from the Administrator.

I find it useful to parameterize the invocation id of multi-instance jobs so that each instance appears separately in Director.

DaMouse,

There are certain members of DSXchange who take a lot of time to share their considerable knowledge with other users of this site. Kenneth Bland is one such member.

Perhaps you should take his advise less personally because then you might learn something...

If you have 3 errors on the same row in your source file do you want three rows in your Oracle table or 1 row detailing the 3 source errors??

If you are using a mv command in an After-Job Subroutine you can do the following:
The ExecSH option should be selected.

You should be able to handle this with the Sequential File Stage.

Set all your datatypes to CHAR and specify the length of each column in the file.

If you are using the LOAD option then Datastage will be using SQL Loader to insert records into the DB. If you check your logs then you should find reference to a SQL Loader Log file called something like ora.23480.494029.0.log This file will be located on the resource scratchdisk defined in your Co...

We are using 7.5.1 Server and Client and have experienced the same problem with Trigger Conditions in Job Sequencers.

I have found that simply closing Designer and Reopening it solves this problem.

Strange...

If you dont need the key value elsewhere in your etl process and only care that it is a unique value then you should consider using a trigger on the table into which you are inserting the data...

Try the following code in a Stage Variable in your transformer

Are you sure that you have exactly the same version of the client software as others in your team??

I had the same problem the other day whereby I was able to compile a job on my machine (Client 7.5.1) but it wouldn't compile on another machine running client 7.5.1a

You need to check the 'Automatically handle activities that fail' checkbox in the job properties of your seqences.

What is you source??

You can either read the date as a string and chop out the /'s and rearrange to the YYYYMMDD format. Then use StringToDate(<YourDate>,'%yyyy%mm%dd') to get it into a date datatype

Or

Do DateToString() Then Rearrange Then do StringToDate()

Its definitely not a coding error - this job has been running on a daily basis for over 3 months now and we have never had this error before... We are also getting this error in other jobs and I think it might be a space issue on the file system but i'm not sure which stuff it is safe to delete othe...