DataStage Job 222 Phantom 26691 (Characters not in NLS map)

pravesh_kushwaha · Post by **pravesh_kushwaha** » Thu May 12, 2005 11:27 am

Hi All,
I am getting the following error:

DataStage Job 222 Phantom 26691
Record 4242 contains characters which are not defined in the file's NLS map.

Attempting to Cleanup after ABORT raised in stage GNSEventPromoteAndValidate.0.PromoteAndValidate
DataStage Phantom Aborting with @ABORT.CODE = 3

Can someone please tell the cause of this error and how can it be resolved.

Thanks,

ray.wurlod · Post by **ray.wurlod** » Thu May 12, 2005 6:01 pm

Record 4242 contains characters which are not defined in the file's NLS map.

ray.wurlod · Post by **ray.wurlod** » Fri May 13, 2005 6:31 pm

I'd also be asking whether there really are "}" and "|" characters in the data, or whether these are being translated from value marks and field marks.

arunverma · Post by **arunverma** » Sat May 14, 2005 2:36 am

HI Battliou ,

If you are getting special character in source column , then you can create routine and use in transformation , it will remove those character .

Ex:- Routine - RemoveUnWantedChar

It removes following character.

Chr(10) , Chr(13) = "Enter Key"
Chr(124) = "|" ---> Pipe
Chr(44) = "," ---> comma
Chr(34) = """ ---> double cots
Chr(37) = "%" ---> percentage

Code :-

* Store in a local variable.

InputString = Arg1

* after trimming the Input value stored in local variable.

Var1 = trimb(trimf(InputString))

* Now remove Enter key and pipe character.

Var2 = Trim(Trim(Trim(Var1,Char(124),"A"),Char(10),"A"),Char(13),"A")

* Now remove comma, double cots and percentage character.

Ans = Trim(Trim(Trim(Var2,Char(37),"A"),Char(34),"A"),Char(44),"A")

anupam · Post by **anupam** » Tue May 24, 2005 9:52 am

Very Rightly said by Arun Verma.

It is better you remove all unwanted special characters using routine.

arunverma · Post by **arunverma** » Tue May 24, 2005 11:14 pm

Hi Anupam ,

Where are you ??? , no communication for last six month ....

Regards

arun

pravesh_kushwaha · Post by **pravesh_kushwaha** » Sun Jun 05, 2005 11:35 pm

The problem got resolved when changed the NLS map to none at the job level.

ray.wurlod · Post by **ray.wurlod** » Mon Jun 06, 2005 2:07 am

The correct NLS map for hashed files is always NONE. This is because hashed files are internal to DataStage; the data have already been mapped from the external representation by the time they get into a hashed file.

Had you mentioned in your original post that a hashed file was involved we probably would have reached the solution more quickly.