If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

i can only tell you that until you started asking question i thought i knew what i was talking about. but going back to me calss material, andthe doc made me understand that you are not alone.
i can only tell you that, and at first i did not whant to put this in writing (for this is just a guess, i can not prov it in the documentation), if you look at the process of sql/plsql statment goes through, from before parsing, v$sqltext_with_newlines, to parsed statment in v$sql, to something ready to be used in v$sqlarea, to something in the sga that is actualy processed by with data feched from the disk (v$sqltext). i do not what to get more into the part of the memory process, but i think that every table is a picture in a different stage of the memory management in the execution process.

Hello ..:-)
The v$sqltext comes from (global view) gv$sqltext comes from oracle kernel X$kglna
The v$sql comes from gv$sql comes from x$kglcursor...
So, the x$kglna meens the Kernel-Generic-Layer-Network-Access
The X$kglcursor is the Kernel-Generic-Layer-Cursor...
The 1' keeps information about the network in your db (so what is going on in that moment)
The 2' is a gather-user dependent (what is+was going on)

[QUOTE][i]Originally posted by aracnid [/i]
[B]
The 1' keeps information about the network in your db (so what is going on in that moment)
The 2' is a gather-user dependent (what is+was going on) [/B][/QUOTE]

This part makes sense, thatīs why i see only the last SQL issued by a user with v$sqltext

My understanding of the difference between v$sql and v$sqltext is this:

v$sqltext is a view of the sql statements currently running in memory.

v$sql is a view of the sql statements that have run over the life of the instance and cumulative statistics regarding their execution (such as how many times that statement has been executed, how many total disk reads and buffer gets are associated with the statement, etc.).

If you want to look at the differences in the actual view definitions against the x$ tables then you can do something like this (under Oracle8):