U_ILLEGAL_ARGUMENT_ERROR encountered in Datastage PX 7.5.2

samyamkrishna · Post by **samyamkrishna** » Mon Nov 02, 2009 4:12 am

Hi All,

Has anyone encountered the following error while running a Datastage PX 7.5.2 Job before?

U_ILLEGAL_ARGUMENT_ERROR encountered
followed by

Conversion problem in import method, trying to import:.

followed by

Operator terminated abnormally: received signal SIGSEGV.

The source file format seems to be correct .The stage which encounters this error is a column import stage.

Thanks for your help in advance.

Regards
samyamkrishna

ArndW · Post by **ArndW** » Mon Nov 02, 2009 5:35 am

how many and what type columns are you importing in that stage?

ram.manojk · Post by **ram.manojk** » Tue Nov 03, 2009 5:27 am

Hi ArndW,

I am samyamkrishna's colleauge and he has posted this on my behalf as I had some login issues yesterday.

The job has a column Import stage and it is importing 17 columns. The first field is of Timestamp type , the third field is of type decimal and the remaining fields are of type Varchar .

A sample record of the source file which is input to this stage is as below

08/Oct/2009 13:43:40 acct-xxxx 200 xxxxxx 100000001 10003400 - 30000000000 XXXX false
1000000 20000000 735 2000 685 - -

Thanks & regards,
Ram Manoj

ArndW · Post by **ArndW** » Tue Nov 03, 2009 5:41 am

Change your timestamp to a char(19) and see if the error goes away. I would think it is the nonstandard "MMM" portion that you haven't catered for.

gssr · Post by **gssr** » Tue Nov 03, 2009 5:45 am

Force Compile the job and try to run..

ram.manojk · Post by **ram.manojk** » Tue Nov 03, 2009 6:17 am

ArndW wrote:Change your timestamp to a char(19) and see if the error goes away. I would think it is the nonstandard "MMM" portion that you haven't catered for. ...

Hi ArndW

Actually this job has been running fine since a long time earlier with similar data that I just illustrated. It failed recently. I thought it was an issue with the record format but could not find any issue with the record.
Please find the exact error message I had in the Job log

21560 INFO Sun Nov 1 17:17:33 2009
Ci_Fic,7: Field "TIMESTAMP" delimiter not seen, at offset: 20
21561 INFO Sun Nov 1 17:17:33 2009
Ci_Fic,7: Import was unsuccessful at record 30965; continuing.
21562 FATAL Sun Nov 1 17:17:33 2009
Ci_Fic,5: U_ILLEGAL_ARGUMENT_ERROR encountered.
21563 FATAL Sun Nov 1 17:17:33 2009
Ci_Fic,5: Conversion problem in import method, trying to import:.
21564 INFO Sun Nov 1 17:17:33 2009

Thanks for your help.

Regards,
Ram Manoj

n.parameswara.reddy@accen · Tue Mar 02, 2010 6:53 am

I am also facing the same issue, please help me regarding this issue.

Ci_Fic,0: U_ILLEGAL_ARGUMENT_ERROR encountered.

ram.manojk wrote:
ArndW wrote:Change your timestamp to a char(19) and see if the error goes away. I would think it is the nonstandard "MMM" portion that you haven't catered for. ...
Hi ArndW

Actually this job has been running fine since a long time earlier with similar data that I just illustrated. It failed recently. I thought it was an issue with the record format but could not find any issue with the record.
Please find the exact error message I had in the Job log

21560 INFO Sun Nov 1 17:17:33 2009
Ci_Fic,7: Field "TIMESTAMP" delimiter not seen, at offset: 20
21561 INFO Sun Nov 1 17:17:33 2009
Ci_Fic,7: Import was unsuccessful at record 30965; continuing.
21562 FATAL Sun Nov 1 17:17:33 2009
Ci_Fic,5: U_ILLEGAL_ARGUMENT_ERROR encountered.
21563 FATAL Sun Nov 1 17:17:33 2009
Ci_Fic,5: Conversion problem in import method, trying to import:.
21564 INFO Sun Nov 1 17:17:33 2009

Thanks for your help.

Regards,
Ram Manoj

ArndW · Post by **ArndW** » Tue Mar 02, 2010 8:12 am

As mentioned before, change the field to a CHAR one and see what the contents are. DataStage is expecting a delimiter and not seeing one; I would point towards data changes.