RE: No data in the sql_address column of v$session

From: Lex de Haan <lex.de.haan_at_naturaljoin.nl>
Date: Sun, 9 Oct 2005 12:25:08 +0200
Message-Id: <20051009102510.066CE1F7714@turing.freelists.org>

in the old days, many releases ago (up until 5.1) Oracle did not even support COMMIT and ROLLBACK as SQL commands;
for example, in SQL*Plus they were SQL*Plus commands. That is: no semicolon needed to execute them, and they would not end up in the SQL buffer. SQL*Plus would simply send the "appropriate" lower level commands to the database.

cheers,

Lex.  

---

Steve Adams Seminar http://www.naturaljoin.nl/events/seminars.html

---

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Alex Gorbachev
Sent: Sunday, October 09, 2005 11:53
To: Brandon.Allen_at_oneneck.com
Cc: Christian.Antognini_at_trivadis.com; arun chakrapani rao; oracle-l_at_freelists.org
Subject: Re: No data in the sql_address column of v$session

AFAIK, calling OCI function to commit/rollback should not generate any statement. Using SQL statement to commit/rollback should produce a statement v$sql. Correct me if I am wrong.

2005/10/4, oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org>:
> Not true.
>
> SQL>select hash_value, sql_text from v$sql where upper(sql_text) in
> SQL>('COMMIT','ROLLBACK');
>
> HASH_VALUE SQL_TEXT
> ---------- --------
> 1470906206 ROLLBACK
> 3615375148 COMMIT
> 3615375148 COMMIT
> 242587281 commit

--
Best regards,
Alex Gorbachev
--
http://www.freelists.org/webpage/oracle-l




--
http://www.freelists.org/webpage/oracle-l

Received on Sun Oct 09 2005 - 05:27:10 CDT