Difference between output of DBA_SEGMENTS,DBA_OBJECTS & DBA_TABLES.

Hi All,
I am a newbie to Oracle, was checking total no. of tables present in the DB, but got little confused now.
I tried querying DBA_SEGMENTS, DBA_OBJECTS and DBA_TABLES but got different outputs.
SQL> select object_type,count(1) from dba_objects where OBJECT_TYPE='TABLE' group by object_type;
OBJECT_TYPE                     COUNT(*)
TABLE                               2437
SQL> select segment_type,count(1) from dba_segments where segment_type='TABLE' group by segment_type;
SEGMENT_TYPE                   COUNT(*)
TABLE                         1631
If a table is a partitioned one, then each partition will be considered as a different segment hence I checked for table partition also.
SQL> select segment_type,count(*) from dba_segments where segment_type like 'TABLE_%' group by segment_type;
SEGMENT_TYPE         COUNT(*)
TABLE SUBPARTITION         32
TABLE PARTITION           215
still the addition of above two does not give (32+215+1631=1878), i.e., not 2437
Then tried querying DBA_TABLES:
SQL> select count(1) from dba_tables;
COUNT(1)
      2417
could you please help me to understand difference between these three and which one is the correct answer ?

Prior to 11.2.0.3, Indexes on LOB columns are not included under DBA_OBJECTS, Whereas From 11.2.0.3 there is a change in which indexes on LOB columns are now included in DBA_OBJECTS.
DBA_TABLES VS DBA_SEGMENTS
DBA_TABLES includes CLUSTERED TABLES, TEMPORARY, PARTITIONED, and INDEX ORGANIZED tables that are not included in DBA_SEGMENTS as they have no storage allocations
DBA_SEGMENTS contains TYPED (for internal use only) tables ( bitand(TAB$.property, 1) = 0 ) that are not included in DBA_TABLES
DBA_TABLES VS DBA_OBJECTS
DBA_TABLES includes the internal table _default_auditing_options_ that is not included in DBA_OBJECTS
DBA_OBJECTS include TYPED (for internal use only) tables ( bitand(TAB$.property, 1) = 0 ) that are not included in DBA_TABLES
DBA_SEGMENTS VS DBA_OBJECTS
DBA_SEGMENTS includes the internal table _default_auditing_options_ that is not included in DBA_OBJECTS
DBA_OBJECTS include CLUSTERED TABLES, TEMPORARY, PARTITIONED, and INDEX ORGANIZED tables that are not included in DBA_SEGMENTS as they have no storage allocations
If you have access to My Oracle Support, Please check Note 363048.1 : WHY DO DBA_TABLES DBA_OBJECTS AND DBA_SEGMENTS DIFFER WHEN SELECTED FOR TABLES?
Regards,
Suntrupth

Similar Messages

Difference between "output type" and "output medium" in interface

Can comebody kindly tell me the difference between "output type" and "output medium" with respect to interface?
Thanks,
Max

Hi,
Output medium means , how you wants to see the output like
Printout, Fax, Mail, or EDI output etc
Output type/Condition Type means for every Application document an Output type is create for the Output Message determination, this is linked with the Condition records, Medium, Program and the Output Script or smartform.
reward points if useful
regards,
ANJI

What is the difference between Output and Master?

I try to understand what the difference is between Master and Output 1-2. In Garageband there was only a Master track. Does the Master volume slider has an effect on the bounce? I don't see a bounce option in the Master slider like in the output 1-2 slider.

The Output 1-2 is a real output channel that audio passes through, corresponding to your audio interface outputs, and where you can insert plugins and bounce from.
The master channel is simply a volume fader that adjusts the levels of all output channels at once - mostly only useful for surround sound.

Difference between HP LaserJet and XPS HP LaserJet

