DSXchange

That error is specific to Sequence jobs.

Easy, yes. Proper? No. Ok... here are two reasons why. 1) Must be repeated for every project. 2) Will not effect the project Template. The second item means that any new projects created will not have the SP stage in them and you'll need to repeat the package install yet again. If you rerun the Serv...

parbados wrote:Thanks, how do I pass the parameter do I define it in the job that requires it and then pass it within the sequence ?

If you still need it - yes. And then wrap it in hash/pound signs in the sql.

No, don't use the package installer for reasons I don't have time to list here. Repeat the server install, it's painless.

I called Ascential for confirmation of this and they said that even logs with errors or warnings in would be purged. I checked this morning and indeed yesterdays logs had been cleared even though there were errors in. That's... interesting. I wonder when this changed? And you are right, just verifi...

With that particular format, I doubt either portion will be of a fixed length. If that's the case, I'd use the FIELD function to split it at the first whitespace:


From memory. Otherwise, you could go with Arnd's solution.

sb_akarmarkar wrote:Julian date provided by you is not correct it should be 106079 i think as per "CCYYDDD".

Huh? Not sure how you came to that conclusion but there's nothing 'wrong' with the date format as posted by Kris.

All plug-in stages are optional. To install some outside of the Server install, repeat the install. It will go into 'Maintenance Mode' and allow you to just install new plug-ins as one of the options.

ray.wurlod wrote:Can I also suggest that 7.5 also appear? It has some version-specific features that diffentiate it from the other 7.x versions.

I second that emotion.

What kind of Oracle field? DATE? It won't take the milliseconds, if that's what that is, so you'd need to truncate that field at six characters. Now, an Oracle TIMESTAMP is another animal...

It's showing job aborted after 50 errors. But while running the same job manually through the client it's running perfectly ok without any error. If the 'client' is the Designer, then I would bet it is not running 'perfectly ok' - but rather you have the warnings set to unlimited. It will look all ...

Two processes - one to get the LAST_PROCESS_DATE and then pass it as a job parameter to the job that runs the second sql. Or perhaps... SELECT * FROM CIS_IMPORT_TS032_BILL_CHRG BCHG where ( BCHG.D_CHRG_CNC >= TRUNC(ADD_MONTHS((SELECT LAST_PROCESS_DATE FROM RSB_PROCESS_DATES WHERE IDENTIFIER = 'CURRE...

I'm curious how any automated cleanup would know what you did or did not want. What kind of rules did you have in mind?

Are these runs being left behind because of warnings and fatal error logs information in them? You tell us. You need to keep in mind the fact that Auto Purge only runs when the job completes cleanly - errors or warnings will disable the purge for that run. If that's the case, switching the number o...

And you are correct that you can't use the 'Insert or update' action. You need to separate the two actions into different links as you'll need to insert all rows and possibly update old ones.