Two secondary indexes in a where clause

Hi All,
Can any one of you let me know wether DB optimizer will use two indexes if given in where clause........
example : primary index A,B.   secondary C,D,E.
select ................ where A in ....
                              B in ....
                              C in ....
so iam using all(two) fields of primary index and one field of secondary so will the DB optimizer search for the index blocks or directly the table blocks when it comes to the C field in the where clause......
Thanks in advance.

Hello,
To do it use the WHERE stm in the same order as the secondary stm is on SE11....To check if the index is used go to tcode ST05.
example
select * from ztable
WHERE BUKRS EQ 'BUK1' AND
ZFIELD EQ 'BOY'.
on se11 on the ZTABLE indexes setion must have a secondary index with
BUKRS and
ZFIELD.
BYE!!
Hope this helps!!
Gabriel

Similar Messages

Use two secondary indexes in a select statement

hi, i want to use two secondary indexes in a select statement.
how can i do it?

Hello,
To do it use the WHERE stm in the same order as the secondary stm is on SE11....To check if the index is used go to tcode ST05.
example
select * from ztable
WHERE BUKRS EQ 'BUK1' AND
ZFIELD EQ 'BOY'.
on se11 on the ZTABLE indexes setion must have a secondary index with
BUKRS and
ZFIELD.
BYE!!
Hope this helps!!
Gabriel

How to set two Conditions Simultaneously in set where clause

Hi,
I have a messgechoice item , and i need to fire messagechoice VO with two conditions.
For Eg:-- we have three Items ProjectContractor& Work Order on a custom Page , now i need work order list should populate on lelection of project & contractor both, so i have apply a fire partial event on contractor where i i get the parameter values as follows:--
CO Code
if("OrderNoself".equals(event))
String value21 = (String)pageContext.getParameter("ProjectName");
System.out.println("The Selected Project Name for self Contractor is "+value21);
String value22 = (String)pageContext.getParameter("ContractorName");
System.out.println("The SelectedContractor Name for ContractorName is "+value22);
Serializable [] params11 = {value21,value22} ;
am.invokeMethod("initWorkOrderNumberself",params11);
AM Code
public void initWorkOrderNumberself(String ProjectName,String ContractorName");
getDprWorkOrderpopVO1().setWhereClause("PROJECT_NAME = " + "'"+ProjectName+"'");
getDprWorkOrderpopVO1().setWhereClause("CONTRACTOR_NAME = " + "'"+ContractorName+"'");
getDprWorkOrderpopVO1().executeQuery();
Now when i run my form then Work order list only populateon set conditions ofContractor NAme only.
Please suggest....

Hi Tarun,
Thanx for ur reply,
i have used below mwntioned code provided by you but still i m getting error...
public void initWorkOrderNumber(String ProjectName,String ContractorName)
//getDprWorkOrderpopVO1().setWhereClause("CONTRACTOR_NAME = " + "'"+ContractorName+"'");
//getDprWorkOrderpopVO1().executeQuery();
getDprWorkOrderpopVO1().setWhereClause("PROJECT_NAME =:1 AND CONTRACTOR_NAME=:2");
getDprWorkOrderpopVO1().setWhereClauseParams(null);
getDprWorkOrderpopVO1().setWhereClauseParam(1,ProjectName);
getDprWorkOrderpopVO1().setWhereClauseParam(2,ContractorName);
getDprWorkOrderpopVO1().executeQuery();
ERROR:---
oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: SELECT * FROM (select * from omaxe_work_order_headers
where work_order_number is not null) QRSLT WHERE (PROJECT_NAME =:1 AND CONTRACTOR_NAME=:2)
     at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:888)
     at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:862)
     at oracle.apps.fnd.framework.OAException.wrapperInvocationTargetException(OAException.java:985)
     at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:210)
     at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:152)
     at oracle.apps.fnd.framework.server.OAApplicationModuleImpl.invokeMethod(OAApplicationModuleImpl.java:721)
     at omaxe.oracle.apps.xxopa.boqmain.webui.OmaxeDPRCO.processFormRequest(OmaxeDPRCO.java:107)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:799)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:363)
     at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processFormRequest(OAPageLayoutHelper.java:1118)
     at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processFormRequest(OAPageLayoutBean.java:1579)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:995)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:961)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:816)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:363)
     at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processFormRequest(OAFormBean.java:395)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:995)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:961)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:816)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:363)
     at oracle.apps.fnd.framework.webui.beans.OABodyBean.processFormRequest(OABodyBean.java:363)
     at oracle.apps.fnd.framework.webui.OAPageBean.processFormRequest(OAPageBean.java:2633)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1659)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:497)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:418)
     at OA.jspService(OA.jsp:40)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:727)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:306)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:767)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:259)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:106)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
     at java.lang.Thread.run(Thread.java:534)
