Discoverer - Report Scheduling

Question

Hi Friends,
I have scheduled discoverer report. Now the status is "Running Query". Can we unschedule this report or need to kill oracle session.
Even if i will kill the session will it take up the next scheduled report automatically.
Pankaj

Answer 1

Hi
Your Discoverer Administrator can unschedule any future schedule so this will stop it being scheduled again.
I appreciate that you may well know how to kill an Oracle session so I include the following for anyone who does not.
To kill a current job, you or your DBA will need access to V$ views, V$SESSION, V$PROCESSS, V$SQLAREA. Also, V$OPEN_CURSOR will have all currently opened cursors.
From V$SESSION you can get the SID and SERIAL#.
SELECT
SESS.SID,
SESS.SERIAL#,
SESS.OS_USER,
SESS.PROGRAM
FROM V$SESSION SESS;
As a DBA, you can kill the session using the following command.
ALTER SYSTEM KILL SESSION 'SID, SERIAL#'
Note: SID and SERIAL# values are separated by a comma and are within single quotes.
In some situations the Oracle.exe is not able to kill the session immediately. In these cases the session will be "marked for kill". It will then be killed as soon as possible.
Issuing the ALTER SYSTEM KILL SESSION command is the only safe way to kill an Oracle session. If the marked session persists for some time you may consider killing the process at the operating system level. Killing OS processes is dangerous and can lead to instance failures, so do this at your own peril.
It is possible to force the kill by adding the IMMEDIATE keyword:
ALTER SYSTEM KILL SESSION 'SID,SERIAL#' IMMEDIATE;
If you're interested in killing sessions at the operating system levele, here's a good link: http://www.dba-oracle.com/tips_killing_oracle_sessions.htm
Best wishes
Michael