02376-02399: Oracle Resources

This section lists messages generated when resources within the Oracle Server are altered.

Cause:	A resource that is not defined or that is specified twice appears in the CREATE or ALTER PROFILE statement.

Action:	Define the resource before issuing a CREATE or ALTER PROFILE command. Also check the statement to see that each resource is listed only once.

ORA-02377 invalid resource limit

Cause:	An invalid resource limit of 0 was specified.

Action:	Specify a resource limit greater than 0.

ORA-02378 duplicate resource name name

Cause:	The same resource was specified twice in a CREATE or ALTER PROFILE statement.

Action:	Issue the statement again, carefully checking that each resource is used only once.

ORA-02379 profile name already exists

Cause:	An attempt was made to create a profile that already exists.

Action:	Create the profile with a name not already used by another profile.

ORA-02380 profile name does not exist

Cause:	An attempt was made to assign a user to a non-existent profile.

Action:	Assign the user to an existing profile.

ORA-02381 cannot drop PUBLIC_DEFAULT profile

Cause:	An attempt was made to drop the PUBLIC_DEFAULT profile.

Action:	The PUBLIC_DEFAULT profile cannot be dropped.

ORA-02382 profile name has users assigned, cannot drop without CASCADE

Cause:	An attempt was made to drop a profile that had users assigned to it without using the CASCADE option of the DROP PROFILE statement. A profile that has users assigned to it cannot be dropped, unless the CASCADE option is specified. CASCADE reassigns users to the PUBLIC_DEFAULT profile before dropping the profile.

Action:	To reassign all users to the PUBLIC_DEFAULT profile, issue the DROP PROFILE statement with the CASCADE option.

ORA-02383 illegal cost factor

Cause:	A negative value or UNLIMITED cost was specified for this resource in the ALTER RESOURCE COST statement.

Action:	Only positive integer values can be specified for resources in the ALTER RESOURCE COST statement. Issue the statement again, using a positive integer value for each resource specified.

ORA-02390 exceeded COMPOSITE_LIMIT, logoff in progress

Cause:	The COMPOSITE_LIMIT for the profile is exceeded. That is, the weighted sum of the connection time, logical reads per session, CPU usage per session, and private SGA space used during the session exceeded the limit set by the COMPOSITE_LIMIT clause set in the user profile.

Action:	If this happens often, ask the database administrator to raise the COMPOSITE_LIMIT of the user profile, or determine which resource is used the most and raise the limit on that resource.

ORA-02391 exceeded simultaneous SESSIONS_PER_USER limit

Cause:	An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSIONS_PER_USER clause of the user profile.

Action:	End one or more concurrent sessions or ask the database administrator to increase the SESSIONS_PER_USER limit of the user profile.

For more information about SESSIONS_PER_USER and the database administrator's specific tasks of adjusting concurrent sessions, see the index entries on "SESSIONS_PER_USER of CREATE PROFILE" in Oracle7 Server SQL Reference and on "LICENSE_MAX_SESSIONS parameter" in the Oracle7 Server Administrator's Guide.

Cause:	An attempt was made to exceed the maximum CPU usage allowed by the CPU_PER_SESSION clause of the user profile.

Action:	If this happens often, ask the database administrator to increase the CPU_PER_SESSION limit of the user profile.

ORA-02393 exceeded call limit on CPU usage

Cause:	An attempt was made to exceed the maximum CPU time for a call, a parse, execute, or fetch, allowed by the CPU_PER_CALL clause of the user profile.

Action:	If this happens often, ask the database administrator to increase the CPU_PER_CALL limit of the user profile.

ORA-02394 exceeded session limit on I/O usage, logging off

Cause:	An attempt was made to exceed the maximum I/O allowed by the LOGICAL_READS_PER_SESSION clause of the user profile.

Action:	If this happens often, ask the database administrator to increase the LOGICAL_READS_PER_SESSION limit of the user profile.

ORA-02395 exceeded call limit on I/O usage

Cause:	An attempt was made to exceed the maximum I/O for a call, a parse, execute, or fetch, allowed by the LOGICAL_READS_PER_CALL clause of the user profile.

Action:	If this happens often, ask the database administrator to increase the LOGICAL_READS_PER_CALL limit of the user profile.

ORA-02396 exceeded max Idle Time, please connect again

Cause:	A user has exceeded the maximum time allowed to remain idle.

Action:	The user must reconnect to the database.

ORA-02397 exceeded PRIVATE_SGA Limit, logging off

Cause:	This error occurs only when using a multi-threaded server.

Action:	Contact the database administrator to expand the PRIVATE_SGA limit.

ORA-02398 exceeded procedure space usage

Cause:	Stored procedures used up too much space in the SYSTEM tablespace.

Action:	Use fewer stored procedures or add an additional file to the system tablespace.

ORA-02399 exceeded maximum connect time, logging off

Cause:	A user has exceeded the maximum time allowed to be connected to the database.

Action:	The user must reconnect to the database.