[ -- Fri 05 Nov 2010 04:08:57 PM EET]
Hi,
Thank you all for answers. So, for SSDb and DDM I'm clear how to
upgrade, first copy to specific folder and then start new
installation.
But what about reporting database and database that contains mibs?
I've read that when installing OneClick with Report Manager, you
will be prompted for option to import data from the old reporting
database. Did any of you done that?
Hello,
The MIB database will be converted to a mysql db from 8.x to 9.x,
I'm not sure how this works if you're not doing the conversion in
place.
For the reporting DB, there are 2 conversions to be handled:
1. Conversion of the CMS internal DB (Business Objects) - this is
explained thoroughly in the documentation for Report Manager. It
depends on where did you install the CMS database, either in the
embedded MS SQL server shipped with Business Objects or a 3rd party
DB. It's quite convoluted and has several steps that must be followed
exactly.
2. Conversion of the Reporting (MySQL) database from the old schema
and old MySQL version to the new schema and new MySQL version.
Depending on the size, you'll need space and time to accommodate this
conversion (at least 2x existing size of the Reporting DB).
In addition to the conversion, if you want to keep the old reports
instances, you need to carefully back-up the OFS (Output file store)
and IFS (Input file store) of the BOXI server.
Note that I performed all the necessary steps when migrating from
8.1 to 9.0, to get to 9.2 I'm not sure it's possible - BOXI version in
9.2 is 2 version ahead of the BOXI in 8.1 and there could not be a
direct upgrade path for the CMS (MySQL Reporting DB could be fine
though).
I'd check the Reporting Manager docs carefully for the Upgrade
instructions, but IMHO Eugen is right - if you have a low retention
period then I'd save the reports I would need start from scratch in
9.2 by initializing the Reporting DB with as many days of data there
are in Archive Manager.
regards,
Cristi Mitrana
---
To unsubscribe from spectrum, send email to [email protected] with the body:
unsubscribe spectrum [email protected]
