Index column limit of 16

Hello,
We are running SAP R/3 Enterprise 4.7 on an Oracle 9.2.0.7.0 database and have an issue with a limit on a table index of 16 fields. The Oracle version has a limit of 32 but the SAP application doesn't allow more than 16.
Has anyone else encountered this problem and, if so, have you found a way around it or just lived with the restriction?
Thanks,
Paul.

Hi Paul,
since the ABAP/4 Dictionary is designed to db independend, there are several occurences where you cannot use up the options of the underlying db to the fullest.
Leaving aside for a moment that a 16 field secondary index is rather big you might use a workaround here.
Define a smaller index in SE11 but do create the index as you like it on the DB via sqlplus. That way you cannot transport the index but the DB02 DB check will find the index from the ABAP/4 DDIC on the DB.
Before you create that kind of index you really should doublecheck if this index is what your application really needs. Keep in mind that there is a considerable amount of work to be done to maintain such a big index and that it will allocate much space as well.
KR Lars

Similar Messages

Default Filter Criteria - "Current (Indexed)" Column?

Hello Technet,
When you create a "Standard View" in SharePoint online, if you look under the Filter section, a default filter is automatically added on the "Current (Indexed)" column, causing the list to show only list items that have Current = Yes.
My question is in two parts;
What does this Current (Indexed) column mean/do?
Why, as my list approached 2500 items, are many of the newly created list items not showing in views that have this criteria?
I am unable to find that column when I modify the list so I assume it has something to do with SharePoint's automatic version control. I'm not getting why all of a sudden this would not be working? One thought, I do know that SharePoint lists
are limited to a 5,000 item limit, is it possible the "versions" list, if that exists on the back-end, has gotten too large and is no longer saving items?

As there is no default view with a filter already enabled OOTB I would suggest you to create a service ticket at O365 support or via MS Premier Support.
Michiel Hamers www.SharePointman.nl Don't hesitate to contact me for a SharePoint/O365 question.

ORDER BY ON INDEX COLUMN IS TAKING MORE TIME

Hi,
The following SQL query when executed with ORDER BY is taking 3 mins. If we remove ORDER BY it is taking 32 secs. We have an index on ID which is used in ORDER BY clause. Can any one tell us what could be wrong? My assumption is ORDER BY on an index column should not take that much of time. Is there any configuration that we need to make or missing?
We are on 11g R2.
Query is
SELECT * FROM (SELECT /*+ FIRST_ROWS */ a.*, ROWNUM rnum FROM
(SELECT DISTINCT ENTITYID AS a1, ENTITYCLASS AS a2, STARTDATE AS a3, ENDDATE AS a4, EXTERNALOBJECTID AS a5, LASTMODIFIEDUSER AS a6, ID AS a7, PARTITION AS a8, DESCRIPTION AS a9, NAME AS a10, PERMISSIONS AS a11, CREATEDDATE AS a12, ACTIVITY AS a13, ENTITYVERSION AS a14, EXTERNALNAME AS a15, NOSPEC AS a16,
ADMINSTATE AS a17, OWNER AS a18, LASTMODIFIEDDATE AS a19, EXTERNALARRANGEMENT AS a20, OBJECTSTATE AS a21, EXTERNALMANAGEMENTDOMAIN AS a22,
CREATEDUSER AS a23, SPECIFICATION AS a24 FROM Service WHERE (ENTITYCLASS = 'SERVICEDAO') ORDER BY ID ASC)
a WHERE ROWNUM <= 25) WHERE rnum > 0Here is the explain plan link
https://stbeehive.oracle.com/content/dav/st/Rama%20%20Public%20Workspace/Public%20Documents/explainplan_13339959.JPG
https://stbeehive.oracle.com/content/dav/st/Rama%20%20Public%20Workspace/Public%20Documents/explainplandetailed_13339959.JPG
Thanks,
Rama
Edited by: user9954330 on Nov 8, 2011 1:16 AM

user9954330 wrote:
We replaced the hint with ALL_ROWS. With this change , we observed the query performed worse. Any other pointers? I will provide the other details as given in the template shortly.
Thanks,
RamaThread: HOW TO: Post a SQL statement tuning request - template posting
HOW TO: Post a SQL statement tuning request - template posting

Why oracle text index column taking long time

