Query does not use index

Hi,
We have a production environment that uses oracle 10GR2.
We have two schemas A and B
A has two tables test1 and test2.
test1 has three columns id, name, add and has an index IDX on id1. This table has close to 500 million rows.
test2 has an column id. this is generally a small table holding 50k rows.
B has the same set of tables and indexes.
Now the question here is:
When I run a join query as
select
t1.id
from
test1 t1, test t2
where t1.id = t2.id
on schema A, the explain plan uses the index IDX
However when I run the same on schema B, the explain plan does not make use of the index.
Any Thoughts?
Karthik

Here is the execution plans:
Schema A:
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| TQ |IN-OUT| PQ Distrib |
| 0 | SELECT STATEMENT | | 571 | 7423 | 37 (0)| | | |
| 1 | PX COORDINATOR | | | | | | | |
| 2 | PX SEND QC (RANDOM) | :TQ10000 | 571 | 7423 | 37 (0)| Q1,00 | P->S | QC (RAND) |
| 3 | NESTED LOOPS | | 571 | 7423 | 37 (0)| Q1,00 | PCWP | |
| 4 | PX BLOCK ITERATOR | | | | | Q1,00 | PCWC | |
| 5 | TABLE ACCESS FULL| TEST2               | 153 | 918 | 6 (0)| Q1,00 | PCWP | |
|* 6 | INDEX RANGE SCAN | IDX                    | 4 | 28 | 0 (0)| Q1,00 | PCWP | |
Predicate Information (identified by operation id):
access("TEST1"."ID"="TEST2"."ID")
Schema B:
Plan hash value: 2574051690
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | TQ |IN-OUT| PQ Distrib |
| 0 | SELECT STATEMENT | | 3108K| 38M| 5581 (3)| 00:01:07 | | | |
| 1 | PX COORDINATOR | | | | | | | | |
| 2 | PX SEND QC (RANDOM) | :TQ10001 | 3108K| 38M| 5581 (3)| 00:01:07 | Q1,01 | P->S | QC (RAND) |
|* 3 | HASH JOIN | | 3108K| 38M| 5581 (3)| 00:01:07 | Q1,01 | PCWP | |
| 4 | PX RECEIVE | | 196K| 1149K| 50 (4)| 00:00:01 | Q1,01 | PCWP | |
| 5 | PX SEND BROADCAST | :TQ10000 | 196K| 1149K| 50 (4)| 00:00:01 | Q1,00 | P->P | BROADCAST |
| 6 | PX BLOCK ITERATOR | | 196K| 1149K| 50 (4)| 00:00:01 | Q1,00 | PCWC | |
| 7 | TABLE ACCESS FULL | TEST2          | 196K| 1149K| 50 (4)| 00:00:01 | Q1,00 | PCWP | |
| 8 | PX BLOCK ITERATOR | | 121M| 809M| 5472 (2)| 00:01:06 | Q1,01 | PCWC | |
| 9 | INDEX FAST FULL SCAN| IDX               | 121M| 809M| 5472 (2)| 00:01:06 | Q1,01 | PCWP | |
Predicate Information (identified by operation id):
access("TEST1"."ID"="TEST2"."ID")

Similar Messages

Query does not uses indices

I am using 10.2.0.1 database instance and wrote a SQL query which involves several tables but I had made sure all columns in where clause has got proper indexes. The query is fairly simple does not use any function etc. in where clause but inner joins.
I have analyzed schema statistics using dbms_stats.gather_schema_stats... procedure and also added new required indexes to support this query.
Now when I see explain plain for this query it still does full table scan? I do not understand why it is not using indices and does full table scan.
Any comments?