## Detail 0 ##
java.sql.SQLException: ORA-01006: bind variable does not exist
Regards
Saurabh

Secondary index not getting picked

Hello All,
I am seeing stange behaviour of picking of secondary indexes.
Example:
Index - I1 is having two fields and the same two fields in giving in where clause of the select and this fields are unque and not used in any other secondary index.
Result in trace(ST05) -- Index I1 is not picked and it extraction went for 'Full table scan'.
But in other system for the same inputs index I1 is picked and it can be seen trace(ST05).
Before posting this query, i have gone through many posts related secondary index and not found helpful.
Any inputs will be appreciated.
Thanks.
Adnan.

Hi,
In the select query have you Called the Secondary Index in the WHERE clause.
Please try with this option it will surely work.
More Information About Index:
Inclusions Index: The index is only created automatically during activation for the database systems specified in the list. The index is not created on the database for the other database systems.
Exclusions Index: The index is not created automatically on the database during activation for the specified database systems. The index is automatically created on the database for the other database systems.
Thanks & Regards,
Saravanan Sambandam

How to check small table scan full table scan if we will use index in where clause.

How to check small table scan full table scan if i will use index column in where clause.
Is there example link there i can test small table scan full table if index is used in where clause.

Use explain plan on your statement or set autotrace traceonly in your SQL*Plus session followed by the SQL you are testing.
For example
SQL> set autotrace traceonly
SQL> select *
2 from XXX
3 where id='fga';
no rows selected
Execution Plan
   0      SELECT STATEMENT Optimizer=ALL_ROWS (Cost=13 Card=1 Bytes=16
          5)
   1    0   PARTITION RANGE (ALL) (Cost=13 Card=1 Bytes=165)
   2    1     TABLE ACCESS (FULL) OF 'XXX' (TABLE) (Cost=13 Card
          =1 Bytes=165)
Statistics
          1 recursive calls
          0 db block gets
       1561 consistent gets
        540 physical reads
          0 redo size
       1864 bytes sent via SQL*Net to client
        333 bytes received via SQL*Net from client
          1 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
          0 rows processed

Re: [iPlanet-JATO] How to make an OR in the WHERE clause of a SELECT

Harry,
If you get a reference to your model, you can set the
whereClauseOverride with exactly the string you want to use. Keep in
mind that you are dealing with a the raw SQL where clause, therefore,
you must use the actual table column names and not the model's logical
field names as they could be different.
QueryModelBase queryModel = (QueryModelBase)getModel(PersonModel.class);
// you must add the "WHERE" as well
String whereClause = "WHERE firstName LIKE '%max' OR lastName LIKE '%max%'";
queryModel.setWhereClauseOverride(whereClause);
Keep in mind that this will override all where criteria: static and
dynamic where criteria. Static criteria can be declared in your model
class: setStaticWhereCriteriaString(STATIC_WHERE_CRITERIA).
You could optionally get the entire SQL statement and replace the
__WHERE__ token yourself with a string replace technique. In fact, if
you want to add an ORDER BY, you will need to get the SQL and append to
the end.
queryModel.getSelectSQL();
Hope this helps. Let me know if you have any questions
craig
hlamer wrote:
Hi,
if I add criterias to my model
with "SelectQueryModel.addUserWhereCriterion()" they will be concated
with AND.
How can I add a criteria with OR?
I want something like:
SELECT personId, firstName, lastName
FROM Person
WHERE firstName LIKE "%max"
OR lastName LIKE "%max%"
Thanks.
Harry
For more information about JATO, including download information, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp

Rewritten your query wuth tags as well
{code}select "P_CIRCUITS_FIBER"."PORTS_1",
        "P_CIRCUITS_FIBER"."PORTS_2",
        CASE WHEN CPORT.ID = (select REGEXP_SUBSTR(ports_1,'[^,]+',1,1) from p_circuits_fiber)
             THEN "CPORT"."PORT_NO" END PORT_NO_1,
        CASE WHEN CPORT.ID = (select REGEXP_SUBSTR(ports_2,'[^,]+',1,1) from p_circuits_fiber)
             THEN "CPORT"."PORT_NO" END PORT_NO_2
from    "CPORT",
        "P_CIRCUITS_FIBER"
where   p_circuits_fiber.fiber_id = :P4000_CIRCUIT_NO
and     (select REGEXP_SUBSTR(ports_1,'[^,]+',1,1) from p_circuits_fiber) = "CPORT"."PORT_NO" "PORT_NO_1"
and     (select REGEXP_SUBSTR(ports_2,'[^,]+',1,1) from p_circuits_fiber) = "CPORT"."PORT_NO" "PORT_NO_2"{code}
Now we can see two columns references which should not be there.
I even not sure to understand why those two conditions are in the WHERE clause. But for sure, CPORT.ID cannot be equal to two values unless they are same.
Is there only one row in p_circuits_fiber ?
Nicolas.

