DSXchange

That would depend on the views - if they're not materialized views then one would certainly expect the response time to be extended, as the view-defining query must be completed first, before the join can be started.

There are lots of ways. Research them by searching the forum.

Did you mean Ln() - logarithm - or Len() - character length - in the highlighted expression?

Each causes additional entries to be logged. APT_RECORD_COUNT causes each player process to log an entry showing the number of records it processed. It does this as part of its shutdown processing. OSH_PRINT_SCHEMAS causes each player process to log an entry showing the actual record schema it used....

This is built-in functionality in the Complex Flat File stage!

When you import the table definition for the Sequential File you can specify a global quote character. On the Format tab of the link properties you can also specify the default quote character. Your properties currently have this set to " - try setting it to None.

No. The .ds files themselves are tiny in any case, and are already in a binary format. The actual data of a Data Set resides elsewhere, on the resource disks specified in your configuration file. Again, these are already in a binary format. Attempting to compress them will not produce any gain worth...

The point is, Shin0066, that you already have the data and the job design. So you can try it and let us know. We'd only be guessing - admittedly an educated guess in some cases - or would have to reproduce your work to answer your question - without being compensated for doing so.

Execute the oerr command (perhaps in an External Filter stage) to decode the error, or query the Oracle system table that decodes error codes.

In what format are the data arriving? That's what you must specify correctly to the stage.

Can you do this with the XML Output stage?

You don't need the linked manual; the DataStage BASIC manual which you have with your client has everything you need.

It's not necessarily a bug. Some stage types simply don't have parallel execution capability. Others that do have their default execution mode as Sequential, usually for obvious reasons. For example a Sequential File stage with an input link and only one File named can only generate one process - th...

The most likely reason is that only 30 characters are coming from source. Please verify that you have checked this possibility. The next possibility is that something in the job is truncating the field to 30 characters. Please verify that you have also checked this possibility.

Direct the flow into a Sequential File stage rather than the SAP stage - you will then be able to see exactly how the data are being delivered.

Good point. The script would also need to construct an appropriate record structure and insert the record into DS_METADATA table. Not a task for the faint-hearted or even for the inexperienced!