We have Windows installation (Cognos 8 Reporting with SQL Server), just upgraded to 8.3 from 8.2, when I pointed the 8.3 server to the old content store, it didn't find it and went ahead to create a set of new tables, thus resulted in an empty portal.
One symptom is: our 8.2 content store was using a particular schema name (Cognos_MR3), and the new 8.3 server created a bunch of tables with schema name DBO in the same content store database.
How should we deal with this?
Thanks!
Create a new sql user in your new sql server with the name "Cognos_MR3". (you can choose your own password)
Then run the following script against your content store database:
EXECUTE sp_change_users_login 'Update_One', 'Cognos_MR3', 'Cognos_MR3'
Now put this user and password in cognos configuration against your content store and restart the service.
You should now be back to how it was, and during the booting of the service, the tables will be converted
from 8.2 to 8.3 format. (just click details to see the magic happening)
Got the solution from Cognos Support -- change the owner from our "Cognos_MR3" to "dbo", and then point Cognos server to it.
We've tried this and it works.