Title: Tales Of Big Hammer #10046 (AKA event 10046)
Arup,
 
Since I didn't see a line reporting error 1403, I was puzzled for a bit. But here is the application knowledge came handy. I should have see a commit for a successful operation. I didn't and instead saw a ROLLBACK. Immediately before the rollback I also saw a 'SQLNet Break' event so I put 2 and 2 togather and concluded that this caused the problem.
 
when I looked up the code, this was a implicit cursor, so it basically confirmed that this was the culprit. Also we took the bind values and the statement from sqlplus, and it *did* return two rows.
 
I highlighted the row with r=1 because according to Tim's explanation, I should have seen r=0. So I got confused and replied with excerpt from the tracefile. I know he will have some explanation about it.
 
For rollback look at Cursor# 45 ...
 
Raj
______________________________________________________

Rajendra Jamadagni              MIS, ESPN Inc.

Rajendra dot Jamadagni at ESPN dot com

Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.

QOTD: Any clod can have facts, but having an opinion is an art!

-----Original Message-----
From: Arup Nanda [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 31, 2002 8:59 AM
To: Multiple recipients of list ORACLE-L
Subject: Re: Tales Of Big Hammer #10046 (AKA event 10046)

Raj,
 
Thanks for sharing this with us. In your original post you mentioned that you saw a "rollback" right after the "SQL*Net break/reset to client" and that was how you figured out the 1403 error. I don't see that in this excerpt from the raw trace file, though. How did you determine it was this particulat SQL? Also the FETCH#54 line you have highlighted has r=1, not r=0; what's special about that line?
 
Thanks in advance.
 
Arup
*********************************************************************This e-mail 
message is confidential, intended only for the named recipient(s) above and may 
contain information that is privileged, attorney work product or exempt from 
disclosure under applicable law. If you have received this message in error, or are 
not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 
and delete this e-mail message from your computer, Thank 
you.*********************************************************************1


Reply via email to