Slow secondary indexes creation

I have a database table where each record is a fixed length of 16 bytes and the key length is 4 bytes.
The table has ~3G records, giving file size of 61GB.
The access method is DB_QUEUE.
I'm using the 5.1.25 version.
I'm trying to create two secondary indexes using DB_HASH as access method.
I set the pagesize to 65K, cachesize to 65M.
When I start to build the indexes I see that the creation time of the indexes will take me something like 3 days which I think is reasonable. But after a day the performances are dropping drastically, giving me approximately creation time of 1 month.
What should I do in order to boost performance on such case?
Edited by: 868434 on Jun 26, 2011 2:07 AM

Hi,
I set the pagesize to 65K, cachesize to 65M.You probably mean 64KB; see the DB->set_pagesize() documentation.
When I start to build the indexes I see that the creation time of the indexes will take me something like 3 days which I think is reasonable. But after a day the performances are dropping drastically, giving me approximately creation time of 1 month. Are you recreating the secondary indexes on a regular basis? If so, what is the reason for this?
Once you open, associate and populate the secondary (using the DB_CREATE flag for the associate() call), you should keep the secondary databases around and not remove them just to recreate them again. Whenever the primary database is updated, the appropriate updates are performed in the secondaries as well to reflect the changes; see Secondary indexes documentation section.
Opening (creating a new database file handle) and populating a secondary database on open are potentially very expensive operations; see the subheading on DB_CREATE in the DB->associate() documentation section.
What should I do in order to boost performance on such case?The best approach would be to not remove and recreate the secondary indexes regularly, but rather create, populate and keep them around as long as the application runs.
If however you need to recreate them again and again, and given that they use the Hash access method, here are some suggestions:
1. If you have a support contract and can access MOS (My Oracle Support) have a look over Doc ID 463613.1 and Doc ID 463507.1 notes in the KM repository (they discuss tuning Hash databases' configuration for speeding up insertion times).
If you cannot access them, let me know and I can make a summary with further guidance.
2. Review the Hash access method specific configuration doc section and try to experiment with appropriately calculated values for the density / page fill factor, hash table size (estimated no of elements that will be stored in the database), and with a hash function that evenly distributes the (secondary) keys across buckets (and eventually with a Hash key comparison function that sorts the keys appropriately respecting their structure/format, data type and size).
3. I assume that this is happening in a transactional environment. If so, it might worth trying to use a transaction handle in the DB->associate() call, which has been opened with the DB_TXN_WRITE_NOSYNC or DB_TXN_NOSYNC flag (see DB_ENV->txn_begin()).
Some general tuning suggestions, that could be used are also given in the following documentation sections: Access method tuning, and Transaction tuning.
Regards,
Andrei

Building secondary Index fails for large number(25,000,000) of records

I am inserting 25,000,000 records of the type:
Key --> Data
[long,String,long] --> [{long,long}, {String}}
using setSecondaryBulkLoad(true) and then build two Secondary indexes on {long,long} and {String} of the data portion.
     private void buildSecondaryIndex(DataAccessLayer dataAccessLayer ) {
          try {
               SecondaryIndex<TDetailSecondaryKey, TDetailStringKey, TDetailStringRecord> secondaryIndex = store.getSecondaryIndex(dataAccessLayer.getPrimaryIndex(), TDetailSecondaryKey.class, SECONDARY_KEY_NAME);
          } catch (DatabaseException e) {
               throw new RuntimeException(e);
It fails when I build the SecondaryIndex probably due to Java Heap Space Error. See the failure trace below.
I do not face this problem when I deal with 250,000 records.
Is there a work around that without haveing to set the memory space configurations of the JVM.
Failure Trace:
java.lang.RuntimeException: Environment invalid because of previous exception: com.sleepycat.je.RunRecoveryException
     at com.infobionics.ibperformance.TDetailStringDAOInsertTest.buildSecondaryIndex(TDetailStringDAOInsertTest.java:444)
     at com.infobionics.ibperformance.TDetailStringDAOInsertTest.insertCellSetInOneTxn(TDetailStringDAOInsertTest.java:280)
     at com.infobionics.ibperformance.TDetailStringDAOInsertTest.mainTest(TDetailStringDAOInsertTest.java:93)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
     at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
     at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
     at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
     at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
     at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66)
     at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
     at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
     at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
     at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
     at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
     at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: Environment invalid because of previous exception: com.sleepycat.je.RunRecoveryException
     at com.sleepycat.je.dbi.EnvironmentImpl.checkIfInvalid(EnvironmentImpl.java:976)
     at com.sleepycat.je.log.LogManager.getLogEntry(LogManager.java:584)
     at com.sleepycat.je.txn.Txn.undo(Txn.java:713)
     at com.sleepycat.je.txn.Txn.abortInternal(Txn.java:631)
     at com.sleepycat.je.txn.Txn.abort(Txn.java:599)
     at com.sleepycat.je.txn.AutoTxn.operationEnd(AutoTxn.java:36)
     at com.sleepycat.je.Environment.openDb(Environment.java:505)
     at com.sleepycat.je.Environment.openSecondaryDatabase(Environment.java:382)
     at com.sleepycat.persist.impl.Store.openSecondaryIndex(Store.java:684)
     at com.sleepycat.persist.impl.Store.getSecondaryIndex(Store.java:579)
     at com.sleepycat.persist.EntityStore.getSecondaryIndex(EntityStore.java:286)
     at com.infobionics.ibperformance.TDetailStringDAOInsertTest.buildSecondaryIndex(TDetailStringDAOInsertTest.java:441)
     ... 22 more
Caused by: java.lang.OutOfMemoryError: Java heap space
     at java.util.HashMap.resize(HashMap.java:462)
     at java.util.HashMap.addEntry(HashMap.java:755)
     at java.util.HashMap.put(HashMap.java:385)
     at java.util.HashSet.add(HashSet.java:200)
     at com.sleepycat.je.txn.Txn.addReadLock(Txn.java:964)
     at com.sleepycat.je.txn.Txn.addLock(Txn.java:952)
     at com.sleepycat.je.txn.LockManager.attemptLockInternal(LockManager.java:347)
     at com.sleepycat.je.txn.SyncedLockManager.attemptLock(SyncedLockManager.java:43)
     at com.sleepycat.je.txn.LockManager.lock(LockManager.java:178)
     at com.sleepycat.je.txn.Txn.lockInternal(Txn.java:295)
     at com.sleepycat.je.txn.Locker.nonBlockingLock(Locker.java:288)
     at com.sleepycat.je.dbi.CursorImpl.lockLNDeletedAllowed(CursorImpl.java:2357)
     at com.sleepycat.je.dbi.CursorImpl.lockLN(CursorImpl.java:2297)
     at com.sleepycat.je.dbi.CursorImpl.fetchCurrent(CursorImpl.java:2227)
     at com.sleepycat.je.dbi.CursorImpl.getCurrentAlreadyLatched(CursorImpl.java:1296)
     at com.sleepycat.je.dbi.CursorImpl.getNextWithKeyChangeStatus(CursorImpl.java:1442)
     at com.sleepycat.je.dbi.CursorImpl.getNext(CursorImpl.java:1368)
     at com.sleepycat.je.Cursor.retrieveNextAllowPhantoms(Cursor.java:1587)
     at com.sleepycat.je.Cursor.retrieveNext(Cursor.java:1397)
     at com.sleepycat.je.SecondaryDatabase.init(SecondaryDatabase.java:182)
     at com.sleepycat.je.SecondaryDatabase.initNew(SecondaryDatabase.java:118)
     at com.sleepycat.je.Environment.openDb(Environment.java:484)
     at com.sleepycat.je.Environment.openSecondaryDatabase(Environment.java:382)
     at com.sleepycat.persist.impl.Store.openSecondaryIndex(Store.java:684)
     at com.sleepycat.persist.impl.Store.getSecondaryIndex(Store.java:579)
     at com.sleepycat.persist.EntityStore.getSecondaryIndex(EntityStore.java:286)
     at com.infobionics.ibperformance.TDetailStringDAOInsertTest.buildSecondaryIndex(TDetailStringDAOInsertTest.java:441)
     at com.infobionics.ibperformance.TDetailStringDAOInsertTest.insertCellSetInOneTxn(TDetailStringDAOInsertTest.java:280)
     at com.infobionics.ibperformance.TDetailStringDAOInsertTest.mainTest(TDetailStringDAOInsertTest.java:93)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

1. Does the speed of building of secondary index
depend on the type of the data in the key? Will
having integers in secondary key as opposed to string
be better?The byte size of the key and data is significant of course, but the data type is not.
2. How much are we bound of the memory? Lets assume
my memory setting is fixed.
a. I know with current memory settings if I set txn
n on, I have java Heap Error.
So will I be limited on the size of
secondary index or
will it just get really slow swapping
tree information from the disk as it builds it.No. The out-of-memory error was caused by a very large transaction that holds locks. When using small transactions or non-transactional access, you won't have this problem. In general, like most databases, JE writes and reads information to/from disk as needed.
b. Is there any other way of speeding the build of
f secondary database?No, other then general performance tuning, nothing I know of.
c. Will it be more beneficial not to bulk
load when the datasize gets large
so that secondary database is built
incrementally?It's up to you whether you want to pay the price during an initial load or incrementally.
d. Do you think it will help to partition the
e original database into smaller databases
using some criteria, and thus build
smaller trees.          Why? You can use deferred write or non-transactional access to load any size database.
The only weak point in this is if we have to bulk
bulk load in one partition
at some time increasing its size we may
face the same problem againFace what problem?
--mark

Unable to Create the Secondary Index for ODS, Please..

Hi All,
The ODS 'A' has two Secondary Indexes ('010' & '020') and I want to create a third index with characteristics X & Y. X is there in both '010' & '020' Indexes.
RSA1 --> Info Provider --> Double click on ODS 'A' --> Right Click on last folder 'Indexes' --> Create --> '030' assigned by the system for the new Index.
I am having all the Characteristics in the left window after clicking the InfoObject Catalog and Characteristics
When I try to drag the 'X' from the left window to keep it under 'Indexes' folder or '030' Index, it gives 'NO'
symbol (a circle with cross line). I am not able to find the cause. I could drag it on to 'Key fields' of 'Data Fields' , but not 'Indexex' folder. Am I doing something wrong, please ?
Thanks,
Venkat.

This appeared in one of the earlier threads..
I think u need to go to se11..there enter the name of the active table of the ODS..name will be../BIC/A<ODS tech name>00'.
Once the table field appear after clicking display..
u will see button 'indexes' on right hand top..
click on that and then trying creating a new secondary index..
cheers,
Vishvesh

Where clause and joins

HI all,
If i Have a select statement that needs two different tables
and a where clause with only 1 join and the rest of conditions dependent on only 1 table such as:
select .... from table a, table b
where a.col1 = b.col1
and b.col2 some condition
and b.col3 some condition;
is it better/optima for performancel for me to have the join right at the beginning of the where clause or after table b has been filtered out such as:
select ... from table a, table b
where b.col2 some condition
and b.col3 some condition
and a.col1 = b.col1

Hi,
The order of conditions in a WHERE clause doesn't effect performance; the Cost-Based Optimizer will decide how to perform them.
The order can make a difference on how easy it is to understand and maintain the code. I find ANSI join syntax far better for this:
select      ...
from      table      a
join     table      b     on     a.col1     = b.col1
where      b.col2 <some condition>
and      b.col3 <some condition>
;

Index usage in depending on where clause changes.

Hello Friends,
I need your help for one issue.
I have one query , which is using two table Say T1 and T2, where C1 is common column using which both are joined.
C1 is primary key in T1, but no index available in T2 for C1. T1C2 is the column which we want to select.
(Note that Either of table can be a Master table)
Now see the query:
Select T1C2
From T1, T2
where T2.C1 = T1.C1
Here where clause may have other conditions and From clause may have others tables as per requirements.
I want to know that, if, I change the query like following to let my query use the available index of T1.C1.
Select T1C2
from T1, T2
where T1.C1 = T2.C1
Then, Will the query use the available index of T1. and Will i get better performance. Even a little improvement in performance may help me a lot as this kind of query is being used within a where loop (so it is going to be executed multiple times).
Please advise on this..
Regards,
Dipali..

Hi,
18:43:17 rel15_real_p>create table t1(c1 number primary key, c2 number);
Table created.
18:43:26 rel15_real_p>create table t2(c1 number, c2 number);
18:45:08 rel15_real_p>
18:45:09 rel15_real_p>begin
18:45:09   2 for i in 1..100
18:45:09   3 loop
18:45:09   4        insert into t1(c1,c2) values (i,i+100);
18:45:09   5 end loop;
18:45:09   6 commit;
18:45:09   7 end;
18:45:09   8 /
PL/SQL procedure successfully completed.
18:45:09 rel15_real_p>
18:45:09 rel15_real_p>
18:45:09 rel15_real_p>begin
18:45:09   2 for i in 1..100
18:45:09   3 loop
18:45:09   4        insert into t2(c1,c2) values (i,i+200);
18:45:09   5 end loop;
18:45:09   6 commit;
18:45:09   7 end;
18:45:09   8 /
18:45:23 rel15_real_p>select count(*) from t1;
COUNT(*)
       100
18:45:30 rel15_real_p>select count(*) from t2;
COUNT(*)
       100
18:45:49 rel15_real_p>select index_name,index_type from user_indexes where table
_name='T1';
INDEX_NAME                     INDEX_TYPE
SYS_C0013059                   NORMAL
18:48:21 rel15_real_p>set autotrace on
18:52:25 rel15_real_p>Select T1.C2
18:52:29   2 From T1, T2
18:52:29   3 where T2.C1 = T1.C1
18:52:29   4 /
        C2
       101
       102
       103
       104
       105
        C2
       200
100 rows selected.
Execution Plan
   0      SELECT STATEMENT Optimizer=ALL_ROWS (Cost=7 Card=100 Bytes=
          900)
   1    0   HASH JOIN (Cost=7 Card=100 Bytes=3900)
   2    1     TABLE ACCESS (FULL) OF 'T1' (TABLE) (Cost=3 Card=100 By
          es=2600)
   3    1     TABLE ACCESS (FULL) OF 'T2' (TABLE) (Cost=3 Card=100 By
          es=1300)
Statistics
          0 recursive calls
          0 db block gets
         21 consistent gets
          0 physical reads
          0 redo size
       1393 bytes sent via SQL*Net to client
        562 bytes received via SQL*Net from client
          8 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
        100 rows processed
18:52:31 rel15_real_p>analyze table t1 compute statistics;
Table analyzed.
18:55:35 rel15_real_p>analyze table t2 compute statistics;
18:55:38 rel15_real_p>set autotrace on
18:55:42 rel15_real_p>Select T1.C2
18:55:43   2 From T1, T2
18:55:45   3 where T2.C1 = T1.C1
18:55:46   4 /
        C2
       101
       102
       103
       104
       105
        C2
       200
100 rows selected.
Execution Plan
   0      SELECT STATEMENT Optimizer=ALL_ROWS (Cost=6 Card=100 Bytes=7
          00)
   1    0   MERGE JOIN (Cost=6 Card=100 Bytes=700)
   2    1     TABLE ACCESS (BY INDEX ROWID) OF 'T1' (TABLE) (Cost=2 Ca
          rd=100 Bytes=500)
   3    2       INDEX (FULL SCAN) OF 'SYS_C0013059' (INDEX (UNIQUE)) (
          Cost=1 Card=100)
   4    1     SORT (JOIN) (Cost=4 Card=100 Bytes=200)
   5    4       TABLE ACCESS (FULL) OF 'T2' (TABLE) (Cost=3 Card=100 B
          ytes=200)
Statistics
          1 recursive calls
          0 db block gets
         23 consistent gets
          0 physical reads
          0 redo size
       1393 bytes sent via SQL*Net to client
        562 bytes received via SQL*Net from client
          8 SQL*Net roundtrips to/from client
          1 sorts (memory)
          0 sorts (disk)
        100 rows processed
18:56:56 rel15_real_p>Select T1.C2
18:56:56   2 From T1, T2
18:56:56   3 where T1.C1 = T2.C1
18:56:58   4 /
        C2
       101
       102
       103
       104
       105
        C2
       200
100 rows selected.
Execution Plan
   0      SELECT STATEMENT Optimizer=ALL_ROWS (Cost=6 Card=100 Bytes=7
          00)
   1    0   MERGE JOIN (Cost=6 Card=100 Bytes=700)
   2    1     TABLE ACCESS (BY INDEX ROWID) OF 'T1' (TABLE) (Cost=2 Ca
          rd=100 Bytes=500)
   3    2       INDEX (FULL SCAN) OF 'SYS_C0013059' (INDEX (UNIQUE)) (
          Cost=1 Card=100)
   4    1     SORT (JOIN) (Cost=4 Card=100 Bytes=200)
   5    4       TABLE ACCESS (FULL) OF 'T2' (TABLE) (Cost=3 Card=100 B
          ytes=200)
Statistics
          1 recursive calls
          0 db block gets
         23 consistent gets
          0 physical reads
          0 redo size
       1393 bytes sent via SQL*Net to client
        562 bytes received via SQL*Net from client
          8 SQL*Net roundtrips to/from client
          1 sorts (memory)
          0 sorts (disk)
        100 rows processed- Pavan Kumar N

Function-based index with OR in the wher-clause

We have some problems with functin-based indexes and
the or-condition in a where-clause.
--We use Oracle 8i (8.1.7)
create table TPERSON(ID number(10),NAME varchar2(20),...);
create index I_NORMAL_TPERSON_NAME on TPERSON(NAME);
create index I_FUNCTION_TPERSON_NAME on TPERSON(UPPER(NAME));
The following two statements run very fast on a large table
and the execution-plan asure the usage of the indexes
(-while the session is appropriate configured and the table is analyzed):
1)     select count(ID) FROM TPERSON where upper(NAME) like 'MIL%';
2)     select count(ID) from TPERSON where NAME like 'Mil%' or (3=5);
In particular we see that a normal index is used while the where-clause contains
an OR-CONDITION.
But if we try the similarly select-statement
3)     select count(ID) FROM TPERSON where upper(NAME) like 'MIL%' or (3=5);
the CBO will not use the function-index I_FUNCTION_TPERSON_NAME and we have a full table scan in the execution-plan.
(This behavior we only expect with views but not with indexes.)
We ask for an advice like a hint, which enable the CBO-usage
of function-based indexes in connection with OR.
This problem seems to be artificial because it contains this dummy logic:
     or (3=5).