Pgoel,
The plan that you posted with the proper tags to help when reading the plan:
| Id | Operation                     | Name               | Rows | Bytes | Cost | Time      |
| 0   | SELECT STATEMENT              |                    |       |       |   279 |           |
| 1   | HASH UNIQUE                  |                    |   692 | 130K |   279 | 00:00:04 |
| 2   |   NESTED LOOPS                |                    |   692 | 130K |   247 | 00:00:03 |
| 3   |    HASH JOIN                  |                    |    12 | 2184 |   223 | 00:00:03 |
| 4   |     HASH JOIN                 |                    |    12 | 2028 |   212 | 00:00:03 |
| 5   |      HASH JOIN                |                    |    12 | 1608 |   203 | 00:00:03 |
| 6   |       HASH JOIN               |                    | 3855 | 248K |    45 | 00:00:01 |
| 7   |        HASH JOIN              |                    | 3855 | 132K |    20 | 00:00:01 |
| 8   |         TABLE ACCESS FULL     | COD_SCHED_ITEMS    | 3970 |   39K |     6 | 00:00:01 |
| 9   |         HASH JOIN             |                    | 3064 |   75K |    13 | 00:00:01 |
| 10 |          INDEX FAST FULL SCAN | COD_SCHED_POLICY_PK| 3064 |   24K |     3 | 00:00:01 |
| 11 |          TABLE ACCESS FULL    | COD_SCHEDULE       | 3155 |   52K |     9 | 00:00:01 |
| 12 |        TABLE ACCESS FULL      | COD_ASSET          | 4982 | 151K |    25 | 00:00:01 |
| 13 |       TABLE ACCESS FULL       | COR_ACL            |   46K | 3124K |   157 | 00:00:02 |
| 14 |      TABLE ACCESS FULL        | COR_POLGROUP       | 3236 | 111K |     8 | 00:00:01 |
| 15 |     TABLE ACCESS FULL         | COR_BASE_PRICE     | 3247 |   41K |    11 | 00:00:01 |
| 16 |    INDEX RANGE SCAN           | QAM_LOG_URI_IX     |    58 |   580 |     2 | 00:00:01 |
----------------------------------------------------------------------------------------------Obtaining the plan from the 10053 trace was likely a minor goal of Sybrand when he suggested activating the trace. The plan implies that the cost based optimizer determined that Oracle would require 0.04 seconds to execute the plan and return the data. Does it take much longer than 0.04 seconds for the query to execute?
As Sybrand pointed out, the 10053 trace shows the decisions made by the cost based optimizer when trying to determine the most efficient plan. If a potential step in the plan is determined to be more expensive (costly, assumed to require more time to execute) than a previously found method, the potential plan step is aborted. This process continues until one of:
* All join order possibilities have been tried (8! = 40,320 possible)
* 2,000 join order possibities have been tried
* The continued examination of join combinations will require more time than Oracle predicts for the execution of the query.
* And probably something else.
The process and decisions made by the cost based optimizer are included in the 10053 trace. For some reason, possibily bad statistics, inappropriate initialization parameters, cardiality calcuation problems, or something else, Oracle calculated that retrieving the data from the tables using a full tablescan is less costly than an index access path. The 10053 trace will show why that happened.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

Simple query but not using index..please help??

I do have this column indexed. Why my query is not using this index?
Any help .
select count(*) from v_dis_sub_har;
SQL>
COUNT(*)
   4543289
1 row selected.
SQL>
select vzw_vendor_id , count(*)
from v_dis_sub_har
group by vzw_vendor_id
SQL>   2    3    4
VZW_VENDOR_ID   COUNT(*)
       200091     908653
       200013     908659
       200012     908659
       200057     908659
       200031     908659
5 rows selected.
SQL> SQL>
explain plan for
select
event_seq
from v_dis_sub_har b
where b.VZW_VENDOR_ID='200013'
-- and b.status='P' and b.extract_date is null
SQL>   2    3    4    5    6    7
Explained.
SQL> SQL>
select plan_table_output from table(dbms_xplan.display)
SQL> SQL>   2
PLAN_TABLE_OUTPUT
Plan hash value: 2852398983
| Id | Operation         | Name          | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |               |   908K| 7986K| 3132 (16)| 00:00:38 |
|* 1 | TABLE ACCESS FULL| V_DIS_SUB_HAR |   908K| 7986K| 3132 (16)| 00:00:38 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
   1 - filter("B"."VZW_VENDOR_ID"=200013)
13 rows selected.
SQL> SQL>

