DSXchange

The MDB file is not deployed to the UNIX server - there's no such thing as Access on UNIX. The most relevant document to read is your licensing agreement, which expressly forbids reverse engineering. Since deployments are not logged on the server you are pretty much restricted to checking each clien...

Umm.. define an explicit length in the export metadata? Maybe that's what you are doing, and the unbounded string is purely internal. In that case (unless you can associate the stage with a schema file) there's not much I can suggest.

Welcome aboard.

Any field that is to appear in the WHERE clause must be marked as Key in the Columns grid. Key in this context does not necessarily mean primary key; it means search key.

Arnd: That's neat. I though it only worked with Data Sets.

fabianorb: Do mark the thread as resolved if that solves your problem.

You only need to partition on Key. Including EffDt in the partitioning may lead to inconsistent results. Though you still may want to sort on EffDt. Could you, instead, use an Aggregator stage, grouping on Key and generating Min(EffDt) and Max(ExpDt) ? The same partitioning considerations as above a...

Replace the field marks with linefeed characters (Char(10)).

<unprintable response>

</unprintable response>

Do you have the environment variable for the conductor node (APT_PM_CONDUCTOR_HOSTNAME) set?

You are stuck with sequential until you can be granted SELECT privilege to the table(s) on which the view is defined. Then you use the view-defining statement in your Oracle Enterprise stage instead of the view name. Argue to the DBA that only the DataStage user needs to be granted this privilege, a...

Do some detective work. Discover why this particular field is being assigned a default value. Could it be that you did not specify it, and have RCP enabled? Once you've discovered the cause, correct the cause.

They are searchable on the IBM "eServices" web site.

In particular look in and around line 20 of your routine. The error message complains of unexpected characters ".;" - can you see them there?

You still didn't define "performance".

I still don't believe you need the named COMMON. I believe you could use a stage variable called svErrLog in exactly the same way. The named COMMON is not wrong, but does preclude you using this job or a fragment of it in a server shared container in a parallel job, if that's a consideration.

What do you believe the "limitations of the dsadmin -listenv command" to be?

Does the script work in its present form?