DSXchange

Yikes. That all probably goes back to the 'so we killed the processes' part of your first post.

You posted this same question two days ago and got an answer. Why post this again? If you don't like the answer or have other questions, ask them in your other post.

Something to keep in mind if you're running 8.1, it seems.

Five weeks? Looks more like a year and a half to me.

Your requirement isn't different, it is still a horizontal pivot of columns to rows around a key column or columns. It's just that you get to pivot only one of the data columns and pitch the rest.

Hashed lookups are equi-joins, so no 'like' or 'contains'. If it's always 2 or 3 characters, however, do two lookups to the same hashed file, one with the first two and the other with the first three characters and then take whichever one succeeds. Define a priority order if there is a possibility f...

That would be a horizontal pivot of rows to columns, search for that phrase here to find the many (many) conversations we've already had on the topic.

That would only be valid in the 'before' or 'after' sql tabs.

Post your complete, unedited abort message(s) when you hit this limit. And you need to run "ulimit -a" from inside a job (ExecSH) not from the command line to check properly.

Hey, it's not my query, just trying to help get it running.

And what it mostly consists of are a crapload of case statements. Perhaps even two craploads.

Of course. That and so much more.

%hh is a 24 hour format, you'd need to use %H or %HH for 12 hour, depending on if the length of that portion is variable (1...12) or fixed (01...12) in size.

So, is this service completely separate from cron/at/etc now? Or is it yet another interlude to them?

What solution did you use - all that extra work using stage variables or the proper StringToTimestamp function syntax that Kryt0n helped out with?

Trying to get some clarifications on this but here's the initial response back from IBM Engineering. Oracle Enteprise ================ The maximum length for the user-specified query is 30000 characters. To use a query of greater length, a workaround would be to define a view (or materialized view) ...