Hi

We have scheduled many jobs in reportcaster as run once immediately , Daily ,
Weekly and monthly . .
Till few days back it was working fine .

But All of a sudden all the jobs irrespective of whatever the frequency is , got
failed.

On seeing the BOTLOG2 , i got the folllowing information for all the jobs which
i scheduled .

************************************QUERY***************************
SELECT MESSAGE FROM BOTLOG2
WHERE STAT_BT_NAME IN
(SELECT STAT_BT_NAME FROM BOTLOG WHERE SCHED_ID = 'S12chu2nd301');

***********************************MESSAGE**************************

Starting task: WebFocus Server Procedure task
Task type: EDA RPC
Starting worker thread
Procedure name: common
Connecting to server EDASERVE with execution id webfocus
Executing focexec.
WFREPORT ID=EANXPOHR
SQLCODE IS 24909 (HEX: 0000614D)
: ORA-24909: call in progress. Current operation cancelled
ROLLBACK ERROR
Task error:Server disconnected, cause 32012 Eda code -12
No report to distribute.

********************************************************************
Any idea ?

Version : 7.1.6

Check this website:

http://www.dbmotive.com/oracle_error_codes.php?errcode=24909

I don't know if this is misleading, but the error appears to have something to do with the version of Oracle:

quote:

ORA-24909: Call in progress. Current operation cancelled

The official Oracle explanation:
The OCI call was invoked when another call on the connection was in progress.

Check if the OCI call is supported when the call is in progress under special conditions; for example, if it is being used by a signal handler.


What this means is that an OCI call (Oracle call interface, the lowest language you can program in to access the Oracle database) is issued, while another call is still being executed.
eg: one OCI call tries to read a cursor, but another OCI call, which closes the cursor is already in progress.

There is a bug when using Oracle version 10.2.0.1 which causes this error. Should you be using this version, you might want to upgrade the version or your Oracle server and / or Oracle client.

Shutdown and restart the Oracle instance that contains your bot tables - you may need your dba to assist in this and you may have to be prepared to lose some data.

quote:

Originally posted by hammo1j:
Shutdown and restart the Oracle instance that contains your bot tables - you may need your dba to assist in this and you may have to be prepared to lose some data.

As this is in Production , It needa a lot of justifications . . It will be great if you give me some justifications for that .

Sorry buddy

I can lead a horse to water but I can't make him drink...