With new Free Characeristics Aggregates are not being used

Hi....i have a query from a multicube with two infocubes where i  have two aggregates one for each cube...in my query both aggregates are being used with no problems....when i add a new free characteristic that appers on aggregates something happens and the aggregates are not being used anymore...i dont understand why this happens because i know that ......free characteristics ....doesnt affects the aggregates usage....is this correct??? or not?
Regards

Since this is an open forum, not Adobe support... you need to contact Adobe staff to help
Adobe contact information - http://helpx.adobe.com/contact.html
-Select your product and what you need help with
-Click on the blue box "Still need help? Contact us"
-or by telephone http://helpx.adobe.com/x-productkb/global/phone-support-orders.html

Similar Messages

  • Some CD's with music burned to it, are not being recognized as having music files on them.

    Some CD's with music burned to it, are not being recognized as having music files on them.

    The format says Mac OS Extended.  All of the settings were set during the disk image restore process.  Even if I format the flash drive as extended journaled or some other format, all of these settings are reverted when I do the restore from the disk image.  I will just copy all of the information that disk utility has so that you can see it.
    Mount Point :     /Volumes/Mac OS X Install ESD     Capacity :     16.11 GB (16,106,110,976 Bytes)       Format :     Mac OS Extended     Available :     12.3 GB (12,303,499,264 Bytes)       Owners Enabled :     Yes     Used :     3.8 GB (3,802,611,712 Bytes)       Number of Folders :     128     Number of Files :     876

  • How to tell which Indexes are not being used?

    We are a large development shop and have many customers. Our database design is very generic so that it works for all of our customers. Each night we use an SSIS ETL process to bring down large amounts of data from the iSeries into SQL. One
    particularily large customer takes a very long time and we are looking for ways to speed up thier data import and transformation. I would like to see which indexes he does not use and possibly remove them. Each night we fully repopulate hundreds of staging
    and ods tables and incrementally delete and repopulate the days work for a handful of history type tables. Removing some indexes off of the large tables could make a big impact. 
    How can i tell which indexes the customer does not use?

    > IDENTIFYING UNUSED INDEXES IN A SQL SERVER DATABASE 
       Just because an index is not being used does not necessarily mean it should be removed.
    > Index This: All About SQL Server Indexes
    sp_BlitzIndex
    José Diz     Belo Horizonte, MG - Brasil

  • Spooling out profile that are not being used

    hi guys,
    is there anyway to spool out those profile that are not in used or assigned to any username or roles?

    flaskvacuum wrote:
    hi guys,
    is there anyway to spool out those profile that are not in used or assigned to any username or roles?
    SQL> CREATE PROFILE test LIMIT
      2     FAILED_LOGIN_ATTEMPTS 5
      3     PASSWORD_LIFE_TIME 60
      4     PASSWORD_REUSE_TIME 60
      5     PASSWORD_REUSE_MAX 5
      6     PASSWORD_VERIFY_FUNCTION null
      7     PASSWORD_LOCK_TIME 1/24
      8     PASSWORD_GRACE_TIME 10;
    Profile created.
    -- Created but not assigned --
    SQL> select distinct profile from dba_profiles where profile not in (select profile from dba_users);
    PROFILE
    TEST
    SQL>

  • Photo Geo tags are not being used by Places

    I have been importing photos into iPhoto with valid geo tags and none of the photos are being shown on the Places map.
    When I initially starting using iPhoto I imported some pictures from my iPhone and realised that the pictures were identified on the Places maps automatically, since I have added photos and manually edited the location information directly in Places.
    If I import pictures from my iPhone they are not entered into Places and if you check all the location information is blank, if you look at the extended information you can see all the correct GPS information...
    I'm confused..

    in your iPhoto preferences is look up places set to "Automatically"? The default is "never" and it must be changed to "automatically" to work.
    LN

  • How to free space that is not being used?

    I have a tablespace with very few data (0.18 Mb) but somehow Oracle is using 10Gb for this tablespace, the tablespace is this one:
    Tablespace Name and Mb FREE_SPACE USED_SPACE TOTAL_SPACE
    HIST_PROMOTIONS_IDX 10099,8125 ,1875 10100
    The tablespace is composed by this 3 data files:
    FILE_NAME ALLOCATED_MB USED_MB FREE_SPACE_MB
    /oraindices/IRI9/data/HIST_PROM_ID1.dbf 5000.00 .06 4999.94
    /oraindices/IRI9/data/HIST_PROM_ID2.dbf 100.00 .06 99.94
    /oraindices/IRI9/data/HIST_PROM_ID3.dbf 5000.00 .06 4999.94
    Is there any way to reasign the space usage for this tablespace?
    thanks

    If I read this correctly, only a couple of MB are used in that tablespace.
    The resize should work, but you'll still have 3 datafiles where 1 would suffice. Also, sometimes, it will give you an error because blocks are located towards the end of the file.
    I would create a new tablespace using the size being used and move the objects in the large tablespace into this new one (move tables and rebuild indexes). When all is completed, take the large tablespace offline and, if all works well after a couple of days, drop that large tablespace.

  • How do I delete places in the organizer that are not being used?

    In Elements Organizer 12, I think I accidentally created a "place" on the map that I do not want to apply to any photos.  When I try to do conduct an advanced search, the place is appearing as a checkbox.  I do not want this place to show up in the search field, as we have never been there.  How do I remove places that are not associated with any photos?

    If you are accessing emails from multiple devices, you are better off using the IMAP protocol. Then the devices sync with the server and they are all looking at the same information. With POP, you are going to get your emails spread about, some on Outlook, some on the iPad. It could get very confusing.
    By default, the iPad will not delete from a POP server. Instructions for changing this are here: http://support.apple.com/kb/HT3228

  • How to remove the bufgs that are not being used

    Hi,
    I have a IP block that has BUFGs that may or may not be used depending on which design the IP block is used. If they are not used I would like them to be removed but the tools are not consistent, sometimes they remove them and sometimes they do not.
    How do I specifically tell Vivado to remove a BUFG in the .XDC file?
    I've seen someone suggest to use the following attribute in the VHDL file but I need something in the XDC file
    attribute buffer_type of drck_i : signal is "none";
    Thank you,
    Luis

    Hi 
    If the BUFG instance is instantiated in the IP or your design then the buffer_type attribute will not work.
    The opt_design trims the unconnected instances during implementation. Ensure that the BUFG does not have  DONT_TOUCH property set on it which might affect trimming.
    Thanks,
    Deepika.

  • How to identify SQL_PROFILES that are not being used?

    In dba_hist_sqlstat table were found 26 Sql_Profiles, some of them are not used.
    Questions:
    - Is there any way to identify which one are not used?
    I tried verifying DBA_SQL_PROFILES but this does not help to much.
    - Analyzing one by one, Is the only way to find why they are not used?
    Thanks,
    Deyanira

    Hello;
    You should be able to Join the views DBA_USERS and DBA_PROFILES to see whats in use. ( or not in use )
    select distinct
      profile
    from
      dba_profiles
    where
      profile not in ( select profile from dba_users )  On the second question I would ask the DBA.
    Best Regards
    mseberg
    Dan is correct. I have misread the question. Sorry about that.
    Edited by: mseberg on Jun 28, 2012 3:06 PM

  • New Iphone 6 messages are not being read

    I just bought the new iPhone 6 (64gb) about 3 days ago. The problem I am facing is that every time I get a message on my phone (be it text or iMessage), I open it, reply to it, and then quit the application but the blue badge icon (implying that I have an unread message) is still on. I went to the Apple store yesterday and changed my phone but the new one still has the same problem. I have to read the messages twice for the blue badge icon to disappear. I tried restarting the phone, resetting it, turning the badge icon on and off, basically everything I read on different forums. Nothing worked. Does anyone have any idea on how to fix this or is this a common bug with iOS 8?

    Mark, my issue was a result of too much fatigue and too few brains. I had merely forgotten to turn on pairing on my bluetooth device. Once I realized my idiotic mistake, it worked immediately. Don’t know what the problem on your side could be. I believe the newest bluetooth technology (iPhone 6) is backward compatible with the oldest bluetooth technology (headphones) so it should work. Might want to check out this link iOS: Troubleshooting Bluetooth connections Good luck!

  • Is there a way of telling if tables in a schema are not being used?

    I've thought about using the AUDIT_TRAIL.
    Is there any query that you can run to tell this, without setting this up?

    v$segment_statistics is one of the accumulator views that gets reset when the database is bounced. You'll probably want to take snapshots of the view regularly into a separate history table because of that.
    Remember that you need to monitor for an appropriate period of time (you may have objects that are used only at month-end, only at year-end, or only for some process that happens on an irregular basis) to ensure that the objects are really and truly unused. Make sure that the business unit agrees as well-- there are plenty of tables that are kept around solely to comply with data retention policies. Dropping one of those tables caan quickly become a career limiting move should there ever be a records request from the legal department.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Nested subQuery results are not being used by Oracle 10g

    Hello, I'm doing the follow query that has a Nested subquery, The explain plan is showing me that Oracle is doing a INDEX FULL SCAN, but I don't understand why?
    select *
    from rdbmx.resources_vt r
    , rdbmx.rsrc_case_qpmcsis_x_vn rad
    where (rad.resource_id,rad.resource_tp) in (
    select t.item_id
    , t.item_tp
    from rdbmx_site.att_hierarchy_level_vw t
    where t.rootitem_id = r.resource_id)
    and r.resource_id =3780
    and r.resource_tp ='BITUMENPRODUCTION'
    and rad.CASE_ID = 599
    and rad.CASE_TP = 'MEASURED'
    and rad.property_nm ='Liquid Volume Flow'
    and rad.qualifier_nm='n/a'
    ATT_HIERARCHY_LEVEL_VW is a complex view and RSRC_CASE_QPMCSIS_X_VN is a view with a UNION ALL.
    The explain plan I'm getting from above query is the follow:
    If you can see on RSRC_CASE_QPMCSI_X_VN vies Oracle is doing a INDEX FULL SCAN over RESOURCE table instead of INDEX RANGE SCAN but I don't undestand why because I'm providing the right values in order to use the right indexes for ORACLE 10gR2. I made a 10053 trace and look seem that oracle is not using the values from the nested query in order to get the better way to pull the information.
    SELECT STATEMENT, GOAL = ALL_ROWS     Id=0     Position=4917          Cost=4917     Cardinality=1     Bytes=21968
    HASH JOIN     Id=1     Position=1          Cost=4917     Cardinality=1     Bytes=21968
    NESTED LOOPS     Id=2     Position=1          Cost=560     Cardinality=1     Bytes=170
    TABLE ACCESS BY INDEX ROWID     Id=3     Position=1     Object name=RESOURCES     Cost=2     Cardinality=1     Bytes=115
    INDEX UNIQUE SCAN     Id=4     Position=1     Object name=RESOURCES_PK     Cost=1     Cardinality=1     
    SORT UNIQUE     Id=5     Position=2          Cost=558     Cardinality=1     Bytes=55
    VIEW     Id=6     Position=1     Object name=ATT_HIERARCHY_LEVEL_VW     Cost=558     Cardinality=1     Bytes=55
    SORT UNIQUE     Id=7     Position=1          Cost=558     Cardinality=3353     Bytes=1181117
    UNION-ALL     Id=8     Position=1                    
    SORT UNIQUE     Id=9     Position=1          Cost=3     Cardinality=1     Bytes=19
    INDEX RANGE SCAN     Id=10     Position=1     Object name=ATTACHITEM_PK     Cost=2     Cardinality=1     Bytes=19
    TABLE ACCESS BY INDEX ROWID     Id=11     Position=2     Object name=ATTACHITEM     Cost=4     Cardinality=43     Bytes=2623
    INDEX RANGE SCAN     Id=12     Position=1     Object name=ATTACHITEM_F3     Cost=2     Cardinality=43     
    NESTED LOOPS     Id=13     Position=3          Cost=5     Cardinality=61     Bytes=6283
    INDEX RANGE SCAN     Id=14     Position=1     Object name=ATTACHITEM_X1     Cost=2     Cardinality=43     Bytes=1806
    TABLE ACCESS CLUSTER     Id=15     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=61
    INDEX UNIQUE SCAN     Id=16     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    NESTED LOOPS     Id=17     Position=4          Cost=10     Cardinality=87     Bytes=12615
    NESTED LOOPS     Id=18     Position=1          Cost=5     Cardinality=61     Bytes=5124
    INDEX RANGE SCAN     Id=19     Position=1     Object name=ATTACHITEM_X1     Cost=2     Cardinality=43     Bytes=1806
    TABLE ACCESS CLUSTER     Id=20     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=21     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=22     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=61
    INDEX UNIQUE SCAN     Id=23     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    NESTED LOOPS     Id=24     Position=5          Cost=17     Cardinality=124     Bytes=23188
    NESTED LOOPS     Id=25     Position=1          Cost=10     Cardinality=87     Bytes=10962
    NESTED LOOPS     Id=26     Position=1          Cost=5     Cardinality=61     Bytes=5124
    INDEX RANGE SCAN     Id=27     Position=1     Object name=ATTACHITEM_X1     Cost=2     Cardinality=43     Bytes=1806
    TABLE ACCESS CLUSTER     Id=28     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=29     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=30     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=31     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=32     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=61
    INDEX UNIQUE SCAN     Id=33     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    NESTED LOOPS     Id=34     Position=6          Cost=27     Cardinality=176     Bytes=40304
    NESTED LOOPS     Id=35     Position=1          Cost=17     Cardinality=124     Bytes=20832
    NESTED LOOPS     Id=36     Position=1          Cost=10     Cardinality=87     Bytes=10962
    NESTED LOOPS     Id=37     Position=1          Cost=5     Cardinality=61     Bytes=5124
    INDEX RANGE SCAN     Id=38     Position=1     Object name=ATTACHITEM_X1     Cost=2     Cardinality=43     Bytes=1806
    TABLE ACCESS CLUSTER     Id=39     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=40     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=41     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=42     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=43     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=44     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=45     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=61
    INDEX UNIQUE SCAN     Id=46     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    NESTED LOOPS     Id=47     Position=7          Cost=41     Cardinality=251     Bytes=68021
    NESTED LOOPS     Id=48     Position=1          Cost=27     Cardinality=176     Bytes=36960
    NESTED LOOPS     Id=49     Position=1          Cost=17     Cardinality=124     Bytes=20832
    NESTED LOOPS     Id=50     Position=1          Cost=10     Cardinality=87     Bytes=10962
    NESTED LOOPS     Id=51     Position=1          Cost=5     Cardinality=61     Bytes=5124
    INDEX RANGE SCAN     Id=52     Position=1     Object name=ATTACHITEM_X1     Cost=2     Cardinality=43     Bytes=1806
    TABLE ACCESS CLUSTER     Id=53     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=54     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=55     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=56     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=57     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=58     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=59     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=60     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=61     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=61
    INDEX UNIQUE SCAN     Id=62     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    NESTED LOOPS     Id=63     Position=8          Cost=60     Cardinality=356     Bytes=111428
    NESTED LOOPS     Id=64     Position=1          Cost=41     Cardinality=251     Bytes=63252
    NESTED LOOPS     Id=65     Position=1          Cost=27     Cardinality=176     Bytes=36960
    NESTED LOOPS     Id=66     Position=1          Cost=17     Cardinality=124     Bytes=20832
    NESTED LOOPS     Id=67     Position=1          Cost=10     Cardinality=87     Bytes=10962
    NESTED LOOPS     Id=68     Position=1          Cost=5     Cardinality=61     Bytes=5124
    INDEX RANGE SCAN     Id=69     Position=1     Object name=ATTACHITEM_X1     Cost=2     Cardinality=43     Bytes=1806
    TABLE ACCESS CLUSTER     Id=70     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=71     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=72     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=73     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=74     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=75     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=76     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=77     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=78     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=79     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=80     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=61
    INDEX UNIQUE SCAN     Id=81     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    NESTED LOOPS     Id=82     Position=9          Cost=88     Cardinality=507     Bytes=179985
    NESTED LOOPS     Id=83     Position=1          Cost=60     Cardinality=356     Bytes=104664
    NESTED LOOPS     Id=84     Position=1          Cost=41     Cardinality=251     Bytes=63252
    NESTED LOOPS     Id=85     Position=1          Cost=27     Cardinality=176     Bytes=36960
    NESTED LOOPS     Id=86     Position=1          Cost=17     Cardinality=124     Bytes=20832
    NESTED LOOPS     Id=87     Position=1          Cost=10     Cardinality=87     Bytes=10962
    NESTED LOOPS     Id=88     Position=1          Cost=5     Cardinality=61     Bytes=5124
    INDEX RANGE SCAN     Id=89     Position=1     Object name=ATTACHITEM_X1     Cost=2     Cardinality=43     Bytes=1806
    TABLE ACCESS CLUSTER     Id=90     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=91     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=92     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=93     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=94     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=95     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=96     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=97     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=98     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=99     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=100     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=101     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=102     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=61
    INDEX UNIQUE SCAN     Id=103     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    NESTED LOOPS     Id=104     Position=10          Cost=128     Cardinality=721     Bytes=286237
    NESTED LOOPS     Id=105     Position=1          Cost=88     Cardinality=507     Bytes=170352
    NESTED LOOPS     Id=106     Position=1          Cost=60     Cardinality=356     Bytes=104664
    NESTED LOOPS     Id=107     Position=1          Cost=41     Cardinality=251     Bytes=63252
    NESTED LOOPS     Id=108     Position=1          Cost=27     Cardinality=176     Bytes=36960
    NESTED LOOPS     Id=109     Position=1          Cost=17     Cardinality=124     Bytes=20832
    NESTED LOOPS     Id=110     Position=1          Cost=10     Cardinality=87     Bytes=10962
    NESTED LOOPS     Id=111     Position=1          Cost=5     Cardinality=61     Bytes=5124
    INDEX RANGE SCAN     Id=112     Position=1     Object name=ATTACHITEM_X1     Cost=2     Cardinality=43     Bytes=1806
    TABLE ACCESS CLUSTER     Id=113     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=114     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=115     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=116     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=117     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=118     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=119     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=120     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=121     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=122     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=123     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=124     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=125     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=126     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=127     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=61
    INDEX UNIQUE SCAN     Id=128     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    NESTED LOOPS     Id=129     Position=11          Cost=174     Cardinality=1026     Bytes=450414
    HASH JOIN     Id=130     Position=1          Cost=117     Cardinality=721     Bytes=272538
    NESTED LOOPS     Id=131     Position=1          Cost=88     Cardinality=507     Bytes=170352
    NESTED LOOPS     Id=132     Position=1          Cost=60     Cardinality=356     Bytes=104664
    NESTED LOOPS     Id=133     Position=1          Cost=41     Cardinality=251     Bytes=63252
    NESTED LOOPS     Id=134     Position=1          Cost=27     Cardinality=176     Bytes=36960
    NESTED LOOPS     Id=135     Position=1          Cost=17     Cardinality=124     Bytes=20832
    NESTED LOOPS     Id=136     Position=1          Cost=10     Cardinality=87     Bytes=10962
    NESTED LOOPS     Id=137     Position=1          Cost=5     Cardinality=61     Bytes=5124
    INDEX RANGE SCAN     Id=138     Position=1     Object name=ATTACHITEM_X1     Cost=2     Cardinality=43     Bytes=1806
    TABLE ACCESS CLUSTER     Id=139     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=140     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=141     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=142     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=143     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=144     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=145     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=146     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=147     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=148     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=149     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=150     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    TABLE ACCESS CLUSTER     Id=151     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=42
    INDEX UNIQUE SCAN     Id=152     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    INDEX FAST FULL SCAN     Id=153     Position=2     Object name=ATTACHITEM_X1     Cost=28     Cardinality=11318     Bytes=475356
    TABLE ACCESS CLUSTER     Id=154     Position=2     Object name=ATTACHITEM     Cost=1     Cardinality=1     Bytes=61
    INDEX UNIQUE SCAN     Id=155     Position=1     Object name=ITEMCLUSTER_CLK     Cost=0     Cardinality=1     
    VIEW     Id=156     Position=2     Object name=RSRC_CASE_QPMCSIS_X_VN     Cost=4356     Cardinality=2     Bytes=43596
    UNION-ALL     Id=157     Position=1                    
    NESTED LOOPS     Id=158     Position=1          Cost=3730     Cardinality=1     Bytes=561
    NESTED LOOPS     Id=159     Position=1          Cost=3729     Cardinality=1     Bytes=475
    HASH JOIN     Id=160     Position=1          Cost=3727     Cardinality=1     Bytes=372
    TABLE ACCESS BY INDEX ROWID     Id=161     Position=1     Object name=RSRCTP_QPMCS     Cost=45     Cardinality=198     Bytes=13662
    INDEX RANGE SCAN     Id=162     Position=1     Object name=RSRCTP_QPMCS_F6     Cost=2     Cardinality=198     
    MERGE JOIN CARTESIAN     Id=163     Position=2          Cost=3682     Cardinality=101     Bytes=30603
    NESTED LOOPS     Id=164     Position=1          Cost=3682     Cardinality=101     Bytes=28684
    HASH JOIN     Id=165     Position=1          Cost=3682     Cardinality=102     Bytes=27030
    TABLE ACCESS BY INDEX ROWID     Id=166     Position=1     Object name=RESOURCES     Cost=2692     Cardinality=92717     Bytes=7973662
    INDEX FULL SCAN     Id=167     Position=1     Object name=RESOURCES_X1     Cost=196     Cardinality=92717     
    TABLE ACCESS FULL     Id=168     Position=2     Object name=RSRC_CASE_QPMCSI     Cost=556     Cardinality=102     Bytes=18258
    INDEX UNIQUE SCAN     Id=169     Position=2     Object name=RESOURCES_PK     Cost=0     Cardinality=1     Bytes=19
    BUFFER SORT     Id=170     Position=2          Cost=3682     Cardinality=1     Bytes=19
    INDEX UNIQUE SCAN     Id=171     Position=1     Object name=RESOURCES_PK     Cost=0     Cardinality=1     Bytes=19
    TABLE ACCESS BY INDEX ROWID     Id=172     Position=2     Object name=RSRCTP_QPMCS     Cost=2     Cardinality=1     Bytes=103
    INDEX RANGE SCAN     Id=173     Position=1     Object name=RSRCTP_QPMCS_F3     Cost=1     Cardinality=1     
    TABLE ACCESS BY INDEX ROWID     Id=174     Position=2     Object name=RESOURCES     Cost=1     Cardinality=1     Bytes=86
    INDEX UNIQUE SCAN     Id=175     Position=1     Object name=RESOURCES_PK     Cost=0     Cardinality=1     
    NESTED LOOPS ANTI     Id=176     Position=2          Cost=626     Cardinality=1     Bytes=662
    NESTED LOOPS     Id=177     Position=1          Cost=624     Cardinality=1     Bytes=582
    NESTED LOOPS     Id=178     Position=1          Cost=300     Cardinality=162     Bytes=77598
    NESTED LOOPS     Id=179     Position=1          Cost=138     Cardinality=162     Bytes=63666
    HASH JOIN     Id=180     Position=1          Cost=116     Cardinality=2     Bytes=614
    TABLE ACCESS BY INDEX ROWID     Id=181     Position=1     Object name=RSRCTP_QPMCS     Cost=45     Cardinality=198     Bytes=20394
    INDEX RANGE SCAN     Id=182     Position=1     Object name=RSRCTP_QPMCS_F6     Cost=2     Cardinality=198     
    MERGE JOIN CARTESIAN     Id=183     Position=2          Cost=70     Cardinality=263     Bytes=53652
    TABLE ACCESS FULL     Id=184     Position=1     Object name=RSRCTP_CASE_QPMCSI     Cost=70     Cardinality=263     Bytes=48655
    BUFFER SORT     Id=185     Position=2          Cost=0     Cardinality=1     Bytes=19
    INDEX UNIQUE SCAN     Id=186     Position=1     Object name=RESOURCES_PK     Cost=0     Cardinality=1     Bytes=19
    TABLE ACCESS BY INDEX ROWID     Id=187     Position=2     Object name=RESOURCES     Cost=11     Cardinality=101     Bytes=8686
    INDEX RANGE SCAN     Id=188     Position=1     Object name=RESOURCES_F1     Cost=2     Cardinality=138     
    TABLE ACCESS BY INDEX ROWID     Id=189     Position=2     Object name=RESOURCES     Cost=1     Cardinality=1     Bytes=86
    INDEX UNIQUE SCAN     Id=190     Position=1     Object name=RESOURCES_PK     Cost=0     Cardinality=1     
    TABLE ACCESS BY INDEX ROWID     Id=191     Position=2     Object name=RSRCTP_QPMCS     Cost=2     Cardinality=1     Bytes=103
    INDEX RANGE SCAN     Id=192     Position=1     Object name=RSRCTP_QPMCS_F3     Cost=1     Cardinality=1     
    INDEX RANGE SCAN     Id=193     Position=2     Object name=RSRC_CASE_QPMCSI_PK     Cost=2     Cardinality=1     Bytes=80

    Hello, I'm attaching the result from XPLAIN: The point I don't understand is why Oracle is doing INDEX FULL SCAN
    Why is doing it because I'm sending the index part when I'm doing :
    where (rad.resource_id,rad.resource_tp) in (
    6 select t.item_id
    7 , t.item_tp
    8 from rdbmx_site.att_hierarchy_level_vw t
    9 where t.rootitem_id = r.resource_id)
    Thanks for your help, I cannot put all on the same space so I'm putting two messages, the second one with the predicate information.
    SQL> EXPLAIN PLAN FOR
    2 select *
    3 from rdbmx.resources_vt r
    4 , rdbmx.rsrc_case_qpmcsis_x_vt rad
    5 where (rad.resource_id,rad.resource_tp) in (
    6 select t.item_id
    7 , t.item_tp
    8 from rdbmx_site.att_hierarchy_level_vw t
    9 where t.rootitem_id = r.resource_id)
    10 and r.resource_id =3780
    11 and r.resource_tp ='BITUMENPRODUCTION'
    12 and rad.CASE_ID = 599
    13 and rad.CASE_TP = 'MEASURED'
    14 and rad.property_nm ='Liquid Volume Flow'
    15 and rad.qualifier_nm='n/a';
    Explained.
    SQL> set linesize 150
    SQL> set pagesize 0
    SQL> SELECT * FROM table(DBMS_XPLAN.DISPLAY);
    Plan hash value: 3132073840
    | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
    | 0 | SELECT STATEMENT | | 1 | 6826 | 216K (1)| 00:43:19 |
    |* 1 | HASH JOIN | | 1 | 6826 | 216K (1)| 00:43:19 |
    | 2 | NESTED LOOPS | | 1 | 170 | 560 (1)| 00:00:07 |
    | 3 | TABLE ACCESS BY INDEX ROWID | RESOURCES | 1 | 115 | 2 (0)| 00:00:01 |
    |* 4 | INDEX UNIQUE SCAN | RESOURCES_PK | 1 | | 1 (0)| 00:00:01 |
    | 5 | SORT UNIQUE | | 1 | 55 | 558 (1)| 00:00:07 |
    |* 6 | VIEW | ATT_HIERARCHY_LEVEL_VW | 1 | 55 | 558 (1)| 00:00:07 |
    | 7 | SORT UNIQUE | | 3353 | 1153K| 558 (100)| 00:00:07 |
    | 8 | UNION-ALL | | | | | |
    | 9 | SORT UNIQUE | | 1 | 19 | 3 (34)| 00:00:01 |
    |* 10 | INDEX RANGE SCAN | ATTACHITEM_PK | 1 | 19 | 2 (0)| 00:00:01 |
    | 11 | TABLE ACCESS BY INDEX ROWID | ATTACHITEM | 43 | 2623 | 4 (0)| 00:00:01 |
    |* 12 | INDEX RANGE SCAN | ATTACHITEM_F3 | 43 | | 2 (0)| 00:00:01 |
    | 13 | NESTED LOOPS | | 61 | 6283 | 5 (0)| 00:00:01 |
    |* 14 | INDEX RANGE SCAN | ATTACHITEM_X1 | 43 | 1806 | 2 (0)| 00:00:01 |
    | 15 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 61 | 1 (0)| 00:00:01 |
    |* 16 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 17 | NESTED LOOPS | | 87 | 12615 | 10 (0)| 00:00:01 |
    | 18 | NESTED LOOPS | | 61 | 5124 | 5 (0)| 00:00:01 |
    |* 19 | INDEX RANGE SCAN | ATTACHITEM_X1 | 43 | 1806 | 2 (0)| 00:00:01 |
    | 20 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 21 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 22 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 61 | 1 (0)| 00:00:01 |
    |* 23 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 24 | NESTED LOOPS | | 124 | 23188 | 17 (0)| 00:00:01 |
    | 25 | NESTED LOOPS | | 87 | 10962 | 10 (0)| 00:00:01 |
    | 26 | NESTED LOOPS | | 61 | 5124 | 5 (0)| 00:00:01 |
    |* 27 | INDEX RANGE SCAN | ATTACHITEM_X1 | 43 | 1806 | 2 (0)| 00:00:01 |
    | 28 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 29 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 30 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 31 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 32 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 61 | 1 (0)| 00:00:01 |
    |* 33 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 34 | NESTED LOOPS | | 176 | 40304 | 27 (0)| 00:00:01 |
    | 35 | NESTED LOOPS | | 124 | 20832 | 17 (0)| 00:00:01 |
    | 36 | NESTED LOOPS | | 87 | 10962 | 10 (0)| 00:00:01 |
    | 37 | NESTED LOOPS | | 61 | 5124 | 5 (0)| 00:00:01 |
    |* 38 | INDEX RANGE SCAN | ATTACHITEM_X1 | 43 | 1806 | 2 (0)| 00:00:01 |
    | 39 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 40 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 41 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 42 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 43 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 44 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 45 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 61 | 1 (0)| 00:00:01 |
    |* 46 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 47 | NESTED LOOPS | | 251 | 68021 | 41 (0)| 00:00:01 |
    | 48 | NESTED LOOPS | | 176 | 36960 | 27 (0)| 00:00:01 |
    | 49 | NESTED LOOPS | | 124 | 20832 | 17 (0)| 00:00:01 |
    | 50 | NESTED LOOPS | | 87 | 10962 | 10 (0)| 00:00:01 |
    | 51 | NESTED LOOPS | | 61 | 5124 | 5 (0)| 00:00:01 |
    |* 52 | INDEX RANGE SCAN | ATTACHITEM_X1 | 43 | 1806 | 2 (0)| 00:00:01 |
    | 53 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 54 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 55 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 56 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 57 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 58 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 59 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 60 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 61 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 61 | 1 (0)| 00:00:01 |
    |* 62 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 63 | NESTED LOOPS | | 356 | 108K| 60 (0)| 00:00:01 |
    | 64 | NESTED LOOPS | | 251 | 63252 | 41 (0)| 00:00:01 |
    | 65 | NESTED LOOPS | | 176 | 36960 | 27 (0)| 00:00:01 |
    | 66 | NESTED LOOPS | | 124 | 20832 | 17 (0)| 00:00:01 |
    | 67 | NESTED LOOPS | | 87 | 10962 | 10 (0)| 00:00:01 |
    | 68 | NESTED LOOPS | | 61 | 5124 | 5 (0)| 00:00:01 |
    |* 69 | INDEX RANGE SCAN | ATTACHITEM_X1 | 43 | 1806 | 2 (0)| 00:00:01 |
    | 70 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 71 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 72 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 73 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 74 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 75 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 76 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 77 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 78 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 79 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 80 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 61 | 1 (0)| 00:00:01 |
    |* 81 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 82 | NESTED LOOPS | | 507 | 175K| 88 (0)| 00:00:02 |
    | 83 | NESTED LOOPS | | 356 | 102K| 60 (0)| 00:00:01 |
    | 84 | NESTED LOOPS | | 251 | 63252 | 41 (0)| 00:00:01 |
    | 85 | NESTED LOOPS | | 176 | 36960 | 27 (0)| 00:00:01 |
    | 86 | NESTED LOOPS | | 124 | 20832 | 17 (0)| 00:00:01 |
    | 87 | NESTED LOOPS | | 87 | 10962 | 10 (0)| 00:00:01 |
    | 88 | NESTED LOOPS | | 61 | 5124 | 5 (0)| 00:00:01 |
    |* 89 | INDEX RANGE SCAN | ATTACHITEM_X1 | 43 | 1806 | 2 (0)| 00:00:01 |
    | 90 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 91 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 92 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 93 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 94 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 95 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 96 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 97 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 98 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |* 99 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 100 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*101 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 102 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 61 | 1 (0)| 00:00:01 |
    |*103 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 104 | NESTED LOOPS | | 721 | 279K| 128 (0)| 00:00:02 |
    | 105 | NESTED LOOPS | | 507 | 166K| 88 (0)| 00:00:02 |
    | 106 | NESTED LOOPS | | 356 | 102K| 60 (0)| 00:00:01 |
    | 107 | NESTED LOOPS | | 251 | 63252 | 41 (0)| 00:00:01 |
    | 108 | NESTED LOOPS | | 176 | 36960 | 27 (0)| 00:00:01 |
    | 109 | NESTED LOOPS | | 124 | 20832 | 17 (0)| 00:00:01 |
    | 110 | NESTED LOOPS | | 87 | 10962 | 10 (0)| 00:00:01 |
    | 111 | NESTED LOOPS | | 61 | 5124 | 5 (0)| 00:00:01 |
    |*112 | INDEX RANGE SCAN | ATTACHITEM_X1 | 43 | 1806 | 2 (0)| 00:00:01 |
    | 113 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*114 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 115 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*116 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 117 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*118 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 119 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*120 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 121 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*122 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 123 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*124 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 125 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*126 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 127 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 61 | 1 (0)| 00:00:01 |
    |*128 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 129 | NESTED LOOPS | | 1026 | 439K| 174 (1)| 00:00:03 |
    |*130 | HASH JOIN | | 721 | 266K| 117 (1)| 00:00:02 |
    | 131 | NESTED LOOPS | | 507 | 166K| 88 (0)| 00:00:02 |
    | 132 | NESTED LOOPS | | 356 | 102K| 60 (0)| 00:00:01 |
    | 133 | NESTED LOOPS | | 251 | 63252 | 41 (0)| 00:00:01 |
    | 134 | NESTED LOOPS | | 176 | 36960 | 27 (0)| 00:00:01 |
    | 135 | NESTED LOOPS | | 124 | 20832 | 17 (0)| 00:00:01 |
    | 136 | NESTED LOOPS | | 87 | 10962 | 10 (0)| 00:00:01 |
    | 137 | NESTED LOOPS | | 61 | 5124 | 5 (0)| 00:00:01 |
    |*138 | INDEX RANGE SCAN | ATTACHITEM_X1 | 43 | 1806 | 2 (0)| 00:00:01 |
    | 139 | TABLE ACCESS CLUSTER| ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*140 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 141 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*142 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 143 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*144 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 145 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*146 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 147 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*148 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 149 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*150 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 151 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 42 | 1 (0)| 00:00:01 |
    |*152 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 153 | INDEX FAST FULL SCAN | ATTACHITEM_X1 | 11318 | 464K| 28 (0)| 00:00:01 |
    | 154 | TABLE ACCESS CLUSTER | ATTACHITEM | 1 | 61 | 1 (0)| 00:00:01 |
    |*155 | INDEX UNIQUE SCAN | ITEMCLUSTER_CLK | 1 | | 0 (0)| 00:00:01 |
    | 156 | VIEW | RSRC_CASE_QPMCSIS_X_VT | 163 | 1059K| 216K (1)| 00:43:13 |
    | 157 | UNION-ALL | | | | | |
    | 158 | NESTED LOOPS | | 1 | 286 | 185K (1)| 00:37:12 |
    | 159 | NESTED LOOPS | | 1 | 267 | 185K (1)| 00:37:12 |
    | 160 | NESTED LOOPS | | 102 | 20196 | 185K (1)| 00:37:11 |
    | 161 | INDEX FULL SCAN | RESOURCES_PK | 92717 | 1720K| 396 (1)| 00:00:05 |
    | 162 | TABLE ACCESS BY INDEX ROWID | RSRC_CASE_QPMCSI | 1 | 179 | 3 (0)| 00:00:01 |
    |*163 | INDEX RANGE SCAN | RSRC_CASE_QPMCSI_PK | 1 | | 2 (0)| 00:00:01 |
    |*164 | INDEX UNIQUE SCAN | RSRCTP_QPMCS_PK | 1 | 69 | 1 (0)| 00:00:01 |
    |*165 | INDEX UNIQUE SCAN | RESOURCES_PK | 1 | 19 | 0 (0)| 00:00:01 |
    | 166 | NESTED LOOPS ANTI | | 162 | 60264 | 30022 (1)| 00:06:01 |
    | 167 | NESTED LOOPS | | 162 | 47304 | 29698 (1)| 00:05:57 |
    | 168 | NESTED LOOPS | | 26511 | 5773K| 3177 (1)| 00:00:39 |
    | 169 | NESTED LOOPS | | 26511 | 5281K| 3175 (1)| 00:00:39 |
    | 170 | TABLE ACCESS BY INDEX ROWID | RSRCTP_CASE_QPMCSI | 263 | 48655 | 376 (0)| 00:00:05 |
    |*171 | INDEX FULL SCAN | RSRCTP_CASE_QPMCSI_PK | 263 | | 175 (0)| 00:00:03 |
    | 172 | TABLE ACCESS BY INDEX ROWID | RESOURCES | 101 | 1919 | 11 (0)| 00:00:01 |
    |*173 | INDEX RANGE SCAN | RESOURCES_F1 | 138 | | 2 (0)| 00:00:01 |
    |*174 | INDEX UNIQUE SCAN | RESOURCES_PK | 1 | 19 | 0 (0)| 00:00:01 |
    |*175 | INDEX UNIQUE SCAN | RSRCTP_QPMCS_PK | 1 | 69 | 1 (0)| 00:00:01 |
    |*176 | INDEX RANGE SCAN | RSRC_CASE_QPMCSI_PK | 1 | 80 | 2 (0)| 00:00:01 |
    See second message....

  • Check what oracle installed components are actually being used in database

    I have been allotted a new database which I have to optimize. So I am thinking about removing some installed components which I think are not being used in any way in database (i.e procedures calls etc). I can see a whole lot of components like "SDO","ORDIM" which I think are not being used but previous DBAs have installed them. So, is there any way to ensure that no part of database are actually using these components so that I can remove these components. Also ,what are your expert comments about this?

    Is this a production or a development environment? If an object isn't being used then it's not necessarily a problem (performance wise) unless it's cluttering up either your dictionary or raising concerns in regards consuming unnecessary space. Personally I'd recommend that it's better to tune what is being used / taking resources. It may be a once a year report or some old utility pulled out once a year, best check why these things are there.
    If you go down the dropping route, rather than drop anything immediately lock accounts for an agreed period of time to make sure that the schema isn't used & check any references from other schemas to objects within the schema that you're planning to drop, potentially audit these to check whether they're being called by other schemas / checking dba_dependencies between schemas & objects using a hierarchical query to check sublevels. 
    There are also quite a few Oracle standard components that are installed by default that have interdependencies and won't necessarily be used in the dictionary (checking dba_features_usage_statistics)

  • I have just started with Logic X, having been a Logic 8 user for many years. I have some expensive plug-ins which are not being recognised by the news Logic. Where should I install them ?  YoursdisillusionedbyLogic

    I have some expensive plug-ins which are not being recognised by the new Logic. Where should I install them ? 
    I am using Mavericks OS, and I am considering transfering my choiceof DAW to Protools.
    YoursdisillusionedbyLogic

    Hi
    LPX only supports 64bit Audio Unit plugins. You probably need to get the latest updates for all of your plugs.
    Some plugs are not currently available as 64bit versions: you may want to try
    http://www.soundradix.com/products/32-lives
    CCT

  • Task Scheduling Script - Need help with passing the scheduled command (variables are not being evaluated)

    Hi Everyone,
    I'm trying to get a simple task scheduler script to work for me and can't get the command I need passed to the scheduler to evaluate properly.
    Here's the script:
    ###Create a new task running $Command and execute it Daily at 6am.
    $TaskName = Read-Host 'What would you like this job to be named?'
    $Proto = Read-Host 'What is the protocol? (FTP/FTPS/SFTP)'
    $User = Read-Host 'What is the user name?'
    $Pwd = Read-Host 'What is the password?'
    $Server = Read-Host 'What is the server address?'
    $NetworkDir = Read-Host 'Please input the network location of the file(s) you wish to send. Refer to documentation for more details.'
    $RemoteDir = Read-Host 'Please input the REMOTE directory to which you will upload your files. If there is none please input a slash'
    $Command = 'winscp.com /command "option batch abort" "option confirm off" "open $Proto://$User:$Pwd@$Server" "put $NetworkDir $RemoteDir" "exit"'
    $TaskAction = New-ScheduledTaskAction -Execute "$Command"
    $TaskTrigger = New-ScheduledTaskTrigger -Daily -At 6am
    Register-ScheduledTask -Action $TaskAction -Trigger $Tasktrigger -TaskName "$TaskName" -User "Administrator" -RunLevel Highest
    Write-Host "$TaskName created to run Daily at $TaskStartTime"
    What's messing up is the $Command creation, the command needs to have the quotes around "option blah blah", but if I wrap the whole line in single quotes the variables that are evaluated for the "open blah blah" strings (which also need
    to be inside quotes) and the "put blah blah" string are not being evaluated properly.
    I've dorked about with different bracketing and quoting but can't nail the syntax down, could someone point me in the right direction? My Google-fu seems to be lacking when it comes to nailing down this issue.
    Thanks

    Hmmn, closer. I'm getting this error now:
    + $Command = $tmpl -f  $User, $Pwd, $Server, $NetworkDir, $RemoteDir
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (winscp.com /com...t {4} {5}" exit:String) [], RuntimeException
        + FullyQualifiedErrorId : FormatError
    And the command being added to the new task looks like this:
    winscp.com /command "option batch abort" "option confirm off" "open ($Proto)://($User):($Pwd)@($Server)" "put $NetworkDir $RemoteDir" "exit"
    Here's the current state of the script. I get what you're doing to try to bypass the quotes issue, using an array. I'm just not awesome at this yet sooooooo...
    $TaskName = Read-Host 'What would you like this job to be named?'
    $Proto = Read-Host 'What is the protocol? (FTP/FTPS/SFTP)'
    $User = Read-Host 'What is the user name?'
    $Pwd = Read-Host 'What is the password?'
    $Server = Read-Host 'What is the server address?'
    $NetworkDir = Read-Host 'Please input the network location of the file(s) you wish to send. Refer to documentation for more details.'
    $RemoteDir = Read-Host 'Please input the REMOTE directory to which you will upload your files. If there is none please input a slash'
    $tmpl = 'winscp.com /command "option batch abort" "option confirm off" "open {0}://{1}:{2}@{3}" "put {4} {5}" exit'
    $Command = $tmpl -f $User, $Pwd, $Server, $NetworkDir, $RemoteDir
    $TaskAction = New-ScheduledTaskAction -Execute $Command
    $TaskTrigger = New-ScheduledTaskTrigger -Daily -At 6am
    Register-ScheduledTask -Action $TaskAction -Trigger $Tasktrigger -TaskName "$TaskName" -User "Administrator" -RunLevel Highest
    Write-Host "$TaskName created to run Daily at $TaskStartTime"

Maybe you are looking for