why oracle text index column is taking long time to return result.I created text index on a column if I run the query on a single table result is very fast.If I join table with other table (10 records only )
it is taking long time but in explain plan it is searching by index only.
I created this index for searching a varchar2 column,the data is comma seperated values like ( UK,US,IT,BR) and the table having records 20 lakhs.Normally if I query with like operater
( like '%US%' ) it is taking full table scan because I am using '%' both sides. Please help me on this regard how to search the data with less time. Here is may sample code and explain plan.
SQL*Plus: Release 9.2.0.1.0 - Production on Wed Jan 28 16:54:22 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> set timing on
SQL> set linesize 180
SQL> explain plan for SELECT T.esongid FROM (SELECT A.ESONGID FROM wcmedeco.EDECO_ESONGS_TERR_CTRY
A WHERE CONTAINS(A.TERR_CTRY_NAMES,'US')>0
2 GROUP BY A.ESONGID)K,T
3 WHERE K.ESONGID=T.ESONGID;
Explained.
Elapsed: 00:00:00.01
SQL> select *from table(dbms_xplan.display);
PLAN_TABLE_OUTPUT
| Id | Operation                      | Name                   | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT               |                         |     1 |    26 |     4 |
|   1 | NESTED LOOPS                  |                         |     1 |    26 |     4 |
|   2 |   VIEW                         |                         |     1 |    13 |     4 |
|   3 |    SORT GROUP BY               |                         |     1 |    89 |     4 |
|   4 |     TABLE ACCESS BY INDEX ROWID| EDECO_ESONGS_TERR_CTRY |     1 |    89 |     2 |
|   5 |      DOMAIN INDEX              | IDX_TERR_CTRY_NAMES     |       |       |     0 |
|   6 |   INDEX RANGE SCAN             | IDX_ESONGID_T           |     1 |    13 |     1 |
PLAN_TABLE_OUTPUT
Note: cpu costing is off, 'PLAN_TABLE' is old version
14 rows selected.
Elapsed: 00:00:00.00
SQL> Regards,
Rajasekhar

You have not formatted your code properly so we cannot see the query you're executing. Please put some line breaks in.
Secondly, how fresh are the statistics on those tables? Are you really returning one record out of twenty million?
Cheers, APC
blog: http://radiofreetooting.blogspot.com

Gather_table_stats with a method opt of "for all indexed columns size 0"

I have 9 databases I support that contain the same structure, and very similar data concentrations. We are seeing inconsistent performance in the different databases due to bind variable peeking.. I have tracked it down to the Min and Max values that are gathered during the analyze. I analyze from one cluster, and export/import those statistics into the other clusters.. I then go about locking down the stats gathered. Some of the statistics are on tables that contain transient data (the older data is purged, and new data gets a new PK sequence number).
Since I am gathering statistics with a 'FOR ALL INDEXED COLUMNS SIZE 1', a min and max value are grabbed. This value is only appropriate for a short period of time, and only for a specific database. I do want oracle to know the density to help calculate, but I don't want cardinality based on whether the current bind values fall in this range..
Example
COLUMN PK
When I analyze the min is 1 and max is 5. I then let the database run, and the new min is 100 and max is 105.. same number of rows, but different min/max. At first a select * from table where pk>=1 and pk <=5 would return a cardinality of 5.. Later, a seelct * from tables where pk>=100 and pk<=105 would return a cardinaility 1.
Any ideas how to avoid this other than trying set min and max to something myself (like min =1 max = 99999999). ??

MarkDPowell wrote:
The Oracle documentation on bind variable peeking said it did not peek without histograms and I cannot remember ever seeing on 9.2 where the trace showed otherwise. Mark,
see this simple test case run on 9.2.0.8. No histograms, but bind variable peeking, as you can see that the EXPLAIN PLAN output generated by AUTOTRACE differs from the estimated cardinality of the actual plan used at runtime.
Which documentation do you refer to?
SQL>
SQL> alter session set nls_language = 'AMERICAN';
Session altered.
SQL>
SQL> drop table bind_peek_test;
Table dropped.
SQL>
SQL> create table bind_peek_test
2 as
3 select
4            100 as n1
5          , cast(dbms_random.string('a', 20) as varchar2(20)) as filler
6 from
7            dual
8 connect by
9            level <= 1000;
Table created.
SQL>
SQL> exec dbms_stats.gather_table_stats(null, 'bind_peek_test', method_opt=>'FOR ALL COLUMNS SIZE 1')
PL/SQL procedure successfully completed.
SQL>
SQL> variable n number
SQL>
SQL> variable n2 number
SQL>
SQL> alter system flush shared_pool;
System altered.
SQL>
SQL> exec :n := 1; :n2 := 50;
PL/SQL procedure successfully completed.
SQL>
SQL> set autotrace traceonly
SQL>
SQL> select * from bind_peek_test where n1 >= :n and n1 <= :n2;
no rows selected
Execution Plan
   0      SELECT STATEMENT Optimizer=CHOOSE (Cost=2 Card=1000 Bytes=24
          000)
   1    0   FILTER
   2    1     TABLE ACCESS (FULL) OF 'BIND_PEEK_TEST' (Cost=2 Card=100
          0 Bytes=24000)
