-------------------
A session is causing the concurrent manager to hang. Jobs are pending since
this session is unprocessed by a user. This article describes how to identify
and kill the problem session.
Additional Search Words
-----------------------
select alter sql*plus
Solution Description
--------------------
Perform the following steps to kill the session:
1. Log into SQL*Plus as sys.
2. To identify the problem session, issue the SQL*Plus statement below:
SQL> select session_id, type, mode_held from dba_locks;
(the type should be that of
3. To kill the problem session once identified, issue the following
SQL*Plus statement:
SQL> alter system kill session
The concurrent manager is now free; there is no need to change its status.
No comments:
Post a Comment