DSXchange

That's actually a NO to the original question, which I read to mean whether the old log can be accessed after a job is renamed.

The moral of this story is "plan ahead". And take a backup before you delete anything.

Before changing the name it can be done. Changing the name allocates a new job number, the new log is empty and the old log is removed. The easiest ways to retrieve the last run are (a) to use the log view in Designer client (Crtl-L), which only ever shows the current run, or (b) to use a Filter in ...

Nope. Guess I don't have as much free time as Ernie! (Also no children of "that age".)

Good catch. It's not that, then.

Actually there's really only one reason. This is failure to authenticate against the Services tier. It means that the user name/password combination cannot be checked - maybe LDAP authentication (if that's what's being used) is not configured correctly, or the user registry is not available.

There is an internal setIsNull() function, used when assigning null into a column in a Connector stage. Apparently your design has sent null into a non-nullable column in the Connector DB2Conn.

Although it seems unlikely for just over 2000 you may not have enough memory to perform all your HJOINS in memory. What happens if you disable this setting?

Are you installing on one of the supported Windows operating systems?

Have you perhaps been using shared table definitions? In that case you may have to re-synchronize your project with the shared metadata repository.

Have you installed version 9.1.2 (that is, Fix Pack 2)?

No, it's one-way traffic. DS.REINDEX drops and re-builds indexes on the local repository table. There's no reversal of DROP INDEX.

Are there any errors reported when you run DS.REINDEX ?

Forget about "mutex" - this is just the way that semaphores are implemented on your system. You've experienced a timeout. Something, somewhere, has failed to respond within the expected time. When using DataStage BASIC components, this might be in invoking the interface between the paralle...

How about null_field = '000000000' ?

Welcome aboard.

I would guess that your DS.REINDEX ALL command did not complete successfully.

Try again when you have guaranteed sole access to the project.

If it's only table definitions, you might prefer DS.REINDEX DS_METADATA

asorrell wrote:If you set record count to 0 in the connector, it will do what you want. If the whole update works, it applies the commit. If any record fails, it rolls the entire transaction back.

Be very nice to your DBA, because it may be necessary to configure abnormally large rollback segments.