Statistics
        236 recursive calls
          0 db block gets
         35 consistent gets
          0 physical reads
          0 redo size
        299 bytes sent via SQL*Net to client
        372 bytes received via SQL*Net from client
          1 SQL*Net roundtrips to/from client
          4 sorts (memory)
          0 sorts (disk)
          0 rows processed
SQL>
SQL> set autotrace off
SQL>
SQL> select
2            cardinality
3 from
4            v$sql_plan
5 where
6            cardinality is not null
7 and      hash_value in (
8    select
9           hash_value
10    from
11           v$sql
12    where
13           sql_text like 'select * from bind_peek_test%'
14    );
CARDINALITY
          1
SQL>
SQL> alter system flush shared_pool;
System altered.
SQL>
SQL> exec :n := 100; :n2 := 100;
PL/SQL procedure successfully completed.
SQL>
SQL> set autotrace traceonly
SQL>
SQL> select * from bind_peek_test where n1 >= :n and n1 <= :n2;
1000 rows selected.
Execution Plan
   0      SELECT STATEMENT Optimizer=CHOOSE (Cost=2 Card=1000 Bytes=24
          000)
   1    0   FILTER
   2    1     TABLE ACCESS (FULL) OF 'BIND_PEEK_TEST' (Cost=2 Card=100
          0 Bytes=24000)
Statistics
        236 recursive calls
          0 db block gets
        102 consistent gets
          0 physical reads
          0 redo size
      34435 bytes sent via SQL*Net to client
       1109 bytes received via SQL*Net from client
         68 SQL*Net roundtrips to/from client
          4 sorts (memory)
          0 sorts (disk)
       1000 rows processed
SQL>
SQL> set autotrace off
SQL>
SQL> select
2            cardinality
3 from
4            v$sql_plan
5 where
6            cardinality is not null
7 and      hash_value = (
8    select
9           hash_value
10    from
11           v$sql
12    where
13           sql_text like 'select * from bind_peek_test%'
14    );
CARDINALITY
       1000
SQL>
SQL> spool offRegards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Column limit of an ALV diplay

Hi All
I have a report which is in ABAP classical report format
since because of exceeding no. of columns of its limit(i.e. 1024) data is not getting displayed.
To alleviate can can we go for ALV display??Kindly let
me know what is column limit for ALVs.
Thanks & Regards
Vipin

HI vipin,
1. the limit is 90 columns
regards,
amit m.

Indexed columns became unusable. how to resolve it

Hi All,
i have truncated the data using alter command as follows .
alter table table_one truncate partition (partitionname);
After that i was trying to insert data into that table am getting an error. And all indexes columns became unusable. i think doing truncate the partition i am facing this problem.
can any one suggest me to how to make it.. usable.
i am using tode
Thanks
Sree

874823 wrote:
Hi All,
i have truncated the data using alter command as follows .
alter table table_one truncate partition (partitionname);
After that i was trying to insert data into that table am getting an error. And all indexes columns became unusable. i think doing truncate the partition i am facing this problem.
can any one suggest me to how to make it.. usable.
i am using tode
Thanks
SreeI assume you have an unusable global index?
http://docs.oracle.com/cd/B10501_01/server.920/a96521/partiti.htm#27573
Rebuild the index, and next time include the "update global indexes" clause with the truncate command.

What value for DBMS_STATS method_opt= 'for all indexed columns ???'

What value, one should use for method_opt , while collecting stats for database/schema/table.
It is obseverd AUTO never give good result, in some case "for all indexed columns 1" work fine and some case "for all indexed columns 254".
Please advise , what is right way to collect stats.
OS : Linux AS 4
DB : 9.2.0.8 , 10.2.0.3
Thanks

Gather AUTO. Gathers all necessary statistics automatically. Oracle implicitly determines which objects need new statistics, and determines how to gather those statistics. When GATHER AUTO is specified, the only additional valid parameters are stattab, statid, objlist and statown; all other parameter settings are ignored. Returns a list of processed objects.
If you specify the for all indexed columns, or specify the column, it will gather histograms. Those are useful if you have an uneven data distribution, and are specially useful for DSS databases, where Oracle will determine if a column is suitable, on a given data rage, to perform full table scan or index scan. If uncertain about it I suggest you not to gather column statistics, as they are costly.
~ Madrid.

