OraFAQ Forum: Designer » 1858 problem after Oracle 10g upgrade

Home » Developer & Programmer » Designer » 1858 problem after Oracle 10g upgrade (Oracle 10.1.0.4, 10.1.0.4 drivers, Jdk 1.3)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

1858 problem after Oracle 10g upgrade [message #321846]

Wed, 21 May 2008 08:55

JasjotS
Messages: 12
Registered: March 2008
Location: India

Junior Member

Hi,

After we upgraded our application database from 9.2.0.8 to 10.1.0.4 Oracle database, we have started getting a strange error, the cause of which seems to be ORA-1858 error. Is it something related to Database-Drivers compatibility or its a known bug of 10.1.0.4, or what?

Please help!

Note that we are using 10.1.0.4 drivers with Oracle 10.1.0.4 database.

Regards,
Jas

Report message to a moderator

Re: 1858 problem after Oracle 10g upgrade [message #321892 is a reply to message #321846]

Wed, 21 May 2008 14:32

Littlefoot
Messages: 21826
Registered: June 2005
Location: Croatia, Europe

Senior Member
Account Moderator

Known bug? Perhaps, but the one your developer has made.

Oracle

ORA-01858: a non-numeric character was found where a numeric was expected

Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a number where a number was required by the format model.

Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.

You might check whether NLS settings are the same as in the "old" database; developer might have relied on implicit date conversion. For example, there's something like this in your code:

... WHERE date_column = '21-may-07'

but should have been

... WHERE date_column = TO_DATE('21-may-07', 'dd-mon-yy')

Therefore, I wouldn't blame Oracle, but human.

Report message to a moderator

Re: 1858 problem after Oracle 10g upgrade [message #322084 is a reply to message #321892]

Thu, 22 May 2008 07:17

JasjotS
Messages: 12
Registered: March 2008
Location: India

Junior Member

Thanks a lot...............
It was a great help, this was the exact cause.
Client DBA had changed the date settings after the Oracle 10g upgrade Smile

Report message to a moderator

Previous Topic:	Reengineering using Oracle Designer
Next Topic:	Data Modelling

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Mar 07 18:54:21 CST 2026