This steams from an prepared statement, where this kind of boolean
flag reduce the amount of different select-statements needed for
covering the hole business-logic, while using bind-variables for the
concrete query-parameters.
A more realistic (still boild down) version of our select-statement is:
select * FROM TPERSON
where (upper(NAME) like 'MIL%' or (NAME is null))
and (upper(FIRSTNAME) like 'MICH% or (FIRSTNAME is null))
and ...;
thank you for time..
email: [email protected]

In the realistic statement you write :
select * FROM TPERSON
where (upper(NAME) like 'MIL%' or (NAME is null))
and (upper(FIRSTNAME) like 'MICH% or (FIRSTNAME is null))
and ...;
as far as i know, NULL values are not indexed, "or (NAME is NULL)" have to generate a full table scan.
HTH
We have some problems with functin-based indexes and
the or-condition in a where-clause.
--We use Oracle 8i (8.1.7)
create table TPERSON(ID number(10),NAME varchar2(20),...);
create index I_NORMAL_TPERSON_NAME on TPERSON(NAME);
create index I_FUNCTION_TPERSON_NAME on TPERSON(UPPER(NAME));
The following two statements run very fast on a large table
and the execution-plan asure the usage of the indexes
(-while the session is appropriate configured and the table is analyzed):
1)     select count(ID) FROM TPERSON where upper(NAME) like 'MIL%';
2)     select count(ID) from TPERSON where NAME like 'Mil%' or (3=5);
In particular we see that a normal index is used while the where-clause contains
an OR-CONDITION.
But if we try the similarly select-statement
3)     select count(ID) FROM TPERSON where upper(NAME) like 'MIL%' or (3=5);
the CBO will not use the function-index I_FUNCTION_TPERSON_NAME and we have a full table scan in the execution-plan.
(This behavior we only expect with views but not with indexes.)
We ask for an advice like a hint, which enable the CBO-usage
of function-based indexes in connection with OR.
This problem seems to be artificial because it contains this dummy logic:
     or (3=5).
