ECTED] Subject: Re: 2 small tables - Query
takes 3 hours
If you have been a DBA for 7 years, then you know the procedure:
Go to V$SESSION_WAIT and see what are you waiting for. You'll get file
and block (P1 & P2), so you can locate the segment. Do explain plan and
see how this segment is used. In my experience, it's usually an index used to
retrieve the
Sam
Well, sometimes ya just gotta tell the vendor NO. I would start by
explaining to the people in your organization and the vendor why this is a
very bad idea, totally unsupported by Oracle. If due to the local politics
this isn't feasible, make sure you keep this application on its own
instanc
This view is part of the upgrade script provided by the Vendor
(duh):
I've been DBA'ing for 7 years in DB2 and Oracle and messing
around with a SYS view is obviously not done- .
I was looking for some proper advise as Ive never seen anything
like it before.
Sam
- Original Message
People should not play with the SYS schema, period. No ifs, no buts,
it just isn't done. You are on your own, pal. If I were your employer,
you would have hit the road by now. Whatever application that Maximo
thing is, creating objects owned by SYS is simply not acceptable.
It's guys like you that
Unix Solaris 8 and Oracle 8.1.7.4
As part of an upgrade to the Maximo application I run a join on 2
tables:
select count(*) from sys.syskeys s, maxsysindexes m where
s.ixname=m.name;
sys.syskeys is 705 rows and maxsysindexes is 443 rows.
when I trace the statement I find it doing a hash join a
