CBO generating different plans for the same data in similar Environments

Hi All
I have been trying to compare an SQL from 2 different but similar environments build of the same hardware specs .The issue I am facing is environment A, the query executes in less than 2 minutes with plan mostly showing full table scans and hash join whereas in environment B(problematic), it times out after 2 hours with an error of unable to extend table space . The statistics are up to date in both environments for both tables and indexes . System parameters are exactly similar(default oracle for except for multiblock_read_count ).
Both Environment have same db parameter for db_file_multiblock_read_count(16), optimizer(refer below),hash_area_size (131072),pga_aggregate_target(1G),db_block_size(8192) etc . SREADTIM, MREADTIM, CPUSPEED, MBRC are all null in aux_stats in both environment because workload was never collected i believe.
Attached is details about the SQL with table stats, SQL and index stats my main concern is CBO generating different plans for the similar data and statistics and same hardware and software specs. Is there any thing else I should consider .I generally see environment B being very slow and always plans tend to nested loops and index scan whereas what we really need is a sensible FTS in many cases. One of the very surprising thing is METER_CONFIG_HEADER below which has just 80 blocks of data is being asked for index scan.
show parameter optimizer
optimizer_dynamic_sampling integer 2
optimizer_features_enable string 10.2.0.4
optimizer_index_caching integer 0
optimizer_index_cost_adj integer 100
optimizer_mode string ALL_ROWS
optimizer_secure_view_merging boolean TRUE
**Environment**
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE     10.2.0.4.0     Production
TNS for Solaris: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Note: : There are slight difference in the no of records in the attached sheet.However, I wanted to tell that i have tested with exact same data and was getting similar results but I couldn't retain the data untill collecting the details in the attachment
TEST1     COMPARE TABLE LEVE STATS used by CBO
ENVIRONMENT A
TABLE_NAME     NUM_ROWS     BLOCKS     LAST_ANALYZED
ASSET     3607425     167760     5/02/2013 22:11
METER_CONFIG_HEADER     3658     80     5/01/2013 0:07
METER_CONFIG_ITEM     32310     496     5/01/2013 0:07
NMI     1899024     33557     18/02/2013 10:55
REGISTER     4830153     101504     18/02/2013 9:57
SDP_LOGICAL_ASSET     1607456     19137     18/02/2013 15:48
SDP_LOGICAL_REGISTER     5110781     78691     18/02/2013 9:56
SERVICE_DELIVERY_POINT     1425890     42468     18/02/2013 13:54
ENVIRONMENT B
TABLE_NAME     NUM_ROWS     BLOCKS     LAST_ANALYZED
ASSET     4133939     198570     16/02/2013 10:02
METER_CONFIG_HEADER     3779     80     16/02/2013 10:55
METER_CONFIG_ITEM     33720     510     16/02/2013 10:55
NMI     1969000     33113     16/02/2013 10:58
REGISTER     5837874     120104     16/02/2013 11:05
SDP_LOGICAL_ASSET     1788152     22325     16/02/2013 11:06
SDP_LOGICAL_REGISTER     6101934     91088     16/02/2013 11:07
SERVICE_DELIVERY_POINT     1447589     43804     16/02/2013 11:11
TEST ITEM 2     COMPARE INDEX STATS used by CBO
ENVIRONMENT A
TABLE_NAME     INDEX_NAME     UNIQUENESS     BLEVEL     LEAF_BLOCKS     DISTINCT_KEYS     AVG_LEAF_BLOCKS_PER_KEY     AVG_DATA_BLOCKS_PER_KEY     CLUSTERING_FACTOR     NUM_ROWS
ASSET     IDX_AST_DEVICE_CATEGORY_SK     NONUNIQUE     2     9878     67     147     12982     869801     3553095
ASSET     IDX_A_SAPINTLOGDEV_SK     NONUNIQUE     2     7291     2747     2     639     1755977     3597916
ASSET     SYS_C00102592     UNIQUE     2     12488     3733831     1     1     3726639     3733831
METER_CONFIG_HEADER     SYS_C0092052     UNIQUE     1     12     3670     1     1     3590     3670
METER_CONFIG_ITEM     SYS_C0092074     UNIQUE     1     104     32310     1     1     32132     32310
NMI     IDX_NMI_ID     NONUNIQUE     2     6298     844853     1     2     1964769     1965029
NMI     IDX_NMI_ID_NK     NONUNIQUE     2     6701     1923072     1     1     1922831     1923084
NMI     IDX_NMI_STATS     NONUNIQUE     1     106     4     26     52     211     211
REGISTER     REG_EFFECTIVE_DTM     NONUNIQUE     2     12498     795     15     2899     2304831     4711808
REGISTER     SYS_C00102653     UNIQUE     2     16942     5065660     1     1     5056855     5065660
SDP_LOGICAL_ASSET     IDX_SLA_SAPINTLOGDEV_SK     NONUNIQUE     2     3667     1607968     1     1     1607689     1607982
SDP_LOGICAL_ASSET     IDX_SLA_SDP_SK     NONUNIQUE     2     3811     668727     1     2     1606204     1607982
SDP_LOGICAL_ASSET     SYS_C00102665     UNIQUE     2     5116     1529606     1     1     1528136     1529606
SDP_LOGICAL_REGISTER     SYS_C00102677     UNIQUE     2     17370     5193638     1     1     5193623     5193638
SERVICE_DELIVERY_POINT     IDX_SDP_NMI_SK     NONUNIQUE     2     4406     676523     1     2     1423247     1425890
SERVICE_DELIVERY_POINT     IDX_SDP_SAP_INT_NMI_SK     NONUNIQUE     2     7374     676523     1     2     1458238     1461108
SERVICE_DELIVERY_POINT     SYS_C00102687     UNIQUE     2     4737     1416207     1     1     1415022     1416207
ENVIRONMENT B
TABLE_NAME     INDEX_NAME     UNIQUENESS     BLEVEL     LEAF_BLOCKS     DISTINCT_KEYS     AVG_LEAF_BLOCKS_PER_KEY     AVG_DATA_BLOCKS_PER_KEY     CLUSTERING_FACTOR     NUM_ROWS
ASSET     IDX_AST_DEVICE_CATEGORY_SK     NONUNIQUE     2     8606     121     71     16428     1987833     4162257
ASSET     IDX_A_SAPINTLOGDEV_SK     NONUNIQUE     2     8432     1780146     1     1     2048170     4162257
ASSET     SYS_C00116157     UNIQUE     2     13597     4162263     1     1     4158759     4162263
METER_CONFIG_HEADER     SYS_C00116570     UNIQUE     1     12     3779     1     1     3734     3779
METER_CONFIG_ITEM     SYS_C00116592     UNIQUE     1     107     33720     1     1     33459     33720
NMI     IDX_NMI_ID     NONUNIQUE     2     6319     683370     1     2     1970460     1971313
NMI     IDX_NMI_ID_NK     NONUNIQUE     2     6597     1971293     1     1     1970771     1971313
NMI     IDX_NMI_STATS     NONUNIQUE     1     98     48     2     4     196     196
REGISTER     REG_EFFECTIVE_DTM     NONUNIQUE     2     15615     1273     12     2109     2685924     5886582
REGISTER     SYS_C00116748     UNIQUE     2     19533     5886582     1     1     5845565     5886582
SDP_LOGICAL_ASSET     IDX_SLA_SAPINTLOGDEV_SK     NONUNIQUE     2     4111     1795084     1     1     1758441     1795130
SDP_LOGICAL_ASSET     IDX_SLA_SDP_SK     NONUNIQUE     2     4003     674249     1     2     1787987     1795130
SDP_LOGICAL_ASSET     SYS_C004520     UNIQUE     2     5864     1795130     1     1     1782147     1795130
SDP_LOGICAL_REGISTER     SYS_C004539     UNIQUE     2     20413     6152850     1     1     6073059     6152850
SERVICE_DELIVERY_POINT     IDX_SDP_NMI_SK     NONUNIQUE     2     3227     660649     1     2     1422572     1447803
SERVICE_DELIVERY_POINT     IDX_SDP_SAP_INT_NMI_SK     NONUNIQUE     2     6399     646257     1     2     1346948     1349993
SERVICE_DELIVERY_POINT     SYS_C00128706     UNIQUE     2     4643     1447946     1     1     1442796     1447946
TEST ITEM 3     COMPARE PLANS
ENVIRONMENT A
Plan hash value: 4109575732
| Id | Operation                       | Name                   | Rows | Bytes |TempSpc| Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                |                        |    13 | 2067 |       |   135K (2)| 00:27:05 |
|   1 | HASH UNIQUE                    |                        |    13 | 2067 |       |   135K (2)| 00:27:05 |
|* 2 |   HASH JOIN                     |                        |    13 | 2067 |       |   135K (2)| 00:27:05 |
|* 3 |    HASH JOIN                    |                        |     6 |   900 |       |   135K (2)| 00:27:04 |
|* 4 |     HASH JOIN ANTI              |                        |     1 |   137 |       |   135K (2)| 00:27:03 |
|* 5 |      TABLE ACCESS BY INDEX ROWID| NMI                    |     1 |    22 |       |     5   (0)| 00:00:01 |
|   6 |       NESTED LOOPS              |                        |     1 |   131 |       | 95137   (2)| 00:19:02 |
|* 7 |        HASH JOIN                |                        |     1 |   109 |       | 95132   (2)| 00:19:02 |
|* 8 |         TABLE ACCESS FULL       | ASSET                  | 36074 | 1021K|       | 38553   (2)| 00:07:43 |
|* 9 |         HASH JOIN               |                        | 90361 | 7059K| 4040K| 56578   (2)| 00:11:19 |
|* 10 |          HASH JOIN              |                        | 52977 | 3414K| 2248K| 50654   (2)| 00:10:08 |
|* 11 |           HASH JOIN             |                        | 39674 | 1782K|       | 40101   (2)| 00:08:02 |
|* 12 |            TABLE ACCESS FULL    | REGISTER               | 39439 | 1232K|       | 22584   (2)| 00:04:32 |
|* 13 |            TABLE ACCESS FULL    | SDP_LOGICAL_REGISTER   | 4206K|    56M|       | 17490   (2)| 00:03:30 |
|* 14 |           TABLE ACCESS FULL     | SERVICE_DELIVERY_POINT |   675K|    12M|       | 9412   (2)| 00:01:53 |
|* 15 |          TABLE ACCESS FULL      | SDP_LOGICAL_ASSET      | 1178K|    15M|       | 4262   (2)| 00:00:52 |
|* 16 |        INDEX RANGE SCAN         | IDX_NMI_ID_NK          |     2 |       |       |     2   (0)| 00:00:01 |
| 17 |      VIEW                       |                        | 39674 |   232K|       | 40101   (2)| 00:08:02 |
|* 18 |       HASH JOIN                 |                        | 39674 | 1046K|       | 40101   (2)| 00:08:02 |
|* 19 |        TABLE ACCESS FULL        | REGISTER               | 39439 |   500K|       | 22584   (2)| 00:04:32 |
|* 20 |        TABLE ACCESS FULL        | SDP_LOGICAL_REGISTER   | 4206K|    56M|       | 17490   (2)| 00:03:30 |
|* 21 |     TABLE ACCESS FULL           | METER_CONFIG_HEADER    | 3658 | 47554 |       |    19   (0)| 00:00:01 |
|* 22 |    TABLE ACCESS FULL            | METER_CONFIG_ITEM      | 7590 | 68310 |       |   112   (2)| 00:00:02 |
Predicate Information (identified by operation id):
   2 - access("METER_CONFIG_HEADER_SK"="METER_CONFIG_HEADER_SK")
   3 - access("NETWORK_TARIFF_CD"="NETWORK_TARIFF_CD")
   4 - access("SERVICE_DELIVERY_POINT_SK"="TMP"."SERVICE_DELIVERY_POINT_SK")
   5 - filter("ROW_CURRENT_IND"='Y' AND ("NMI_STATUS_CD"='A' OR "NMI_STATUS_CD"='D'))
   7 - access("ASSET_CD"="EQUIP_CD" AND "SAP_INT_LOG_DEVICE_SK"="SAP_INT_LOG_DEVICE_SK")
   8 - filter("ROW_CURRENT_IND"='Y')
   9 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")
