Reports on DB2

Hi All,

We are moving to DB2 and the universe development in DB2 is in process.
What additional steps need to taken in the report side?

We have both Deski and Webi reports.

  1. Should we have to recreate reports from the scratch? (I believe this is not required)
  2. Just pointing to DB2 universe and some additonal testing of report is sufficient?
  3. Any other extra efforts?

All suggestions / tips are welcome from their similar experiences.
Thanks…


JohnJustus :us: (BOB member since 2007-06-25)

Once the universe is designed successfully with no flaws, then you just need to re-point the reports to that universe. I think that’s sufficient.


Jansi :india: (BOB member since 2008-05-12)

And,You should have the same connection name in both environments.


Arjun (BOB member since 2008-07-28)

When you say moving to DB2, what is the current DB datasource being used?
If its a totally different DB then you need to probably do modifications in the universe for any derived object containing functions specific to current datasource, apart from some tweakings and testing to be carried out while running DeskI reports
That said, there should be no changes on the report side unless the generated SQL in query panel has been overridden
.


haider :es: (BOB member since 2005-07-18)

Thanks for the suggestions.
The current data source is Sybase.
What type of testing should be carried out in Deski? Anything specific? We have lots of reports having Custom SQL, so I believe this SQL has to be modified and validated again… Any thing specific for custom SQLreports?
Thanks…


JohnJustus :us: (BOB member since 2007-06-25)

Reports don’t always re-point well, unfortunately. I have found Deski re-point better than Webi, even with the Webi new mapping feature, I have founf formulae break :nonod:.
Also, you are shafted if you have multiple Dps from different universes - Webi re-points all queries
If the data structures are going to be the same, I would probably go with re-pointing the - existing - universe and making amendments to the existing objects, or replacing the universe, see here:-

https://bobj-board.org/t/106492

Well, you have just hit the nail on the head with regards to, not ,running custom SQL in production :nonod: .
This is going to be a major overhead, especially if many non-Ansi SQL functions are used, as Haider previously mentioned.


Mak 1 :uk: (BOB member since 2005-01-06)

A question Strike now to my mind.
If we point to a Webi report (Which has Custom SQL) from a Sybase Universe to a DB2 Universe, will my Custom SQL be lost?

What major overhead there would be?

Thanks?


JohnJustus :us: (BOB member since 2007-06-25)

If your Custom SQL has sybase related keywords/commands, then you’ve to rework on it to have DB2 commands.

As others said, don’t go for Custom SQL. My clients hate it. It is a real headache for the one who is going to support the report.


Jansi :india: (BOB member since 2008-05-12)

Alost certainly, the SQL will regenerate and refer to the objects that you originally put in the query, prior to amending the SQL.


Mak 1 :uk: (BOB member since 2005-01-06)