Failing Scheduled Job

[adam_mc]

We have a scheduled jobs based on a Cube which is kicked off by a trigger.
During the job, after a couple of the reports have already complete, we encountered failures.

It failed with the following error message:
•   "CM-REQ-4039 An error occurred while reading or formatting the "specification" property value. Protocol violation"
         Note: the report in the job started at 7:09am, but did not give this message until 8:04am

In looking thru the cogserver log, I noticed the following:

•   Several  messages of (or similar to) "Content Manager waited for 601.068 seconds to access objects that are currently locked"
•   Followed by "CM-SYS-5225 Content Manager has detected a long running request. The request took 3286 seconds to finish"
•   Followed by "CM-SYS-5144 While processing your request, Content Manager locked a number of objects for 3286.848 seconds"
        Note: This equates close to the 55 minutes between the report starting and then the failure.

Does anyone have any thoughts about what caused this?
What would "lock" the Content Manager?

Also, how can we setup automatic monitoring for this kind of error/alert?

Any thoughts woud be gratefully appreciated.
Thanks in advance,
Adam.

[MFGF]

We have a scheduled jobs based on a Cube which is kicked off by a trigger.
During the job, after a couple of the reports have already complete, we encountered failures.

It failed with the following error message:
•   "CM-REQ-4039 An error occurred while reading or formatting the "specification" property value. Protocol violation"
         Note: the report in the job started at 7:09am, but did not give this message until 8:04am

In looking thru the cogserver log, I noticed the following:

•   Several  messages of (or similar to) "Content Manager waited for 601.068 seconds to access objects that are currently locked"
•   Followed by "CM-SYS-5225 Content Manager has detected a long running request. The request took 3286 seconds to finish"
•   Followed by "CM-SYS-5144 While processing your request, Content Manager locked a number of objects for 3286.848 seconds"
        Note: This equates close to the 55 minutes between the report starting and then the failure.

Does anyone have any thoughts about what caused this?
What would "lock" the Content Manager?

Also, how can we setup automatic monitoring for this kind of error/alert?

Any thoughts woud be gratefully appreciated.
Thanks in advance,
Adam.

Hi,

What is the underlying data source? Does it by any chance happen to be Oracle?

If so, this might help:

http://www-01.ibm.com/support/docview.wss?uid=swg21344363

Cheers!

MF.

[adam_mc]

Thx MFGF...

Our source database is Oracle and the Content Store database is in Oracle too.
However, the data source for the reports is a Cognos Transformer Cube.

Are you referring to the Content Manager or the data source?

As it's a Cognos Cube, I was under the impression that we wouldn't be accessing the Oracle database.
But, perhaps, my assumption is wrong!

[maxmito]

Hi,
I have the same issue "long running request: but we have MSSQL DB.
An idea?