DSXchange

I had something very similar happen with a Sequence job with a Start/End loop structure. It would enter the loop for the first time and show that the included Job Activity had been started, but then immediately exit not only the loop but the Sequence job as well. Logs looked just like you posted. It...

Any number of indexes on a target table will affect the load speed as each one adds overhead to the process... bitmapped ones even more so. But that doesn't mean it's always a good idea performance-wise to drop them all first and rebuild them all afterwards. However, if you do switch to a bulk load ...

probably you have guessed it correctly...the size of the log file is exceeding the default limit...that is why this error is being thrown... any command or option in DS to increase the limit of the hashed file manually? The command is RESIZE and the syntax for it is out there is the forums somewher...

Aren't you working with parallel jobs? How is a hash file coming into the picture? Because we're talking about a PX job's log, which is stored in a hashed file in all but the most recent release of the product. And from what we've seen here, the change to store them in the XMETA repository instead ...

First tell us what you mean by 'load' here - what Update Action are you using in your OCI stage? Do your lookups prequalify the action needed on the database side, insert versus update, or are you using one of the crutch 'combo' actions to handle that for you? As for the 'bulk load' question, you do...

Is that because you're reading a 'DOS' file and not handling the record delimiter properly?

Yes, they can be converted to 64BIT hashed files, the 'limitation' is a function of the 32bit addressing they use by default. However, you really should look at why your jobs are logging that many messages. Is it simply a factor of the number of unique InvocationIDs you are using? Are they generatin...

I would say so, too. What does your official support provider have to say on the subject?

Druid_Elf wrote:But now you are actually reading the value of the project variable and you are not reading from the parameterset.

As the ancient philosopher Sam Ting would say - they are equivalent in this case.

We'll need to wait and see, but guessing the advice will be to upgrade to 8.1 as soon as possible as the 8.0.1 release is generally considered to be a buggy mess.

Try just GetEnvironment(DEF_UNKNOWN) as the parameter set name isn't part of the environment variable name that is actually set.

No, all it seems to mean is you had one at one point. Once the membership expires, the logo remains but they are unable to view Premium content. I would think the 'membership.director' would be the right one to contact, but adding the 'webmaster' in couldn't hurt.

A "blink" is a "backwards link" which means your logs are corrupting, more than likely from blowing through the 2GB barrier for the hashed file in question due to the volume of entries being written to it. And a MI job still has a single hashed file log that everything writes to,...

Been discussed here many times, routines that do not return a zero are considered to have failed if the 'Automatically handle' option is ticked and you don't have the proper triggers set up from the Routine.

Use a combination of the other two options, not the 'summary' one.