You are right Justin. Oracle is not stupid as you may want to say some times when things do not happen according to you. I just created a bitmap index on status field and look what appened. Som times it uses bitmap index and some times it does not. And the reason is clear. Row count by status. 'S' status uses bitmap index where 'P' does not.
Thanks for your help.
select   status, count(*)
from v_dis_sub_har
group by status
;SQL>   2    3    4
S   COUNT(*)
A    5844982
P    2312759
S      20178
3 rows selected.
SQL>
explain plan for
select
event_seq
from v_dis_sub_har b
where
--b.VZW_VENDOR_ID=200013
-- and
b.status='S'
--and b.extract_date is null
select plan_table_output from table(dbms_xplan.display)
SQL>   2    3    4    5    6    7    8    9   10
Explained.
SQL> SQL> SQL> SQL>   2
PLAN_TABLE_OUTPUT
Plan hash value: 829738689
| Id | Operation                    | Name                         | Rows | Bytes | Cost (%CPU)| T
ime     |
PLAN_TABLE_OUTPUT
|   0 | SELECT STATEMENT             |                              | 20290 |   118K| 2772   (1)| 0
0:00:34 |
|   1 | TABLE ACCESS BY INDEX ROWID | V_DIS_SUB_HAR                | 20290 |   118K| 2772   (1)| 0
0:00:34 |
|   2 |   BITMAP CONVERSION TO ROWIDS|                              |       |       |            |
        |
|* 3 |    BITMAP INDEX SINGLE VALUE | V_DISPATCH_SUBSCRIPTION_NDX2 |       |       |            |
        |
PLAN_TABLE_OUTPUT
Predicate Information (identified by operation id):
   3 - access("B"."STATUS"='S')
15 rows selected.
SQL> SQL> set line 120
SQL> /
PLAN_TABLE_OUTPUT
Plan hash value: 829738689
| Id | Operation                    | Name                         | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT             |                              | 20290 |   118K| 2772   (1)| 00:00:34 |
|   1 | TABLE ACCESS BY INDEX ROWID | V_DIS_SUB_HAR                | 20290 |   118K| 2772   (1)| 00:00:34 |
|   2 |   BITMAP CONVERSION TO ROWIDS|                              |       |       |            |          |
|* 3 |    BITMAP INDEX SINGLE VALUE | V_DISPATCH_SUBSCRIPTION_NDX2 |       |       |            |          |
PLAN_TABLE_OUTPUT
Predicate Information (identified by operation id):
   3 - access("B"."STATUS"='S')
15 rows selected.
SQL>
explain plan for
select
event_seq
from v_dis_sub_har b
where
--b.VZW_VENDOR_ID=200013
-- and
b.status='P'
--and b.extract_date is null
select plan_table_output from table(dbms_xplan.display)
      SQL>   2    3    4    5    6    7    8    9   10
Explained.
SQL> SQL> SQL> SQL>   2
PLAN_TABLE_OUTPUT
Plan hash value: 2852398983
| Id | Operation         | Name          | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |               | 2325K|    13M| 5784 (18)| 00:01:10 |
|* 1 | TABLE ACCESS FULL| V_DIS_SUB_HAR | 2325K|    13M| 5784 (18)| 00:01:10 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
   1 - filter("B"."STATUS"='P')
13 rows selected.
SQL>

Query can not use index

1,i found a sql :select userid,repute from user_attribute where
repute>3000 order by repute desc
cost heavily;
SELECT STATEMENT Cost = 637
SORT ORDER BY
TABLE ACCESS FULL USER_ATTRIBUTE
2,i use: select index_name from user_indexes where table_name
= 'USER_ATTRIBUTE'
INDEX_NAME
IDX_USER_ATTRIBUTE_FACE
IDX_USER_ATTRIBUTE_POWER
IDX_USER_ATTRIBUTE_REPUTE
IDX_USER_ATTRIBUTE_USERID
so column repute has indexed
3, i use CBO with analysize shema compute
optimizer_index_caching integer 99
optimizer_index_cost_adj integer 5
4,i use: select /*index(IDX_USER_ATTRIBUTE_REPUTE)*/
userid,repute from user_attribute where repute>3000 order by
repute desc
i got same explain plan as old
5,why it can not use index to query,thanks.

I think your optimizer hint syntax is wrong. you need a "+"
sign to indicate that the comment block is an optimizer hint,
and the table name is not optional in the index hints
select /*+ index(user_attribute
IDX_USER_ATTRIBUTE_REPUTE)*/
userid,repute from user_attribute where repute>3000 order
by
repute desc
also, try ...
select /*+ index_desc(user_attribute
IDX_USER_ATTRIBUTE_REPUTE)*/
userid,repute from user_attribute where repute>3000
This should order the result for you.