10 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")
11 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
12 - filter("REGISTER_TYPE_CD"='C' AND (SUBSTR("REGISTER_ID_CD",1,1)='4' OR
              SUBSTR("REGISTER_ID_CD",1,1)='5' OR SUBSTR("REGISTER_ID_CD",1,1)='6') AND "ROW_CURRENT_IND"='Y')
13 - filter("ROW_CURRENT_IND"='Y')
14 - filter("ROW_CURRENT_IND"='Y')
15 - filter("ROW_CURRENT_IND"='Y')
16 - access("NMI_SK"="NMI_SK")
18 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
19 - filter("REGISTER_TYPE_CD"='C' AND (SUBSTR("REGISTER_ID_CD",1,1)='1' OR
              SUBSTR("REGISTER_ID_CD",1,1)='2' OR SUBSTR("REGISTER_ID_CD",1,1)='3') AND "ROW_CURRENT_IND"='Y')
20 - filter("ROW_CURRENT_IND"='Y')
21 - filter("ROW_CURRENT_IND"='Y')
22 - filter("ROW_CURRENT_IND"='Y' AND "CONROL_REGISTER"='X')
ENVIRONMENT B
Plan hash value: 2826260434
| Id | Operation                            | Name                   | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                     |                        |     1 |   181 |   103K (2)| 00:20:47 |
|   1 | HASH UNIQUE                         |                        |     1 |   181 |   103K (2)| 00:20:47 |
|* 2 |   HASH JOIN ANTI                     |                        |     1 |   181 |   103K (2)| 00:20:47 |
|* 3 |    HASH JOIN                         |                        |     1 |   176 | 56855   (2)| 00:11:23 |
|* 4 |     HASH JOIN                        |                        |     1 |   163 | 36577   (2)| 00:07:19 |
|* 5 |      TABLE ACCESS BY INDEX ROWID     | ASSET                  |     1 |    44 |     4   (0)| 00:00:01 |
|   6 |       NESTED LOOPS                   |                        |     1 |   131 | 9834   (2)| 00:01:59 |
|   7 |        NESTED LOOPS                  |                        |     1 |    87 | 9830   (2)| 00:01:58 |
|   8 |         NESTED LOOPS                 |                        |     1 |    74 | 9825   (2)| 00:01:58 |
|* 9 |          HASH JOIN                   |                        |     1 |    52 | 9820   (2)| 00:01:58 |
|* 10 |           TABLE ACCESS BY INDEX ROWID| METER_CONFIG_HEADER    |     1 |    14 |     1   (0)| 00:00:01 |
| 11 |            NESTED LOOPS              |                        |     1 |    33 |   116   (2)| 00:00:02 |
|* 12 |             TABLE ACCESS FULL        | METER_CONFIG_ITEM      |     1 |    19 |   115   (2)| 00:00:02 |
|* 13 |             INDEX RANGE SCAN         | SYS_C00116570          |     1 |       |     1   (0)| 00:00:01 |
|* 14 |           TABLE ACCESS FULL          | SERVICE_DELIVERY_POINT |   723K|    13M| 9699   (2)| 00:01:57 |
|* 15 |          TABLE ACCESS BY INDEX ROWID | NMI                    |     1 |    22 |     5   (0)| 00:00:01 |
|* 16 |           INDEX RANGE SCAN           | IDX_NMI_ID_NK          |     2 |       |     2   (0)| 00:00:01 |
|* 17 |         TABLE ACCESS BY INDEX ROWID | SDP_LOGICAL_ASSET      |     1 |    13 |     5   (0)| 00:00:01 |
|* 18 |          INDEX RANGE SCAN            | IDX_SLA_SDP_SK         |     2 |       |     2   (0)| 00:00:01 |
|* 19 |        INDEX RANGE SCAN              | IDX_A_SAPINTLOGDEV_SK |     2 |       |     2   (0)| 00:00:01 |
|* 20 |      TABLE ACCESS FULL               | REGISTER               | 76113 | 2378K| 26743   (2)| 00:05:21 |
|* 21 |     TABLE ACCESS FULL                | SDP_LOGICAL_REGISTER   | 5095K|    63M| 20245   (2)| 00:04:03 |
| 22 |    VIEW                              |                        | 90889 |   443K| 47021   (2)| 00:09:25 |
|* 23 |     HASH JOIN                        |                        | 90889 | 2307K| 47021   (2)| 00:09:25 |
|* 24 |      TABLE ACCESS FULL               | REGISTER               | 76113 |   966K| 26743   (2)| 00:05:21 |
|* 25 |      TABLE ACCESS FULL               | SDP_LOGICAL_REGISTER   | 5095K|    63M| 20245   (2)| 00:04:03 |
Predicate Information (identified by operation id):
   2 - access("SERVICE_DELIVERY_POINT_SK"="TMP"."SERVICE_DELIVERY_POINT_SK")
   3 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK" AND
              "SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
   4 - access("ASSET_CD"="EQUIP_CD")
   5 - filter("ROW_CURRENT_IND"='Y')
   9 - access("NETWORK_TARIFF_CD"="NETWORK_TARIFF_CD")
