Okay this may be a desperate attempt to fit something I've discovered to this problem, but you could use the Connector Import Wizard in DataStage to import via ODBC using the FILE ODBC driver. This leads to a file called QETXT.INI. This file can be easily written out based on your spreadsheet data t...
Hi folks, I am using an FTP stage to retrieve data from a remote server. The FTP stage is the first stage in my ETL job. I have a blue table def and an orange shared table associated to it. The table def is associated to the ftp stage in DataStage (find where used confirms this). Metadata Workbench ...
Hi folks, we are standardizing on the Connector Import Wizard for the purpose of importing table defs into DataStage, and I want to apply this also to sequential file sources. To that end, I am looking at the DataDirect text driver for ODBC (VMtxt24.so). Has anyone got a sample config in .odbc.ini? ...
I wonder how many are supplying a data dictionary at all? The plan here is to publish datamart views. One view per grain definition (eg. Customer, Order, Department, etc). Every column in every datamart view is assigned a glossary term. Each glossary term may have many columns assigned to it, so a r...
did the code that priyadarshikunal sent worked. Since there is no free statement, the routine would blow up if there are many incoming records. Do a vmstat and the free memory should be coming down drastically depending on the number of records you are processing. What do you think should be freed?...
eostic wrote:Did you configure your Database Alias settings? (assignment of DataStage's abstract "server" string to the host-database combination for your imported Database (Shared) Tables)....
Hi folks, since upgrading to 8.5, I have the following problems in Metadata Workbench 1) Database tables are not associated to database connectors. Lineage and impact requires that I manually associate them. 2) Even with tables manually associated to stages, column lineage returns nothing. Column im...
The inputs to the CDC stage are supposed to be sorted on the primary key. If you don't put one there, one will be added automatically, unless you have prevented sort insertion via environment variable.
It should be correct to compare all columns except the primary key(s).