DSXchange

For example there really may be a bug in the software - a thing called a "null pointer", for example, pointing to a non-existent memory location. Segmentation violation can also occur if you try to shoehorn 15 characters into a Char(12) column, depending upon how well (or badly) the processing appli...

Guess which one of us is a trainer by profession?

If I understand the requirement, it is to get the output column name from Column1 of the input, and the output column value from Column2 of the input. Is this a correct understanding?

Is the number of possible output column names small and finite, large and finite, or arbitrarily large?

Are there any newline characters in your user-defined SQL? I find that it (user-defined SQL) generally works best if there are none.

... because that's not what it does.

The Two Secrets of Success

1. Don't tell everything you know.

If you can describe exactly how you are attempting to undertake this task, we might be in a better position to offer coherent diagnosis. What stage types are you using? How did you import the metadata? Are you using default style sheets or customized ones? And so on.

If performance is being an issue, stage into text files and use sqlldr to get the data from there into the Oracle staging tables, perhaps in an after-job subroutine running ExecSH. You'll be amazed how much faster this can go. Don't use the ORABULK stage though - its performance is abysmal.

In a lookup situation, only Key columns are bound to the parameter markers. Therefore, if you have three ? characters in your WHERE clause, you need three columns marked as Key. The first-named Key column (top-down in the Columns grid) substitutes for the first-occurring parameter marker, the second...

That's where "dynamic" hashed file comes in. It self-manages its space.

Clever, innit?

The fault type codes are, most of the time, signal numbers. These are included in a signal.h file somewhere on your system. To find out which file it is, execute find / -name signal.h -print -exec grep SIGBUS {} \; 2> /dev/null You can then look through the file of signal numbers at your l...

Yep, that'd sure do it. Maybe you need to build a check for that situation into a job sequence? Perhaps an Execute Command activity (ping or something slightly more esoteric).

Just noticed an anagram. :D

... or even as a filter command (without the filename) in a Sequential File stage, which will then read the stdout of sed

Using seat power one can work on laptop on flights.
Without seat power one can read or write, or use laptop on battery. I carry a spare battery so can get over eight hours use, which is enough for most flights.

Change your run command to two commands.