DSXchange

ray.wurlod

Re-read Paul's response. The additional information you provided does not obviate the fact that you need WAS running where currently it is not.

ray.wurlod

I thought that the Dads and Grads would have been more likely to have had this particular experience if anyone had.

Alas 'twould seem that no-one has.

ray.wurlod

You have seen an unexpected internal error that you probably won't be able to reproduce.

If it happens again, involve your official support provider, always best for internal errors.

ray.wurlod

You are using version 8. The unstructured data stage is not available until version 9.1.

ray.wurlod

Your job or stage appears to be using UTF-16LE.

ray.wurlod

Why do you not specify the same encoding (UTF-8) that Teradata is using?

ray.wurlod

Are the three outputs delivered through three procedure arguments, or via its return value?

ray.wurlod

The lookup functions in the Modify stage, such as lookup_int16_from_string(), may suit your requirement.

ray.wurlod

Is it repeatable for those two projects?
Are the identifiers (host names, project names) spelled correctly and in the correct case?

ray.wurlod

Code: Select all

JobA   ----->  NestedCondition --->  JobB
                      |                |
                      |                |
                      |                V
                      +-----------> Sequencer  ----->  JobC
                                      (any)

ray.wurlod

Teradata is using some kind of Unicode encoding (such as UTF-8). Your job is specifying VarChar(20) but is not specifying Unicode in the Extended column of the Columns grid.

ray.wurlod

Courier New is wasteful of screen space. Also, the Data Viewer (log viewer) has to work with all character sets, and not all of these are supported by Courier New (for example the CJK language character sets). That's why it will never happen out of the box.

ray.wurlod

Better is to use the colon notation.

Code: Select all

TX=:/etc/localtime ; export TZ

ray.wurlod

Well, the typeface is not stored in the log, it's a function of the viewing interface. You could always write your own log viewer.

ray.wurlod

It needs this information so that the SAP components can talk to the installed Information Server components. It will not install another engine. Give precisely the same information that you used when installing Information Server.

Search found 53125 matches