DSXchange

Contact your official support provider, that smells like a bug.

ps. When someone asks for an Oracle version, it means all 4 digits. Saying "10g" is way too generic, it should be more like "10.2.0.1" or some such. Some specific versions are more problematic than others.

True, forgot you can only do it from the main job. Did you get a count of log entries before and after? That should confirm the amount of records that were actually deleted.

Multi-instance jobs are a little trickier - where did you do the purge from, the 'base' job or from one / all of the invocation ids? How long had it been since the last '30 days' purge?

Please post the exact error messages. Cut and paste, don't summarize.

You've been supplied an invalid csv file. Those amounts need to be quoted so they can be properly read, that or they should not have those internal commas. pdid,pdcost,pdnm a001,"10,000",XXX b001,"20,000",YYY c001,"1,00,000",ZZZ pdid,pdcost,pdnm a001,10000,XXX b001,2000...

Why would you think you'd need to know the "exact length"? It's just a csv file, the Sequential File stage will worry about that.

What does this mean?

rajan.n wrote:but it wont generate sequence number as I am on 2 node structure.

They're Type30 dynamic hashed files, so that purge should automatically be reducing the log's size as well. Are you certain that it is not?

True. Usually you'd have to ask for the grants the Session Browser needs. See if your DBA will help you monitor this and check your runtime explain plan.

I've never seen that. As noted, an Oracle DATE does not support milliseconds. Which 'generation' option are you using? What version of the Oracle client is installed on your server?

And then unjar it later on some toast.

Thanks Ernie.

You've already been replied.

...and we particularly don't like to answer questions that can readily be answered by invoking on-line help or by reading the manuals.

Read about it in the help and documentation, then let us know if you have any specific questions.

Yes, through the Session Browser assuming you have the grants for that. Or have your DBA do that for you. And just cause they're both done in Toad doesn't mean they're the same thing!

Check the docs, I don't recall if that's strictly a load option or not.

Arise! :D

Out of curiousity, is there a way to do this without TX or the Java pack? I've been offered up a perl script shooting LDAP information out to standard out as a possible solution but wondering what other approach there might be. For us 'Don't Haves', that is.