View with renamed column does not use index

Is there any reason why a view that renames the columns presented to the users would ignore an index?
For example:
CREATE OR REPLACE VIEW ENROLLMENT
(ENROLLMENT_ID, ENROLLMENT_DATE, FIRST_NAME)
AS
select distinct
a.col1 as enrollment_id,
a.col2 as enrollment_date,
a.col3 as first_name
from t1 a
When a user queries the view, with a WHERE FIRST_NAME = 'TOM", it results in a FTS. However, if you run the query against the base table (using col1, col2, and col3), it uses the index against t1 on (col3, col2, col1).

Well, I tried to create the supporting evidence afterwards (sigh, why do I keep doing that ...), it seems that Oracle has addressed this problem already:
SQL> create table t1
2 as
3 select l col1, sysdate - l/86400 col2, decode(l,1,'TOM',to_char(l)) col3
4    from (select level l from dual connect by level <= 100000)
5 /
Tabel is aangemaakt.
SQL> create index i1 on t1 (col3, col2, col1)
2 /
Index is aangemaakt.
SQL> exec dbms_stats.gather_table_stats(user,'T1',method_opt=>'FOR ALL INDEXED COLUMNS')
PL/SQL-procedure is geslaagd.
SQL> create view enrollment
2 (enrollment_id, enrollment_date, first_name)
3 as
4 select distinct
5 a.col1 as enrollment_id,
6 a.col2 as enrollment_date,
7 a.col3 as first_name
8 from t1 a
9 /
View is aangemaakt.
SQL> set autotrace on explain
SQL> select * from enrollment where first_name = 'TOM'
2 /
                         ENROLLMENT_ID ENROLLMENT_DATE     FIRST_NAME
                                     1 16-01-2007 14:41:25 TOM
1 rij is geselecteerd.
Uitvoeringspan
   0      SELECT STATEMENT Optimizer=CHOOSE (Cost=3 Card=1 Bytes=44)
   1    0   VIEW OF 'ENROLLMENT' (Cost=3 Card=1 Bytes=44)
   2    1     SORT (UNIQUE NOSORT) (Cost=3 Card=1 Bytes=18)
   3    2       INDEX (RANGE SCAN) OF 'I1' (NON-UNIQUE) (Cost=3 Card=1
           Bytes=18)I'm on 9.2.0.7.0 here, what's your version ?
Regards,
Rob.

Query does not use aggregate ?

Hi,
how can I check if a query uses an aggregate ?
How can I force a query to use an aggregate ?
ThanXs
Martin

Hi,
You can check in RSRT whether a query is hitting aggregate or not. Otherwise you run the query and go to aggregate maintanence and see the last used date. In order to make the query hit the aggregate all the fields in query including filters should be in the aggregate.
Regards,
Raghavendra.

Query is not using the INDEX

I have issue with a query as follows. It is not using index when i keep a function on the left hand side of comparison in where condition.
But when I remove the function it is using index.
With BLC AS
Name                                      Null?    Type
ID                                        NOT NULL NUMBER
MASTER_VALUE               NOT NULL NUMBER(8)
DESC_TEXT_ID                                    NUMBER
GVM                                                     VARCHAR2(50)
MASTER_LOOKUP_ID    NOT NULL NUMBER
WORK_SECTION_ID                          NUMBER
AUDIT_TRAIL_NO                              NUMBER
SQL> SELECT COUNT(*) FROM BLC;
COUNT(*)
      7769
SQL> SELECT COUNT(DISTINCT(GVM)) "distinct" FROM BLC;
distinct
      1350
SQL> SELECT COUNT(*) "nulls" FROM BLC WHERE GVM IS NULL;
     nulls
      6419
