Resource control
Each user profile has eight individual resource limits and one composite limit that can be specified. For each limit, the possible values are an integer or the keywords UNLIMITED or DEFAULT. When DEFAULT is used, the value is replaced by the corresponding value in the DEFAULT profile.
The limits are summarized here:
- COMPOSITE_LIMIT
Weighed sum of CPU_PER_SESSION, CONNECT_TIME, LOGICAL_READS_PER_SESSION, and PRIVATE_SGA. The weights applied to each parameter are specified using the ALTER RESOURCE COST command. Parameters that are not specified take a weighted value of 0. Initially, each parameter has a weighted value of 0. If this value is exceeded, the current operation is aborted, an error message is returned, and the user is only able to commit or roll back and then exit.
Tip
The data dictionary view RESOURCE_COST shows the assigned values for each parameter.
- CPU_PER_SESSION
Total amount of CPU that can be used by the session. Value is in hundredths of a second. If this value is exceeded, the current operation is aborted, an error message is returned, and the user is only able to commit or roll back and then exit.
- CPU_PER_CALL
Total amount of CPU that can be used by any one parse, execute, or fetch call. Value is in hundredths of a second. This can be used to terminate runaway queries. If this value is exceeded, the current operation is aborted, an error message is returned, and the user is only able to commit or roll back and then exit.
- CONNECT_TIME
Total amount of elapsed ...
Get Oracle Database Administration: The Essential Refe now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
