Hi,
I’m using BO 6.5 and created a derived table, but in my machine it works but in others, the sql of it doesn’t apear and in reports returns an error because the sql produced is only two parentesis and the alias.
Did this happen to anyone?
Thanks a lot
Best Regards
Freitich
freitich (BOB member since 2005-07-01)
Freitich;
Welcome to B:bob:B!
Are the users using version 6.5? If they are using an earlier version, then the derived tables won’t work.
MichaelWelter 
(BOB member since 2002-08-08)
Hi!!
Thank you very much for the welcome! 
Thank you for your feedback too.
The users are also using 6.5 so it’s another problem.
Thanks a lot
Freitich
freitich (BOB member since 2005-07-01)
Is this happening all on one machine? In other words, as you work on the universe, are you testing it and seeing these problems on your machine? Or is this also happening to the users?
MichaelWelter (BOB member since 2002-08-08)
No, in my machine it works fine, but in the users machine i won’t work.
freitich (BOB member since 2005-07-01)
After adding the Derived table, did you export the universe to the repository? If so, did you make sure that the users got the latest version of the universe?
MichaelWelter (BOB member since 2002-08-08)
Yes, i exported it to the repository, and the users have the latest version.
Also, i tried to import the universe to edit the universe in another machine and it imported with an error, that had to do with the derived tables, and looking at the derived tables, they had no sql associated, and that’s the same thing with the users reports, they can’t get the sql form the derived tables and just put the parentesis in the query with no sql on it.
Hope my english it’s understandable! 
Thanks
Freitich
freitich (BOB member since 2005-07-01)
Hmmmm, interesting! Open the Derived table in Designer (in edit mode). Is there SQL there? If not, add it in. Then save the universe, export it, and try again. But this time, before the user uses it, have them delete the old copy from their machine, then import a new copy.
MichaelWelter (BOB member since 2002-08-08)
Done that. But still the same results.
When importing the universe in another machine for the designer, the error shown in the importing is connection error, because of not importing the sql from the derived table.
freitich (BOB member since 2005-07-01)
Can you post the exact error that your seeing?
MichaelWelter (BOB member since 2002-08-08)
Hi,
Just interested to know if you ever worked out the problem here as I am experiencing the same thing. Without fixing it or working out what is wrong I am unable to utilise Derived Tables at all which would be a shame. 
thanks - jon
jonh (BOB member since 2002-12-18)
Are all your connections, security etc all mirrored correctly between your machine, server and other workstations?
MikeD 
(BOB member since 2002-06-18)
I believe so. We run very simple 2-tier with a single key file and the ODBC connection defined the same on each PC.
I’ve wondered where the Derived Table definition is stored as it does seem very odd that on a second PC I can see it in the Universe, together with its class and objects but when I try to look at the SQL through “Edit Derived Table” I see no code.
Any further clues would be gratefully recieved.
Thanks - Jon
jonh (BOB member since 2002-12-18)
Are you using the same userid on both workstations? i.e. is this not an auth/permissions problem in BO?
DO you also export them in the correct sequence.
MikeD (BOB member since 2002-06-18)
Mike,
yes, whether I use the same user_id or a different one on the second workstation I still cannot see the code.
I’m not too sure what you mean by exporting in the correct sequence but I can sit on PC1 and add a new DT to the Universe and then export it. I then move to the second PC, import the Universe and I can now see the DT itself but not the code that should be in it.
I have wondered whether it is a connection issue and I must admit I don’t think I am totally across where all the connection info is picked up from.
As stated before we have a common key file (does that contain any connection info?) and then the same odbc connections on each PC which have the same user set up in them. I also log into BO with the same usename on the two PCs. Is there something I am perhaps missing here?
Thanks for your assistance.
Jon
jonh (BOB member since 2002-12-18)
Have you tried running a scan repair on the Repos. via Supervisor, then importing both universes to the 2nd PC?
MikeD (BOB member since 2002-06-18)
What database are you using (Oracle, SQL Server, etc.)? Try reinstalling the related Data Access pack on that PC.
MichaelWelter (BOB member since 2002-08-08)
Scan/repair has the Scan button greyed out for the universe domain - all other domains scan OK saying nothing to repair.
Then ran “Integrity” against the Universe domain and got “The Universe domain “Universe” is no longer valid. (ADM0003)” which doesn’t sound too good. Error message does not give too many hints as to how to fix it up?
Everything else is working OK so there doesn’t appear to be anything amiss with the Universe. Guess I need to follow up on this one though.
I am running Teradata for both the repository and the user database.
jonh (BOB member since 2002-12-18)
jonh,
Have you resolved this (Universe Domain Not Valid)? If so do you mind sharing the workflow on how you did it?
BOB_DW (BOB member since 2004-08-26)
Hi, It was a while ago now but essentially the issue was that in upgrading from 5.1.7 to 6.5 I somehow managed to lose some of the tables of the Universe data model. Once I fixed this up everything was OK. I believe another viewer of the same stream had a similar problem whereby they had created the new Universe tables from a user who had permissions issues ie no-one else (includeing their standard BO users) could see that tables he created and so got the invalid message.
If you follow the URL below you will see another BOBS entry where I more fully documented my problem.
Good Luck
Jon
jonh (BOB member since 2002-12-18)