ORA-01722 Invalid number Error

We periodically get Oracle errors from LAPI calls made in our Production environment. The LAPI calls are made from a Java application. Looks like the LAPI call passes in an objectid that Oracle does not recognize as a number. The error is "ORA-01722 Invalid number."We are able to solve the problem by recycling our Livelink servers. Has anyone else experienced this problem or something like it? We hate to have to bounce the servers every time the problem comes up.

Find more posts tagged with

Comments

Andrew_Byng-Hall

We are also experiencing this problem randomly. Did you get to the cause of this?

Donna Nalls

I ran across an issue at a client site recently that may be related.....oracle was choking on insert statements -- it appeared that the numbers i was pulling from one (non-Livelink) oracle table and passing into another (Livelink) table through an insert stmt were being interpreted as real datatypes instead of integers - i could see in the array returned from the select stmt that all of the numbers had a "G" at the beginning (indicating a real datatype).....it was custom code, so we were able to work around it by performing some crazy datatype conversions after the select and before the insert. I have continued to wonder what in the world caused the problem and if others had encountered it -- and why it wasn't happening with core livelink if it was happening in my code.I almost feel like it is an Oracle version and configuration issue...but, not being a dba, i really don't know what or why.Sorry - this is not really a solution, just a possibly related incident.regards,donna

Philippe Gauvin

I have this problem too, with IE not LAPI. When it comes up, I do "refresh" with the browser and it works after some clics

)). This is really randomly and unfortunatly, I don't have an workaround nor a solution

((

Janusz_Frydecki

Neither of you had grab connect logs?

Nick_Gilbert

We get the same error on some standard select statements, see below:

05/09/2010 07:44:23 [1188094843] 0000023586: KSqlCursor::Open(2000,'select OWNERID,PARENTID,DATAID,NAME,ORIGINOWNERID,ORIGINDATAID,USERID,GROUPID,UPERMISSIONS,GPERMISSIONS,WPERMISSIONS,SPERMISSIONS,ACLCOUNT,PERMID,DATATYPE,RESERVED,SUBTYPE from DTree where DataID=:A') -->'SUCCESS'

05/09/2010 07:44:23 [1188094867] 0000023587: KSqlCursor::Prepare() --> 'SUCCESS'

05/09/2010 07:44:23 [1188094886] 0000023588: KSqlCursor::Bind(1,{32220905}) --> 'SUCCESS'

05/09/2010 07:44:23 [1188100013] 0000023589: Oracle error: (1722) --> ORA-01722: invalid number

All it did was this – any ideas? Are we any closer to figuring out why the ORA-01722 errors keep occurring? See a previous post stated that a TAR had been raised with Oracle - any outcome?

SELECT

OWNERID, PARENTID, DATAID, NAME, ORIGINOWNERID, ORIGINDATAID, USERID, GROUPID, UPERMISSIONS,

GPERMISSIONS, WPERMISSIONS, SPERMISSIONS, ACLCOUNT, PERMID, DATATYPE, RESERVED, SUBTYPE

FROM

DTree

WHERE

DataID=32220905

Nick_Gilbert

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.4
This problem can occur on any platform.

Symptoms

ORA-1722 error in PL/SQL after upgrading from 10.2.0.2 to 10.2.0.4.

Changes

Applied the 10.2.0.4 patchset on top of a 10.2.0.2 database.

Cause

Bug 8479537 where an incorrect child cursor might be chosen which does not have
correctly matching bind variables.

Solution

Applied the merge patch, Bug 8548100, which contains the fix for Bug 8479537 and the fix for unpublished Bug 7025450 to correct problems with the dbms_shared_pool.keep package.

After the patch was applied we also pinned the problem package to the shared pool.
exec dbms_shared_pool.keep('<package>');

References

BUG:8479537 - WRONG DATA INSERTED WHEN WHEN CURSORS GETS FREQUENTLY FLUSHED FROM SHARED POOL
NOTE:8479537.8 - Bug 8479537 - Wrong child cursor with mismatching binds executed