10 - filter("ROW_CURRENT_IND"='Y')
12 - filter("ROW_CURRENT_IND"='Y' AND "CONROL_REGISTER"='X')
13 - access("METER_CONFIG_HEADER_SK"="METER_CONFIG_HEADER_SK")
14 - filter("ROW_CURRENT_IND"='Y')
15 - filter("ROW_CURRENT_IND"='Y' AND ("NMI_STATUS_CD"='A' OR "NMI_STATUS_CD"='D'))
16 - access("NMI_SK"="NMI_SK")
17 - filter("ROW_CURRENT_IND"='Y')
18 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")
19 - access("SAP_INT_LOG_DEVICE_SK"="SAP_INT_LOG_DEVICE_SK")
20 - filter((SUBSTR("REGISTER_ID_CD",1,1)='4' OR SUBSTR("REGISTER_ID_CD",1,1)='5' OR
              SUBSTR("REGISTER_ID_CD",1,1)='6') AND "REGISTER_TYPE_CD"='C' AND "ROW_CURRENT_IND"='Y')
21 - filter("ROW_CURRENT_IND"='Y')
23 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
24 - filter((SUBSTR("REGISTER_ID_CD",1,1)='1' OR SUBSTR("REGISTER_ID_CD",1,1)='2' OR
              SUBSTR("REGISTER_ID_CD",1,1)='3') AND "REGISTER_TYPE_CD"='C' AND "ROW_CURRENT_IND"='Y')
