We are using Supervisor 4.1.4 on Win95. The repository is Oracle 7.3
running on a NT 4.0 server. We are in the process of Y2K testing all of
the BO modules and have encountered some strange behavior with Supervisor.
The system dates for both the client and the database server have been set
forward. Once they were changed to reflect a future date, any changes made
through the Supervisor module are not relfected unless Supervisor is closed
and started again. When any change is made, like adding a group or a user,
it disappears like it was never added. However, if it is shut down and
restarted, the new group or user appears. All dates for the client and the
server have been set back to todays date and the problem is still occuring.
It seems related to the system date changing on the server, as the problem
still reproduces from a client that has not had any date changing on it. We
also have other repositories that are not on this Y2K test server and
everything works as expected. Any ideas??
When any change is made, like adding a group or a user,
it disappears like it was never added. However, if it is shut down and
restarted, the new group or user appears.
I am not sure of the exact cause of the strange behavior, but I am not sure if
it is related to Y2K. We experienced a similar problem with 4.1.2 and Oracle.
It occurred and acted in this manner (not showing updates) one day, then went
away the next. I was not aware of any Y2K activities at the time on either
the client or server. The problem only occurred for one day.
We put in a ticket to BO tech support, but neither one of us could ever
identify the cause. The problem went away, so we never pursued it any
farther. Don’t know if this helps, but it may give you hope that it will
disappear tomorrow!
Brent Houk
Eli Lilly and Company
(317)433-1911 bhouk@lilly.com
Check the connection string parameters on your BOMAIN.KEY. If it was not
set to “Disconnect after each Transaction” and Lock to “Wait for
Resources” than this could be a problem. Also, check the Repository
users profile on the Database for the resource limits.
Good Luck
We experience this problem on a daily basis. We have our repository in
Access97 and are using BusinessObjects v 4.1.4. There is a known bug to
BusinessObjects that Access cannot adequately handle dynamic updates of the
repository. Sometimes, we can get our updates to show dynamically through
Supervisor, usually after a compact of the Access repository and a scan,
repair & compact from BusinessObjects. The dynamic updates showing are very
short lived, usually only for a couple of hours. For the most part, we
refresh the display in Supervisor by CTRL+Refresh. Using Refresh alone has
no effect.
Best regards,
Crystal Golding
Senior Systems Analyst
Management Information Section
University of Queensland
Brisbane Australia 4072
E-mail: c.golding@mailbox.uq.edu.au
Phone: +61 7 336 57289
Fax: +61 7 336 58202
Where do you go to check this connection string? Is this in Designer or
Supervisor?
Thanks,
Angelia
-----Original Message-----
Check the connection string parameters on your BOMAIN.KEY. If it was not
set to “Disconnect after each Transaction” and Lock to “Wait for
Resources” than this could be a problem. Also, check the Repository
users profile on the Database for the resource limits.
Good Luck
Angela,
There is no way to check the connection string for the
BOMAIN.KEY. That’s why in my message I mentioned how the BOMAIN.KEY was
created. The best option will be to recreate the BOMAIN.KEY, test it
and distribute it only to the security folks who do the security for
Business Objects.
Good Luck
If you are having this issue with ACCESS97 then your problem most likely
lies in having the wrong Middleware Chosen.
If you are using Access97, then make sure you are using the MS ACCESS 97
driver (versus the MS ACCESS 7.0). Both of these drivers handle timestamps
differently. Since the Updates are driven by timestamps, you will not see
the changes until you exit (or relog into) the application.
Change your repository connection to use the other driver (by Recreating the
BOMAIN.KEY) and see if that makes a difference.