Home » RDBMS Server » Server Administration » understanding user profile resource parameter CPU_PER_CALL (Oracle Database 19c Enterprise Edition Release 19.0.0.0.0)
understanding user profile resource parameter CPU_PER_CALL [message #684908] |
Fri, 24 September 2021 08:56  |
wtolentino
Messages: 422 Registered: March 2005
|
Senior Member |
|
|
i am trying to understand the user profile resource parameter CPU_PER_CALL. basically i know that this has something to do about the amount of CPU that a single SQL statement can be run.
i alter the profile and set the CPU_PER_CALL to 300 -- for 5 minutes
alter profile NYS_ADHOC_PROFILE_00 limit CPU_PER_CALL 300;
then i purposely run a query
select a.* from table_a a, table_b;
in less than 1 minute it throws an erorr:
ERROR at line 1:
ORA-02393: exceeded call limit on CPU usage
was that the default behavior because if i understand it correctly should have been reach 5 minutes before it throws the error. or was it that the optimizer already knows that the query will go beyond the 5 minutes and that is why it throws the error even before the 5 minutes?
|
|
|
|
Goto Forum:
Current Time: Sun May 04 02:39:09 CDT 2025
|