Database Administration (MOSC)

MOSC Banner

Understand a quey : update seg$ set type#=:4,blocks=:5,extents

edited Jun 20, 2015 10:01AM in Database Administration (MOSC) 4 commentsAnswered

Hello

In Our Production database, we have a query executed by oracle user, with  elapsed time 3260h49min37s (value of LAST_CALL_ET) , it's still running !

update seg$ set type#=:4,blocks=:5,extents=:6,minexts=:7,maxexts=:8,extsize=:9,extpct=:10,user#=:11,iniexts=:12,lists=decode(:13, 65535, NULL, :13),groups=decode(:14, 65535, NULL, :14), cachehint=:15, hwmincr=:16, spare1=DECODE(:17,0,NULL,:17),scanhint=:18, bitmapranges=:19 where ts#=:1 and file#=:2 and block#=:3

I need to understand this query, why it’s executed. The 3260h is really elapsed time!! Do we need to optimize it?

 

I use this query to find  it :

    

   SELECT   Elapsed_Time,   a.OSUSER, b.sql_text

   FROM gv$session a, gv$sqlarea b

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center