If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Cognos 8.3 audit restore on 8.4 issue

Started by Suraj, 03 May 2010 01:26:58 PM

Previous topic - Next topic

Suraj

 ???
We recently upgraded from 8.3 to 8.4.1 and we restored audit db from 8.3 to 8.4.
The issue is 8.4 audit has 18 tables vs. 14 in 8.3. However, all 8.3 tables exist in 8.4.
After restore, it was not logging any more data into the database.
We cleaned it up, re-initialized and it worked for 8.4.
Looks like restore does not let anything to be written on the db from new version.

Has anyone experienced this?
We need old audit data for our analysis.
We are planning on appending data table by table but wondering if there is a better way.
Thanks

angela

I just noticed the exact same thing.  I think I'll open a ticket.  I noticed there was a PK about it but I guess we can't see other people's tickets.

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

PK88928: UPGRADING FROM 8.X TO 8.4 LEADS TO NO LOGGING IN THE AUDIT DATABASE.
...server.Audit.IPF StartService LogService FAILED Log Server Database error <parameters><item name="DB URL"><![CDATA[jdbc...server.Audit.IPF StartService LogService FAILED Log Server Database error...

CognosSupport

Yes, few has opened tickets for these, a bug of course...
I guess the workaround for now is to keep your old audit database separated, publish through FM, and build reports on that...

Regards,
Z

Suraj

Yes, we did open a ticket and confirmed this as a bug.
Cognos support also confirmed that our plan of appending/importing data table by table is the only way for now.
However, there was a FK or PK on one of the table that needed to be removed with a script.

outsidethebox

Could you provide more information on the table name and exactly what you removed? We have the same problem and haven't been able to solve it.

Suraj

The only one that would not copy over is the  dbo.cogipf_sysprops as it violated a primary key constraint.    The rest of them copied over just fine.

Here is the summary of steps:
-> Created a new Audit database on SQL Server
-> From the backup of your 8.3 audit database, I performed a restore using the SQL Server Management Studio
i) right-click the database - Tasks - Restore - Database
ii) select From device  [...] - File - Add
iii) select the .bak file - OK
iv) OK
-> Verify the records are present in any table of the database to ensure proper restore was done
NOTE*** If you will be using the existing 8.4.1 audit database, stop all services prior to doing the following.
-> From the existing 8.4.1 audit database I performed an import of all records from SQL Server Management Studio
i) right-click the database - Tasks - Import
ii) Next
iii) Choose the 8.3 audit database
iv) Choose the 8.4 audit database
v) Copy data from one or more tables or views
vi) Choose which tables you want to import - do all of them EXCEPT COGIPF_SYSPROPS
NOTE*** When I did all of them but that one, I got an out of memory error. I then did them one at a time and this worked just fine. The errors seen previously show up when you try to import the COGIPF_MIGRATION table. In your case there are no records in this table so the errors are irrelevant.
vii) Next
viii) Finish
-> Restart services, run reports and test whether or not auditing continues to work and if history is also available.