DSXchange

Just an update. IBM says v8.1.2 FP3 resolves this and other issues. They add though that you have to export and re-import the jobs after applying the fixpack. We haven't got the patch installed yet. I'll update again after we do.

What exactly do you mean by: "a bunch of Table Defs that accurately reflect exactly what's in the database, but aren't connected to any jobs (because jobs require the tweaked versions)" Hi Ernie, I took this statement If you change the local tabledef for DS users only, a good practice mig...

Your pattern sounds like another twist.....you are apparently changing the local datastage tabledef only......? The Table Def requires some tweaks to make it work. The varchar limits have to be removed, and in the case of orchdbutil, the primary keys have to be asserted. I think in general the Tabl...

Yes...the Connector import is more mature.....use it if you can. It not only avoids breaking things, it even brought the description updates added in Workbench into the "DataStage" tabledef for any DS developers who may not have access to Workbench. ...and yes, it creates the Datastage ta...

Hi Ernie, thanks for the clarification. I am indeed gathering that the ODBC Connector import is different than the ODBC Metabroker via Import Export Manager, but I am not sure what those differences are. I have yet to use it! It throws an error about an agent when I use it. It appears from your desc...

Hi Ernie, it looks like you are talking about using the DS Designer ODBC connector to update Table Definitions. Is that correct?

The trouble is with importing Database Tables in Workbench. Table Defs seem to work fine.


Thanks,
Doug

Hmm....I've tested this sequence of activity with other import methods (IDA as I recall recently) and it was fine, preserving descriptions, asset assignments, etc. That might be an anomaly with that particular broker. You might want to try the ODBC Connector import and see if that has better behavi...

Recently I have been living in the next release, and lineage thru Stage Variables there works great. I have specific examples that trace back directly....from an output link Derivation to a StageVariable used in that Derivation...then up above to the StageVariable Derivation and then upstream to th...

Hi folks, I noticed today that importing a database table into MW using the ODBC 3.0 Metabroker will blow away the descriptions on the table (if it already exists) and the descriptions on the parent schema, the database, and host objects in the repository. I don't see any option during the import pr...

Well after thinking about this a little my guess is the answer is that column lineage doesn't really work so well through stage variables, but it doesn't matter. Just drop down to the table level in Metadata Workbench and do not create or worry about column lineages. It appears that this is reinforc...

Hi folks, I am finding that the column lineage reports in Workbench won't span transformer stages. I can get lineage up to the transformer, and lineage after the transformer, but the two are disconnected. Is this normal? By the way, I am using stage variables in the transformer stage as a "best...

Hi folks, I found this excellent document on metadata management in Infosphere:

http://www.ibm.com/developerworks/data/ ... erecognos/

Ultimately, what's your goal? Ernie Hi Ernie, thanks for your continued patience. Our ultimate aim is to have lineage available from within Cognos. I understand that the "link" between the shared table and table def is not essential at runtime, the problem arises in design time when there...

Apparently, and I may be wrong on this, BOTH the stream link and the reference link must have the partition flag cleared. That means going upstream on both links and clearing the partition flag there. This is true even if you aren't repartitioning ONE of the links. If either link is being repartitio...

In that case dsenv should have been executed. Look in the second event in the job log (environment variables) and confirm that all the search list environment variables are correctly set. If not, fix dsenv. If they are, check the execution permissions for the library. Also check that the required g...