Audit DB from 8.4.1 to 10.2.1

[Nimirod]

Hi all,

We're migrating all Cognos stuff from 8.4.1 to 10.2.1 FP1 but we need to preserve the Audit data for analysis in the same DB. It is possible to do it automatically (as for content store) or shall we go with an ETL tool. If so the Audit tables got the same names and columns (and types) or should we expect some incoherence in this.

Can we run audit reports developed on the old Audit Model (v8.4.1)  against the new one (v10.2.1). I tried to find details about this in docs but didn't find anything.

Thanks for your help.  ;)

[Nimirod]

Hi all,
A little update from my side. I imported the v8.4.1 Audit Package to the new V10.2.1 and much of those reports works but many of them give me errors related to character types...

(http://www-01.ibm.com/support/docview.wss?uid=swg21359432)

So it seems that the types are not equal (maybe useful to use an ETL tool). In v10.2.1 there are 5 new tables but the old (v8.4.1) are still there.

I hope it could help someone else.

Bye.

[bdbits]

There is a new audit package from IBM/Cognos for 10.2. Although many table and column names are the same, there were some changes. Some of these are to accomodate new features that have related audit log entries.

We had made some minor modifications to the audit package. To migrate those, we opened the new audit package in Framework Manager, then re-applied the relevant pieces from the old modified model's transaction history. In FM take a look at Project > View Transaction History and Project > Run Script. It's not terribly difficult to do this. If you publish the new package under the same name you may find most of your reports still work without modifications. If you publish a new package, make sure you relink your reports (this is in the report object properties).

[Grim]

Didn't read everything but here's my $0.02. From a new 10 install...

- Leave the 8.4.1 Audit DB where it is. If you need to report off of it create a new connection to it in 10.
-- You can export/import your previous audit stuffs if really needed.

- Create a brand spankin new empty Audit DB for 10. Let 10 create it's tables.
-- Import new 10 audit samples packages and use those going forward
-- if you have custom audit reports migrate them and upgrade them accordingly