Thanks for the question, brezig.
Asked: April 26, 2017 - 1:41 pm UTC
Last updated: April 27, 2017 - 6:37 am UTC
Version: 11.2.0.4
Viewed 1000+ times
You Asked
Hi Tom,
From the application side, an application owner was trying to do an update on the Appendix column of a table whose datatype is CLOB. What she actually tried doing was change an "I" into an "O" then she received the ODBC Error:[Oracle][ODBC][Ora]ORA-01410:Invalid ROWID.
As the DBA, I've gone into the database to do my findings, the row she's trying to an edit on actually exists in the database. I have no clue of what to do to prevent her from getting that error from the application side. Please, any suggestion?
and Connor said...
Best was would be to put a trace on the session - my guess is either
- the bind variable is perhaps getting corrupted or mangled.
- the time at which the rowid is being used, it does not exist
but do this:
- exec dbms_monitor.session_trace_enable(binds=>true)
- run the process that gets the error
- exec dbms_monitor.session_trace_disable
then examine the trace file to see what SQL was run, and what binds were passed in.
If you can't tweak the code to do it inline, then you can either
a) pass in the sid/serial# from another session, or
b) create a login trigger to enable trace as soon as the odbc session connects
Is this answer out of date? If it is, please let us know via a Comment