I use EasyLoader v 7.0 and Oracle 8.1.7. I try to upload only single table with one column of decimal(8,3) datatype.
I think this error (ORA-01722, invalid number) caused by wrong SQL query generated by EasyLoader. Maybe Oracle don't accept this queries generating by EasyLoader. I think this exception raises when EasyLoader call INSERT operator. The Oracle documentation states the following: ORA-01722: invalid number Cause: The attempted conversion of a character string to a number failed because the character string was not a valid numeric literal. Only numeric fields or character fields containing numeric data may be used in arithmetic functions or expressions. Only numeric fields may be added to or subtracted from dates. Action: Check the character strings in the function or expression. Check that they contain only numbers, a sign, a decimal point, and the character "E" or "e" and retry the operation. So, this error caused by invalid decimal separator representation? Maybe Oracle requires something else to be tuned? Yuri ----- Original Message ----- From: "Guy Groves" <[EMAIL PROTECTED]> To: "'Yuri Kruglov'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, August 05, 2003 10:17 PM Subject: RE: MI-L EasyLoader error while loading tables to Oracle Spatial > What versions of Easyloader and Oracle are you using? > > EasyLoader: 6.70.08 > Oracle 9i (9.0.1.1.1 and up) and 8i (8.1.7) > > I have not had any problems loading Float or decimal. I don't have > time, but you should look up the Ora error number for more details. > > You dialog below indicates that you select multiple TABs. Are you > loading all the TABs into a single Oracle table? If so I would suspect > one of your tab files has the right column name but not the right column > datatype. The error seems to indicate that the datatype being passed is > not of the expected datatype. It may look like a float or decimal but > in fact you may be trying to pass a character string? > > I would recommend you inspect the data structure of all the import files > carefully. If they are to go into a single Oracle table they MUST be > identical in structure. Next test for bad data values (out of range). > > Consider the order of the load. The first table will define the data > structure. You might load one file at a time into separate tables to > find which TAB file is creating the problem. > > PS. > If you are loading multiple TAB files into a single table TURN OFF index > creation. Create the indexes after all loads are complete, this will > save time. If you want you can load the last TAB file as a single run > and create the indexes then to simplify (I prefer to create my indexes > afterward in Oracle using SQL statements. The advantage is I can > perform several query tests and tune the indexes in the process. > > -----Original Message----- > From: Yuri Kruglov [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 05, 2003 03:49 AM > To: [EMAIL PROTECTED] > Subject: MI-L EasyLoader eroor while loading tables to Oracle Spatial > > Hi, All, > > I have the fololowing problem while attempting to load TAB files to > Oracle Spayial. > > I do the following. > > I connect to Oracle Spatial, then select necessary tables, then press > Upload Tables. > > If TAB table contains columns with the datatype of Float or Decimal all > operation going failed > with the message ORA-01722 Wrong Number "2.003", for example. > > How do I resolve this problem? > > Sincerely, > Yuri Kruglov > --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 7903
