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.
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.
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.
Cause: An unexpected error occurred while executing a periodically invoked action. Action: Check the error stack for detailed error information.
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…
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.
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.
Cause: An attempt was made to issue a commit or rollback from a PL/SQL object (procedure, function, package) in a session that has this disabled (by ‘alter session disable commit in procedure’) Action: Enable commits from PL/SQL in this session, or do not attempt to use commit or rollback in PL/SQL when they are disabled…
Cause: An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed. Action: Create the session with a non-empty migration password.
Cause: The session migration password specified in a session creation call was invalid (probably too long). Action: Retry with a valid password (less than 30 chars)
Cause: The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately (because it is rolling back or blocked on a network operation), but it has been marked for kill. This means it will be killed as soon as possible after its current uninterruptable operation is done. Action: No action is required…