Greetings, after insatling all printer software including XPS driver I can see two virtual printers for my physical device - HP LaserJet Pro and XPS HP LaserJet Pro.
I printed same page via both virtual printers and can't find any visible difference between outputs. Wanted to know what's the difference between these two virtual printers (if any) and which is recommended to use (if that's multivalent then which printer to use for which job)

Bucky_ Kid,
First, what LaserJet Pro device are you using?
Second, the XPS driver is a Microsoft print driver. The HP laserjet driver will either be a full solution driver (PCL 5 or 6 depending on which what device you are us have). Again, depending on the device, there is also a driver only option available.
It is usually always recommended to go with the HP Laserjet driver as you will have more functionality and options.
I am an HP employee.
Say Thanks by clicking the Kudos Star in the post that helped you.
Please mark the post that solves your problem as Accepted Solution

Why a difference between picture quality in InDesign and PDF output

We are comparing the CS5 pdf output of our book with the ID version. The images are MUCH clearer and the colors are better when we view a page inside of ID side by side with the PDF. The pictures actually look blurry in the PDF, even though we are outputting at 600dpi.When we export to PDF in cs6, the clarity is much better but the color is still a little off. Is this normal?

The X-1a exporting from CS5 looks much better than the normal output, and better than the CS6 output. What would cause that?
If you export a CMYK PDF with no profiles and open it in AcrobatPro, Acrobat's Color Management's Working CMYK space handles the preview. So here's the difference between two very different profiles Fogra Coated and SNAP Newsprint:
When you export PDF/X-1a an output intent profile is included (usually your document's CMYK profile) and that is used in Acrobat for previewing CMYK instead of the current CMYK working space.

Difference between execution mode of Print preview and Print for Output

Hello,
Can anybody tell the difference between execution mode of print preview and print for an output (For eg. PO output or Invoice)?. I am trying to download some documents linked to Purchase order to desktop. The code is written in the same driver program for printing PO and it is executed after smartform function module is called. It works fine in print preview mode and it fails in print mode. The reason why download fails in print mode is that GUI not available (just found from debugging).
Any ideas?
Thanks
Anil

HI
try using any other printer and find out if you are getting the correct output. The printer needs to support Multiple Unicode encoding schemes like UTF 8, UTF 16BE, and UTF 16LE, plus special characters and logos, bi-directional text layout, and custom characters..

Difference between ALC Forms ES module and ALC Output ES module

Hi,
I would like to know if anyone has implemented just the Adobe Output ES module in any of the projects.
I am into a project where we are integrating ALC with one of the insurance application for document generation and correspondence generation.
Confused whether to go with Forms ES module, Output ES module or both?
Can someone please throw light on these modules? I know there is info on the website but would like to know the advantages and disadvnantages of using either one of the module or both?
If just Output module is used how will the insurance application interact with ALC?

Jianghuai,
The link you have gotten from Ivan provides great information sources.
Note that those are not four different distributions, meaning linux-based operating systems, all are RHEL -- check out the FAQ, items 1 and 2. I would say main differences between family members are licensing and support offerings or subscriptions. AS, ES for "server" and WS, Desktop for the "desktop".
"ES is licensed for servers with up to 2 CPUs and 16GB of main memory while AS is licensed for servers of any size and any architecture."
Oracle products are generally not supported on the desktop variants.

Whats difference between dba_segments in 10g and 11.2

Hi Everyone,
The Space related Queries on DBA_SEGMENTS on 10g is running for more than 10 minutes and the same queries running within 2 seconds 11.2 for same database..
Please some one can explain the differences between 10g and 11.2 on this and is there any improvements in LMT tablespaces in 11.2 because this is issue related to LMT.
Thanks
Vijay

*10.2.0.4*
SQL> explain plan for
2 select owner owner, segment_name segment, a.tablespace_name name, a.next_extent next_extent, a.next_extent/1024/1024 MB, sum(floor(b.bytes/a.next_extent)) avail_extents from dba_SEGMENTS a, dba_FREE_SPACE b where a.tablespace_name = b.tablespace_name   and a.next_extent>0 group by owner, segment_name,a.tablespace_name, a.next_extent having sum(floor(b.bytes/a.next_extent)) < 8 order by 3,6;
Explained.
Elapsed: 00:00:00.45
SQL> select * from table(dbms_xplan.display());
PLAN_TABLE_OUTPUT
Plan hash value: 3420003334
| Id | Operation                           | Name             | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                    |                  |    42 | 4998 | 20360 (91)| 00:03:37 |
|   1 | SORT ORDER BY                      |                  |    42 | 4998 | 20360 (91)| 00:03:37 |
|* 2 |   FILTER                            |                  |       |       |            |          |
|   3 |    HASH GROUP BY                    |                  |    42 | 4998 | 20360 (91)| 00:03:37 |
|* 4 |     HASH JOIN                       |                  |    42 | 4998 | 20358 (91)| 00:03:37 |
|   5 |      VIEW                           | SYS_DBA_SEGS     |     3 |   267 | 1520   (1)| 00:00:17 |
|   6 |       UNION-ALL                     |                  |       |       |            |          |
|   7 |        NESTED LOOPS OUTER           |                  |     1 |   291 | 1322   (1)| 00:00:15 |
|   8 |         NESTED LOOPS                |                  |     1 |   261 | 1321   (1)| 00:00:15 |
|   9 |          NESTED LOOPS               |                  |     1 |   205 | 1320   (1)| 00:00:15 |
|* 10 |           HASH JOIN                 |                  |     4 |   596 | 1319   (1)| 00:00:15 |
| 11 |            NESTED LOOPS             |                  |    19 | 1729 |   156   (0)| 00:00:02 |
| 12 |             TABLE ACCESS FULL       | FILE$            |    77 | 2002 |     2   (0)| 00:00:01 |
| 13 |             TABLE ACCESS CLUSTER    | SEG$             |     1 |    65 |     2   (0)| 00:00:01 |
|* 14 |              INDEX RANGE SCAN       | I_FILE#_BLOCK#   |    15 |       |     1   (0)| 00:00:01 |
| 15 |            VIEW                     | SYS_OBJECTS      | 30274 | 1714K| 1162   (1)| 00:00:13 |
| 16 |             UNION-ALL               |                  |       |       |            |          |
|* 17 |              TABLE ACCESS FULL      | TAB$             | 3109 |   197K|   272   (1)| 00:00:03 |
| 18 |              TABLE ACCESS FULL      | TABPART$         |   354 | 18408 |     3   (0)| 00:00:01 |
| 19 |              TABLE ACCESS FULL      | CLU$             |    65 | 3380 |   272   (1)| 00:00:03 |
|* 20 |              TABLE ACCESS FULL      | IND$             | 7364 |   467K|   272   (1)| 00:00:03 |
| 21 |              TABLE ACCESS FULL      | INDPART$         |   970 | 50440 |     5   (0)| 00:00:01 |
|* 22 |              TABLE ACCESS FULL      | LOB$             | 1997 |   126K|   272   (1)| 00:00:03 |
| 23 |              TABLE ACCESS FULL      | TABSUBPART$      | 1000 | 52000 |     6   (0)| 00:00:01 |
| 24 |              TABLE ACCESS FULL      | INDSUBPART$      | 15382 |   781K|    58   (2)| 00:00:01 |
| 25 |              TABLE ACCESS FULL      | LOBFRAG$         |    33 | 1782 |     2   (0)| 00:00:01 |
|* 26 |           TABLE ACCESS CLUSTER      | TS$              |     1 |    56 |     1   (0)| 00:00:01 |
|* 27 |            INDEX UNIQUE SCAN        | I_TS#            |     1 |       |     0   (0)| 00:00:01 |
|* 28 |          TABLE ACCESS BY INDEX ROWID| OBJ$             |     1 |    56 |     1   (0)| 00:00:01 |
|* 29 |           INDEX UNIQUE SCAN         | I_OBJ1           |     1 |       |     0   (0)| 00:00:01 |
| 30 |         TABLE ACCESS CLUSTER        | USER$            |     1 |    30 |     1   (0)| 00:00:01 |
|* 31 |          INDEX UNIQUE SCAN          | I_USER#          |     1 |       |     0   (0)| 00:00:01 |
| 32 |        NESTED LOOPS                 |                  |     1 |   246 |    75   (0)| 00:00:01 |
| 33 |         NESTED LOOPS OUTER          |                  |     1 |   203 |    74   (0)| 00:00:01 |
| 34 |          NESTED LOOPS               |                  |     1 |   173 |    73   (0)| 00:00:01 |
| 35 |           NESTED LOOPS              |                  |    71 | 6745 |     2   (0)| 00:00:01 |
|* 36 |            TABLE ACCESS FULL        | UNDO$            |    76 | 5244 |     2   (0)| 00:00:01 |
|* 37 |            INDEX UNIQUE SCAN        | I_FILE2          |     1 |    26 |     0   (0)| 00:00:01 |
|* 38 |           TABLE ACCESS CLUSTER      | SEG$             |     1 |    78 |     1   (0)| 00:00:01 |
|* 39 |            INDEX UNIQUE SCAN        | I_FILE#_BLOCK#   |     1 |       |     0   (0)| 00:00:01 |
| 40 |          TABLE ACCESS CLUSTER       | USER$            |     1 |    30 |     1   (0)| 00:00:01 |
|* 41 |           INDEX UNIQUE SCAN         | I_USER#          |     1 |       |     0   (0)| 00:00:01 |
|* 42 |         TABLE ACCESS CLUSTER        | TS$              |     1 |    43 |     1   (0)| 00:00:01 |
|* 43 |          INDEX UNIQUE SCAN          | I_TS#            |     1 |       |     0   (0)| 00:00:01 |
| 44 |        NESTED LOOPS                 |                  |     1 |   203 |   123   (0)| 00:00:02 |
| 45 |         NESTED LOOPS OUTER          |                  |     1 |   147 |   122   (0)| 00:00:02 |
| 46 |          NESTED LOOPS               |                  |     1 |   117 |   121   (0)| 00:00:02 |
| 47 |           TABLE ACCESS FULL         | FILE$            |    77 | 3003 |     2   (0)| 00:00:01 |
|* 48 |           TABLE ACCESS CLUSTER      | SEG$             |     1 |    78 |     2   (0)| 00:00:01 |
|* 49 |            INDEX RANGE SCAN         | I_FILE#_BLOCK#   |    15 |       |     1   (0)| 00:00:01 |
| 50 |          TABLE ACCESS CLUSTER       | USER$            |     1 |    30 |     1   (0)| 00:00:01 |
|* 51 |           INDEX UNIQUE SCAN         | I_USER#          |     1 |       |     0   (0)| 00:00:01 |
|* 52 |         TABLE ACCESS CLUSTER        | TS$              |     1 |    56 |     1   (0)| 00:00:01 |
|* 53 |          INDEX UNIQUE SCAN          | I_TS#            |     1 |       |     0   (0)| 00:00:01 |
| 54 |      VIEW                           | DBA_FREE_SPACE   | 1393 | 41790 | 18837 (99)| 00:03:21 |
| 55 |       UNION-ALL                     |                  |       |       |            |          |
| 56 |        NESTED LOOPS                 |                  |     1 |   121 |    11   (0)| 00:00:01 |
| 57 |         NESTED LOOPS                |                  |     1 |    65 |    10   (0)| 00:00:01 |
| 58 |          TABLE ACCESS FULL          | FET$             |     1 |    39 |    10   (0)| 00:00:01 |
|* 59 |          INDEX UNIQUE SCAN          | I_FILE2          |     1 |    26 |     0   (0)| 00:00:01 |
|* 60 |         TABLE ACCESS CLUSTER        | TS$              |     1 |    56 |     1   (0)| 00:00:01 |
| 61 |        NESTED LOOPS                 |                  | 1377 |   158K|    58 (83)| 00:00:01 |
| 62 |         NESTED LOOPS                |                  | 72400 | 6504K|    41 (76)| 00:00:01 |
|* 63 |          TABLE ACCESS FULL          | TS$              |    54 | 4428 |    10   (0)| 00:00:01 |
|* 64 |          FIXED TABLE FIXED INDEX    | X$KTFBFE (ind:1) | 1342 | 13420 |     1 (100)| 00:00:01 |
|* 65 |         INDEX UNIQUE SCAN           | I_FILE2          |     1 |    26 |     0   (0)| 00:00:01 |
| 66 |        NESTED LOOPS                 |                  |    14 | 2324 | 18498 (100)| 00:03:18 |
| 67 |         NESTED LOOPS                |                  |   640 | 89600 | 18498 (100)| 00:03:18 |
|* 68 |          HASH JOIN                  |                  |   640 | 77440 |    59   (2)| 00:00:01 |
| 69 |           TABLE ACCESS FULL         | RECYCLEBIN$      |   651 | 25389 |    48   (0)| 00:00:01 |
|* 70 |           TABLE ACCESS FULL         | TS$              |    54 | 4428 |    10   (0)| 00:00:01 |
|* 71 |          FIXED TABLE FIXED INDEX    | X$KTFBUE (ind:1) |     1 |    19 |    29 (100)| 00:00:01 |
|* 72 |         INDEX UNIQUE SCAN           | I_FILE2          |     1 |    26 |     0   (0)| 00:00:01 |
|* 73 |        HASH JOIN                    |                  |     1 |   173 |   270   (1)| 00:00:03 |
| 74 |         NESTED LOOPS                |                  |     1 |   134 |   221   (1)| 00:00:03 |
| 75 |          NESTED LOOPS               |                  |     1 |    78 |   220   (1)| 00:00:03 |
| 76 |           TABLE ACCESS FULL         | UET$             |     1 |    52 |   220   (1)| 00:00:03 |
|* 77 |           INDEX UNIQUE SCAN         | I_FILE2          |     1 |    26 |     0   (0)| 00:00:01 |
|* 78 |          TABLE ACCESS CLUSTER       | TS$              |     1 |    56 |     1   (0)| 00:00:01 |
|* 79 |           INDEX UNIQUE SCAN         | I_TS#            |     1 |       |     0   (0)| 00:00:01 |
| 80 |         TABLE ACCESS FULL           | RECYCLEBIN$      |   651 | 25389 |    48   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   2 - filter(SUM(FLOOR("B"."BYTES"/"NEXT_EXTENT"))<8)
   4 - access("TABLESPACE_NAME"="B"."TABLESPACE_NAME")
10 - access("S"."FILE#"="SO"."HEADER_FILE" AND "S"."BLOCK#"="SO"."HEADER_BLOCK" AND
              "S"."TS#"="SO"."TS_NUMBER" AND "S"."TYPE#"="SO"."SEGMENT_TYPE_ID")
14 - access("S"."TS#"="F"."TS#" AND "S"."FILE#"="F"."RELFILE#")
17 - filter(BITAND("T"."PROPERTY",1024)=0)
20 - filter("I"."TYPE#"=1 OR "I"."TYPE#"=2 OR "I"."TYPE#"=3 OR "I"."TYPE#"=4 OR "I"."TYPE#"=6
              OR "I"."TYPE#"=7 OR "I"."TYPE#"=8 OR "I"."TYPE#"=9)
22 - filter(BITAND("L"."PROPERTY",64)=0 OR BITAND("L"."PROPERTY",128)=128)
26 - filter(DECODE(BITAND("TS"."FLAGS",3),1,TO_NUMBER(NULL),"S"."EXTSIZE"*"TS"."BLOCKSIZE")>0)
27 - access("S"."TS#"="TS"."TS#")
28 - filter("O"."TYPE#"="SO"."OBJECT_TYPE_ID")
29 - access("O"."OBJ#"="SO"."OBJECT_ID")
31 - access("O"."OWNER#"="U"."USER#"(+))
36 - filter("UN"."STATUS$"<>1)
37 - access("UN"."TS#"="F"."TS#" AND "UN"."FILE#"="F"."RELFILE#")
38 - filter("S"."TYPE#"=1 OR "S"."TYPE#"=10)
39 - access("S"."TS#"="UN"."TS#" AND "S"."FILE#"="UN"."FILE#" AND "S"."BLOCK#"="UN"."BLOCK#")
41 - access("S"."USER#"="U"."USER#"(+))
42 - filter("S"."EXTSIZE"*"TS"."BLOCKSIZE">0)
43 - access("S"."TS#"="TS"."TS#")
48 - filter("S"."TYPE#"<>1 AND "S"."TYPE#"<>5 AND "S"."TYPE#"<>6 AND "S"."TYPE#"<>8 AND
              "S"."TYPE#"<>10)
49 - access("S"."TS#"="F"."TS#" AND "S"."FILE#"="F"."RELFILE#")
51 - access("S"."USER#"="U"."USER#"(+))
52 - filter(DECODE(BITAND("TS"."FLAGS",3),1,TO_NUMBER(NULL),"S"."EXTSIZE"*"TS"."BLOCKSIZE")>0)
53 - access("S"."TS#"="TS"."TS#")
59 - access("F"."TS#"="FI"."TS#" AND "F"."FILE#"="FI"."RELFILE#")
60 - filter("TS"."BITMAPPED"=0 AND "TS"."TS#"="F"."TS#")
63 - filter(("TS"."ONLINE$"=1 OR "TS"."ONLINE$"=4) AND "TS"."CONTENTS$"=0 AND
              "TS"."BITMAPPED"<>0)
64 - filter("TS"."TS#"="F"."KTFBFETSN")
65 - access("F"."KTFBFETSN"="FI"."TS#" AND "F"."KTFBFEFNO"="FI"."RELFILE#")
68 - access("TS"."TS#"="RB"."TS#")
70 - filter(("TS"."ONLINE$"=1 OR "TS"."ONLINE$"=4) AND "TS"."CONTENTS$"=0 AND
              "TS"."BITMAPPED"<>0)
71 - filter("U"."KTFBUESEGTSN"="RB"."TS#" AND "U"."KTFBUESEGFNO"="RB"."FILE#" AND
              "U"."KTFBUESEGBNO"="RB"."BLOCK#")
72 - access("RB"."TS#"="FI"."TS#" AND "U"."KTFBUEFNO"="FI"."RELFILE#")
73 - access("U"."TS#"="RB"."TS#" AND "U"."SEGFILE#"="RB"."FILE#" AND
              "U"."SEGBLOCK#"="RB"."BLOCK#")
77 - access("U"."TS#"="FI"."TS#" AND "U"."SEGFILE#"="FI"."RELFILE#")
78 - filter("TS"."BITMAPPED"=0)
79 - access("TS"."TS#"="U"."TS#")
11.2
SQL> explain plan for
2   select owner owner, segment_name segment, a.tablespace_name name, a.next_extent next_extent, a.next_extent/1024/1024 MB, sum(floor(b.bytes/a.next_extent)) avail_extents from dba_SEGMENTS a, dba_FREE_SPACE b where a.tablespace_name = b.tablespace_name   and a.next_extent>0 group by owner, segment_name,a.tablespace_name, a.next_extent having sum(floor(b.bytes/a.next_extent)) < 8 order by 3,6;
Explained.
SQL> select * from table(dbms_xplan.display());
PLAN_TABLE_OUTPUT
Plan hash value: 1346760999
| Id | Operation                            | Name             | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                     |                  |     3 |   333 | 1481   (1)| 00:00:27 |
|   1 | SORT ORDER BY                       |                  |     3 |   333 | 1481   (1)| 00:00:27 |
|* 2 |   FILTER                             |                  |       |       |            |          |
|   3 |    HASH GROUP BY                     |                  |     3 |   333 | 1481   (1)| 00:00:27 |
|* 4 |     HASH JOIN                        |                  | 8243 |   893K| 1479   (1)| 00:00:27 |
|   5 |      VIEW                            | DBA_FREE_SPACE   |   101 | 2626 |    55 (11)| 00:00:01 |
|   6 |       UNION-ALL                      |                  |       |       |            |          |
|   7 |        NESTED LOOPS                  |                  |     1 |    69 |     7   (0)| 00:00:01 |
|   8 |         NESTED LOOPS                 |                  |     1 |    45 |     6   (0)| 00:00:01 |
|   9 |          TABLE ACCESS FULL           | FET$             |     1 |    39 |     6   (0)| 00:00:01 |
|* 10 |          INDEX UNIQUE SCAN           | I_FILE2          |     1 |     6 |     0   (0)| 00:00:01 |
|* 11 |         TABLE ACCESS CLUSTER         | TS$              |     1 |    24 |     1   (0)| 00:00:01 |
| 12 |        NESTED LOOPS                  |                  |    98 | 7350 |    33   (0)| 00:00:01 |
| 13 |         NESTED LOOPS                 |                  |    98 | 6762 |    33   (0)| 00:00:01 |
|* 14 |          TABLE ACCESS FULL           | TS$              |    59 | 1770 |    33   (0)| 00:00:01 |
|* 15 |          FIXED TABLE FIXED INDEX     | X$KTFBFE (ind:1) |     2 |    78 |     0   (0)| 00:00:01 |
|* 16 |         INDEX UNIQUE SCAN            | I_FILE2          |     1 |     6 |     0   (0)| 00:00:01 |
| 17 |        NESTED LOOPS                  |                  |     1 |   140 |    10 (60)| 00:00:01 |
| 18 |         NESTED LOOPS                 |                  |     1 |   134 |    10 (60)| 00:00:01 |
| 19 |          NESTED LOOPS                |                  |     1 |    69 |     4   (0)| 00:00:01 |
| 20 |           TABLE ACCESS FULL          | RECYCLEBIN$      |     1 |    39 |     3   (0)| 00:00:01 |
|* 21 |           TABLE ACCESS CLUSTER       | TS$              |     1 |    30 |     1   (0)| 00:00:01 |
|* 22 |            INDEX UNIQUE SCAN         | I_TS#            |     1 |       |     0   (0)| 00:00:01 |
|* 23 |          FIXED TABLE FIXED INDEX     | X$KTFBUE (ind:1) |   100K| 6347K|     6 (100)| 00:00:01 |
|* 24 |         INDEX UNIQUE SCAN            | I_FILE2          |     1 |     6 |     0   (0)| 00:00:01 |
| 25 |        NESTED LOOPS                  |                  |     1 |   121 |     5   (0)| 00:00:01 |
| 26 |         NESTED LOOPS                 |                  |     1 |    97 |     4   (0)| 00:00:01 |
| 27 |          MERGE JOIN CARTESIAN        |                  |     1 |    45 |     4   (0)| 00:00:01 |
| 28 |           TABLE ACCESS FULL          | RECYCLEBIN$      |     1 |    39 |     3   (0)| 00:00:01 |
| 29 |           BUFFER SORT                |                  |    78 |   468 |     1   (0)| 00:00:01 |
| 30 |            INDEX FULL SCAN           | I_FILE2          |    78 |   468 |     1   (0)| 00:00:01 |
| 31 |          TABLE ACCESS CLUSTER        | UET$             |     1 |    52 |     0   (0)| 00:00:01 |
|* 32 |           INDEX UNIQUE SCAN          | I_FILE#_BLOCK#   |     1 |       |     0   (0)| 00:00:01 |
|* 33 |         TABLE ACCESS CLUSTER         | TS$              |     1 |    24 |     1   (0)| 00:00:01 |
|* 34 |          INDEX UNIQUE SCAN           | I_TS#            |     1 |       |     0   (0)| 00:00:01 |
| 35 |      VIEW                            | SYS_DBA_SEGS     | 4897 |   406K| 1423   (1)| 00:00:26 |
| 36 |       UNION-ALL                      |                  |       |       |            |          |
| 37 |        NESTED LOOPS OUTER            |                  |     1 |   158 | 1128   (1)| 00:00:21 |
| 38 |         NESTED LOOPS                 |                  |     1 |   141 | 1127   (1)| 00:00:21 |
| 39 |          NESTED LOOPS                |                  |     1 |   120 | 1126   (1)| 00:00:21 |
|* 40 |           HASH JOIN                  |                  |     3 |   246 | 1120   (1)| 00:00:21 |
| 41 |            NESTED LOOPS              |                  | 36056 |   845K|   122   (0)| 00:00:03 |
| 42 |             INDEX FULL SCAN          | I_FILE2          |    78 |   468 |     1   (0)| 00:00:01 |
| 43 |             TABLE ACCESS CLUSTER     | SEG$             |   462 | 8316 |     2   (0)| 00:00:01 |
|* 44 |              INDEX RANGE SCAN        | I_FILE#_BLOCK#   |     1 |       |     1   (0)| 00:00:01 |
| 45 |            VIEW                      | SYS_OBJECTS      | 39147 | 2217K|   997   (1)| 00:00:18 |
| 46 |             UNION-ALL                |                  |       |       |            |          |
|* 47 |              TABLE ACCESS FULL       | TAB$             | 4543 |   102K|   237   (0)| 00:00:05 |
| 48 |              TABLE ACCESS FULL       | TABPART$         |   424 | 6784 |     4   (0)| 00:00:01 |
| 49 |              TABLE ACCESS FULL       | CLU$             |    10 |   140 |   237   (0)| 00:00:05 |
|* 50 |              TABLE ACCESS FULL       | IND$             | 11060 |   205K|   237   (0)| 00:00:05 |
| 51 |              TABLE ACCESS FULL       | INDPART$         |   587 | 9392 |     5   (0)| 00:00:01 |
|* 52 |              TABLE ACCESS FULL       | LOB$             |   938 | 17822 |   234   (0)| 00:00:05 |
| 53 |              TABLE ACCESS FULL       | TABSUBPART$      |   968 | 15488 |     5   (0)| 00:00:01 |
| 54 |              TABLE ACCESS FULL       | INDSUBPART$      | 20616 |   322K|    33   (0)| 00:00:01 |
| 55 |              TABLE ACCESS FULL       | LOBFRAG$         |     1 |    17 |     3   (0)| 00:00:01 |
| 56 |           TABLE ACCESS BY INDEX ROWID| OBJ$             |     1 |    38 |     2   (0)| 00:00:01 |
|* 57 |            INDEX RANGE SCAN          | I_OBJ1           |     1 |       |     1   (0)| 00:00:01 |
|* 58 |          TABLE ACCESS CLUSTER        | TS$              |     1 |    21 |     1   (0)| 00:00:01 |
|* 59 |           INDEX UNIQUE SCAN          | I_TS#            |     1 |       |     0   (0)| 00:00:01 |
| 60 |         TABLE ACCESS CLUSTER         | USER$            |     1 |    17 |     1   (0)| 00:00:01 |
|* 61 |          INDEX UNIQUE SCAN           | I_USER#          |     1 |       |     0   (0)| 00:00:01 |
|* 62 |        HASH JOIN OUTER               |                  |    21 | 2121 |   133   (1)| 00:00:03 |
| 63 |         NESTED LOOPS                 |                  |    21 | 1764 |   128   (0)| 00:00:03 |
| 64 |          NESTED LOOPS                |                  |    21 | 1323 |   107   (0)| 00:00:02 |
| 65 |           NESTED LOOPS               |                  |    21 | 1197 |   107   (0)| 00:00:02 |
|* 66 |            TABLE ACCESS FULL         | UNDO$            |   104 | 3640 |     3   (0)| 00:00:01 |
|* 67 |            TABLE ACCESS CLUSTER      | SEG$             |     1 |    22 |     1   (0)| 00:00:01 |
|* 68 |             INDEX UNIQUE SCAN        | I_FILE#_BLOCK#   |     1 |       |     0   (0)| 00:00:01 |
|* 69 |           INDEX UNIQUE SCAN          | I_FILE2          |     1 |     6 |     0   (0)| 00:00:01 |
|* 70 |          TABLE ACCESS CLUSTER        | TS$              |     1 |    21 |     1   (0)| 00:00:01 |
|* 71 |           INDEX UNIQUE SCAN          | I_TS#            |     1 |       |     0   (0)| 00:00:01 |
| 72 |         TABLE ACCESS FULL            | USER$            |   111 | 1887 |     4   (0)| 00:00:01 |
|* 73 |        HASH JOIN RIGHT OUTER         |                  | 4875 |   328K|   162   (1)| 00:00:03 |
| 74 |         TABLE ACCESS FULL            | USER$            |   111 | 1887 |     4   (0)| 00:00:01 |
|* 75 |         HASH JOIN                    |                  | 4875 |   247K|   158   (1)| 00:00:03 |
| 76 |          TABLE ACCESS FULL           | TS$              |    60 | 1260 |    33   (0)| 00:00:01 |
| 77 |          NESTED LOOPS                |                  | 4875 |   147K|   124   (0)| 00:00:03 |
| 78 |           TABLE ACCESS FULL          | FILE$            |    78 |   702 |     3   (0)| 00:00:01 |
|* 79 |           TABLE ACCESS CLUSTER       | SEG$             |    62 | 1364 |     2   (0)| 00:00:01 |
|* 80 |            INDEX RANGE SCAN          | I_FILE#_BLOCK#   |     1 |       |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   2 - filter(SUM(FLOOR("B"."BYTES"/"NEXT_EXTENT"))<8)
   4 - access("TABLESPACE_NAME"="B"."TABLESPACE_NAME")
10 - access("F"."TS#"="FI"."TS#" AND "F"."FILE#"="FI"."RELFILE#")
11 - filter("TS"."BITMAPPED"=0 AND "TS"."TS#"="F"."TS#")
14 - filter("TS"."CONTENTS$"=0 AND "TS"."BITMAPPED"<>0 AND ("TS"."ONLINE$"=1 OR
              "TS"."ONLINE$"=4))
15 - filter("TS"."TS#"="F"."KTFBFETSN")
16 - access("F"."KTFBFETSN"="FI"."TS#" AND "F"."KTFBFEFNO"="FI"."RELFILE#")
21 - filter("TS"."CONTENTS$"=0 AND "TS"."BITMAPPED"<>0 AND ("TS"."ONLINE$"=1 OR
              "TS"."ONLINE$"=4))
22 - access("TS"."TS#"="RB"."TS#")
23 - filter("U"."KTFBUESEGTSN"="RB"."TS#" AND "U"."KTFBUESEGFNO"="RB"."FILE#" AND
              "U"."KTFBUESEGBNO"="RB"."BLOCK#")
24 - access("RB"."TS#"="FI"."TS#" AND "U"."KTFBUEFNO"="FI"."RELFILE#")
32 - access("U"."TS#"="RB"."TS#" AND "U"."SEGFILE#"="RB"."FILE#" AND
              "U"."SEGBLOCK#"="RB"."BLOCK#")
       filter("U"."TS#"="FI"."TS#" AND "U"."SEGFILE#"="FI"."RELFILE#")
33 - filter("TS"."BITMAPPED"=0)
34 - access("TS"."TS#"="U"."TS#")
40 - access("S"."FILE#"="SO"."HEADER_FILE" AND "S"."BLOCK#"="SO"."HEADER_BLOCK" AND
              "S"."TS#"="SO"."TS_NUMBER" AND "S"."TYPE#"="SO"."SEGMENT_TYPE_ID")
44 - access("S"."TS#"="F"."TS#" AND "S"."FILE#"="F"."RELFILE#")
47 - filter(BITAND("T"."PROPERTY",1024)=0)
50 - filter("I"."TYPE#"=1 OR "I"."TYPE#"=2 OR "I"."TYPE#"=3 OR "I"."TYPE#"=4 OR "I"."TYPE#"=6
              OR "I"."TYPE#"=7 OR "I"."TYPE#"=8 OR "I"."TYPE#"=9)
52 - filter(BITAND("L"."PROPERTY",64)=0 OR BITAND("L"."PROPERTY",128)=128)
57 - access("O"."OBJ#"="SO"."OBJECT_ID" AND "O"."TYPE#"="SO"."OBJECT_TYPE_ID")
       filter("O"."TYPE#"="SO"."OBJECT_TYPE_ID")
58 - filter("S"."EXTSIZE"*"TS"."BLOCKSIZE">0)
59 - access("S"."TS#"="TS"."TS#")
61 - access("O"."OWNER#"="U"."USER#"(+))
62 - access("S"."USER#"="U"."USER#"(+))
66 - filter("UN"."STATUS$"<>1)
67 - filter("S"."TYPE#"=1 OR "S"."TYPE#"=10)
68 - access("S"."TS#"="UN"."TS#" AND "S"."FILE#"="UN"."FILE#" AND "S"."BLOCK#"="UN"."BLOCK#")
69 - access("UN"."TS#"="F"."TS#" AND "UN"."FILE#"="F"."RELFILE#")
70 - filter("S"."EXTSIZE"*"TS"."BLOCKSIZE">0)
71 - access("S"."TS#"="TS"."TS#")
73 - access("S"."USER#"="U"."USER#"(+))
75 - access("S"."TS#"="TS"."TS#")
       filter("S"."EXTSIZE"*"TS"."BLOCKSIZE">0)
79 - filter("S"."TYPE#"<>6 AND "S"."TYPE#"<>5 AND "S"."TYPE#"<>8 AND "S"."TYPE#"<>10 AND
              "S"."TYPE#"<>1)
80 - access("S"."TS#"="F"."TS#" AND "S"."FILE#"="F"."RELFILE#")
135 rows selected.
SQL>

Is there a difference between the earphone output and the audio output of the docking connector, or is it in fact the same signal ?

Is there a difference between the earphone output and the audiooutput of the docking connector of the iphone 4, or is it in fact the same signal ?

One basic difference is that the LTE frequencies each is able to operate on are different. After that, it is pretty much the same phone. Others might be able to add to this.

Difference between Page cache and cahelist in mdb output

Hello
When perfoming a "mdb -k" dee command ::memstat a got an output which summerize memory allocation and I cannot make the difference between the "page cache" and the "Free(cachelist)" rows. Both are used by file data by I can't make any difference.
Does anyone know which differs between these two counter?
Thank you

Hi,
Query Precalculation
The distribution type Precalculated Value Set allows you to fill variables of the type precalculated value sets with values for characteristic values in the background. The precalculated value sets are then available as variable values in BEx queries.
The following cases are typical examples of where the execution of precalculated value sets in the background is used:
●     When analyzing target groups, because you can specify a fixed value
●     When complex selections are involved such as with top N queries, used to greatly improve query performance
●     Instead of variables that are filled from a query event
http://help.sap.com/saphelp_nw70ehp1core/helpdata/en/2a/b37f425b595551e10000000a1550b0/frameset.htm
Filling OLAP Cache
The distribution type Fill OLAP Cache allows you to precalculate queries and to fill the OLAP cache with the generated data.
If the users call Web Applications, queries, reports or workbooks that are based on this data, the access time is significantly reduced and the workload on the application server is considerably less.
http://help.sap.com/saphelp_nw70ehp1core/helpdata/en/2a/b37f425b595551e10000000a1550b0/frameset.htm
Hope this helps
Regards
Snehith

No difference between High and Normal output sharpening

I was going to post a topic about how small is difference between screen output sharpening settings, when some tests revealed that in fact the difference is nil.
b Can anyone see any difference between Normal and High screen sharpening in applied at export?
I even stacked the two versions in Photoshop with the Difference blending mode on and a Levels adjustment layer amplifying the difference, and even the histogram was showing that I'be got big plain black rectangle.
Sharpening for paper seems to work fine.
Lightroom 2.3 Windows.

Just took the time to test this on my 'calibration' image and there is indeed no difference in Standard and High sharpening for screen.
Same result with and without resizing image; with and without jpeg compression; with both tif and jpeg files.
Lr 2.3 on XP.

Difference between the 5 generating outputs using RH10

I have created a Help File using RH10. I have been asked to find the pros and cons of between the five different generated outputs. I have searched the forums and have not really found a solid answer. Can anyone answer this question for me? I am new to RH and the extent of my training is from lynda.com and using the application.
I have been told that FlashHelp and WebHelp are the best options when dealing with multiple users.
Thanks!

Hi there
Indeed I can see where it can be very confusing if you aren't all that familiar.
I would agree that WebHelp and FlashHelp are common. Both of these outputs are intended to be copied to and delivered from a web server. With both outputs, the web browser is divided into frames. The top frame has the main toolbar, the left frame presents the TOC or Index or Glossary or Search and the right frame presents the topic content. The main difference between WebHelp and FlashHelp is how the information is presented in the top frame and the left frame. In FlashHelp, Adobe Flash is used and you see subtle animation effects. With WebHelp, it's a collection of HTML pages and images and links.
Another type of output is Microsoft HTML help, This output is created as a single file with a .CHM file extension. You would create this type of file if you want to copy the help system to each PC that will use it instead of having the individual PCs connect to a server to see the help.
RoboHelp version 10 introduced a new help output type called "Multiscreen". You have likely heard the buzzword "HTML 5". Multiscreen output is intended to be the HTML 5 choice,
The issue here is typically how easy is it to customize the output. With Microsoft HTML Help (CHM output) you don't have many options. Some say the output looks dated, But with RoboHelp 10 you are able to create WebHelp output with a skin and use that inside a CHM file to provide an updated look and feel.
If you wish to customize FlashHelp output, you must have a copy of Adobe Flash and the knowledge of how to use it. So it's not all that easy for most folks. Likewise, if you wish to customize the Multiscreen outputs, you have to have a pretty good understanding of CSS and be pretty patient with poking around the editor in RoboHelp. It's a fairly daunting task. The easiest to customize is the WebHelp output, because you just choose different images and configure things in an easy to navigate "Skin Editor".
You will see that there are other output types such as AIR Help. But that was more of a "flash in the pan" and it never really took off the way Adobe hoped it would. So personally, I'd recommend to avoid that output.
There is also the eBook output. You would choose that if you wanted to create a help system that would be presented on a Nook or a Kindle device. Not many folks are really "into" that space as far as I know.
Note that there is a "Pro" output type for WebHelp and for FlashHelp. This output isn't "better" than basic WebHelp or FlashHelp. Instead, it is a special output variant that is intended to work with another product called "RoboHelp Server". If you have purchased RoboHelp Server, you install it and configure it and maintain it on your web server. Then you create the "Pro" output type of choice and publish it to the RoboHelp Server. RoboHelp Server provides some management capabilities, special reporting and special configuraiton options that relate to these "Pro" output types.
There is more info on other outputs, but I think this covers what most folks might be interested in.
Hopefully this helps... Rick

Difference in output

Hi,
Her i post two queries ,the output of the two queries has some different(i.e total number of rows)
select a.owner,a.table_name, nvl(sum(bytes)/1024/1024,0)
from dba_segments b, dba_tables a
where a.table_name = b.segment_name(+)
and a.owner = b.owner(+)
group by a.table_name,a.owner
order by 1,2
select count(*) from dba_objects where object_type='TABLE';
Why it shows the difference in my output result?
Kindly suggest me

mafaiz wrote:
Hi,
The query posted by you was giving the differenece,
exactly all those table was storage tables.
Could u explain me about storage tables for nested-tables ?
thanks for providing valuable resultPlease refer to:
http://www.orafaq.com/wiki/NESTED_TABLE
It is like "a row in the table contains a column whose value itself is a table" (hence the term nested-table). For example, DEPT and EMPLOYEE tables are parent-child [ master-detail ] tables. Both need their own storage for data. If we decide to store EMPLOYEE table's inside DEPT table [ as nested-table ], the nested-employee-table still needs its storage area for data. Perhaps Oracle does not treat these nested-table-sotarge-tables differently.
This nested table can grow and shrink (data wise) just like regular relational tables and needs a separate storage area for its data [ just like regular relational table ].
CREATE OR REPLACE TYPE my_tab_t AS TABLE OF VARCHAR2(30);
CREATE TABLE nested_table (id NUMBER, col1 my_tab_t)
NESTED TABLE col1 STORE AS col1_tab;Notice the "STORE AS col1_tab" option - col1_tab is the storage table for the nested-table. If you don't provide this, then Oracle will assign a name implicitly to the storage-table.
HTH
Edited by: user130038 on Sep 13, 2011 5:10 AM

What is difference between sy-index and sy-tabix and where both are using ?

what is difference between sy-index and sy-tabix and where both are using ?

hi nagaraju
sy-tabix is in Internal table, current line index. So it can only be used while looping at the internal table.
sy-index is in Loops, number of current pass. This you can use in other loop statements also (like do-enddo loop, while-endwhile)
SY-INDEX is a counter for following loops: do...enddo, while..endwhile
SY-TABIX is a counter for LOOP...ENDLOOP, READ TABLE...
Here is an example from which you can understand the difference between sy-tabix and sy-index.
Itab is an internal table with the following data in it.
id Name
198 XYZ
475 ABC
545 PQR.
loop at itab where id > 300.
write :/ itab-id, itab-name , sy-tabix, sy-index.
endloop.
My output will be :
475 ABC 2 1
545 PQR 3 2
Sy-tabix is the index of the record in internal table.
sy-index gives the no of times of loop passes.
So, for the first record in the output (475 ABC), 2 is the index of the record in internal table and as it is first time loop pass occured, sy-index value is 1.
Regards,
navjot
award points

Select query differences between oracle 9 and oracle 8.

Hi,
I have a problem using the select query between oracle 7 and oracle 9i I don't have the same result :
ex:
With oracle7
SQL> select 'champ1','champ2' from DUAL;
'CHAMP 'CHAMP
champ1 champ2
With Oracle 9
SQL> select 'champ1','champ2' from DUAL;
'CHAMP1' 'CHAMP2'
champ1 champ2
So Can someone tell me how to solve this problem ? Is there a parameter in oracle 9 to set?
Thanx.

Whenever you are posting anything over internet forums like this - you should be very careful about not just posting the details which requires to solve the problem - also should be sensible about your question.
This is not at all desired when you are posting such question. It may be because - you may not well aware of the fact.
My suggestion is -> First Go through the basics Of SQL in general.
Then go for any specific product like Oracle/ SQL Server/ Sybase etc.
And, finally learn the advanced commands of that DB.
You asked it - may be you thought the difference in output in terms of lines. But, that is not your actual output. That is the graphical display part only.
Anyway,
You can get the quite familier output by first type the following command ->
set lin 310Regards.
Satyaki De.

Difference between output of DBA_SEGMENTS,DBA_OBJECTS & DBA_TABLES.

Similar Messages

Maybe you are looking for