This steams from an prepared statement, where this kind of boolean
flag reduce the amount of different select-statements needed for
covering the hole business-logic, while using bind-variables for the
concrete query-parameters.
A more realistic (still boild down) version of our select-statement is:
select * FROM TPERSON
where (upper(NAME) like 'MIL%' or (NAME is null))
and (upper(FIRSTNAME) like 'MICH% or (FIRSTNAME is null))
and ...;
thank you for time..
email: [email protected]

When is a secondary index used (in select or where)

HI All,
We are confused (and new to ABAP) on the various postings on SDN concerning this topic. Replies seem to vary.
We have the following select statement:
SELECT date1 FROM table2
WHERE material (from a stored internal table) = material-table2
AND order (from a stored internal table) = order-table2
AND delivery method (from a stored internal table) = specific value of table2.
For a second index to be created, would we create the index for only date1 (since it's the only field we are selecting from table 2) or an index with date1, material, order, delivery method or just what's in the WHERE clause of material, order and delivery method?
How can you be sure that an index will be used?
Thank you!

> We are confused (and new to ABAP)
seem you are very very new.
Your question is actually not ABAP indexes etc are SQL and can be found in many textbooks also on Wiki pages. ABAP uses SQL, but does not change much.
The use index is determined nearly only by the WHERE clause. You want to know the phone number of somebody and you know the name and the address. The Index uses the name and the address as a telephone book. The phone number comes from the table not the index! This is not the secondary index, but the primary index.
If you search in the internet for phone number, then you can use also a secondary index, i.e. you know only the complete address but not the name. A phone book would not help here.
Which index is used, if often very simple as in the example, but can become very difficult. That is done by a sophisticated program of the database, the optimizer. Check other resoucres for details.
Siegfried

Function-based Index and an OR-condition in the WHERE-clause

We have some problems with functin-based indexes and
the or-condition in a where-clause.
(We use oracle 8i (8.1.7))
create table TPERSON(ID number(10),NAME varchar2(20),...);
create index I_NORMAL_TPERSON_NAME on TPERSON(NAME);
create index I_FUNCTION_TPERSON_NAME on TPERSON(UPPER(NAME));
The following two statements run very fast on a large table
and the execution-plan asure the usage of the indexes
(-while the session is appropriate configured and the table is analyzed):
1)     select count(ID) FROM TPERSON where upper(NAME) like 'MIL%';
2)     select count(ID) from TPERSON where NAME like 'Mil%' or (3=5);
In particular we see that a normal index is used while the where-clause contains
an OR-CONDITION.
But if we try the similarly select-statement
3)     select count(ID) FROM TPERSON where upper(NAME) like 'MIL%' or (3=5);
the CBO will not use the function-index.
(This behavior we only expect with views but not with indexes.)
We ask for an advice like an hint, which enable the CBO-usage
of function-based indexes in connection with OR.
This problem seems to be artificial because it contains this dummy logic:
     or (3=5).
