Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: OEM Table Editor discrepancies

Re: OEM Table Editor discrepancies

From: Lloyd Sheen <sqlguy_at_hotmail.com>
Date: Mon, 27 Jan 2003 19:54:17 GMT
Message-ID: <J7gZ9.132587$ej1.116296@news02.bloor.is.net.cable.rogers.com>


If you are using 9i OEM or up there is a simple way to see the SQL that OEM uses. In the tools menu you can configure SQL Logging to put all SQL to a file. Easier if you want to capture just some of the SQL is to use the Application SQL History in the Navigator menu item.

Lloyd Sheen

"Paul Murphy" <pmurphy_at_scsinet.com> wrote in message news:kTzY9.8635$ZA1.2005788_at_twister.nyroc.rr.com...
> "DA Morgan" <damorgan_at_exesolutions.com> wrote in message
> news:3E32AA8C.39E4B94D_at_exesolutions.com...
> > However you seem to somehow expect Oracle to sort rows ... and it never
> ever
> > will unless you explicitly use the ORDER BY clause and specify an order.
> > Otherwise ... basic Oracle tables are heap tables ... and the data is,
by
> > definition, unordered and any tool retrieving it can retrieve it any way
> it
> > wishes.
> >
> > Daniel Morgan
> >
>
> The sorting I was talking about is if you use an ORDER BY clause in
SQL*Plus
> such as:
>
> SELECT * FROM Sherlock ORDER BY title;
>
> SQL*Plus will order all the rows by title with capital letters being
sorted
> before lowercase letters.
>
> If you are in the OEM Table Editor and click the column label button, it
> will sort by that column (just like an ORDER BY clause) except, it will
sort
> lowercase and uppercase together a=A, b=B, etc. so the rows end up in a
> different order than when you issue an ORDER BY in SQL*Plus. Whereas in
> SQL*Plus T=84 and t=116 for ordering purposes.
>
> I've been using OEM's "Show SQL" button to get to know a lot of the
> administrative SQL commands, but in this particular case, it seems like an
> OEM action is not just an underlying SQL statement. No big deal, but I
just
> thought I'd let people know, because it can make it more difficult to
> visually compare the output to find out which row is missing if you end up
> with my missing row problem.
>
> Thanks for anyone who takes the time to respond, especially about the
> missing row issue.
> -Paul Murphy
>
>
Received on Mon Jan 27 2003 - 13:54:17 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US