DSXchange

& is (matches) only ever a single token (of any type).

Do you need to handle the possibility of multiple tokens being matched by the pattern?

Why? Doesn't the Search facility work for you?

Step 1. Disable operator combination so you can see which stage is generating the error.

Step 2. Find out where a timestamp format string might be coming from.

Step 3. Include an Else path in your If expression.

You don't have to save them to Oracle - you can adapt the application and save wherever you wish.

It DOES use the & pattern. That's why it's there.

Pattern action language is predicated on the "if you encounter this pattern do these actions" syntax. So the pattern is "used" to trigger the actions, irrespective of whether the actions use the token(s) associated with the pattern.

Download ETLStats from Kim Duke's website - note, however, that the row counts from DataStage are simply the rows that are sent to the database - not necessarily the same as the number that were successfully inserted/updated/deleted.

Top Left : Post New Topic

Use Director client.

Time, I feel, that you took the DataStage Essentials class.

Choose "Concatenation" from the expression editor's operator menu, and it will insert the correct operator.

Search this forum for an EReplace() function written by one of our contributors.

Use pools = "Conductor" (the actual pool name is irrelevant, so long as it is non-empty) and, specifically, don't use pools = "" for node1.

Don't process empty files.

Stage names do not carry invocation IDs. Only job names do.

Are you attaching the correct instance when invoking DSGetLinkInfo() ?

What stage type are you using? Usually this is by setting transaction size to 0 (which means "all rows are one transaction").