This steams from an prepared statement, where this kind of boolean
flag reduce the amount of different select-statements needed for
covering the hole business-logic, while using bind-variables for the
concrete query-parameters.
A more realistic (still boild down) version of our prepared select-statement run in
SQL Plus:
define x_name = 'MIL%';
define x_firstname = '';
select * FROM TPERSON
where (upper(NAME) like '&x_name' or ( '&x_name' = ''))
and (upper(FIRSTNAME) like '&x_firstname' or ('&x_firstname' = ''))
and ...;
In particular we dont refernce the tablecolumn , but the QUERY-Parameter
yield the second boolean value in the or-condition.
The problem is that this condition ('&x_name' = '') dont use any index.
thanks a lot for spending your time with this problem

Try
SELECT /*+ RULE */
as your hint. I don't have the book with me, but this last weekend I read a section about your very problem. The book was a Oracle Press gold cover about Oracle 8i Performance tuning. If you e-mail me I can quote you the chapter when I get home Friday.

Using a dummy where-clause to force the use of an index

I notice that an index only gets used when I use the index key in the where clause. Should I use a dummy where clause to force the index to be used?
SQL> create table emp (
2 empno NUMBER(5),
3 empname VARCHAR2(15) );
Table created.
SQL> create index idx_emp_no on emp (empno);
Index created.
SQL> insert into emp (empno, empname) values (1, 'Peter');
1 row created.
SQL> set autotrace traceonly;
SQL> select empno from emp;
Execution Plan
Plan hash value: 3956160932
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 1 | 13 | 3 (0)| 00:00:01 |
| 1 | TABLE ACCESS FULL| EMP | 1 | 13 | 3 (0)| 00:00:01 |
SQL> select empno from emp where empno > 0;
Execution Plan
Plan hash value: 434430053
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 1 | 13 | 1 (0)| 00:00:01 |
|* 1 | INDEX RANGE SCAN| IDX_EMP_NO | 1 | 13 | 1 (0)| 00:00:01 |
As you can see, using a dummy where clause (empno > 0), I manage to reduce the cost from 3 to 1.

