Page 1 of 1
NLS Mapping Warning/error
Posted: Wed Aug 13, 2008 4:18 pm
by ds2000
CFF -> Tx -> Seq. File
When extracting cff file it warns with following msg. I tried different NLS mapping but same error. Input file is in CR/LF format. I viewed the data and some rows were having : character in it, i replaced : with blanks but still warning out.
Extract702..seqTRANKEY.outTRAN: nls_map_buffer_out() - NLS mapping error, row 154 (approx), row = "& , ?,000I00000,000,, ,000-- ::"
Posted: Wed Aug 13, 2008 8:54 pm
by ds2000
ANY GURU AROUND ?
Posted: Thu Aug 14, 2008 9:29 am
by ds2000
Any Comments ?
Posted: Thu Aug 14, 2008 9:39 am
by ArndW
3 Steps for that line:
1. Display the Hex/Octal values of the characters to see what you have.
2. Determine which NLS character set you are mapping from and going to.
3. see if the character is legally mappable.
If yes, you have a problem. If no, then you have found your problem.
Posted: Thu Aug 14, 2008 10:18 am
by chulett
Four steps actually.
4. Learn patience.
Posted: Thu Aug 14, 2008 11:53 am
by ds2000
1. How to display hex/octal values of a row.
2. MS1253
Posted: Thu Aug 14, 2008 12:36 pm
by ArndW
1. use "od"
2. Ok, "MS1253" is Greek. Is that what the CFF was originally created in? And what is your DataStage output file NLS character set?
Posted: Thu Aug 14, 2008 12:58 pm
by ds2000
Im sorry it was MS1252 not MS1253.
Posted: Thu Aug 14, 2008 1:04 pm
by chulett
Still need to answer the question. And if "od" doesn't mean much, you can google for "free windows hex editors" and take your pick.
Posted: Thu Aug 14, 2008 2:22 pm
by ds2000
Actual Row:
995100003 213576 001950449803503 2008050700000000 003 SHORT TERM PREM 100 ANNUAL PREM 100
Hex format:
39 39 35 31 30 30 30 30 33 20 20 20 32 31 33 35 37 36 20 20 30 30 31 39 35 30 34 34 39 38 30 33 35 30 33 20 20 20 20 20 20 20 20 32 30 30 38 30 35 30 37 30 30 30 30 30 30 30 30 20 20 20 20 20 20 30 30 33 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 53 48 4F 52 54 20 54 45 52 4D 20 50 52 45 4D 20 20 20 31 30 30 20 20 20 20 20 41 4E 4E 55 41 4C 20 50 52 45 4D 20 20 20 20 20 31 30 30
Posted: Thu Aug 14, 2008 4:04 pm
by ray.wurlod
Please enclose the Actual Row in Code tags so we can see the extra spaces.
However, the hex dump does not show any byte over 7F, which means that code page 1252 should have no problem at all with these particular data.
Code: Select all
9 39
9 39
5 35
1 31
0 30
0 30
0 30
0 30
3 33
20
2 32
:
S 53
H 48
O 4F
R 52
T 54
20
T 54
E 45
R 52
M 4D
32
:
1 31
0 30
0 30
Posted: Thu Aug 14, 2008 6:30 pm
by ds2000
995100003 213576 001950449803503 2008050700000000 003 SHORT TERM PREM 100 ANNUAL PREM 100
Coding:
--- ----
39 9
39 9
35 5
31 1
30 0
30 0
30 0
30 0
33 3
20
20
20
32 2
31 1
33 3
35 5
37 7
36 6
20
20
30 0
30 0
31 1
39 9
35 5
30 0
34 4
34 4
39 9
38 8
30 0
33 3
35 5
30 0
33 3
20
20
20
20
20
20
20
20
32 2
30 0
30 0
38 8
30 0
35 5
30 0
37 7
30 0
30 0
30 0
30 0
30 0
30 0
30 0
30 0
20
20
20
20
20
20
30 0
30 0
33 3
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
53 S
48 H
4F O
52 R
54 T
20
54 T
45 E
52 R
4D M
20
50 P
52 R
45 E
4D M
20
20
20
31 1
30 0
30 0
20
20
20
20
20
41 A
4E N
4E N
55 U
41 A
4C L
20
50 P
52 R
45 E
4D M
20
20
20
20
20
31 1
30 0
30 0
Posted: Thu Aug 14, 2008 7:32 pm
by chulett
How is any of this helping? As Ray notes, there's nothing in the record being shown here with a byte value over 7F so this is all perfectly normal boring text. And the semi-colons you were worried about in the first post are not an issue either.
What happened to dumping the record being complained about?
NLS mapping error, row 154 (approx), row = "& , ? , 000I00000,000,, ,000-- ::"