Oracle internals, debugging and undocumented features

DBA_JOBS_RUNNING definition still not corrected for RAC 11g

Just found this one  and since I do not trust until I see it..

Here is Bug description.Only affects RAC…

There will be no output when queried for information on same job from other RAC instances. This is because the view definition makes use of v$lock information in joins and not the gv$lock.

According to Oracle this is Bug and should be fixed in 11g but it is NOT.

SQL> set long 1000
SQL> select * from v$version;

Oracle Database 11g Enterprise Edition Release – 64bit Production
PL/SQL Release – Production
CORE      Production
TNS for Linux: Version – Production
NLSRTL Version – Production

SQL> select text from dba_views where view_name=’DBA_JOBS_RUNNING’;

select v.SID, v.id2 JOB, j.FAILURES,
    LAST_DATE, substr(to_char(last_date,’HH24:MI:SS’),1,8) LAST_SEC,
    THIS_DATE, substr(to_char(this_date,’HH24:MI:SS’),1,8) THIS_SEC,
    j.field1 INSTANCE
  from sys.job$ j, v$lock v
  where v.type = ‘JQ’ and j.job (+)= v.id2

The v$lock is still there.So if you running RAC redefine it yourself and DO NOT WAIT FOR ORACLE ( See previous post ).

Details Metalink Note: 357564.1


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: