Re: OEM Table Editor discrepancies

From: Niall Litchfield <niall.litchfield_at_dial.pipex.com>
Date: Sun, 26 Jan 2003 21:36:19 -0000
Message-ID: <3e3454d1$0$232$cc9e4d1f@news.dial.pipex.com>

"Paul Murphy" <pmurphy_at_scsinet.com> wrote in message news:kTzY9.8635$ZA1.2005788_at_twister.nyroc.rr.com...
> Thanks for anyone who takes the time to respond, especially about the
> missing row issue.

I'd fire up one session using oem, then grab the sid and serial# of that session in a second session using sqlplus and trace it. perform your table editor stuff and then kill off the session. you should end up with all the oem sql in a trace file. IIRC an awful lot of it comes in the form

select /* OEM */ .... etc anyway.

You could also create a second table with x rows in it and see if table editor sees x or x-1 rows.

--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************

Received on Sun Jan 26 2003 - 15:36:19 CST