DSXchange

There are two variants of the command. The one that is used with a pathname does not have a dot (it is SETFILE). The one with the dot creates a logical pointer (also known as a Q pointer for historical reasons) and must perforce work with VOC entries in the project account. In your case, simply lose...

Have you looked in the install log (or, perhaps, at the screen if you were using the -verbose option) to get more information about what the problem is? From the small amount of information you've provided, it appears that the problem was in installing the client component of InfoSphere Metadata Ass...

"Completed successfully" does not strike me as being an error. Perhaps you can be a bit more explicit about the actual error you allege is being thrown, which would allow more targeted diagnosis.

You have two choices in the Lookup stage. Set the Lookup Failed property to Continue, making sure that all columns coming from the reference input are define as nullable there and on the output link, and check for NULL downstream. Set the Lookup Failed property to Output (the name of this value may ...

Maybe there was no other way for DataStage to be aware of the value of APT_CONFIG_FILE environment variable ?

Why not save the table definition from the Sequential File stage Columns tab, then view the table definition as a record schema on the Layout tab?

Consider an alternative - keeping your reference data in a table (or more than one), and associating the table(s) with term(s) in your Glossary.

By this means your lineage reports will be more meaningful.

Retrieving reference data through an API may not prove fast enough for your ETL activity.

What's the business case behind the requirement? That may assist in deciding the most appropriate algorithm - there are at least five different ways to solve this one.

You can try declaring the metadata for the input file as data type string (that is, SQL data type Char), with an appropriate format string in the extended properties if YYYY-MM-DD is not your system's default format. This will read the date and convert it to a binary date type, which should be able ...

Does your source really have five digit year? (The good news is that server jobs support this, but can't reliably convert a five digit year into a four digit format.)

Another surprise for me today (may exist in previous versions). orchadmin check objects to comments in the beginning of the configuration file. $ bin/orchadmin check ##E IIS-DSEE-TFRM-00003 While parsing ORCHESTRATE config file, near line 1: Expecting open brace at beginning of config file, instead ...

What are your source and target? What data types pertain to each for these "date" fields.

If Date, there's nothing to do.
If a string of some kind, then you have some flexibility.

Read up about format strings for date functions.

The solution is in Craig's response so, yes, obtaining a premium membership would be a good idea for you. It will also help to defray the hosting and bandwidth costs incurred by DSXchange.

Do you have an XSD that describes that layout? If yes, import the "table definition" from that XSD. Then using any of the XML stage types will be a doddle.

ODBC is necessarily slower than native connectivity, not least because of the extra layer of software (the ODBC driver) that has to be involved.

Try using a native Oracle stage; for preference the Oracle Connector stage.