Oracle Tips and Techniques

ORA-00052: maximum number of enqueue resources (string) exceeded

Cause: Ran out of enqueue resources.

Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter.

ORA-00053: maximum number of enqueues exceeded

Cause: Ran out of enqueue state objects.

Action: Increase the value of the ENQUEUES initialization parameter.

ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired

Cause: Interested resource is busy.

Action: Retry if necessary or increase timeout.

ORA-00055: maximum number of DML locks exceeded

Cause: Ran out of DML lock state objects.

Action: Increase the value of the DML_LOCKS initialization parameter and warm start.

ORA-00056: DDL lock on object ‘string.string’ is already held in an incompatible mode

Cause: An attempt was made to acquire a DDL lock that is already locked.

Action: This happens if you attempt to drop a table that has parse locks on it.

ORA-00057: maximum number of temporary table locks exceeded

Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.

Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start.

ORA-00043: remote operation failed

Cause: Execution of the inter-instance operation failed.

Action: Check the status of the target instance. The operation may have partially executed. Verify the result of the intended operation.

ORA-00044: timed_statistics must be TRUE when statistics_level is not BASIC

Cause: The user attempted to set timed_statistics to FALSE when statistics_level was not BASIC. timed_statistics is required to be TRUE to collect meaningful statistics when statistics_level is set to TYPICAL or ALL.

Action: Either set timed_statistics to TRUE or set statistics_level to BASIC.

ORA-00050: operating system error occurred while obtaining an enqueue

Cause: Could not obtain the operating system resources necessary to cover an oracle enqueue. This is normally the result of an operating system user quota that is too low.

Action: Look up the operating system error in your system documentation and perform the needed action.

ORA-00051: timeout occurred while waiting for a resource

Cause: Usually due to a dead instance.

Action: Check for any dead, unrecovered instances and recover them.

ORA-00038: Cannot create session: server group belongs to another user

Cause: An attempt was made to create a non-migratable session in a server group that is owned by a different user.

Action: A server group is owned by the first user who logs into a server in the server group in non-migratable mode. All subsequent non-migratable mode logins must be made by the user who owns the server group. To have a different user login in non-migratable mode, the ownership of the server group will have to be changed. This can be done by logging off all current sessions and detaching from all existing servers in the server group and then having the new user login to become the new owner.

ORA-00039: error during periodic action

Cause: An unexpected error occurred while executing a periodically invoked

Action: Check the error stack for detailed error information.

ORA-00040: active time limit exceeded – call aborted

Cause: The Resource Manager SWITCH_TIME limit was exceeded.

Action: Reduce the complexity of the update or query, or contact your database administrator for more information.

ORA-00041: active time limit exceeded – session terminated

Cause: The Resource Manager SWITCH_TIME limit was exceeded.

Action: Reduce the complexity of the update or query, or contact your database administrator for more information.

ORA-00042: Unknown Service name string

Cause: An attempt was made to use an invalid application service.
ction: Use a valid service name from SERVICE$ or add a new service using the DBMS_SERVICE package.

ORA-00037: cannot switch to a session belonging to a different server group

Cause: An attempt was made to switch to a session in a different server group. This is not allowed.

Action: Make sure the server switches to a session that belongs to its server group.

ORA-00036: maximum number of recursive SQL levels (string) exceeded

Cause: An attempt was made to go more than the specified number of recursive SQL levels.

Action: Remove the recursive SQL, possibly a recursive trigger.