Again. Be careful with comparisons. But I like the discussion. It is usefull to carefully look at what happens "behind the scenes" and find a sensible explaination for that.
Your new scenario now is different. By selecting one specific row instead of selection all you already made an assumption. That only one or few of the rows are returned. Andre's statement still is correct. Now the CBO will prefere the index scan.
The CBO now has to decide between two options.
Option a) use the index.
This means =>
Step 1: Access the index to find the value
Step 2: Access the table using the rowid that was found in the index leaf entry.
Option b) scan the full table
This means =>
Step 1: Iterate over all rows of the table
Step 2: Apply a filter condition (empno = :x)
We can see this execution plan by adding a hint to the query.
select /*+ FULL(emp) */ * from emp where empno = 1;This hint will force the CBO to access the table emp using a full table scan.
The cost in my environment for option B is 3.
Option A has a cost with 2. Therefore the CBO prefers Option A.
However this can easily change.
Consider the following
begin
for i in 1..1000 loop
    insert into emp (empno, empname) values (1, 'Employee');
end loop;
end;
commit;
execute dbms_stats.gather_table_stats(user,'EMP');The run the select again.
SQL> set autotrace traceonly
SQL> select * from emp where empno = 1;
1001 Zeilen ausgewõhlt.
Ausf³hrungsplan
Plan hash value: 3956160932
| Id | Operation         | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |      | 1001 | 12012 |     3   (0)| 00:00:01 |
|* 1 | TABLE ACCESS FULL| EMP | 1001 | 12012 |     3   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter("EMPNO"=1)
Statistiken
          1 recursive calls
          0 db block gets
         74 consistent gets
          0 physical reads
          0 redo size
      18356 bytes sent via SQL*Net to client
       1250 bytes received via SQL*Net from client
         68 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
       1001 rows processedThe CBO now prefers the full table scan and not the index access.
If we force it to use an index then the cost increases.
SQL> set linesize 100
SQL> select /*+INDEX(emp) */ * from emp where empno = 1
1001 Zeilen ausgewõhlt.
Ausf³hrungsplan
Plan hash value: 2426388914
| Id | Operation                   | Name      | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT            |           | 1001 | 12012 |     5   (0)| 00:00:01 |
|   1 | TABLE ACCESS BY INDEX ROWID| EMP       | 1001 | 12012 |     5   (0)| 00:00:01 |
|* 2 |   INDEX RANGE SCAN          | IDX_EMPNO | 1001 |       |     2   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   2 - access("EMPNO"=1)
Statistiken
          0 recursive calls
          0 db block gets
        139 consistent gets
          0 physical reads
          0 redo size
      30550 bytes sent via SQL*Net to client
       1250 bytes received via SQL*Net from client
         67 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
       1001 rows processed
SQL>The cost using the index range scan is now 5. WHile the FTS is still 3. Therefore the CBO prefers to use the FTS.

Two secondary indexes in a where clause

Similar Messages

Maybe you are looking for