Bug in ODT 11720 - indexed columns list in Design Table is disabled

Start VS2008
Server Explorer
Expand any oracle db
Expand Tables
Design any existing table that has an existing index that indexes more than 3 columns
Click Indexes tab
Click the index name
Try to scroll the list of indexed columns, because youre curious which columns are indexed and what order
You cant, because the control is disabled

Checks should be made to see if other controls (such as the text box for CHECK code, or the list for PKs) are similarly affected

Opening TDMS files in Excel - column limit

Hi all,
I'm saving data I obtain using LabVIEW as a TDMS file and have downloaded the add-in to open the files in Excel:
http://zone.ni.com/devzone/cda/epd/p/id/2944
I'm using Excel 2007, which has a column limit of 16384 and a row limit of 1048576. Each of my datasets is 1024 rows values large and I have 10,000 datasets in total - well within either limit. However, the Excel importer will not open the file - pop-up errors occur and Excel opens multiple files. Has anyone encountered this before?
Miika

Have the same issue. As requested, I've attached a file with 300 dummy groups, each of which as 4 channels of dummy data.
When loaded into Excel, only the first 254 groups are shown:
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs
Attachments:
abc.vi ‏3381 KB

Order of indexed columns in the index

Hi Gurus,
I have a small problem in front of me and I wud like to take some inputs
from you Gurus.Here is question
1. Is order of the index is important in CBO?
say
1.I have a concatenated index on col1,col2
2.In the sql statement's used in my project I have statements "where
col1=1 and col2 = 1" as well as
"where col2=1 and col1=1" and my opinion is that CBO will use the Index
in both the scenarios( I have cheked RBO for the same and RBO is able to
use the index) whereas some senior persons out here are telling
otherwise..... that it will not use the index for "where col2=1 and
Col1=1)
pls clarify
Cheers
Sriram Kumar

When I attended an Oracle 8i SQL Statement Tuning Workshop, I believe I understood things as in the response above. However, the class was applicable to Oracle 8.1.5 and I am now using Oracle 8.1.7, so some things may have changed. I have included a test of various scenarios below. I would have expected all except the last one to use the index, because col2 is not the leading edge of the composite index on col1, col2. Much to my surprise it also used the index there.
SQL> CREATE TABLE test_table AS
2 SELECT empno col1, mgr col2 FROM emp
3 /
Table created.
SQL> UPDATE test_table
2 SET    col1 = 1, col2 = 1
3 WHERE col1 = 7782
4 AND    col2 = 7839
5 /
1 row updated.
SQL> CREATE INDEX test_idx
2 ON test_table (col1, col2)
3 /
Index created.
SQL> ANALYZE TABLE test_table
2 COMPUTE STATISTICS
3 FOR TABLE
4 FOR ALL INDEXES
5 FOR ALL INDEXED COLUMNS
6 /
Table analyzed.
SQL> SET AUTOTRACE ON EXPLAIN
SQL> SELECT * FROM test_table
2 WHERE col1 = 1 AND col2 = 1
3 /
      COL1       COL2
         1          1
1 row selected.
Execution Plan
   0
SELECT STATEMENT Optimizer=CHOOSE (Cost=1 Card=1 Bytes=6)
   1    0
INDEX (RANGE SCAN) OF 'TEST_IDX' (NON-UNIQUE) (Cost=1 Card
=1 Bytes=6)
SQL> SELECT * FROM test_table
2 WHERE col2 = 1 AND col1 = 1
3 /
      COL1       COL2
         1          1
1 row selected.
Execution Plan
   0
SELECT STATEMENT Optimizer=CHOOSE (Cost=1 Card=1 Bytes=6)
   1    0
INDEX (RANGE SCAN) OF 'TEST_IDX' (NON-UNIQUE) (Cost=1 Card
=1 Bytes=6)
SQL> SELECT * FROM test_table
2 WHERE col1 = 1
3 /
      COL1       COL2
         1          1
1 row selected.
Execution Plan
   0
SELECT STATEMENT Optimizer=CHOOSE (Cost=1 Card=1 Bytes=6)
   1    0
INDEX (RANGE SCAN) OF 'TEST_IDX' (NON-UNIQUE) (Cost=1 Card
=1 Bytes=6)
SQL> SELECT * FROM test_table
2 WHERE col2 = 1
3 /
      COL1       COL2
         1          1
1 row selected.
Execution Plan
   0
SELECT STATEMENT Optimizer=CHOOSE (Cost=1 Card=1 Bytes=6)
   1    0
