on 06-01-2012 2:10 AM
Hi experts.
Our DB is Oracle 10g.
The problem is
our update processes are only 7, and when I try to create a index in huge table,
all the update process is fulled with index creation(in SM50), so no one can update to any other table.
I mean that when I create an index, all the other update processes are delayed.
I think I can set the maximum process usage when create index.
Then I'll set 3 or 4 process at once when create index, but I can't find the way to do.
Or am I have to increase the number of update process?
Which one is possible? And how can I do that?
It looks like you are having a lot of user activity on that table. One possibility is to try to create the index, when not nothing else is running on the system.
Cheers Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Kim,
I agree with Joe answer. You don't need to increase number update. It won't solve your problem. You should follow below recommendation:
For tables larger than 1GB:
You may need a long time to create the index. Database specific options may be available to accelerate index creation.
When you want to use a database specific method to accelerate index creations you can use the following method:
Template: Create the index using SQLPLUS with the following command:
CREATE INDEX "BSIS~Z" ON BSIS (BUKRS, HKONT, BUDAT, BLART) TABLESPACE PSAPBTABI ONLINE COMPRESS 6 PCTFREE 1 PARALLEL 6 NOLOGGING;
ALTER INDEX "BSIS~Z" NOPARALLEL LOGGING;
-----------------------------------------------------------------------------
SAP Note released: 334224 - Important notes for creating indexes
Hope it help you,
Jairo Pedroza
In short, you said that I have to make the shape of the index first what is empty at QA system.
Then make the index at Developement system and transport to QA system.
And if it's not in trouble, make the shape of the index at Production system.
And transport from QA to Production.
Is this right?
And I wonder that if I'm not make the shape of the index and transport to Production system, then the Update process is fully used?
Am I right?
Hello Kim,
I have used this process often. Let me try to explain.
1.You will create index in Development System using SE11. In this case, it will create in SAP Dictionary and in DB.
2.Generate request
3. Go to Quality Assurance and create index using SQLPLUS and later, transport request in order to adjust SAP Dictionary.
4.If everything is OK, repeat process 3 in production system.
You won't have problem with SAP update process, because when you transport request, it will see index already exist in DB and will create in SAP Dictionary. It is really fast.
Regards,
Jairo Pedroza
Increasing number of update processes won't help.
I think your problem is quite different.
Table will be locked during index creation, and update processes have to wait.
There used to be a SAP note describing a workaround,
Note 334224 - Important notes for creating indexes
Unfortunately that note isn't available currently.
If your index isn't that urgent, you might consider to wait till that SAP note will be there again.
hope this helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.