DSXchange

Are there any warnings in the DataStage log or in the Oracle logs?

Search DSXchange for DSJS.RUNNING - worst case you can clear the job status file using administrative menu option in Director.

System variable @INROWNUM contains this count. Note that it is per-node.
You can not get the final count until the final row has been processed (on the current node).

IBM is running training class Information Server Administration (DX447) in Singapore 6-8 Feb 2012. I will be the presenter.

Not every thought about column names is printable either.

If you're running 8.7 the command line interface for Metadata Asset Manager is imam.

The command line interface for Import Export Manager is the imaginatively-named ImportExportManager.

Probably.

^@ is Char(0)
^A through ^Z are Char(1) through Char(26) (easy to remember!)
^[ is Char(27) (Esc)
^\ is Char(28)
^[ is Char(29)
^^ is Char(30)
^_ is Char(31)

Char(32) is space (" "), the first of the printable characters. All characters from 32 through 127 are printable.

IBM are running a training class Metadata Workbench Essentials (KM620) in Singapore on 9-10 Feb 2012. I'll be the presenter.

Yes.

The ^@ you see in vi is ASCII NUL, or Char(0), or \x00 - however you want to represent it. It's the default value of APT_STRING_PADCHAR environment variable, which is the character with which Char data types are padded. It may also exist in your data, particularly binary numbers.

Here is a good IBM tutorial available: http://www.ibm.com/developerworks/data/tutorials/dm-1007infospherecognos/index.html?ca=drs- It steps through all the tasks for metadata integration between Information Server and Cognos. It's from July 2010 so it will not have the version 8.7 Asset Manager and...

Off the top of my head: Connectors (including DRS Connector) Data Connection objects Parameter Sets Support for connection to newer versions of databases Job log visible in Designer New XML handling - effectively unlimited document size Faster startup of Designer, particularly with complex job desig...

Make sure that your data are partitioned on the key. Sort the data by key, generating a Key Change column. If the data are already sorted, indicate this fact in the Sort stage. In a Transformer stage stage variable maintain the concatenated string. If KeyChanged Then input.String Else svConcatenated...

You are too hasty in using the term "junk". This raw string contains your client's real data - not rubbish. Not every character in a raw string is necessarily printable. This does not preclude valid data being stored.

The key expression in the Transformer stage should have the constant "X". This means that the "X" record is looked up for every row processed. It should be quick, as it will tend to have this record cached in memory.

Look in the manual for how to use metabrokers and bridges.