SQL> SELECT COLUMN_NAME,INDEX_NAME FROM DBA_IND_COLUMNS WHERE TABLE_NAME='BLC';
COLUMN_NAME                              INDEX_NAME
MASTER_LOOKUP_ID      LKPCDE_MSTLKP_FK_I
WORK_SECTION_ID        LKPCDE_WRKSEC_FK_I
GVM                                   LKPCDE_UK
MASTER_VALUE              LKPCDE_MASTERID_VALUE_UK
MASTER_LOOKUP_ID     LKPCDE_MASTERID_VALUE_UK
ID                                       LKPCDE_PK
SQL> EXPLAIN PLAN FOR SELECT ID FROM BLC WHERE UPPER ( GVM) = 'MAIN_ORG';
Explained.
SQL> SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY);
PLAN_TABLE_OUTPUT
Plan hash value: 3196655606
| Id | Operation         | Name             | Rows | Bytes | Cost (%CPU)| Time|
PLAN_TABLE_OUTPUT
|   0 | SELECT STATEMENT |                  |    78 |   624 |    18   (0)| 00:00:01 |
|* 1 | TABLE ACCESS FULL| BLC |    78 |   624 |    18   (0)| 00:00:01 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
   1 - filter(UPPER("GVM")='MAIN_ORG')
13 rows selected.
SQL> EXPLAIN PLAN FOR SELECT ID FROM BLC WHERE GVM
= 'MAIN_ORG';
Explained.
SQL> SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY);
PLAN_TABLE_OUTPUT
Plan hash value: 1620245961
| Id | Operation                   | Name             | Rows | Bytes | Cost (%
CPU)| Time     |
PLAN_TABLE_OUTPUT
|   0 | SELECT STATEMENT            |                  |     1 |     8 |     2
(0)| 00:00:01 |
|   1 | TABLE ACCESS BY INDEX ROWID| BLC |     1 |     8 |     2
(0)| 00:00:01 |
|* 2 |   INDEX UNIQUE SCAN         | LKPCDE_UK        |     1 |       |     1
(0)| 00:00:01 |
PLAN_TABLE_OUTPUT
Predicate Information (identified by operation id):
   2 - access("GVM"='MAIN_ORG')
14 rows selected.
SQL> EXPLAIN PLAN FOR SELECT /* INDEX(LKPCDE_UK) */ ID FROM BLC WHE
RE UPPER ( GVM ) = 'MAIN_ORG';
Explained.
SQL> SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY);
PLAN_TABLE_OUTPUT
Plan hash value: 3196655606
| Id | Operation         | Name             | Rows | Bytes | Cost (%CPU)| Time
     |
PLAN_TABLE_OUTPUT
|   0 | SELECT STATEMENT |                  |    78 |   624 |    18   (0)| 00:0
0:01 |
|* 1 | TABLE ACCESS FULL| BLC |    78 |   624 |    18   (0)| 00:0
0:01 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
   1 - filter(UPPER("GVM")='MAIN_ORG')
13 rows selected.
Please let me know how i can force to use an index as it is causing CPU usage.
I can not change the query in application as it is used at many places.
Thanks

Hi,
Version is
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE    10.2.0.5.0      Production
TNS for 64-bit Windows: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production
Sorry, in my last post i forgot to mention that i already created a function based index but still it is not using because, there is a UNIQUE constraint on that column.
Thanks

Queries not using indexes

We installed and configured a new environment of OBIEE and are trying to run a simple query in our data warehouse. This simple query takes only 7 seconds to complete in our previous data warehouse using TOAD but is taking 8+ minutes to complete in our new environment also using TOAD.
Looking at the explain plans, the query in the new environment is not using indexes. Does anyone have an idea why it is not using the indexes? We checked and all of the indexes have been created and still exist. We also ran Analyze again on the two tables used n the query but the query still did not use the indexes.
Please let me know if anyone has ideas ASAP since we are baffled.

- Are the object statistics identical? The ANALYZE statement has been depricated for a while, particularly for data warehouse environments where there may be partitioning. Were you not using the DBMS_STATS package to gather statistics in the previous environment? Were statistics computed on the indexes?
- Can you post the two query plans (formatted via DBMS_XPLAN and including the filter conditions)? It is not immediately obvious to me what index(es) might be useful here unless one of the two conditions is particularly selective which doesn't seem terribly likely based on just the table names involved.
- When you do post the query plans, please use the \[code\] and \[code\] tags to preserve the white space so that the output is readable.
Justin

Not Using Index on File Server When Accessing User Files Directly on Server

