Adding a secondary index to a cluster table (e.g. CDCLS)
As far as I am aware it is not possible to add a secondary index to a SAP cluster table such as CDCLS.
During our Unicode upgrade the big SAP cluster tables are taking a long time so we emailed SAP about the problem. Their reply was to add a secondary index to the cluster table with the field 'pagelg'. I replied that I didn't think that is possible to add a second index and they have sent a reply back saying that it is not possible through SE11 but you can use database utilities.
Anyone any ideas? The unicode help at SAP have not given us this advice (they can't seem to answer the question) it was someone else in their active global support.
I'm going to move this to the BASIS forum as indexes really aren't an ABAP issue, however I've just been in SE14 in our 4.6C system and if I look at Pool/Cluster tables I cannot create a secondary index at all.... so I am wondering if you have just had a really bad bit of support.
I would go back to SAP (preferably by phone) and ask the monkey that told you it could be done to talk you through the procedure / put you on to someone who can *that'll sort out the bull from the useful*
_________________
Kind Regards
Rosie Brent
Please remember to search the forum and check the FAQ before posting questions, thank you.
Tuly Idiot most of the time, part-time Guru
Hi Rosie,
I wasn't sure myself which was the most appropriate forum for this to be honest. Went for ABAP because it is usually the ABAPer who gets to make changes to the tables.
Here is one line of the response from the person at SAP...
I had also found that other customer can create index on table cluster. It also say that index on table cluster can only created with database utilities, and not via SE14, or SE11 etc. I hope the above is of help and clear to you.
RESOLVED!
SAP now replied saying "Database Utilities meaning Oracle Sqlplus"
Always confusing: Table cluster vs. Cluster table. A SAP Cluster table is a transparent table in Oracle. So through Oracle you can put indexes on them.
I agree with Rosie.
Once on 3.1H I added an index to a cluster table, and had "HELL" fall upon me. The response time went down by 50% and said table was always present in sm50. Dropped the index and everything came back to normal. I would say stick to the primary key index these tables have and don't fool around with them.