I checked the Instance Manager and found the max_rollback_segments were used out(used 26 of 26),
enqueue_locks and processes are also nearly used out
(both used 12 of 17). What can I do to it?
Your questions are somewhat confusing.
This parameters limits the number of rollback segments that can be online simultaneously. You said you have 26 of 26 "used" - this means that you have 26 rollback segments online which is also the above limit for your instance currently. Nothing wrong with this. I f you realy need more rollback segments online then you must restart the instance with a higher value for this parameter.
"used 12 of 17". If this means that you have set the processes to 17 and you currently have 12 processes, than something is wrong with the whole setup of your database (or maybe I'm missing something). First of all if your process parameter is realy set to 17 then you definitelly don't need 26 rollback segments!! Or do you maybe have multithreaded server configuration? For non MTS configuration 17 is far to low value (at least 5 processes are reserved for background processees, depending on the version and configuration you are using the number of background processes can be even much higher), as it will not allow you to have more than about 10 concurent sessions opened.
AFAIK there is no such parameter. Maybe you mean enque_resources. Anyway I don't thing you nid to worry about such an "obscure" parameter unless you are totaly sure this is causing major problems. I think there are far more important parameters that you have to "tune". If your "processes" and "sessons" parameter are sufficiently high you better leave this parameter out of your init file, so that it takes the default value, which is derrived from sessions.
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Click Here to Expand Forum to Full Width