Hi Mirali,

I have tried same setup in out internal core environment(app10) and data loaded successfully. 

No idea on the error without checking further analysing the code. Let’s see if anyone will give some input. 

Regards,

Sahan

Hi @Sahan Udana 

Thanks for the reply. I have check in multiple environments but it is coming up with the same error.

What could be the issue? any idea…

Hi Mirali,

It's due to the SQL keyword which are present in your migration Job. Sahan made an typo in his reference screenshot (VLAUES). But both IDENTITY as VALUES are SQL keywords. If you wish to use them (i suggest using something different it will cause errors in other areas as well), you can keep them between quotes;

Edit: Seems only ‘VALUES’ is an official SQL keyword But the PL/SQL tool will also highlight the IDENTITY column as such. So only VALUES need to be between double quotes.

Regards,

Mitchel

@Mirali , recreated the same error with above column names in APP10. but when you change the column name values to something like “VALUES1” it was resolved. So the issue is with that.

THanks @MiLeNL and @Manoj Ruwanhewa for responding. 

I have changed the column name and its working now. Thank you both.

Now i am wondering, if there is any way i can view all the official SQL keywords used in IFS applications as a list, so that I’ll be aware of this kind of issue beforehand.

Regards