25 - filter("ROW_CURRENT_IND"='Y')Edited by: abhilash173 on Feb 24, 2013 9:16 PM
Edited by: abhilash173 on Feb 24, 2013 9:18 PM

Hi Paul,
I misread your question initially .The system stats are outdated in both ( same result as seen from aux_stats) .I am not a DBA and do not have access to gather system stats fresh.
select * from sys.aux_stats$
SNAME     PNAME     PVAL1     PVAL2
SYSSTATS_INFO     STATUS     NULL     COMPLETED
SYSSTATS_INFO     DSTART     NULL     02-16-2011 15:24
SYSSTATS_INFO     DSTOP     NULL     02-16-2011 15:24
SYSSTATS_INFO     FLAGS     1     NULL
SYSSTATS_MAIN     CPUSPEEDNW     1321.20523     NULL
SYSSTATS_MAIN     IOSEEKTIM     10     NULL
SYSSTATS_MAIN     IOTFRSPEED     4096     NULL
SYSSTATS_MAIN     SREADTIM     NULL     NULL
SYSSTATS_MAIN     MREADTIM     NULL     NULL
SYSSTATS_MAIN     CPUSPEED     NULL     NULL
SYSSTATS_MAIN     MBRC     NULL     NULL
SYSSTATS_MAIN     MAXTHR     NULL     NULL
SYSSTATS_MAIN     SLAVETHR     NULL     NULL

Similar Messages

Different execution plans for the same sql

