Why? Please use statspack or query v$sql after the statement has
completed.

Please do not crosspost to every group you can spell, especially if
they don't exist anymore.

--
Sybrand Bakker
Senior Oracle DBA

I have reported by a report tool (crystal), which has to run a single sql,
so everything should be in the sql statement.
(It cannot perform otherwise, and I would be glad if it does).

I don't know about statspack nor query v$sql.
I need some sample codes, please.

Thanks )

On Wed, 26 Apr 2006 16:09:28 +0200, "Eitan" <nospam (AT) nospam_please (DOT) com>
wrote:

don't get your wage for doing your work, don't we?

--
Sybrand Bakker, Senior Oracle DBA

Oh ...
Newsgroup should be the best way to learn,
if there are somewhere good people to learn from
(it can be any).
I am also myself send my answers and help peoples arround the internet's
newsgroups
for no fee.

All I want is a simple way to write on the db, via select statement + sample
code, please.

Thanks

A session can only do one thing at once, unless you thread a call to
another method that is posted when the select completes. You would
have to write your procedure as an external procedure, or better yet, a
Java stored procedure in the database that your Crytsal Report invokes
as its data source. You could also use DBM_JOBS as your thread source.
That sounds really ugly, though. Talk about re-inventing the wheel...

Why not just turn on trace? It captures the exact time statement is
run in microseconds relative to an arbitrary epoch. You can always
parse the trace file later and do the math to get the difference (and
associated run time).

Regards,

Steve

Read up on v$session_longops. Do some testing, determine what is
good/bad/ugly about it.

That's a good starting point.