Could anyone give me ideas on the following problem: I messed up the connections between the database and universe by changing the connection string via Supervisor in the repository but not changing the connection in the .UNV file, the result was the universe would not open, and I got the error “The connection associated with the Universe has not been defined. You must create a connection”. Without knowing much about Designer I simply opened another copy of the (same) .UNV file from another PC, changed the connection to what I wanted, exported it to the repository and then imported it back to the C: drive on my PC. I now get message ‘some obselete objects have been removed’ and I am forced to recreate all reports I need to refresh. Is this simply a date problem where the report dates are older than the .UNV file date? Or have I done real damage. Please help.
Make sure that you copy any User Defined Objects files (.udo) onto your PC from the server. Without that, you’ll get that error message.
Michael Welter
Sr. Technical Analyst
AirTouch
I now get message ‘some
obselete objects have been removed’ and I am forced to recreate all reports I need to refresh. Is this simply a date problem where the report dates are older than the .UNV file date? Or have I done real damage. Please help.
We have a production database and a reporting database 99.9% of our connections are defined against our reporting database because our users do not need to run in real time some they run against a drop down.
Anyway, on with my story, I changed a connection from one to the other to run a quick test on some real time data; anyway, when I did this another user lauched some large queries that set off some alarms. I get calls from the DBA; oops, my bad, let me change the connection back. All should be good, right? Nope, about an hour after I made the change this user shows up again hitting the production connection. Why?
This was happening via the BCA, could this have something to do with the user never logging out of BO and security params not getting reset? But I thought this change would picked up when she lauched the query. Isn’t this connection tied to the query/universe not the user’s session.
Help! Any explanations would be appreciated. I’m trying to provide some answers. Thanks.
***************************************************************************** CONFIDENTIALITY NOTICE: This e-mail transmission, and any attachments, is intended only for the use of the individual or entity named above and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in this transmission is strictly PROHIBITED.
If you have received this transmission in error, please immediately notify us at postmaster@kci1.com
If the users don’t log out, the universe doesn’t seem to get re-imported, thus the connection change doesn’t seem to take hold. I think you’ll have to bounce WebI or kill the sessions.
In a message dated 01-07-06 15:56:33 EDT, you write:
This was happening via the BCA, could this have something to do with the
user never logging out of BO and security params not getting reset?
By default, BCA caches login information for 6 hours. It may do the same for connection information as well, since that also comes from the repository. If the same problem occurs tomorrow (or Monday) then something else is going on. But if the problem has gone away between now and then, this could be the culprit.
This setting is to allow BCA to process a bunch of jobs without having to revalidate a user’s login and permissions. It saves time by not having to query the repository to authenticate the same user over and over again. You can set this value to a lower number, with the downside that there will be more I/O on your repository.