What this is?

select c.name, u.name
from con$ c, cdef$ cd, user$ u=20
where c.con# =3D cd.con# and cd.enabled =3D :1 and c.owner# =3D u.user#;

After some concern about a database running slower than desired and slower than normal, the statement that shows up as being the biggest for the number executions and buffer gets (but NOT buffer gets per execution) is above. I know that a large table is getting data inserted, and there are two unique constraints, one primary key, three foreign keys, and a few not null constraints on the table. The table has 321 million rows, and sum(bytes) from dba_segments comes back with 44,669,337,600.

I can understand how constraint validation could certainly incur some overhead on stuffing rows into this table. I can't see how the above select ties in since it appears to be a query of: gimme all the constraints where cd.enabled =3D some value. It is being executed by = SYS.
Would anyone care to speculate if the query is part of the system doing constraint validation, or might it be the result of something else ... like maybe that Embarcadero Performance Center installation that just got installed around here.

--
http://www.freelists.org/webpage/oracle-l