It appears to me that on a server with an indexed network share (Desktop Experience and Search Indexing roles/features installed), if you access the share directly on the server using its drive path, you can search the folders using the index, which
is much faster and supports finding words inside of the files in seconds). However, if you access the same shared folder via its network path from the server itself, the server ignores the index. I have this experience/problem across all shared folders on
the Windows 2012 R2 Server. Details and my most specific goal follows.
In addition to a laptop, I frequently work directly on a Windows Server 2012 R2 computer. We have Redirected Folders set up on DFS (for failover redundancy) so that my Documents folder is in:
\\network\redirections\user\documents. This all works fine on Windows 7 and 8 client computers connected to the network via Offline Files.
The problem is on the server itself. The server has Desktop Experience enabled and Windows Search is installed. If I navigate manually through the DFS root folder to my documents folder, I can search and it properly uses the index. This proves the location
is properly indexed. However, if I access the folders through the official "Documents" folder from the Folder Redirection (a network share pointing to the same server computer I'm working on), it performs an un-indexed search (slow and ignores file
contents, but does find files eventually if the search term is in their filename). Is there a way to force the server to use the indexed search on the Redirected Folders (my Documents folder in particular) when working on that server when logged in locally
on that server?
I suspect a workaround would be to go into the Registry and manually change the HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders to point to the local DFS folder instead of the network share name, but at least one problem
with this is then if I save files with links to other files (e.g., a linked Excel table in a PowerPoint, a mail merge to Access database in Word, etc.) on the server computer, those links will point to d:\DFSroot\... (a physical drive on the computer) instead
of \\network\redirections\user\... (a universally accessible network path) and so none of the other computers will be able to find the linked files, defeating one of the
major benefits of using Redirected Folders.
I can't believe that I need to choose between indexed searching and proper path names in saved files. Surely there is a way to use an indexed search on the server itself?
If you need any more info to help me troubleshoot, please let me know.
Thanks for any help,
Colin

Hi Colin,
It seems that we can not use indexed search on DFS shares. Windows Search works well when users directly access the server. That is, the server is not made available through Distributed File System (DFS).
For more detailed information, you could refer to the links below:
Windows Search Service, Clustered File Services, DFS, Win7 Libraries
https://social.technet.microsoft.com/Forums/windowsserver/en-US/31ac4c16-948b-4ca4-b18f-3a339cdfd5b9/windows-search-service-clustered-file-services-dfs-win7-libraries?forum=winserverfiles
Windows Browse and Organize Features
https://technet.microsoft.com/en-us/library/dd744693(WS.10).aspx
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Requested query does not exist on the current server.

Hi All,
I am facing a problem in BI 7.0 related to query view.I am able to create a view on a query and can successfully save it .But when I am trying to open it using Bex Analyzer, it throws an error that query does not exist on the current server.
Please find the steps below which I did to create a query view in BI 7.0.
1.Executed query and then clicked on save from the tool bar.It asks me to save as workbook or save as view.I clicked on save as view and gave some name to view.It saved successfully.
2.Now when in Bex I am trying to open the view , it gives the message 'The requested query does not exist on the current server'.
Please help me in solving the issue.
Regards,
Phani.

Hi,
I am facing the same problem, though some others of my views can be opened.
We had an upgrade of the system to Support Package stack 13. Maybe this caused problems.
My BEx Analyzer Version is:
Support Package 14, Patch 3, Revision 811
Philipp

Problem in WAD (The requested query / does not exist on the current server)

Dear Guru's
When i execute a Web Application in WAD in the selection screen suppose if i give Key product as 86000 then check and execute i get correct data. Then if i come to backpage (Selection screen again using backspace) and change Key product as 86022 then check and execute then i get following error
The requested query / does not exist on the current server
System error in program CL_RSR_OLAP_VAR and form BAD STATE (see long text)
Can any one please provide me some good solution...
We are using BI 7.0 sp 16, But i am executing this Wed Application in 3.1WAD.
Thanks and Regards,
kalyan

Dear Jai,
Issue is in WAD selection screen for first product valuse every thing if fine, when i go back and change product value and then CHECK and EXECUTE the following error comes.
The requested query / does not exist on the current server
System error in program CL_RSR_OLAP_VAR and form BAD STATE (see long text)
Any one have any idea plssssssssssssssssssssssssssssssssssss..........
dude's some soln.....
Thanks and Regards,
Dev
Edited by: Srinivas dev on Jul 4, 2008 2:45 PM

