Doing some testing before a migration. Using BI 4.1 SP1
Version 14.1.1.1036
When I create a simple query for a report say…using between ‘submit date’ 03/01/2015 12:00:00AM and 03/02/2015 12:00:00AM …
I save the query. Then I go back to edit the query or look at the SQL statement and it shows 02/28/2015 23:30:00 and 03/01/2015 23:30:00.
Each time I ‘Apply changes and Close’ it backs up the time element in the query by 30 minutes. Any ideas?
Thank you
I dont know why you would be migrating to such an old patch level and SP1 is not a good choice, in any case.
You are missing the 4.1 SP3 Webi variable re-write functionality for one .
Thank you for the information. As to why upgrade only to SP1, well some things are not under my control nor my decision to make. I suppose one step at a time and maybe we will get to the current version. In any case, thank you so much for posting about the problem. Hopefully this information will get us a few steps further along that line. It was good to see that others have had some similar issues.
You should show this to the people making the decision.
Without us applying SP3 our migratiion project would have been running a very high risk of failure.
Thanks all for the advice. I was able to get the decision makers to do the upgrade to 4.1 SP5. There have been a few configuration issues that needed correcting. I was not the developer or implementor. What was used was pretty much out of the box defaults.
Only a couple of items or issues now remain and I only have one remaining issue that so far has no solution.
I think it is most likely another parameter/configuration item. Maybe someone can offer some suggestions I can psss along.
Seems most all reports were moved over and execute with a bit greater speed. However, there are two reports that instead of running in approx 50 minutes each, one finishes in a bit over 10 hrs and another finishes in approx 40 hours. Unreal!
The ten hour run has 3 simple queries. The 40 hr run has only one simple query.
I have other reports that are more complex and they run fine.
Of note; both reports contain quite a few objects that I am selecting. So I am thinking there is some limiter or configuration item in either the servers or the universe that is in need of change.
Any suggestions of what to look at and share with those who are responsible for configuring these would be appreciated.
These queries previously ran fine on the old platform. This is run against a Remedy database in Oracle.
(BOB member since 2005-07-18)
.
(BOB member since 2005-01-06)
(BOB member since 2005-01-06)