RE: Question about parsing

Sorry, I think it is because it is html formated and your reader has not that
capacity. (Thats the reason it was in a follow up) I truncated the sqltext, the 31 rows where not in the response as I think the only
important point is to be sure they are identical (and I did it thoroughly) .

Trying to summarize the information there, the locked query has 1 loaded_versions,
1 open_sessions, 1 users_opening, 0 executions, 1 users_executing. 3 LOADS, 0 invalidatios, 0 parse_calls.

After trying to run the query I have an exlusive library cache pin on that session

Sybrand Bakker <postbus_at_sybrandb.demon.nl> escribió en el mensaje de noticias ovoq4ukvuc075e542cd1qrpr3gdpnams5r_at_4ax.com...
> On Tue, 22 Jan 2002 12:37:36 +0100, "Julio German Rojas Pelaez"
> <jgrp_at_tid.es> wrote:
>
> >These are the records in v_$sql.
> >SQL_TEXT is truncated. It is long. (31 rows each in V_$SQLTEXT)
> >
> >
> > SQL_TEXT SHARABLE_MEM PERSISTENT_MEM RUNTIME_MEM SORTS
LOADED_VERSIONS OPEN_VERSIONS USERS_OPENING EXECUTIONS USERS_EXECUTING LOADS FIRST_LOAD_TIME INVALIDATIONS PARSE_CALLS DISK_READS BUFFER_GETS ROWS_PROCESSED COMMAND_TYPE OPTIMIZER_MODE OPTIMIZER_COST PARSING_USER_ID PARSING_SCHEMA_ID KEPT_VERSIONS ADDRESS TYPE_CHK_HEAP HASH_VALUE CHILD_NUMBER MODULE MODULE_HASH ACTION ACTION_HASH SERIALIZABLE_ABORTS
> > select /*+ ORDERED */ 65124 1008 9648 0 1 0 0 4 0 2
2002-01-22/09:26:36 0 1 0 2 0 3 CHOOSE 7 17 17 0 81EEB098 00 868177513 0 01@ jj.sql 729151101 -265190056 0
> > select /*+ ORDERED */ 55224 868 0 0 1 1 1 0 1 3
2002-01-22/09:16:36 0 0 0 0 0 3 CHOOSE 0 17 17 0 820C3F88 82078F74 3152812833 0 0 0 0
>
> Please retry using v$sqltext_with_newlines.
> This output is unreadable
>
> Regards
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Tue Jan 22 2002 - 09:15:32 CST