DSXchange

No, but you can multi-select the column derivations then choose Derivation Substitution from the right-click menu. By this means you can change as many derivation expressions as you wish at one time.

Why must you do this "using DataStage"?

This is a deliberate change. Customer feedback in general was against the graphical panel and more for the "let's have everything work the same".

None of that tells me anything about why you believe the stage makes any use of indexes. What it actually makes use of is the fact that the data are sorted by the defined key.

What data type is the stage variable whose value you set to -1? If it's a string of some kind, any literal value needs to appear inside quotation marks, for example "-1".

Any reply,hint,documentation pointer, please !! Learn patience! Most of the members were asleep in the seven hours between posting and pushing. If you want urgent assistance sign up with your official support provider for premium support, and learn just how expensive "urgent" can be. DSXc...

I'm confused (which doesn't happen often). What have indexes got to do with the Change Capture stage, which processes streams of data?

One would have to guess that you're using either internal user registry or LDAP-accessible user registry.

Have you considered using MATCHES_REGEX to handle the zero-or-more "any" characters?

Quite possibly.

They should always be synchronized.

Possibly a permissions issue (or a disk full issue?) in the local repository database.

OK, I've dug out the routine I was thinking of. Note that it's a recursive routine, so I hope you don't have hierarchies of sequences hundreds of sequences deep! The code is provided "as is". FUNCTION TraceSequence(aSequenceName,aLevel) $COPYRIGHT "Copyright (C) 2008, Ray Wurlod. All ...

Do the metadata on the output link specify Decimal(15,3)?

And you really should try to avoid "#" characters in identifier names, since DataStage uses these to flag job parameter references.

Then I think it's time to involve your official support provider.

When you ran through the identify flat file process, did you specify any field(s) as primary key? The error is being thrown by the SQLPrimaryKey() function in the ODBC API, the purpose of which is to identify whether a column is a primary key or not. It really should not throw an error if no primary...