Reports created in higher version of Cognos if version rolled back

[bren1519]

We upgraded last weekend to version IBM Cognos Analytics 11.1 R3 and I created a couple of reports in the test environment.  We may be rolling the version back to IBM Cognos Analytics 11.0.12.  Will these reports fail because they were created in a higher version?  Just wondered if that was the case if I could do anything prior to the roll back to prevent losing them.  Thanks! Brenda

[Penny]

Hi Brenda

I don't have an answer for your question, but did wonder why you were rolling back if you have time to share.


Thank-you

[MFGF]

We upgraded last weekend to version IBM Cognos Analytics 11.1 R3 and I created a couple of reports in the test environment.  We may be rolling the version back to IBM Cognos Analytics 11.0.12.  Will these reports fail because they were created in a higher version?  Just wondered if that was the case if I could do anything prior to the roll back to prevent losing them.  Thanks! Brenda

Hi,

Did you take a backup of your content store before you moved to 11.1? If not, you're going to struggle to roll back to 11.0 as the content store tables will have been upgraded to 11.1 spec.

Assuming you did, then obviously the new reports won't exist in the backup you took. Before you roll back, grab a copy of the XML report spec for each of the reports you created in 11.1. Pay careful attention to the schema version in the first line. It will be higher than the schema version from 11.0.12 reports. If you are lucky, you can manually set the schema version to the 11.0.12 value and your reports will open successfully when you try to open them in 11.0.12. There's no guarantee it will work, though.

Good luck!

MF.

[dougp]

MFGF is right.  11.0.12 won't know what to do with a 11.1.3 Content Store.  You'll need to use your backup.

Since it's just a couple of new reports, hacking the XML should do the trick.  You may want to open and save an old report in 11.1.3 so you can compare before and after XML.  That will help you identify other possible problems rolling back these reports.

[bren1519]

Thanks!  I did copy and save the xml for each report so will give your suggestions a try if they roll back the version. 

To answer the "why", we had some issues in FM after the upgrade where they had to disable the firewall for data source access.  I don't know all the detail but hopefully this will get resolved with IBM and the rollback will prove unnecessary.

[Penny]

Hi again.  I am just in the middle of an upgrade to 11.1.3 from 11.0.9.  I have upgraded our Test environment - gateway and application server and am doing some initial, but upgrading Framework Manager is next on my list so I am interested in your problem with that if you are able to provide any more details. 

[bren1519]

Hi Penny,
We upgraded Cognos Analytics last weekend to 11.1.3 and since then I was unable to run the metadata wizard either in an existing package or a new one as I would receive a firewall error (I received it trying to connect to an AS400 data source but we were getting it on other data sources as well).  I.T. changed the CAF flag to false and disabled the firewall and it removed the problem but that is not a solution obviously.  IBM advised to upgrade FM as well which was done today but the error persists so that's where we are at the moment.  I'd love to know if you have the same issue or not with your upgrade.

[MFGF]

Hi Penny,
We upgraded Cognos Analytics last weekend to 11.1.3 and since then I was unable to run the metadata wizard either in an existing package or a new one as I would receive a firewall error (I received it trying to connect to an AS400 data source but we were getting it on other data sources as well).  I.T. changed the CAF flag to false and disabled the firewall and it removed the problem but that is not a solution obviously.  IBM advised to upgrade FM as well which was done today but the error persists so that's where we are at the moment.  I'd love to know if you have the same issue or not with your upgrade.

Hi,

You should always keep your FM version and your CA server version aligned - you can get big problems if you don't. Make sure you remember to run the Cognos Configuration for the new FM install too - this keeps the crypto keys up to date.

Cheers!

MF.

[bren1519]

Hi,

You should always keep your FM version and your CA server version aligned - you can get big problems if you don't. Make sure you remember to run the Cognos Configuration for the new FM install too - this keeps the crypto keys up to date.

Cheers!

MF.

So we did upgrade FM on advice from IBM but it didn't help with the firewall error.  I don't know all the ins and outs and not sure if they ran the config or not but I will ask.  Would that have any bearing on the firewall issue?

thanks!

[MFGF]

So we did upgrade FM on advice from IBM but it didn't help with the firewall error.  I don't know all the ins and outs and not sure if they ran the config or not but I will ask.  Would that have any bearing on the firewall issue?

thanks!

I can't tell you for definite that it would, but it's certainly possible. Keeping the versions in sync and making sure the config gets updated will either fix it or rule this out as a cause, so either way you will be one step further forward.

Is FM installed on the same machine as CA? If not, have you added the domain of the FM machine to the CAF Domains list?

MF.

[bren1519]

I can't tell you for definite that it would, but it's certainly possible. Keeping the versions in sync and making sure the config gets updated will either fix it or rule this out as a cause, so either way you will be one step further forward.

Is FM installed on the same machine as CA? If not, have you added the domain of the FM machine to the CAF Domains list?

MF.

Thanks for the info.  I've forwarded both your comments to our IT dept.  Really appreciate the assistance!  Brenda

[Cape Cod Gunny]

Hi,

You should always keep your FM version and your CA server version aligned - you can get big problems if you don't. Make sure you remember to run the Cognos Configuration for the new FM install too - this keeps the crypto keys up to date.

I assume FM = Framwork Manager. What does CA refer to?

[MFGF]

I assume FM = Framwork Manager. What does CA refer to?

Hi,

Yes, FM is Framework Manager. CA is Cognos Analytics :)

I'm guessing the next question is "what does MFGF refer to"? :)

Cheers!

MF.

[Cape Cod Gunny]

I'm guessing the next question is "what does MFGF refer to"? :)

OK, I'll bite. What does MFGF refer to?  8)

[MFGF]

OK, I'll bite. What does MFGF refer to?  8)

That, sir, is the million-dollar question ;)

The one clue I'll give is that my parents bestowed upon me the privilege of having two middle names...

MF.

[bren1519]

I can't tell you for definite that it would, but it's certainly possible. Keeping the versions in sync and making sure the config gets updated will either fix it or rule this out as a cause, so either way you will be one step further forward.

Is FM installed on the same machine as CA? If not, have you added the domain of the FM machine to the CAF Domains list?

MF.

Just wanted to update anyone interested or perhaps experiencing the same issue.  At the advice of IBM we changed the dispatcher URI to .../p2pd/servlet/dispatch.  All is now working :)

Per IBM
"The changes are required only on some of the FM installs due to some OS dependencies or some other requirement. This was a known defect back in the days when we introduced dispatcher URI as bi/ v1/disp.

Essentially bi/v1/disp is targeting p2pd/serlvet/dispatch but just via another route. Using the old URI would not be harmful or would not change product functionality in any case.

I tried to narrow down the issue to any specifics but could not do it from my end. As I mentioned earlier  I was getting the same error using CJAP namespace on my Linux server, but did not get any error using any namespace on newly created Windows server. After changing the URI on FM connecting to my Linux, it worked as expected and also published a package and ran a report off it. After getting satisfactory results informed about the changes to be made."