Poor performance while join of 2 comprehensive large views and small table

Hi,
The following SQL statement has been identified to perform poorly. It currently takes up to 6 seconds to execute, but it's supposed to take ~30-40ms at most.
This is the statement(all bind variables change to numbers):
SELECT v__96.connector_objectid, v__96.connector_classid, v__96.from_objectid,
       v__96.to_objectid, v__96.from_classid, v__96.to_classid,
       v__96.from_firstunit, v__96.to_firstunit, v__96.number_of_units,
       tmp_trace.first_unit, tmp_trace.last_unit, v__96.inv_status_number,
       tmp_trace.first_unit, tmp_trace.last_unit, v__96.answers,
       v__96.priority, v__97.first_unit, v__97.n_units,
       v__97.mid_span_distance
  FROM ne.tmp_trace,
       (SELECT b.objectid, b.answers, b.connector_classid,
               b.connector_objectid, b.from_classid, b.from_objectid,
               b.to_classid, b.to_objectid, b.from_firstunit, b.to_firstunit,
               b.number_of_units, b.inv_status_number, b.splice_closure_name,
               b.work_order_name, b.work_order_item_number,
               b.inventory_status_code, b.priority
          FROM ne.connection b
         WHERE b.objectid NOT IN (
                  SELECT /*+ HASH_AJ */
                         sde_deletes_row_id
                    FROM ne.d96
                   WHERE deleted_at IN (
                            SELECT l.lineage_id
                              FROM sde.state_lineages l
                             WHERE l.lineage_name = 2
                               AND l.lineage_id <= 115)
                     AND sde_state_id = 0)
        UNION ALL
        SELECT a.objectid, a.answers, a.connector_classid,
               a.connector_objectid, a.from_classid, a.from_objectid,
               a.to_classid, a.to_objectid, a.from_firstunit, a.to_firstunit,
               a.number_of_units, a.inv_status_number, a.splice_closure_name,
               a.work_order_name, a.work_order_item_number,
               a.inventory_status_code, a.priority
          FROM ne.a96 a, sde.state_lineages sl
         WHERE (a.objectid, a.sde_state_id) NOT IN (
                  SELECT /*+ HASH_AJ */
                         sde_deletes_row_id, sde_state_id
                    FROM ne.d96
                   WHERE deleted_at IN (
                            SELECT l.lineage_id
                              FROM sde.state_lineages l
                             WHERE l.lineage_name = 2
                               AND l.lineage_id <= 115)
                     AND sde_state_id > 0)
           AND a.sde_state_id = sl.lineage_id
           AND sl.lineage_name = 2
           AND sl.lineage_id <= 115) v__96,
       (SELECT b.objectid, b.tray_number, b.db_loss, b.first_unit, b.n_units,
               b.connection_objectid, b.connector_type_name,
               b.dedicated_status, b.mid_span_distance
          FROM ne.connection_attributes b
         WHERE b.objectid NOT IN (
                  SELECT /*+ HASH_AJ */
                         sde_deletes_row_id
                    FROM ne.d97
                   WHERE deleted_at IN (
                            SELECT l.lineage_id
                              FROM sde.state_lineages l
                             WHERE l.lineage_name = 2
                               AND l.lineage_id <= 115)
                     AND sde_state_id = 0)
        UNION ALL
        SELECT a.objectid, a.tray_number, a.db_loss, a.first_unit, a.n_units,
               a.connection_objectid, a.connector_type_name,
               a.dedicated_status, a.mid_span_distance
          FROM ne.a97 a, sde.state_lineages sl
         WHERE (a.objectid, a.sde_state_id) NOT IN (
                  SELECT /*+ HASH_AJ */
                         sde_deletes_row_id, sde_state_id
                    FROM ne.d97
                   WHERE deleted_at IN (
                            SELECT l.lineage_id
                              FROM sde.state_lineages l
                             WHERE l.lineage_name = 2
                               AND l.lineage_id <= 115)
                     AND sde_state_id > 0)
           AND a.sde_state_id = sl.lineage_id
           AND sl.lineage_name = 2
           AND sl.lineage_id <= 115) v__97