Hi,
Im testing our new 10gR2 database on Linux and I can't understand why the same query use different plan.
Here are the details.
Table name: invoice_detail
Records: About 10,670,900
Columns:
No
seq (the primary key is No+Seq). Each invoices contains +/- 10 invoice_details.
category ( <- 10 different values )
State ( <- 3 different values )
Basically, I have an index on the primary key and another index on Category + State.
My request:
select *
from invoice_detail
where no=123456 <- Best index to use
and state <> 'CANCEL'
and category = 'INVOICE'
If i run this query from Toad or sql+, that's fine.
The same query (i'm watching it from EM) executed via Forms use the category+state index.
When I first import the database, the last thing I do is to run DBMS_STATS.GATHER_DATABASE_STATS.
At this point, Forms use the right index.
The day after (after the database has been analyzed with the predefined job via EM) Forms use the wrong index.
I re-analyzed everything with exec DBMS_STATS.GATHER_DATABASE_STATS but the problem is still there.
Thanks in advance

I'm already using bind variables.
I changed the "Estimated Percentage" to 100% in "Gather Optimizer Statistics Default Options" and now it seems to use the correct index. I'm stressed because I dont understand why it chooses different plan for the same sql.
Actually, my users test the migration 1 day after I load all the data (drop schema-create schema-load data-analyze database) and at this point everythings go fine. After the second analyze of the database, the DB choose the wrong indexes.
I really cannot migrate until I understand why it happens.
Any ideas?
TIA

Multiple Executions Plans for the same SQL statement

Dear experts,
awrsqrpt.sql is showing multiple executions plans for a single SQL statement. How is it possible that one SQL statement will have multiple Executions Plans within the same AWR report.
Below is the awrsqrpt's output for your reference.
WORKLOAD REPOSITORY SQL Report
Snapshot Period Summary
DB Name         DB Id    Instance     Inst Num Release     RAC Host
TESTDB          2157605839 TESTDB1               1 10.2.0.3.0 YES testhost1
              Snap Id      Snap Time      Sessions Curs/Sess
Begin Snap:     32541 11-Oct-08 21:00:13       248     141.1
End Snap:     32542 11-Oct-08 21:15:06       245     143.4
   Elapsed:               14.88 (mins)
   DB Time:               12.18 (mins)
SQL Summary                            DB/Inst: TESTDB/TESTDB1 Snaps: 32541-32542
                Elapsed
   SQL Id      Time (ms)
51szt7b736bmg     25,131
Module: SQL*Plus
UPDATE TEST SET TEST_TRN_DAY_CL = (SELECT (NVL(ACCT_CR_BAL,0) + NVL(ACCT_DR_BAL,
0)) FROM ACCT WHERE ACCT_TRN_DT = (:B1 ) AND TEST_ACC_NB = ACCT_ACC_NB(+)) WHERE
TEST_BATCH_DT = (:B1 )
SQL ID: 51szt7b736bmg                  DB/Inst: TESTDB/TESTDB1 Snaps: 32541-32542
-> 1st Capture and Last Capture Snap IDs
   refer to Snapshot IDs witin the snapshot range
-> UPDATE TEST SET TEST_TRN_DAY_CL = (SELECT (NVL(ACCT_CR_BAL,0) + NVL(AC...
    Plan Hash           Total Elapsed                 1st Capture   Last Capture
#   Value                    Time(ms)    Executions       Snap ID        Snap ID
1   2960830398                 25,131             1         32542          32542
2   3834848140                      0             0         32542          32542
Plan 1(PHV: 2960830398)
Plan Statistics                        DB/Inst: TESTDB/TESTDB1 Snaps: 32541-32542
-> % Total DB Time is the Elapsed Time of the SQL statement divided
   into the Total Database Time multiplied by 100
Stat Name                                Statement   Per Execution % Snap
Elapsed Time (ms)                            25,131       25,130.7     3.4
CPU Time (ms)                                23,270       23,270.2     3.9
Executions                                        1            N/A     N/A
Buffer Gets                               2,626,166    2,626,166.0    14.6
Disk Reads                                      305          305.0     0.3
Parse Calls                                       1            1.0     0.0
Rows                                        371,735      371,735.0     N/A
User I/O Wait Time (ms)                         564            N/A     N/A
Cluster Wait Time (ms)                            0            N/A     N/A
Application Wait Time (ms)                        0            N/A     N/A
Concurrency Wait Time (ms)                        0            N/A     N/A
Invalidations                                     0            N/A     N/A
Version Count                                     2            N/A     N/A
Sharable Mem(KB)                                 26            N/A     N/A
Execution Plan
| Id | Operation                    | Name            | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | UPDATE STATEMENT             |                 |       |       | 1110 (100)|          |
|   1 | UPDATE                      | TEST            |       |       |            |          |
|   2 |   TABLE ACCESS FULL          | TEST            |   116K| 2740K| 1110   (2)| 00:00:14 |
|   3 |   TABLE ACCESS BY INDEX ROWID| ACCT            |     1 |    26 |     5   (0)| 00:00:01 |
|   4 |    INDEX RANGE SCAN          | ACCT_DT_ACC_IDX |     1 |       |     4   (0)| 00:00:01 |
Plan 2(PHV: 3834848140)
Plan Statistics                        DB/Inst: TESTDB/TESTDB1 Snaps: 32541-32542
-> % Total DB Time is the Elapsed Time of the SQL statement divided
   into the Total Database Time multiplied by 100
Stat Name                                Statement   Per Execution % Snap
Elapsed Time (ms)                                 0            N/A     0.0
CPU Time (ms)                                     0            N/A     0.0
Executions                                        0            N/A     N/A
Buffer Gets                                       0            N/A     0.0
Disk Reads                                        0            N/A     0.0
Parse Calls                                       0            N/A     0.0
Rows                                              0            N/A     N/A
User I/O Wait Time (ms)                           0            N/A     N/A
Cluster Wait Time (ms)                            0            N/A     N/A
Application Wait Time (ms)                        0            N/A     N/A
Concurrency Wait Time (ms)                        0            N/A     N/A
Invalidations                                     0            N/A     N/A
Version Count                                     2            N/A     N/A
Sharable Mem(KB)                                 26            N/A     N/A
Execution Plan
| Id | Operation                    | Name         | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | UPDATE STATEMENT             |              |       |       |     2 (100)|          |
|   1 | UPDATE                      | TEST         |       |       |            |          |
|   2 |   TABLE ACCESS BY INDEX ROWID| TEST         |     1 |    28 |     2   (0)| 00:00:01 |
|   3 |    INDEX RANGE SCAN          | TEST_DT_IND |     1 |       |     1   (0)| 00:00:01 |
|   4 |   TABLE ACCESS BY INDEX ROWID| ACCT         |     1 |    26 |     4   (0)| 00:00:01 |
|   5 |    INDEX RANGE SCAN          | INDX_ACCT_DT |     1 |       |     3   (0)| 00:00:01 |
Full SQL Text
SQL ID       SQL Text
51szt7b736bm UPDATE TEST SET TEST_TRN_DAY_CL = (SELECT (NVL(ACCT_CR_BAL, 0) +
              NVL(ACCT_DR_BAL, 0)) FROM ACCT WHERE ACCT_TRN_DT = (:B1 ) AND PB
             RN_ACC_NB = ACCT_ACC_NB(+)) WHERE TEST_BATCH_DT = (:B1 )Your input is highly appreciated.
Thanks for taking your time in answering my question.
Regards

Oracle Lover3 wrote:
Dear experts,
awrsqrpt.sql is showing multiple executions plans for a single SQL statement. How is it possible that one SQL statement will have multiple Executions Plans within the same AWR report.If you're using bind variables and you've histograms on your columns which can be created by default in 10g due to the "SIZE AUTO" default "method_opt" parameter of DBMS_STATS.GATHER__STATS it is quite normal that you get different execution plans for the same SQL statement. Depending on the values passed when the statement is hard parsed (this feature is called "bind variable peeking" and enabled by default since 9i) an execution plan is determined and re-used for all further executions of the same "shared" SQL statement.
If now your statement ages out of the shared pool or is invalidated due to some DDL or statistics gathering activity it will be re-parsed and again the values passed in that particular moment will determine the execution plan. If you have skewed data distribution and a histogram in place that reflects that skewness you might get different execution plans depending on the actual values used.
Since this "flip-flop" behaviour can sometimes be counter-productive if you're unlucky and the values used to hard parse the statement leading to a plan that is unsuitable for the majority of values used afterwards, 11g introduced the "adaptive" cursor sharing that attempts to detect such a situation and can automatically re-evaluate the execution plan of the statement.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Schedule parallel activities on different resources for the same period

Hi,
I am trying to create a PPM where I need to define parallel activities on different resources for the same time period.
For example:
Input prod: P1
Output prod: O1
Now I define a dummy activity A1 to define this consumption i.e. 1 PC of P1 gives 1 PC of O1.
Now I have got 3 resources R1, R2, R3.
I define 3 activities A2, A3, A4 for these resources.
Now I have to arrange activities A2, A3, A4 such that they start simultaneouly after activity A1 and also end simultaneouly.
The Fixed duration for all the resources is 1 week.
My requirement is that out of these resources system should plan for demand considering the resource with minimum capacity
i.e. kind of bottleneck resource.
I am using CTM engine for planning.
I have defined A1 as predecessor for all the 3 activities A2, A3, A4 and after completion all the activities have a dummy successor activity S.
But this setting is not working and PPM is not getting exploded, If I use a normal linear relationship between activities it works fine but my requirement is not getting satisfied.
Can anyone please help me in this case or suggest some alternate method.
Thanks & Regards,
Sanjog Mishrikotkar

Hi,
You cannot use the old solman key as systems are on different server.
I think you have to delete the old Dev system and then generate new solman key.
Thanks
Sunny

[JAXB] Several different prefixes for the same namespace

Hi!
I have generated some code from 2 schemas using JAXB. One of them (the main) defines some elements and the other one defines values for those elements. Then, when runring my code, I get an XML document with elements from the main schema an elements from the other one. However, elements from the second schema are qualified with different names. That is:
<party>
<ns3:uid xmlns:ns3="http:/schema1.com/schema1">CN=User1 - RSA/RSA,OU=IAIK,O=TU Graz,C=AT</ns3:uid>
<ns4:role xmlns:ns4="http:/schema1.com/schema1">client</ns4:role>
</party>
As you can see, I get two different prefixes for the same namespace.
Could you be so kind as to tell me if there is a way of getting only one prefix for each namespace, please? Do I have to modify JAXB compiler's properties???
Thanks a lot in advance.

No, I don't know how to do that. I also don't think it should matter. Are these multiple prefixes causing you any problems other than offending against Occam's Razor?

Filter the content on different queries for the same infoprovider and user

Hello,
We are trying to make the following security scenario in BI, and have
problem with the analysis object concept to filter at query level.
The idea is to permit to :
- user A
  - to execute query Q1 and view information about sites 1,2,3
  - to execute query Q2 and view information about sites 4,5,6
but for example for another user :
- user B
  - to execute query Q1 and view information about site 1,3
  - to execute query Q2 and view information about site 5,6,7
Q1 and Q2 are queries from the same infoprovider.
The idea is to make an automatic generation of analysis objects based
on the standard program : RSEC_GENERATE_AUTHORIZATIONS.
During tests, we have faced a problem with the object 0TCTQUERY that we
thought will permit us to filter at the query level, but unless we add
the name on the query on a role in the S_RS_COMP authorization object,
field RSZCOMPID, the query is not granted to the user.
The fact that we use both authorization objects : one for the query
definition, and another for the analysis authorization concept
(S_RS_AUTH, field BIAUTH), has disastrous effect : all values given in
the analysis objects are for all queries of an indicated infoprovider.
With that system, it's then not possible to propose dynamically different
views of the same data (ie from same infoprovider) based on the
authorization concept unless using the technic of customer-exit variable,
but with variable you will have a problem with old queries that doesn't
have a variable and that will permit to see all data given in the new
authorization objects.
Is there exists another object to filter at the query level in the
analysis objects ? If it's not the case, what is possible to do to reach
our goal with the new authorization concept ?
Thank you in advance for your help.
Best regards,
Gaël.

The data is protected on infoprovider level and not on the query level, so when two querys are build from the same Infoprovider then the authorizations are the same,
To achieve what you want to do, the querys must be built off different providers.   This can be achieved by placing the infoprovider in 2 differnt multiproviders and building the querys and authorizations seperatly on these.

APs using different channels for the same SSID

Hi,
This might be a stupid question, but I am wondering why my Aironet 1602i and 2602i access points connected to the same controller would use different channels for the same network. Would this be to avoid interference? If so, I am planning to put 9 access points throughout the office and they will be fairly close to each other. Would this increase the risk of interference?
Thanks,
Tibet

That is normal. The WLC is determining the best channel and being in different channels is the best. When you add more, the WLC will decide by the use if RRM what channels and power levels to allocate to each AP.
Sent from Cisco Technical Support iPhone App

If I already have a particular app under one apple Id and I purchase the same app under a different Id for the same device, will it overwrite or replace the previous or will I have two of the same app on the same device??

If I already have a particular app under one apple Id and I purchase the same app under a different Id for the same device, will it overwrite or replace the previous or will I have two of the same app on the same device??
I'm asking because I purchased an app with an id that has been cancelled so I cannot update that particular app. I can purchase the app with my new id but I don't want to do so if its going to erase all the data I have with the previous purchase...

Figured it out. Thanks.

Different authorizations on different cubes for the same characteristic

Hello,
Is it possible to implement different authorizations on different groups for the cubes characteristic?
For example a user should be authorized to see just the data of company code 101 on Cube A but he should see the data of all company codes on Cube B (Cube B also contains the company code. ":"-Authorization is not an option)?
In transaction RSECADMIN it is possible to insert the "special characteristics" Acitivty, InfoProvider and Validity into an authorization. But standard setting for InfoProvider is * and I get an error message if I want to modify for just 1 Cube because the characteristic "InfoProvider" (SAP Content) isn't marked as authorization relevant.
Can you please answer:
1) If it is possible to implement different authorizations on different cubes for the same characteristic?
2) What is the function of the special charactristics if I can't maintain the values?
Thank you
Johannes

Hi there,
Yes it is possible.
The new authorization concept created union also based on InfoProvider Characteristic.
You have to change in rsd1 transaction the characteristics 0TCAACTVT, 0TCAKYFNM, 0TCAIPROV and 0TCAVALID to be authorization relevant.
So you can do this:
Create two authorizations in rsecadmin like this:
Aut_1:
0comp_code: 101
0TCAACTVT: 03 (activity of display)
0TCAKYFNM: * (all key figures)
0TCAIPROV: Cube A
0TCAVALID: * (authorization valid for ever)
Aut_2:
0comp_code: *
0TCAACTVT: 03 (activity of display)
0TCAKYFNM: * (all key figures)
0TCAIPROV: Cube B
0TCAVALID: * (authorization valid for ever)
Now in rsecadmin give both authorizations aut_1 and aut_2 for the user.
If the user opens a query built on cube a he will be having authorizations only for company code 101. If the user opens a query for cube B he will be having authorizations for all the company codes.
Diogo.

Invoice posting with different currency for the same PO

Hi,
Can we post the the Invoice with different currencies for the same PO.
For example.
PO has Qty 100 pcs. amount 100 USD
GR Qty 100 pcs.
Is it possible to post Invoice of 50 pc with 50 USD, and 50pcs with some other currency.
Any sugggestions pls.
Thanks,
Satya

Hello
As per my knowledge, that is not possible.
And in whjat scenario, we need to do that?
In MIRO header itself we have the vendor currency, so it is not posbile to maintain different currency in different line items in MIRO.
If you want, you can do MIRO in different currency that what is in PO.
In the example given, you have o post 2 invoices, one for 50 qty in USD and the other 50 in different currency in other invoice transaction by giving the currency in basic data-invoice header and then only press ENTER after giving the PO number.
Hope this helps
Regards

Outlook-2 different entries for the same person (but not the same email)

i was asked to switch from outlook 2007 to outlook 2013 as a trial.
For some reason, I get two different entries for the same person (but not the same email), one which is the name as normal and one where the name has ' around it. In the below example:
I have 24 emails sent to Ciaran and then a further 14 sent to 'Ciaran'
The email address for both is exactly the same and it does not seem to matter if I create a new email or reply to an incoming one.
I switched back to Outlook 2007 and the issue is still the same.
any suggestions?

I would say that there is no way to prevent Outlook from doing it, it dependents on how the sender formatted the sending address, not the recipient who replies.
To fix this:
Open the message and double click the address and view source
Just replace the generated Display As with the Display As you want
Thanks,
Ethan Hua CHN
TechNet Community Support

PT_QTA00 is generating repetative records for the same quota type

PT_QTA00 is generating repetative records for the same quota type and one more thing i have already maintained 10 days of quota in 2006 and when i run for the same employee its creating one more record with 10 days again how can we restrict it in configuration

As said earlier, you want to setup Time Constraints for It2006 which is in table: V_T582A
You should set the Time Constraint to 2.
HR master data uses the following three time constraints:
Time Constraint 1
For the entire time that the employee works at the enterprise, exactly one valid infotype record must exist. The validity periods of the individual records must not overlap. If a new record is created, the system automatically uses the start date of the new record as the delimitation date of the old record. Gaps are only allowed between the employeeu2019s entry date and the start date of the first record.
Time constraint 1 must be used for all of the infotypes containing information that must be available at all times. This is particularly true of personal and organizational assignment data.
If a record is delimited because of time constraint 1, the system displays an appropriate message.
Time Constraint 2
No more than one valid record can exist at any one time. Records with constraint 2 must not overlap. Their existence is not obligatory. If a new record is created, the system automatically delimits the previous record, if one exists.
If a record is delimited because of time constraint 2, the system displays an appropriate message.
Time Constraint 3
Any number of valid records can exist at any one time. The individual records do not conflict with each other.

Multiple MM schedule lines for the same date

Hello All Gurus,
I am facing a problem where the MM schedule lines are divided into various quantites for the same date. For example on 02/11/2010 the total quantity is 120, it is appearing in the below form in ME38:
02/11/2010 - 40
02/11/2010 - 40
02/11/2010 - 40
Although this is not an error, but my client is not happy with this. Can someone tell me why I am getting this error? Is it because of the rounding value that we maintain in MRP 1 view of material master record? Or is there any other setting that I am missing?
Please let me know. I would be very much thankful to you.
Thanks and Regards,
Umakanth

Hi,
Before changing the setup, note that sometimes it is beneficial to split one demand into multiple delivery schedules. Especially if the demand is bigger than equipment type (container/truck etc.). If you want to manage inbound transportation for such delivery schedules, it is much simpler to do this when each delivery schedule is not bigger than one equipment.
Regards,
Dominik Modrzejewski

I bought an iphone 5 about 4 months ago and got applecare. yesterday I had to get on a different plan within the same company so i traded in my phone and got a new iphone 5. can i transfer my applecare to this new phone or would I have to buy it again?

I bought a 16gb iphone 5 about 3 months ago and got applecare. yesterday I had to get on a different plan within the same company so i traded in my phone and got a new 32gb iphone 5. can i transfer my applecare to this new phone or would I have to buy it again?

As this is a WW forum with different AppleCrare offerings you need to specify which Country
as in North America has AppleCare+ and everywhere else AppleCare ,very different products
So to avoid incorrect guidance suggest you specify Country

Can we get a output in different languages for the same configuration

Hi All,
Can we get a output in different languages for the same configuration done in NACE. or it is language specific.
They have symbols which have values both in german and english. But when we run the transaction we are getting the output only in german language.We want the out put in english
language.
Thanks in Advance.
Rajesh

A Smartform can be maintained in many languages other than the language that it is created. Translations for the texts have to be maintained for this purpose.
To maintain the translations:
Go to transaction SE63 in R/3.
Go to menu Translation->R/3 Enterprise->Other Long Texts
Select the object type in the pop up. Smartform(SSF) object type is found under Forms and Styles(FS).
Enter the name of the Smart form and choose the source and target language. This would open a screen with the Smartform code in Source language on the top and an editor with the same code in the bottom.
Find the text for which you need to maintain the translation and insert the translation in that place. As usual after required texts are maintained Save and Activate.
To see the translated Smartform create an output type and assign the smartform and the driver program to this output type. In the transaction that sends output to this smartform, select the output type and select the language in which the smartform has to be displayed (translations have to be maintained in this lanuage).This will give the smartform in the required language.
Madhavi

CBO generating different plans for the same data in similar Environments

Similar Messages

Maybe you are looking for