Hi everyone.
I'm with a really weird situation and I need your help.
I have a powercube connection created in cognos and sucessfully tested. My cube works fine with new and old reports.
Here's the catch:
I have a few scheduled reports views for this cube. Most of the times the scheduler works fine, but sometimes gives an error: "BMT.MD-6003 No connection to the data source could be stablished".
Don't know what the cause is, but it's like an intermittent error.
Any ideas?
Plus I'm working with version 11.0.12 of IBM Cognos Analytics.
Thanks in advance.
Quote from: rrvars on 05 Nov 2018 04:40:56 AM
Hi everyone.
I'm with a really weird situation and I need your help.
I have a powercube connection created in cognos and sucessfully tested. My cube works fine with new and old reports.
Here's the catch:
I have a few scheduled reports views for this cube. Most of the times the scheduler works fine, but sometimes gives an error: "BMT.MD-6003 No connection to the data source could be stablished".
Don't know what the cause is, but it's like an intermittent error.
Any ideas?
Plus I'm working with version 11.0.12 of IBM Cognos Analytics.
Thanks in advance.
Hi,
Do you have more than one application server in your CA architecture? If so, it's possible a few of the requests are being load balanced to the second app server, and failing. This is often because the cube is sitting on a drive the first server can see but the second one cannot.
Just a thought?
MF.
Quote from: MFGF on 05 Nov 2018 07:22:30 AM
Hi,
Do you have more than one application server in your CA architecture? If so, it's possible a few of the requests are being load balanced to the second app server, and failing. This is often because the cube is sitting on a drive the first server can see but the second one cannot.
Just a thought?
MF.
Hi MF.
I just have one application server, so I don't think that's the situation.
I know this problem is really weird and probably a "shot in the dark". I've checked the cube time creation just to make sure that the time for the scheduled reports was different from it, and yes. Plus, if it was a problem with mdc creation, would probably give an error in all report views and not only in a few.
I must say this scheduled reports (almost 20) are running at the same time and this error only occurs 2 times a week. Also, it's not for just one cube data source, today I found the exact same error for another mdc data source.
Thanks in advance.