INDEX (FULL SCAN) OF 'TEST_IDX' (NON-UNIQUE) (Cost=1 Card=
1 Bytes=6)

1.5PROD/EA3/EA2 - Issues removing indexed column through Edit Table dialog

The Edit Table dialog does not cope well with removing a column which is used in indexes.
If you simply remove the column and hit OK, you get a Validation Failed error saying that "Column <column> is not a column of table <table>". Given that you are trying to remove the column, this is confusing.
Most times, you can navigate to the indexes but the column no longer shows in the index which contained (and all other columns in the index appear to be removed as well). At least you can remove the index and then accept the change. However, some times (couldn't reproduce consistently), the index didn't display properly (no name displayed) and I couldn't leave the record without entering a dummy name before removing it.
Shouldn't the behaviour be equivalent to the "corresponding" alter table drop column command which automatically drops the indexes referring to the dropped column? I know that it isn't always nice to "silently" remove an index or indexes, but couldn't we display a dialog that indicates which indexes we are going to drop to warn the user?
theFurryOne

No response to this, but it is still a problem in EA3.
I assume it is not intended that you cannot drop an indexed column through the Edit Table dialog, without having to first drop the index - it is certainly not required in direct SQL and the Drop Column via the Table context menu works as well (as that simply generates the SQL).
theFurryOne

Opty-Prod Reports: Indexed columns of Opty-Prod

Hi,
I am hoping to understand the reasons why the indexed columns of the Opty-Product object are not available for Opty-Product Report. I need to explain this to our users and I have no clue. Our users are reasonably aware of reports/analytics and the absence of indexed columns in reports is confusing.
Any thoughts?

PR, the missing indexed fields in the Opty-Prod real-time reports is something I reported to Oracle a few months ago, their response was "thankyou for you request we'll consider this at a future date". I don't use the Indexed fields for Opty-Product I create new ones, you can't use them in lists and reporting can be pretty quick anyway so I don't see a benfit to using them. # periods and the date field is missing too ;-D
cheers
Alex

Histogram on non-indexed columns

Hi All,
Is there any point in having histogram on non-indexed column? If we use a non-indexed column for filtering data, there will be a full table scan anyway.
Does having histogram in such column make any difference.
I am on v11.2. Are there any differences/advances in this respect in 11g ?
Thanks in advance.

rahulras wrote:
Hi All,
Is there any point in having histogram on non-indexed column? If we use a non-indexed column for filtering data, there will be a full table scan anyway.
Does having histogram in such column make any difference.
I am on v11.2. Are there any differences/advances in this respect in 11g ?
Thanks in advance.Histogram used to correct estimate selectivity(~ cardinality) by CBO if there are indexes or no!.So if there are indexes then after estimating selectivity based on values CBO can be select FULL TABLE SCAN but not INDEX SCAN!.Finally histograms use when your columns data non uniform distributed(actually skewed).

How to retrieve the content of the indexed column

In Oracle UltraSearch, how to retrieve the content of the file in the indexed column cache_file_path.
we try the flowing sql
SELECT cache_file_path FROM mytable
WHERE contains (mytable.cache_file_path, 'viet', 1) > 0
but we only have the cache_file_path column, not the content of the file were indexed.

I think this is what you're looking for:
DECLARE @table TABLE (amountPaid FLOAT, datePaid DATE, memberID INT)
INSERT INTO @table (amountPaid, datePaid, memberID) VALUES
(10.00, '2014-01-01',1),(10.00, '2014-02-01',2),(10.00, '2014-03-01',3),(10.00, '2014-04-01',4),(10.00, '2014-05-01',5),(10.00, '2014-06-01',6),(10.00, '2014-07-01',7),(10.00, '2014-08-01',8),(10.00, '2014-01-01',9),(10.00, '2014-10-01',10)
SELECT *
FROM (
SELECT *, SUM(amountPaid) OVER (ORDER BY datePaid ROWS UNBOUNDED PRECEDING) AS runningTotal, ((SELECT SUM(amountPaid) FROM @table) / 100) * 50 AS percentileAmount
FROM @table
) x
WHERE percentileAmount >= runningTotal
It depends upon SQL Server 2012's windowed functions. It would be possible to also do this with a rCTE in earlier versions.
Giving your code an eyball, I think I see what it's doing. Unfortunately, I'm stuck using 2008 R2, so I don't have access to UNBOUNDED or PRECEDING. I'll have to research rCTE - I know what a CTE is, but not the 'r' prefix.

Index column limit of 16

Similar Messages

Maybe you are looking for