SQL-Developer 1.5.4 - SQL-Worksheet does not use Table-Owner

In old versions of the sql-Developer you can drop a Table in the Worksheet and a select Query was built. With the new version 1.5.4 the table-owner is missng and you must fill in the table-owner or the query does not work with tables of other users.
Is that a bug or are there the posibility of change settings to drop tables in the SQL-worksheet with table-owners.

The drag and drop functionality was updated so that when you use drag and drop the schema is not prefixed for the current user you are connected to. However it is appended if you drag a table form another connection. It appears to have been overlooked for Other Users. We will address this in a future release. In the meantime,a workaround is to create a connection to the other users and then the drag and drop will append the connection name.
Sue

Ad hoc query does not contain a list

Hi,
We created an infoset using table join (T5U13, PA0001 and T5UEE). But as we run transaction PAAH and choose a query assigned to the new infoset, we are getting a pop up screen that says "Query does not contain a list". The button hitlist does not appear in the screen and when we try to search we get the prompt "No data was selected".
Thanks in advance!

Hi,
I am getting the similar error.waht i have done is as follows.may I know the resolution.
After creating the Adhoc query using the join table functionality the resulting adhoc query does not results any out put.
What I have done is :
1.Created a user group through SQ03
2.Attched user to My user group
3.Created an infoset using join table functionality(SQ02).
4.Saved and generated the infoset
5.Added the user group to the infoset and than run the ADHOC query.
The table I have used to join is all PA table (For test pupose)
Though the purpose of the custom infoset is to join PA,OM and E rec infotypes, for testing purpose I have joined only PA infotypes.
Result:The adhoc query does not gives any out put instead it says no data could be read.
Could you please tell what else I need to do so that the custom infosets gives an out put.
Will greatly appreciate your help.
Thanks and best regards
Rajeev

Error: Scope in your query does not exist...

I have an advanced search web part on my page, and wanting to narrow the search scope to my particular site. In trying to accomplish this, I have created a scope in central admin, and modified the Advanced Search web part properties xml to reflect the scope
I created. Within the ResultType tag of that xml, I have this to specify my scope
<KeywordQuery>"scope"='This Site'</KeywordQuery>
After doing this, I attempt a search, but I am getting the following error "Scope in your query does not exist". Am I missing anything? Has anyone ran into this previously? If so, I would appreciate your insight...I have not been able to find any
blogs on this issue. This is on SharePoint 2010.
Thanks

Hi Spawn,
You can specify your search scope in the ResultType tag like below:
<Query>"scope"='Your Scope'</Query>
Here is a detailed artcile, I suggest you can take a look for reference:
Specify Default Scope for Advanced Search Box Web Part without Using Scope Picker
Best Regards
Zhengyu Guo
TechNet Community Support

The '' secondary data source is not a relational data source, or does not use an OLE DB provider.

Hi,
We are using Teradata as data source in SSAS 2008R2, it’s using ‘.Net Providers\.Net Data Provider for Teradata’.
In DSV, we have two data sources both using Teradata. While processing dimensions, all dimensions coming from secondary data source has error message”
The '' secondary data source is not a relational data source, or does not use an OLE DB provider.”
But we are not using OLE DB provider for now, we’ve searched some threads that named queries can be replaced for secondary ds, but since we have a lot of tables, it’s hard to implement using named queries.
Any inputs would be appreciated.

Hi memostone,
When defining a data source view that contains tables, views, or columns from multiple data sources, the first data source from which you add objects to the data source view is designated as the primary data source (you cannot change the primary data
source after it is defined). After defining a data source view based on objects from a single data source, you can then add objects from other data sources.
If an OLAP processing or a data mining query requires data from multiple data sources in a single query, the primary data source must support remote queries using
OpenRowset. Typically, this will be a SQL Server data source.
Here are the restrictions:
The primary data source should be SQL Server and support OpenRowset to the secondary data source.
Or you design the cube in such a way that rocessing for each object only needs to access data from a single data source
I recommand you refer to the following article:
Defining a Data Source View (Analysis Services):
http://technet.microsoft.com/en-us/library/ms174600.aspx
Regards,
Bin Long
TechNet Community Support

Query does not use index

Similar Messages

Maybe you are looking for