All Forums Tools
arjune 14 posts Joined 07/11
14 Sep 2011
double pipe delimiter ('||') in Mload script.

Hi,

Can I use '||'  as delimiter in Mload script?

Pls reply asap.

Thanks in advance.

feinholz 1234 posts Joined 05/08
14 Sep 2011

Did you try it?

If it works, it is supported.

If it does not work, then it is probably not supported.

What version of MultiLoad are you using?

 

 

--SteveF

arjune 14 posts Joined 07/11
14 Sep 2011

I am using teradata 13 version,  I am in dillemma whether it works or not ,I m using MULTILOAD 13.0.0 version .I want any previous experience of success using it or any drawbacks encountered bcaz i can start all the way i need to check it.

feinholz 1234 posts Joined 05/08
15 Sep 2011

Why do you say you are in a dilemma?

Have you tried it?

Does the MultiLoad manual indicate that multibyte delimiters are supported?

(BTW, I believe as of TTU12.0 they are.)

 

 

--SteveF

arjune 14 posts Joined 07/11
18 Sep 2011

 

Feinholz, thanks Its working ,but this reference from TTU 13.0.0(underlined one) confused me

If a 'c' specification is not used, the default is the pipe character (|).

Except for the UTF16 client character set, the delimiter character must be a single byte in the client

character set. When the character set of the job script is different from the client character set used

for the job, Teradata MultiLoad translates the effective delimiter from the script character encoding

to the client character encoding before separating fields with it.

For example, the job script must be in Teradata EBCDIC when using the UTF8 client character set

on z/OS; the job script can be in UTF8 when using the UTF16 client character set on networkattached

systems.

----------------from TTU 13.0 manual

 

 

 

feinholz 1234 posts Joined 05/08
21 Sep 2011

I will check with the developers to see why our documentation has not been updated.

It is possible the feature was added to a more recent release, and then backported to a prior releases.

We are not allow to update documents once they go to the web (yes, I know, not good, but I cannot control that).

 

--SteveF

feinholz 1234 posts Joined 05/08
21 Sep 2011

I looked at the FastLoad manual, and the MultiLoad manual (for 13.00).

FastLoad says this:

Delimiters can be a multi-character sequence up to a maximum of 10 bytes.
Note: Multibyte characters can be 1 byte, 2 bytes or 3 bytes depending on
the session character set. The number of characters that can be used as
delimiters is limited by the byte size of the characters
For example: Setting 10 Japanese characters with KANJIEUC_0U code has
a string length of 20 bytes. In this case, FastLoad will fail with an error
message of “The xxxxxxxxxx string exceeds the length limit.” The number
of Japanese characters must be reduced to 5, which equals 10 bytes.
The default, if a “c” specification is not used, is the pipe character ( | ).

 

MultiLoad shows what you indicated.

Not good. I will notify the engineering team.

But we cannot go back and correct old documentation.

Hopefully, things are better in the newer release documents.

--SteveF

arjune 14 posts Joined 07/11
04 Oct 2011

Thanks feinholz for your response.

25 Oct 2011

can you explain me clearly about double pipe delimiters pls.......

feinholz 1234 posts Joined 05/08
26 Oct 2011

Please be more specific about your request.

--SteveF

You must sign in to leave a comment.