Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: commits and sql trace
Just an idea: why don't you start sqlplus, start with alter session set
sql_trace=true, do the sequence of statements you suspect that happen and
look at the trace file created.
You should be able to figure out what statements make trace you see from the
real application.
Scott Gamble <zifnab_at_islandsofmyth.org> schreef in berichtnieuws
qKGi9.113$0I3.6350_at_petpeeve.ziplink.net...
| The table is not dropped, its defined as a global temp table (on commit
| preserve rows) due to the third party app and its processing.
|
| I am trying to figure out why I am not getting the actual 'commit' text in
| the trace of this new release as we did in the old. I suppose it is
| possible that they are not reparsing the statement as they have in the
| past.
|
| Thanks for the answer
|
| Scott
|
|
| Tanel Poder <tanel_at_peldik.kom> wrote in
| news:3d8b3150$1_1_at_news.estpak.ee:
|
| > Hello!
| >
| > XCTEND means transaction end, thus commit or rollback
| >
| > rlbk=0 - commit was done
| > rlbk=1 - rollback was done
| >
| > rd_only=0 means that changes were made in this transaction
| > rd_only=1 means that transaction didn't change any data
| >
| > So, it seems that you do have several commits in your code.
| >
| > Do you just delete from this temp table or drop it as well?
| >
| > Tanel.
| >
Received on Sun Sep 22 2002 - 13:23:19 CDT