WHERE (    (    (    (    (   (    ne.tmp_trace.equipment_object_id =
                                                             v__96.to_objectid
                                AND v__96.to_classid = 9
                            OR (    ne.tmp_trace.transmedia_object_id =
                                                             v__96.to_objectid
                                AND v__96.to_classid = 5
                       AND (   (v__96.to_firstunit
                                   BETWEEN ne.tmp_trace.first_unit
                                       AND ne.tmp_trace.last_unit
                            OR (ne.tmp_trace.first_unit
                                   BETWEEN v__96.to_firstunit
                                       AND   v__96.to_firstunit
                                           + v__96.number_of_units
                                           - 1
                  AND v__96.answers = 0
             AND v__96.objectid = v__97.connection_objectid
        AND (ne.tmp_trace.session_id = -1234)
       );It should return many values from 2 comprehensive views (v__96, v__97) and business table (tmp_trace). 2 comprehensive views ~1,000,000 recs each, business table ~ 10 recs.
The version of the database is 11.1.0.6.
These are the parameters relevant to the optimizer:
SQL> show parameter optimizer
NAME                                 TYPE                             VALUE
optimizer_capture_sql_plan_baselines boolean                          FALSE
optimizer_dynamic_sampling           integer                          2
optimizer_features_enable            string                           11.1.0.6
optimizer_index_caching              integer                          0
optimizer_index_cost_adj             integer                          100
optimizer_mode                       string                           ALL_ROWS
optimizer_secure_view_merging        boolean                          TRUE
optimizer_use_invisible_indexes      boolean                          FALSE
optimizer_use_pending_statistics     boolean                          FALSE
optimizer_use_sql_plan_baselines     boolean                          TRUE
SQL> show parameter db_file_multi
NAME                                 TYPE                             VALUE
db_file_multiblock_read_count        integer                          128
SQL> show parameter db_block_size
NAME                                 TYPE                             VALUE
db_block_size                        integer                          8192
SQL> show parameter cursor_sharing
NAME                                 TYPE                             VALUE
cursor_sharing                       string                           FORCE
SQL> column sname format a20
SQL> column pname format a20
SQL> column pval2 format a20
SQL> select sname, pname, pval1, pval2 from sys.aux_stats$;
SNAME                PNAME                     PVAL1 PVAL2
SYSSTATS_INFO        STATUS                          COMPLETED
SYSSTATS_INFO        DSTART                          07-15-2009 10:27
SYSSTATS_INFO        DSTOP                           07-15-2009 10:27
SYSSTATS_INFO        FLAGS                         1
SYSSTATS_MAIN        CPUSPEEDNW           1812.32129
SYSSTATS_MAIN        IOSEEKTIM                    10
SYSSTATS_MAIN        IOTFRSPEED                 4096
SYSSTATS_MAIN        SREADTIM
SYSSTATS_MAIN        MREADTIM
SYSSTATS_MAIN        CPUSPEED
SYSSTATS_MAIN        MBRC
SNAME                PNAME                     PVAL1 PVAL2
SYSSTATS_MAIN        MAXTHR
SYSSTATS_MAIN        SLAVETHR
13 rows selected.Here is the output of EXPLAIN PLAN:
explain plan for -- statement above
SQL> select * from table(dbms_xplan.display);
PLAN_TABLE_OUTPUT
Plan hash value: 1005186751
| Id  | Operation                          | Name                  | Rows  | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                   |                       |     1 |   282 |   268   (2)| 00:00:04 |
|   1 |  NESTED LOOPS                      |                       |     1 |   282 |   268   (2)| 00:00:04 |
|   2 |   MERGE JOIN CARTESIAN             |                       |     1 |   119 |   260   (1)| 00:00:04 |
|*  3 |    TABLE ACCESS FULL               | TMP_TRACE             |     1 |    65 |     2   (0)| 00:00:01 |
|   4 |    BUFFER SORT                     |                       |   103K|  5467K|   258   (1)| 00:00:04 |
|   5 |     VIEW                           |                       |   103K|  5467K|   258   (1)| 00:00:04 |
|   6 |      UNION-ALL                     |                       |       |       |            |       |
|   7 |       NESTED LOOPS ANTI            |                       |     1 |    82 |     3   (0)| 00:00:01 |
|   8 |        TABLE ACCESS FULL           | CONNECTION_ATTRIBUTES |     1 |    78 |     2   (0)| 00:00:01 |
|   9 |        VIEW PUSHED PREDICATE       | VW_NSO_1              |     1 |     4 |     1   (0)| 00:00:01 |
|  10 |         NESTED LOOPS               |                       |     1 |    20 |     1   (0)| 00:00:01 |
|* 11 |          INDEX RANGE SCAN          | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 12 |          INDEX UNIQUE SCAN         | D97_PK                |     1 |    13 |     0   (0)| 00:00:01 |
|* 13 |       HASH JOIN RIGHT ANTI         |                       |   103K|  5568K|   255   (1)| 00:00:04 |
|  14 |        VIEW                        | VW_NSO_2              |     1 |    26 |     2   (0)| 00:00:01 |
|  15 |         NESTED LOOPS               |                       |     1 |    20 |     2   (0)| 00:00:01 |
|* 16 |          INDEX FAST FULL SCAN      | D97_PK                |     1 |    13 |     2   (0)| 00:00:01 |
|* 17 |          INDEX UNIQUE SCAN         | LINEAGES_PK           |     1 |     7 |     0   (0)| 00:00:01 |
|  18 |        NESTED LOOPS                |                       |       |       |            |       |
|  19 |         NESTED LOOPS               |                       |   103K|  2936K|   252   (1)| 00:00:04 |
|* 20 |          INDEX RANGE SCAN          | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 21 |          INDEX RANGE SCAN          | A97_STATEID_IX1       | 17731 |       |    32   (0)| 00:00:01 |
|  22 |         TABLE ACCESS BY INDEX ROWID| A97                   | 21491 |   461K|   123   (1)| 00:00:02 |
|* 23 |   VIEW                             |                       |     1 |   163 |     8  (13)| 00:00:01 |
|  24 |    UNION ALL PUSHED PREDICATE      |                       |       |       |            |       |
|  25 |     NESTED LOOPS ANTI              |                       |     1 |   185 |     1   (0)| 00:00:01 |
|* 26 |      TABLE ACCESS BY INDEX ROWID   | CONNECTION            |     1 |   181 |     0   (0)| 00:00:01 |
|* 27 |       INDEX UNIQUE SCAN            | R96_SDE_ROWID_UK      |     1 |       |     0   (0)| 00:00:01 |
|  28 |      VIEW PUSHED PREDICATE         | VW_NSO_3              |     1 |     4 |     1   (0)| 00:00:01 |
|  29 |       NESTED LOOPS                 |                       |     1 |    20 |     1   (0)| 00:00:01 |
|* 30 |        INDEX RANGE SCAN            | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 31 |        INDEX UNIQUE SCAN           | D96_PK                |     1 |    13 |     0   (0)| 00:00:01 |
|* 32 |     HASH JOIN ANTI                 |                       |     1 |    97 |     7  (15)| 00:00:01 |
|  33 |      NESTED LOOPS                  |                       |     1 |    71 |     4   (0)| 00:00:01 |
|* 34 |       TABLE ACCESS BY INDEX ROWID  | A96                   |     1 |    64 |     4   (0)| 00:00:01 |
|* 35 |        INDEX RANGE SCAN            | A96_PK                |     1 |       |     3   (0)| 00:00:01 |
|* 36 |       INDEX UNIQUE SCAN            | LINEAGES_PK           |     1 |     7 |     0   (0)| 00:00:01 |
|  37 |      VIEW                          | VW_NSO_4              |     1 |    26 |     2   (0)| 00:00:01 |
|  38 |       NESTED LOOPS                 |                       |     1 |    20 |     2   (0)| 00:00:01 |
|* 39 |        INDEX FAST FULL SCAN        | D96_PK                |     1 |    13 |     2   (0)| 00:00:01 |
|* 40 |        INDEX UNIQUE SCAN           | LINEAGES_PK           |     1 |     7 |     0   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   3 - filter("TMP_TRACE"."SESSION_ID"=(-1234))
  11 - access("L"."LINEAGE_NAME"=2 AND "L"."LINEAGE_ID"<=115)
  12 - access("DELETED_AT"="L"."LINEAGE_ID" AND "SDE_DELETES_ROW_ID"="B"."OBJECTID" AND
              "SDE_STATE_ID"=0)
       filter("DELETED_AT"<=115)
  13 - access("A"."OBJECTID"="SDE_DELETES_ROW_ID" AND "A"."SDE_STATE_ID"="SDE_STATE_ID")
  16 - filter("DELETED_AT"<=115 AND "SDE_STATE_ID"<=115 AND "SDE_STATE_ID">0)
  17 - access("L"."LINEAGE_NAME"=2 AND "DELETED_AT"="L"."LINEAGE_ID")
       filter("L"."LINEAGE_ID"<=115)
  20 - access("SL"."LINEAGE_NAME"=2 AND "SL"."LINEAGE_ID"<=115)
  21 - access("A"."SDE_STATE_ID"="SL"."LINEAGE_ID")
       filter("A"."SDE_STATE_ID"<=115)
  23 - filter(("TMP_TRACE"."EQUIPMENT_OBJECT_ID"="V__96"."TO_OBJECTID" AND "V__96"."TO_CLASSID"=9
              OR "TMP_TRACE"."TRANSMEDIA_OBJECT_ID"="V__96"."TO_OBJECTID" AND "V__96"."TO_CLASSID"=5) AND
              ("V__96"."TO_FIRSTUNIT">="TMP_TRACE"."FIRST_UNIT" AND
              "V__96"."TO_FIRSTUNIT"<="TMP_TRACE"."LAST_UNIT" OR "TMP_TRACE"."FIRST_UNIT">="V__96"."TO_FIRSTUNIT"
              AND "TMP_TRACE"."FIRST_UNIT"<="V__96"."TO_FIRSTUNIT"+"V__96"."NUMBER_OF_UNITS"-1))
  26 - filter("B"."ANSWERS"=0)
  27 - access("B"."OBJECTID"="V__97"."CONNECTION_OBJECTID")
  30 - access("L"."LINEAGE_NAME"=2 AND "L"."LINEAGE_ID"<=115)
  31 - access("DELETED_AT"="L"."LINEAGE_ID" AND "SDE_DELETES_ROW_ID"="B"."OBJECTID" AND
              "SDE_STATE_ID"=0)
       filter("DELETED_AT"<=115)
  32 - access("A"."OBJECTID"="SDE_DELETES_ROW_ID" AND "A"."SDE_STATE_ID"="SDE_STATE_ID")
  34 - filter("A"."ANSWERS"=0)
  35 - access("A"."OBJECTID"="V__97"."CONNECTION_OBJECTID" AND "A"."SDE_STATE_ID"<=115)
  36 - access("SL"."LINEAGE_NAME"=2 AND "A"."SDE_STATE_ID"="SL"."LINEAGE_ID")
       filter("SL"."LINEAGE_ID"<=115)
  39 - filter("DELETED_AT"<=115 AND "SDE_STATE_ID"<=115 AND
              "SDE_DELETES_ROW_ID"="V__97"."CONNECTION_OBJECTID" AND "SDE_STATE_ID">0)
  40 - access("L"."LINEAGE_NAME"=2 AND "DELETED_AT"="L"."LINEAGE_ID")
       filter("L"."LINEAGE_ID"<=115)
Note
   - dynamic sampling used for this statement
87 rows selected.Here is the output of SQL*Plus AUTOTRACE including the TIMING information:
SQL> set autotrace traceonly arraysize 100
Elapsed: 00:00:01.64
Execution Plan
Plan hash value: 1198408274
| Id  | Operation                          | Name                  | Rows  | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                   |                       |   876K|   238M|  1301   (2)| 00:00:16 |
|   1 |  CONCATENATION                     |                       |       |       |            |       |
|*  2 |   HASH JOIN                        |                       |   438K|   119M|   651   (2)| 00:00:08 |
|*  3 |    HASH JOIN                       |                       |   423 | 98559 |   390   (2)| 00:00:05 |
|*  4 |     TABLE ACCESS FULL              | TMP_TRACE             |    82 |  5330 |    29   (0)| 00:00:01 |
|*  5 |     VIEW                           |                       |   103K|    16M|   360   (1)| 00:00:05 |
|   6 |      UNION-ALL                     |                       |       |       |            |       |
|   7 |       NESTED LOOPS ANTI            |                       |     1 |   185 |     3   (0)| 00:00:01 |
|*  8 |        TABLE ACCESS FULL           | CONNECTION            |     1 |   181 |     2   (0)| 00:00:01 |
|   9 |        VIEW PUSHED PREDICATE       | VW_NSO_3              |     1 |     4 |     1   (0)| 00:00:01 |
|  10 |         NESTED LOOPS               |                       |     1 |    20 |     1   (0)| 00:00:01 |
|* 11 |          INDEX RANGE SCAN          | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 12 |          INDEX UNIQUE SCAN         | D96_PK                |     1 |    13 |     0   (0)| 00:00:01 |
|* 13 |       HASH JOIN RIGHT ANTI         |                       |   103K|  9820K|   357   (1)| 00:00:05 |
|  14 |        VIEW                        | VW_NSO_4              |     1 |    26 |     2   (0)| 00:00:01 |
|  15 |         NESTED LOOPS               |                       |     1 |    20 |     2   (0)| 00:00:01 |
|* 16 |          INDEX FAST FULL SCAN      | D96_PK                |     1 |    13 |     2   (0)| 00:00:01 |
|* 17 |          INDEX UNIQUE SCAN         | LINEAGES_PK           |     1 |     7 |     0   (0)| 00:00:01 |
|  18 |        NESTED LOOPS                |                       |       |       |            |       |
|  19 |         NESTED LOOPS               |                       |   103K|  7188K|   354   (1)| 00:00:05 |
|* 20 |          INDEX RANGE SCAN          | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 21 |          INDEX RANGE SCAN          | A96_STATEID_IX1       | 17731 |       |    32   (0)| 00:00:01 |
|* 22 |         TABLE ACCESS BY INDEX ROWID| A96                   | 21491 |  1343K|   224   (1)| 00:00:03 |
|  23 |    VIEW                            |                       |   103K|  5264K|   258   (1)| 00:00:04 |
|  24 |     UNION-ALL                      |                       |       |       |            |       |
|  25 |      NESTED LOOPS ANTI             |                       |     1 |    82 |     3   (0)| 00:00:01 |
|  26 |       TABLE ACCESS FULL            | CONNECTION_ATTRIBUTES |     1 |    78 |     2   (0)| 00:00:01 |
|  27 |       VIEW PUSHED PREDICATE        | VW_NSO_1              |     1 |     4 |     1   (0)| 00:00:01 |
|  28 |        NESTED LOOPS                |                       |     1 |    20 |     1   (0)| 00:00:01 |
|* 29 |         INDEX RANGE SCAN           | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 30 |         INDEX UNIQUE SCAN          | D97_PK                |     1 |    13 |     0   (0)| 00:00:01 |
|* 31 |      HASH JOIN RIGHT ANTI          |                       |   103K|  5568K|   255   (1)| 00:00:04 |
|  32 |       VIEW                         | VW_NSO_2              |     1 |    26 |     2   (0)| 00:00:01 |
|  33 |        NESTED LOOPS                |                       |     1 |    20 |     2   (0)| 00:00:01 |
|* 34 |         INDEX FAST FULL SCAN       | D97_PK                |     1 |    13 |     2   (0)| 00:00:01 |
|* 35 |         INDEX UNIQUE SCAN          | LINEAGES_PK           |     1 |     7 |     0   (0)| 00:00:01 |
|  36 |       NESTED LOOPS                 |                       |       |       |            |       |
|  37 |        NESTED LOOPS                |                       |   103K|  2936K|   252   (1)| 00:00:04 |
|* 38 |         INDEX RANGE SCAN           | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 39 |         INDEX RANGE SCAN           | A97_STATEID_IX1       | 17731 |       |    32   (0)| 00:00:01 |
|  40 |        TABLE ACCESS BY INDEX ROWID | A97                   | 21491 |   461K|   123   (1)| 00:00:02 |
|* 41 |   HASH JOIN                        |                       |   438K|   119M|   651   (2)| 00:00:08 |
|* 42 |    HASH JOIN                       |                       |   423 | 98559 |   390   (2)| 00:00:05 |
|* 43 |     TABLE ACCESS FULL              | TMP_TRACE             |    82 |  5330 |    29   (0)| 00:00:01 |
|* 44 |     VIEW                           |                       |   103K|    16M|   360   (1)| 00:00:05 |
|  45 |      UNION-ALL                     |                       |       |       |            |       |
|  46 |       NESTED LOOPS ANTI            |                       |     1 |   185 |     3   (0)| 00:00:01 |
|* 47 |        TABLE ACCESS FULL           | CONNECTION            |     1 |   181 |     2   (0)| 00:00:01 |
|  48 |        VIEW PUSHED PREDICATE       | VW_NSO_3              |     1 |     4 |     1   (0)| 00:00:01 |
|  49 |         NESTED LOOPS               |                       |     1 |    20 |     1   (0)| 00:00:01 |
|* 50 |          INDEX RANGE SCAN          | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 51 |          INDEX UNIQUE SCAN         | D96_PK                |     1 |    13 |     0   (0)| 00:00:01 |
|* 52 |       HASH JOIN RIGHT ANTI         |                       |   103K|  9820K|   357   (1)| 00:00:05 |
|  53 |        VIEW                        | VW_NSO_4              |     1 |    26 |     2   (0)| 00:00:01 |
|  54 |         NESTED LOOPS               |                       |     1 |    20 |     2   (0)| 00:00:01 |
|* 55 |          INDEX FAST FULL SCAN      | D96_PK                |     1 |    13 |     2   (0)| 00:00:01 |
|* 56 |          INDEX UNIQUE SCAN         | LINEAGES_PK           |     1 |     7 |     0   (0)| 00:00:01 |
|  57 |        NESTED LOOPS                |                       |       |       |            |       |
|  58 |         NESTED LOOPS               |                       |   103K|  7188K|   354   (1)| 00:00:05 |
|* 59 |          INDEX RANGE SCAN          | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 60 |          INDEX RANGE SCAN          | A96_STATEID_IX1       | 17731 |       |    32   (0)| 00:00:01 |
|* 61 |         TABLE ACCESS BY INDEX ROWID| A96                   | 21491 |  1343K|   224   (1)| 00:00:03 |
|  62 |    VIEW                            |                       |   103K|  5264K|   258   (1)| 00:00:04 |
|  63 |     UNION-ALL                      |                       |       |       |            |       |
|  64 |      NESTED LOOPS ANTI             |                       |     1 |    82 |     3   (0)| 00:00:01 |
|  65 |       TABLE ACCESS FULL            | CONNECTION_ATTRIBUTES |     1 |    78 |     2   (0)| 00:00:01 |
|  66 |       VIEW PUSHED PREDICATE        | VW_NSO_1              |     1 |     4 |     1   (0)| 00:00:01 |
|  67 |        NESTED LOOPS                |                       |     1 |    20 |     1   (0)| 00:00:01 |
|* 68 |         INDEX RANGE SCAN           | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 69 |         INDEX UNIQUE SCAN          | D97_PK                |     1 |    13 |     0   (0)| 00:00:01 |
|* 70 |      HASH JOIN RIGHT ANTI          |                       |   103K|  5568K|   255   (1)| 00:00:04 |
|  71 |       VIEW                         | VW_NSO_2              |     1 |    26 |     2   (0)| 00:00:01 |
|  72 |        NESTED LOOPS                |                       |     1 |    20 |     2   (0)| 00:00:01 |
|* 73 |         INDEX FAST FULL SCAN       | D97_PK                |     1 |    13 |     2   (0)| 00:00:01 |
|* 74 |         INDEX UNIQUE SCAN          | LINEAGES_PK           |     1 |     7 |     0   (0)| 00:00:01 |
|  75 |       NESTED LOOPS                 |                       |       |       |            |       |
|  76 |        NESTED LOOPS                |                       |   103K|  2936K|   252   (1)| 00:00:04 |
|* 77 |         INDEX RANGE SCAN           | LINEAGES_PK           |     5 |    35 |     1   (0)| 00:00:01 |
|* 78 |         INDEX RANGE SCAN           | A97_STATEID_IX1       | 17731 |       |    32   (0)| 00:00:01 |
|  79 |        TABLE ACCESS BY INDEX ROWID | A97                   | 21491 |   461K|   123   (1)| 00:00:02 |
Predicate Information (identified by operation id):
   2 - access("V__96"."OBJECTID"="V__97"."CONNECTION_OBJECTID")
   3 - access("TMP_TRACE"."TRANSMEDIA_OBJECT_ID"="V__96"."TO_OBJECTID")
       filter("V__96"."TO_FIRSTUNIT">="TMP_TRACE"."FIRST_UNIT" AND
              "V__96"."TO_FIRSTUNIT"<="TMP_TRACE"."LAST_UNIT" OR "TMP_TRACE"."FIRST_UNIT">="V__96"."TO_FIRSTUNIT"
              AND "TMP_TRACE"."FIRST_UNIT"<="V__96"."TO_FIRSTUNIT"+"V__96"."NUMBER_OF_UNITS"-1)
   4 - filter("TMP_TRACE"."SESSION_ID"=(-1234))
   5 - filter("V__96"."TO_CLASSID"=5)
   8 - filter("B"."ANSWERS"=0)
  11 - access("L"."LINEAGE_NAME"=2 AND "L"."LINEAGE_ID"<=115)
  12 - access("DELETED_AT"="L"."LINEAGE_ID" AND "SDE_DELETES_ROW_ID"="B"."OBJECTID" AND
              "SDE_STATE_ID"=0)
       filter("DELETED_AT"<=115)
  13 - access("A"."OBJECTID"="SDE_DELETES_ROW_ID" AND "A"."SDE_STATE_ID"="SDE_STATE_ID")
  16 - filter("DELETED_AT"<=115 AND "SDE_STATE_ID"<=115 AND "SDE_STATE_ID">0)
  17 - access("L"."LINEAGE_NAME"=2 AND "DELETED_AT"="L"."LINEAGE_ID")
       filter("L"."LINEAGE_ID"<=115)
  20 - access("SL"."LINEAGE_NAME"=2 AND "SL"."LINEAGE_ID"<=115)
  21 - access("A"."SDE_STATE_ID"="SL"."LINEAGE_ID")
       filter("A"."SDE_STATE_ID"<=115)
  22 - filter("A"."ANSWERS"=0)
  29 - access("L"."LINEAGE_NAME"=2 AND "L"."LINEAGE_ID"<=115)
  30 - access("DELETED_AT"="L"."LINEAGE_ID" AND "SDE_DELETES_ROW_ID"="B"."OBJECTID" AND
              "SDE_STATE_ID"=0)
       filter("DELETED_AT"<=115)
  31 - access("A"."OBJECTID"="SDE_DELETES_ROW_ID" AND "A"."SDE_STATE_ID"="SDE_STATE_ID")
  34 - filter("DELETED_AT"<=115 AND "SDE_STATE_ID"<=115 AND "SDE_STATE_ID">0)
  35 - access("L"."LINEAGE_NAME"=2 AND "DELETED_AT"="L"."LINEAGE_ID")
       filter("L"."LINEAGE_ID"<=115)
  38 - access("SL"."LINEAGE_NAME"=2 AND "SL"."LINEAGE_ID"<=115)
  39 - access("A"."SDE_STATE_ID"="SL"."LINEAGE_ID")
       filter("A"."SDE_STATE_ID"<=115)
  41 - access("V__96"."OBJECTID"="V__97"."CONNECTION_OBJECTID")
  42 - access("TMP_TRACE"."EQUIPMENT_OBJECT_ID"="V__96"."TO_OBJECTID")
       filter((LNNVL("TMP_TRACE"."TRANSMEDIA_OBJECT_ID"="V__96"."TO_OBJECTID") OR
              LNNVL("V__96"."TO_CLASSID"=5)) AND ("V__96"."TO_FIRSTUNIT">="TMP_TRACE"."FIRST_UNIT" AND
              "V__96"."TO_FIRSTUNIT"<="TMP_TRACE"."LAST_UNIT" OR "TMP_TRACE"."FIRST_UNIT">="V__96"."TO_FIRSTUNIT"
              AND "TMP_TRACE"."FIRST_UNIT"<="V__96"."TO_FIRSTUNIT"+"V__96"."NUMBER_OF_UNITS"-1))
  43 - filter("TMP_TRACE"."SESSION_ID"=(-1234))
  44 - filter("V__96"."TO_CLASSID"=9)
  47 - filter("B"."ANSWERS"=0)
  50 - access("L"."LINEAGE_NAME"=2 AND "L"."LINEAGE_ID"<=115)
  51 - access("DELETED_AT"="L"."LINEAGE_ID" AND "SDE_DELETES_ROW_ID"="B"."OBJECTID" AND
              "SDE_STATE_ID"=0)
       filter("DELETED_AT"<=115)
  52 - access("A"."OBJECTID"="SDE_DELETES_ROW_ID" AND "A"."SDE_STATE_ID"="SDE_STATE_ID")
  55 - filter("DELETED_AT"<=115 AND "SDE_STATE_ID"<=115 AND "SDE_STATE_ID">0)
  56 - access("L"."LINEAGE_NAME"=2 AND "DELETED_AT"="L"."LINEAGE_ID")
       filter("L"."LINEAGE_ID"<=115)
  59 - access("SL"."LINEAGE_NAME"=2 AND "SL"."LINEAGE_ID"<=115)
  60 - access("A"."SDE_STATE_ID"="SL"."LINEAGE_ID")
       filter("A"."SDE_STATE_ID"<=115)
  61 - filter("A"."ANSWERS"=0)
  68 - access("L"."LINEAGE_NAME"=2 AND "L"."LINEAGE_ID"<=115)
  69 - access("DELETED_AT"="L"."LINEAGE_ID" AND "SDE_DELETES_ROW_ID"="B"."OBJECTID" AND
              "SDE_STATE_ID"=0)
       filter("DELETED_AT"<=115)
  70 - access("A"."OBJECTID"="SDE_DELETES_ROW_ID" AND "A"."SDE_STATE_ID"="SDE_STATE_ID")
  73 - filter("DELETED_AT"<=115 AND "SDE_STATE_ID"<=115 AND "SDE_STATE_ID">0)
  74 - access("L"."LINEAGE_NAME"=2 AND "DELETED_AT"="L"."LINEAGE_ID")
       filter("L"."LINEAGE_ID"<=115)
  77 - access("SL"."LINEAGE_NAME"=2 AND "SL"."LINEAGE_ID"<=115)
  78 - access("A"."SDE_STATE_ID"="SL"."LINEAGE_ID")
       filter("A"."SDE_STATE_ID"<=115)
Note
   - dynamic sampling used for this statementThe TKPROF output for this statement looks like the following:
TKPROF: Release 11.1.0.6.0 - Production on Thu Sep 24 09:30:01 2009
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
Trace file: pro                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           &

The TKPROF output for this statement looks like the following:
TKPROF: Release 11.1.0.6.0 - Production on Thu Sep 24 09:30:01 2009
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
Trace file: problem.trc
Sort options: default
count    = number of times OCI procedure was executed
cpu      = cpu time in seconds executing
elapsed  = elapsed time in seconds executing
disk     = number of physical reads of buffers from disk
query    = number of buffers gotten for consistent read
current  = number of buffers gotten in current mode (usually for update)
rows     = number of rows processed by the fetch or execute call
SELECT  V__96.CONNECTOR_OBJECTID,  V__96.CONNECTOR_CLASSID,  V__96.FROM_OBJECTID,  V__96.TO_OBJECTID,  V__96.FROM_CLASSID,  V__96.TO_CLASSID, 
V__96.FROM_FIRSTUNIT,  V__96.TO_FIRSTUNIT,  V__96.NUMBER_OF_UNITS,  TMP_TRACE.FIRST_UNIT,  TMP_TRACE.LAST_UNIT,  V__96.INV_STATUS_NUMBER, 
TMP_TRACE.FIRST_UNIT,  TMP_TRACE.LAST_UNIT,  V__96.ANSWERS,  V__96.PRIORITY,  V__97.FIRST_UNIT,  V__97.N_UNITS,  V__97.MID_SPAN_DISTANCE  FROM 
NE.TMP_TRACE,(SELECT
b.OBJECTID,b.ANSWERS,b.CONNECTOR_CLASSID,b.CONNECTOR_OBJECTID,b.FROM_CLASSID,b.FROM_OBJECTID,b.TO_CLASSID,b.TO_OBJECTID,b.FROM_FIRSTUNIT,b.TO_FIRSTUNIT,b.NUM
BER_OF_UNITS,b.INV_STATUS_NUMBER,b.SPLICE_CLOSURE_NAME,b.WORK_ORDER_NAME,b.WORK_ORDER_ITEM_NUMBER,b.INVENTORY_STATUS_CODE,b.PRIORITY  FROM NE.connection b
WHERE b.OBJECTID NOT IN (SELECT /*+ HASH_AJ */ SDE_DELETES_ROW_ID FROM NE.D96 WHERE DELETED_AT IN (SELECT l.lineage_id FROM SDE.state_lineages l WHERE
l.lineage_name = :"SYS_B_00" AND l.lineage_id <= :"SYS_B_01") AND SDE_STATE_ID = :"SYS_B_02") UNION ALL SELECT
a.OBJECTID,a.ANSWERS,a.CONNECTOR_CLASSID,a.CONNECTOR_OBJECTID,a.FROM_CLASSID,a.FROM_OBJECTID,a.TO_CLASSID,a.TO_OBJECTID,a.FROM_FIRSTUNIT,a.TO_FIRSTUNIT,a.NUM
BER_OF_UNITS,a.INV_STATUS_NUMBER,a.SPLICE_CLOSURE_NAME,a.WORK_ORDER_NAME,a.WORK_ORDER_ITEM_NUMBER,a.INVENTORY_STATUS_CODE,a.PRIORITY  FROM NE.A96
a,SDE.state_lineages SL WHERE (a.OBJECTID, a.SDE_STATE_ID) NOT IN (SELECT /*+ HASH_AJ */ SDE_DELETES_ROW_ID,SDE_STATE_ID  FROM NE.D96 WHERE DELETED_AT IN
(SELECT l.lineage_id FROM SDE.state_lineages l WHERE l.lineage_name = :"SYS_B_03" AND l.lineage_id <= :"SYS_B_04") AND SDE_STATE_ID > :"SYS_B_05") AND
a.SDE_STATE_ID = SL.lineage_id AND SL.lineage_name = :"SYS_B_06" AND SL.lineage_id <= :"SYS_B_07") V__96,(SELECT
b.OBJECTID,b.TRAY_NUMBER,b.DB_LOSS,b.FIRST_UNIT,b.N_UNITS,b.CONNECTION_OBJECTID,b.CONNECTOR_TYPE_NAME,b.DEDICATED_STATUS,b.MID_SPAN_DISTANCE  FROM
NE.connection_attributes b WHERE b.OBJECTID NOT IN (SELECT /*+ HASH_AJ */ SDE_DELETES_ROW_ID FROM NE.D97 WHERE DELETED_AT IN (SELECT l.lineage_id FROM
SDE.state_lineages l WHERE l.lineage_name = :"SYS_B_08" AND l.lineage_id <= :"SYS_B_09") AND SDE_STATE_ID = :"SYS_B_10") UNION ALL SELECT
a.OBJECTID,a.TRAY_NUMBER,a.DB_LOSS,a.FIRST_UNIT,a.N_UNITS,a.CONNECTION_OBJECTID,a.CONNECTOR_TYPE_NAME,a.DEDICATED_STATUS,a.MID_SPAN_DISTANCE  FROM NE.A97
a,SDE.state_lineages SL WHERE (a.OBJECTID, a.SDE_STATE_ID) NOT IN (SELECT /*+ HASH_AJ */ SDE_DELETES_ROW_ID,SDE_STATE_ID  FROM NE.D97 WHERE DELETED_AT IN
(SELECT l.lineage_id FROM SDE.state_lineages l WHERE l.lineage_name = :"SYS_B_11" AND l.lineage_id <= :"SYS_B_12") AND SDE_STATE_ID > :"SYS_B_13") AND
a.SDE_STATE_ID = SL.lineage_id AND SL.lineage_name = :"SYS_B_14" AND SL.lineage_id <= :"SYS_B_15") V__97  WHERE (((((   (
                                         NE.tmp_trace.equipment_object_id = V__96.to_objectid
                                          AND
                                         V__96.to_classid = :"SYS_B_16"
                                       OR
                                         NE.tmp_trace.transmedia_object_id = V__96.to_objectid
                                           AND
                                         V__96.to_classid = :"SYS_B_17"
                                         )) AND (
                                        (V__96.to_firstunit
                                            BETWEEN NE.tmp_trace.first_unit AND NE.tmp_trace.last_unit)
                                          OR
                                        (NE.tmp_trace.first_unit BETWEEN V__96.to_firstunit
                                             AND V__96.to_firstunit + V__96.number_of_units - :"SYS_B_18")
                                      )) AND V__96.answers = :"SYS_B_19") AND V__96.objectid = V__97.connection_objectid) AND (NE.tmp_trace.session_id =
:"SYS_B_20"))
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        1      5.98       5.99          0      22652          0          10
total        3      5.98       5.99          0      22652          0          10
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 45 
Rows     Row Source Operation
     10  NESTED LOOPS  (cr=22652 pr=0 pw=0 time=654515 us cost=67 size=282 card=1)
     10   NESTED LOOPS  (cr=22436 pr=0 pw=0 time=653673 us cost=61 size=235 card=1)
     10    TABLE ACCESS FULL TMP_TRACE (cr=5 pr=0 pw=0 time=7 us cost=2 size=65 card=1)
     10    VIEW  (cr=22431 pr=0 pw=0 time=0 us cost=59 size=170 card=1)
1773000     UNION-ALL  (cr=22431 pr=0 pw=0 time=93649 us)
      0      NESTED LOOPS ANTI (cr=30 pr=0 pw=0 time=0 us cost=3 size=185 card=1)
      0       TABLE ACCESS FULL CONNECTION (cr=30 pr=0 pw=0 time=0 us cost=2 size=181 card=1)
      0       VIEW PUSHED PREDICATE  VW_NSO_3 (cr=0 pr=0 pw=0 time=0 us cost=1 size=4 card=1)
      0        NESTED LOOPS  (cr=0 pr=0 pw=0 time=0 us cost=1 size=20 card=1)
      0         INDEX RANGE SCAN LINEAGES_PK (cr=0 pr=0 pw=0 time=0 us cost=1 size=7 card=1)(object id 34021)
      0         INDEX UNIQUE SCAN D96_PK (cr=0 pr=0 pw=0 time=0 us cost=0 size=13 card=1)(object id 35121)
1773000      HASH JOIN RIGHT ANTI (cr=22401 pr=0 pw=0 time=75084 us cost=56 size=46948 card=484)
      0       VIEW  VW_NSO_4 (cr=180 pr=0 pw=0 time=0 us cost=2 size=26 card=1)
      0        FILTER  (cr=180 pr=0 pw=0 time=0 us)
      0         NESTED LOOPS  (cr=180 pr=0 pw=0 time=0 us cost=2 size=20 card=1)
      0          INDEX FAST FULL SCAN D96_PK (cr=180 pr=0 pw=0 time=0 us cost=2 size=13 card=1)(object id 35121)
      0          INDEX UNIQUE SCAN LINEAGES_PK (cr=0 pr=0 pw=0 time=0 us cost=0 size=7 card=1)(object id 34021)
1773000       NESTED LOOPS  (cr=22221 pr=0 pw=0 time=56155 us)
1773000        NESTED LOOPS  (cr=3231 pr=0 pw=0 time=15078 us cost=53 size=34364 card=484)
     50         INDEX RANGE SCAN LINEAGES_PK (cr=10 pr=0 pw=0 time=7 us cost=1 size=7 card=1)(object id 34021)
1773000         INDEX RANGE SCAN A96_STATEID_IX1 (cr=3221 pr=0 pw=0 time=6810 us cost=32 size=0 card=1774)(object id 35116)
1773000        TABLE ACCESS BY INDEX ROWID A96 (cr=18990 pr=0 pw=0 time=0 us cost=52 size=82560 card=1290)
     10   VIEW  (cr=216 pr=0 pw=0 time=0 us cost=7 size=47 card=1)
     10    UNION ALL PUSHED PREDICATE  (cr=216 pr=0 pw=0 time=0 us)
      0     NESTED LOOPS ANTI (cr=1 pr=0 pw=0 time=0 us cost=2 size=82 card=1)
      0      TABLE ACCESS BY INDEX ROWID CONNECTION_ATTRIBUTES (cr=1 pr=0 pw=0 time=0 us cost=1 size=78 card=1)
      0       INDEX RANGE SCAN GDB_59_CONNECTIO (cr=1 pr=0 pw=0 time=0 us cost=1 size=0 card=1)(object id 34346)
      0      VIEW PUSHED PREDICATE  VW_NSO_1 (cr=0 pr=0 pw=0 time=0 us cost=1 size=4 card=1)
      0       NESTED LOOPS  (cr=0 pr=0 pw=0 time=0 us cost=1 size=20 card=1)
      0        INDEX RANGE SCAN LINEAGES_PK (cr=0 pr=0 pw=0 time=0 us cost=1 size=7 card=1)(object id 34021)
      0        INDEX UNIQUE SCAN D97_PK (cr=0 pr=0 pw=0 time=0 us cost=0 size=13 card=1)(object id 35127)
     10     HASH JOIN ANTI (cr=215 pr=0 pw=0 time=0 us cost=5 size=55 card=1)
     10      NESTED LOOPS  (cr=35 pr=0 pw=0 time=0 us cost=2 size=29 card=1)
     10       TABLE ACCESS BY INDEX ROWID A97 (cr=25 pr=0 pw=0 time=0 us cost=2 size=22 card=1)
     10        INDEX RANGE SCAN GDB_59_CONNECTIO_A (cr=15 pr=0 pw=0 time=0 us cost=1 size=0 card=1)(object id 35122)
     10       INDEX UNIQUE SCAN LINEAGES_PK (cr=10 pr=0 pw=0 time=0 us cost=0 size=7 card=1)(object id 34021)
      0      VIEW  VW_NSO_2 (cr=180 pr=0 pw=0 time=0 us cost=2 size=26 card=1)
      0       FILTER  (cr=180 pr=0 pw=0 time=0 us)
      0        NESTED LOOPS  (cr=180 pr=0 pw=0 time=0 us cost=2 size=20 card=1)
      0         INDEX FAST FULL SCAN D97_PK (cr=180 pr=0 pw=0 time=0 us cost=2 size=13 card=1)(object id 35127)
      0         INDEX UNIQUE SCAN LINEAGES_PK (cr=0 pr=0 pw=0 time=0 us cost=0 size=7 card=1)(object id 34021)
Elapsed times include waiting on following events:
  Event waited on                             Times   Max. Wait  Total Waited
  ----------------------------------------   Waited  ----------  ------------
  SQL*Net message to client                       2        0.00          0.00
  SQL*Net message from client                     2        0.00          0.00After manually rewrite query in TOAD it produces nested loops on business table and than access v__96, v__97 produce desired quick performance.
I can use stored outlines but this is the last chance. I am playing with hints right now to produce desired plan with no result yet.
Does anybody know how to insist Oracle to merge internal views to bigger query block, so Oracle can choose better plan?
Or any guide what hints to use from ol$hints to get desired result via hints addition to original sql query (thanks God application don't cut hints just pass-through to Oracle)?
Thanks,
Sergiy

Similar Messages

  • Can we write a join on a view and a table

    Hi all,
    can we write a join on a view and a table. i got the requirement from my functional people about the following one
    Select CAUFV-AFUNR, CAUFV-AUART, AFVC-VORNR, CAUFV-FTRMI, CRHD-ARBPL
    into <ProOrd>, <OrdTyp>, <Opt>, <RelDat>, <WorCen>
    from CAUFV, AFVC, CRHD
    where CAUFV-WERKS = plant in selection screen
    and CAUFV-AFUNR = production order in selection screen
    and CAUFV-AUART = production order type in selection screen
    and CAUFV-FTRMI = range of release date in selection screen
    and CAUFV-AUFPL = AFVC-AUFPL
    and AFVC-ARBID = CRHD-OBJID
    and CRHD-OBJTY = ‘A’
    here CAUFV is a view and CRHD and AFVC are transperent tables.
    please tell me any feasible solution for this..
    Thanks  in Advance..

    Hi
    Refer these links:
    <u>http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ec84446011d189700000e8322d00/content.htm</u>
    <u>http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm</u>
    <u>http://www.karakas-online.de/forum/viewtopic.php?t=730</u>
    Thanks
    Vasudha
    Message was edited by:
            Vasudha L

  • MSOutlook HTML newsletter issues - large gaps between large images and small gaps...

    Please can you help me!
    Searched the web & found plently of advice but still getting formatting display issue when viewing HTML newsletter in MS Outlook.
    Fully aware on the basics regarding the multiple issues when creating HTML newsletters but this is driving me crazy.
    Apparently there is a image height limit within Outlook (can't find out what this is) so I have sliced my larger images into 5/6 parts which solves the display issue in Outlook.
    But the gaps between the slices are now being displayed as small blank spaces within Hotmail.
    I did use <br> between each slice as without caused the fixed 600px wide containing table to expand due to the slices stacking hoz.
    Also still getting small gaps (like <br> spaces) between all images in Outlook when displaying perfectly (no gaps) in a browser.
    This is my newsletter displaying correctly via a browser:
    http://eu.shorts.tv/site-admin/modules/mod_mail/SHORTSTV_DECEMBER_2012.htm
    Using Dreamweaver 4 (do have the latest version via Adobe Creative Cloud Membership but not on this system).
    Hope you can help
    Many thanks

    Many thanks David
    I also found this article which is currently sitting on my desk.
    Pdf would make perfect sense or even a url link to view via a browser but these guys need it contained within the email.
    Thanks again for your kind advice.
    Regards
    ShortsTV
    Date: Fri, 30 Nov 2012 18:05:08 -0700
    From: [email protected]
    To: [email protected]
    Subject: MSOutlook HTML newsletter issues - large gaps between large images and small gaps...
        Re: MSOutlook HTML newsletter issues - large gaps between large images and small gaps...
        created by David__B in Adobe Creative Cloud - View the full discussion
    Hey Shortstv, Not something I know much about, searched and found thishttp://robcubbon.com/create-html-email-newsletters-outlook/ Maybe create it as a PDF attachment instead? -Dave
         Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4888255#4888255
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4888255#4888255
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4888255#4888255. In the Actions box on the right, click the Stop Email Notifications link.
         Start a new discussion in Adobe Creative Cloud by email or at Adobe Community
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Poor performance on admin console after adding 1k+ teams and member profile

    We run v7sp3p2 (MS) now but even back on v5.1 see degraded performance in form of response times over 60 seconds when browsing security hierarchy in admin console after adding over 1000 teams and member access profiles.  We need the granularity in access for our many users.  Does anyone know any tricks to prevent the glacial and disappointing response times while maintaining the necessary security?  This behavior reflects poorly on the product's scalability.
    Thanks,
    Erik

    Sorin, I want to make sure I understand your recommendation.
    First, we do have more than 1000 users.  Each location has a unique team to which their users belong, and each of these teams has a member access profile with corresponding read/write access to the dimension member representing their location.  The users at each location only view data for their own location.
    Is your recommendation to use another interface besides the admin console for accomplishing security updates?
    We have a custom package that uses an API to upload data files with mass updates to security assignments and definitions, but hesitate to use this method for mundane changes for add/remove/change just a few users as this method bypasses the domain validation we get on the front end wherein we can only add users to the domain they correctly belong to.
    To dodge the risk of a bad user/domain matchup we'd like to use front end but it appears to not support our scale well.
    Thoughts on a setting or configuration we could manipulate to resolve the poor performance would be great - what levers can we pull?  If this is all the tool can support we just live with it and pay the cost in wasted man hours over the life of the product...

  • Performance tuning fro a select stmnt consisting of View and DB Table

    Hi Gurus ,
    I have a select query which is consuming a lot of time for execution. Well it selects details from a custom view ZV_MKPF_MSEG (join of MKPF and MSEG) and table MARA as following
    SELECT GI~BUKRS                                   "company code
             GI~WERKS                                    "Plant
             GI~BWART                                    "Movement Type
             GI~BUDAT                                    "Posting Date
             GI~MBLNR                                    "Mat Doc Number
             GI~ZEILE                                    "Item
             GI~KOSTL                                    "cost center
             GI~MENGE                                    "Quantity
             GI~SHKZG                                    "Debit credit ind
             MAMATKL MAMATNR MA~MEINS
             INTO CORRESPONDING FIELDS OF TABLE PT_GITAB
             FROM ZV_MKPF_MSEG AS GI INNER JOIN MARA AS MA
                  ON MAMATNR = GIMATNR
             WHERE GI~BUKRS IN S_BUKRS AND
                   GI~WERKS IN S_WERKS AND
                   GI~BUDAT IN S_BUDAT AND
                   GI~BWART IN S_BWART AND
                   GI~MBLNR IN S_MBLNR AND
                   MA~MATKL IN S_MATKL                
             ORDER BY GIMBLNR GIZEILE.
    how we should manipulate this query in order to increase the perfromance ? And could anybody give some idea about the use of indexes for a table since both MSEG and MKPF tables have indexes attached.
    Thanx
    Kylie
    Edited by: kylietisha on Jun 7, 2010 5:01 PM

    Moderator message - Please see Please Read before Posting in the Performance and Tuning Forum before posting - post locked
    Rob

  • Poor performance while battery connected

    Hey guys,
    I have a late 09 Macbook Pro with a fixed battery. After this laptop was dropped the performance was horrible. This was caused by kernel_task using about 300-340% CPU all the time. I went through a lot of different forums trying to find a fix (SMC etc), and discovered that
    1) The MBP works 100% with the battery disconnected
    2) The MBP works 100% when in safe mode regardless of if the battery is disconnected or not
    I think potentially buying a new battery may solve my issue, but I don't want to go through this to find that the same issue is present. The battery itself is working as intended.
    Does anyone have any advice on this issue?

    Mezevenf,
    your second finding suggests that the problem is software-related rather than hardware-related.
    If you haven’t done so already, download and install EtreCheck. Please include in your reply the output from a run of EtreCheck.

  • Poor performance while executing

    hi,
    the java pgm involves display of pictures and movies... but if there are other applications running then it becomes very very slow. WHy is it so? I am using Redhat 9 Linux platform and jdk1.4.5. i have to run the other applciations... y is it that its takin so much time to display each pic. Could there b some memory problem as the pic and movies take a lot of space and the garbage collector doesnt ahve enuf time to recollect the memory?

    I would try settings a lower (=higher value) process priority with nice...The nice level influences only the contest for the processor. It won't help with I/O issues.
    It would be worth to try to run the other applciation so that it writes into a file instead of to a console and compare the outcome.

  • Oracle Query Performance While calling a function in a View

    Hi,
    We have a performance issue in one of our Oracle queries.
    Here is the scenario
    We use a hard coded value (which is the maximum value from a table) in couple of DECODE statements in our query. We would like to remove this hard coded value from the query. So we wrote a function which will return a maximum value from the table. Now when we execute the query after replacing the hard coded value with the function, this function is called four times which hampers the query performance.
    Pl find below the DECODE statements in the query. This query is part of a main VIEW.
    Using Hardcoded values
    =================
    DECODE(pro_risk_weighted_ctrl_scr, 10, 9.9, pro_risk_weighted_ctrl_scr)
    DECODE(pro_risk_score, 46619750, 46619749, pro_risk_score)
    Using Functions
    ============
    DECODE (pro_risk_weighted_ctrl_scr, rprowbproc.fn_max_rcsa_range_values ('CSR'), rprowbproc.fn_max_rcsa_range_values('CSR')- 0.1, pro_risk_weighted_ctrl_scr)
    DECODE (pro_risk_score, rprowbproc.fn_max_rcsa_range_values ('RSR'), rprowbproc.fn_max_rcsa_range_values ('RSR') - 1, pro_risk_score)
    Can any one suggest a way to improve the performance of the query.
    Thanks & Regards,
    Raji

    drop table max_demo;
    create table max_demo
    (rcsa   varchar2(10)
    ,value  number);
    insert into max_demo
    select case when mod(rownum,2) = 0
                then 'CSR'
                else 'RSR'
           end
    ,      rownum
    from   dual
    connect by rownum <= 10000;   
    create or replace function f_max (
      i_rcsa    in   max_demo.rcsa%TYPE
    return number
    as
      l_max number;
    begin
       select max(value)
       into   l_max
       from   max_demo
       where  rcsa = i_rcsa;
       return l_max;
    end;
    -- slooooooooooooowwwwww
    select m.*
    ,      f_max(rcsa)
    ,      decode(rcsa,'CSR',decode(value,f_max('CSR'),'Y - max is '||f_max('CSR'),'N - max is '||f_max('CSR'))) is_max_csr
    ,      decode(rcsa,'RSR',decode(value,f_max('RSR'),'Y - max is '||f_max('RSR'),'N - max is '||f_max('RSR'))) is_max_rsr
    from   max_demo m
    order by value desc;
    -- ssllooooowwwww
    with subq_max as
         (select f_max('CSR') max_csr,
                 f_max('RSR') max_rsr
          from   dual)
    select m.*
    ,      decode(rcsa,'CSR',s.max_csr,'RSR',s.max_rsr) max
    ,      decode(rcsa,'CSR',decode(value,s.max_csr,'Y - max is '||s.max_csr,'N - max is '||s.max_csr)) is_max_csr
    ,      decode(rcsa,'RSR',decode(value,s.max_rsr,'Y - max is '||s.max_rsr,'N - max is '||s.max_rsr)) is_max_rsr
    from   max_demo m
    ,      subq_max s
    order by value desc;
    -- faster
    with subq_max as
         (select /*+materialize */
                 f_max('CSR') max_csr,
                 f_max('RSR') max_rsr
          from   dual)
    select m.*
    ,      decode(rcsa,'CSR',s.max_csr,'RSR',s.max_rsr) max
    ,      decode(rcsa,'CSR',decode(value,s.max_csr,'Y - max is '||s.max_csr,'N - max is '||s.max_csr)) is_max_csr
    ,      decode(rcsa,'RSR',decode(value,s.max_rsr,'Y - max is '||s.max_rsr,'N - max is '||s.max_rsr)) is_max_rsr
    from   max_demo m
    ,      subq_max s
    order by value desc;
    -- faster
    with subq_max as
         (select f_max('CSR') max_csr,
                 f_max('RSR') max_rsr,
                 rownum
          from   dual)
    select m.*
    ,      decode(rcsa,'CSR',s.max_csr,'RSR',s.max_rsr) max
    ,      decode(rcsa,'CSR',decode(value,s.max_csr,'Y - max is '||s.max_csr,'N - max is '||s.max_csr)) is_max_csr
    ,      decode(rcsa,'RSR',decode(value,s.max_rsr,'Y - max is '||s.max_rsr,'N - max is '||s.max_rsr)) is_max_rsr
    from   max_demo m
    ,      subq_max s
    order by value desc;
    -- sloooooowwwwww
    select m.*
    ,      decode(rcsa,'CSR',s.max_csr,'RSR',s.max_rsr) max
    ,      decode(rcsa,'CSR',decode(value,s.max_csr,'Y - max is '||s.max_csr,'N - max is '||s.max_csr)) is_max_csr
    ,      decode(rcsa,'RSR',decode(value,s.max_rsr,'Y - max is '||s.max_rsr,'N - max is '||s.max_rsr)) is_max_rsr
    from   max_demo m
    ,      (select /*+ materialize */
                 f_max('CSR') max_csr,
                 f_max('RSR') max_rsr
          from   dual) s
    order by value desc;
    -- faster
    select m.*
    ,      decode(rcsa,'CSR',s.max_csr,'RSR',s.max_rsr) max
    ,      decode(rcsa,'CSR',decode(value,s.max_csr,'Y - max is '||s.max_csr,'N - max is '||s.max_csr)) is_max_csr
    ,      decode(rcsa,'RSR',decode(value,s.max_rsr,'Y - max is '||s.max_rsr,'N - max is '||s.max_rsr)) is_max_rsr
    from   max_demo m
    ,      (select f_max('CSR') max_csr,
                   f_max('RSR') max_rsr,
                   rownum
            from   dual) s
    order by value desc;

  • How to define join in physical layer between cube and relational table

    Hi
    I have a aggregated data in essbase cube. I want to supplement the information in the cube with data from relational source.
    I read article http://community.altiusconsulting.com/blogs/altiustechblog/archive/2008/10/24/are-essbase-and-oracle-bi-enterprise-edition-obiee-a-match-made-in-heaven.aspx which describes how to do it.
    From this article I gather that I have to define a complex join between the cube imported from essbase to my relational table in physical layer.
    But when I use Join Manager I am only able to define jooin between tables from relation source but not with the imported cube.
    In My case I am trying to join risk dimension in the cube based on risk_type_code (Gen3 member) with risk_type_code in relation table dt_risk_type.
    How can I create this join?
    Regards
    Dhwaj

    Hi
    This has worked the BI server has joined the member from the oracle database to cube. So Now for risk type id defined in the cube I can view the risk type code and risk type name from the relational db.
    But now if I want to find aggregated risk amount against a risk type id it brings back nothing. If I remove the join in the logical model then I get correct values. Is there a way by which I can combine phsical cube with relational model and still get the aggregated values in the cube?
    I have changed the column risk amount to be sum in place of aggr_external both in logical and phsical model.
    Regards,
    Dhwaj

  • Is is possible to have the images as thumbnails and make it so you can click on them for a larger view and then click them again to have it go back to the original size? In an interactive pdf?

    I am designing an interactive catalog in a pdf. Is it possible to have the images as a thumbnail and then click them to enlarge the image and then click again to make them go back to the original size?
    Thank you in advance!
    Stephanie

    It can be done with Show/Hide buttons:
    Here's a button created from a small version of the image (notice that it's selected in the image below):
    The small button has a Show/Hide Buttons and Forms action. It's action is to make the Larger Image visible (eyeball turned on) with the small image hidden (eyeball turned off).
    The large image is also turned into a button (shown below):
    Notice the checkbox "Hidden Until Triggered". The large button is hidden until it's triggered by the small button. Clicking on the large image also causes a Show/Hide action which shows the Small button and hides the large button.

  • DOI - I_OI_SPREADSHEET, poor performance when reading more than 9999 record

    Hi,
    Please read this message in the [ABAP Performance and Tuning|DOI - I_OI_SPREADSHEET, poor performance when reading more than 9999 record; section and see if you have any advise.
    Best Regards,
    Marjo

    Hi,
    I met this issue when I tried to write vaule to massive fields of excel range.
    And I solve this issue by using CL_GUI_FRONTEND_SERVICES=>CLIPBOARD_EXPORT.
    So, I think you may fix it in the same way.
    1. Select range in by the I_OI_SPREADSHEET
    2. Call method I_OI_DOCUMENT_PROXY->COPY_SELECTION
    3. Call method CL_GUI_FRONTEND_SERVICES=>CLIPBOARD_IMPORT
    Cheers,

  • Poor performance of VL10A transaction

    Hello Experts,
    We are facing very poor performance in One of our production system in VL10A transaction
    I checked for the response time and it is going up to 5 seconds
    I checked for :
    Table Space > it is fine
    Pending updates ? it is fine
    Available workprocesses > it is fine
    Abap Dumps > no major issues.
    Could any body suggest ??
    Thank you
    Regards,
    Amber S

    Hi
    Try to get a working example of the transaction with poor performance. I would just run the transaction and monitor the work processes SM50 at same time. If you always see your request on a certain table, for example VEPVG, then I would take an SQL trace with transaction ST05.
    If the process in SM50 is only on a table (-> accessing the database) for a short time, then you would investigate more on the Abap side.
    Btw, if you did not modifiy anything, then you can always go to SAP support (-> look for SAP notes first!) as this is a standard functionality.
    Best regards, Michael

  • X100e poor performance

    Hello guys, could anyone have a hint on how to improve this lappy poor performance?
    I have the AMD processor series and put 2GB extra ram, it was worthless...  the machine freezes frequently, this is so disappointing, I never have had such issue in other Thinkpads... come on Lenovo!!! what´s going on with you?

    Mark_Lenovo doesn't read every posts and this is a peer to peer support forum.
    I doubt Atom processor is going to be any better for the apps that you are using. The CPU simply doesn't have the grunt to run through these applications.
    I don't know whether you should blame Lenovo for this debacle, unless it is a Lenovo employee whom recommended you to buy this. Sometimes, it is prudent to read up on your purchase, especially when your work depends on it, as you can see people do give wrong advice, whether or not it was intentional or accidental. 
    Regards,
    Jin Li
    May this year, be the year of 'DO'!
    I am a volunteer, and not a paid staff of Lenovo or Microsoft

  • Crashing and poor performance during playback of a large project.

    Hi,
    I've been a regular user of iMovie for about 3 years and have edited several 50GB+ projects of DV quality footage without too many major issues with lag or 'dropped frames'. I currently have a 80GB project that resides on a 95% full 320GB Firewire 400 external drive that has been getting very slow to open and near impossible to work with.
    Pair the bursting-at-the-seams external drive, with an overburdened 90% full internal drive - the poor performance wasn't to be unexpected. So I bought a 1TB Firewire 400 drive to free up some space on my Mac. My large iTunes library (150GB) was the main culprit and it was quickly moved onto the new drive.
    The iMovie project was then moved onto my Mac's movie folder - I figured that the project needs some "room" to work (not that I really understand how Macs use memory) and that having roughly 80GB free with 1.5GB RAM (which is more than used to have) would make everything just that much smoother.
    Wrong.
    The project opened in roughly the same amount of time - but when I tried to play back the timeline, it plays like rubbish and then after 10-15 secs the Mac goes into 'sleep' mode. The screen goes off, the fans dies down and the 'heartbeat' light goes on. A click of the mouse 'wakes' the Mac only to find that if i try again, I get the same result.
    I've probably got so many variables going on here that it's probably hard to suggest what the problem might be but all I could think of was repairing permissions (which I did and none needed it).
    Stuck on this. Anyone have any advice?

    I understand completely, having worked with a 100 GB project once. I found that getting a movie bloated up to that size was just more difficult with jerky playback.
    I do have a couple of suggestions for you.
    You may need more than that 80GB free space for this movie. Is there any reason you cannot move it to the 1TB drive? If you have only your iTunes on it, you should have about 800 GB free.
    If you still need to have the project on your computer's drive, set your computer to never sleep.
    How close to finishing editing are you with this movie? If you are nearly done except for adding audio clips, you can export (share) it as QuickTime Full Quality movie. The resultant quicktime version of your iMovie will be smaller because it will contain only the clips actually used in the movie, not all the saved whole clips that iMovie keeps as its nondestructive editing feature. The quicktime movie will be one continuous clip, incorporating all your edits and added audio. It CAN be further edited, but you cannot change text of titles already there, or change transitions or remove already added audios.
    I actually do this with nearly every iMovie. I create my movies by first importing videos, then adding still photos, then editing with titles, effects and transitions. I add audio last, and if it becomes too distorted in playback, I export the movie and then continue adding audio clips.
    My 100+ GB movie slimmed down to only 8 GB with this method. (The large size was due to having so many clips. The movie was from VHS footage of my son's little league all-star game, and the video had so many skipped segments that I had to split it into thousands of clips to remove the dropped ones. Very old VHS tape!).
    I haven't upgraded to QT 7.5.5, but I heard that the jerky playback issue is mostly resolved with this new upgrade. I am in mid-project with about 5 iMovies, so I will probably plod along with my work-around method, not wanting to upgrade in the middle of any of them.
    Hope this is helpful to you.

  • Poor performance of facetime on macbook air while it works fine with other devices

    Hi all,
    I am experiencing poor performance when using facetime with my macbook air (image is poor and voice keeps breaking) while facetime works absolutely fine with my iphone or ipad. Skype works fie with the macbook as well. I have fiber optic connection with plenty of bandwidth. Any ideas?
    Dimitri

    Reboot and try again.

Maybe you are looking for