We have a universe which has many tables. Two days ago, when I ran an Integrity Check on the universe structure, I got several messages that the tables are not in the database structure. I tried the insert table command to see if these tables were visible, and they were not. I logged onto SQL*PLUS as the same user as I logged into BO and ran a DESC command (Oracle 7). The command ran fine, so I know that the permissions are set correctly. Next, I ran an Integrity Check to parse the objects (Thorough checking). There were no errors, so BO must have found the correct tables and columns for all the objects. Finally, I ran the reporter module and created a report from objects which were tied to the tables which Designer indicated were not in the database structure; these reports ran fine.
I am totally baffled about what happened here. We were able to see these tables two days ago. Has anyone experienced anything like this? If so, how did you fix it?
We have a universe which has many tables. Two days ago, when I ran an Integrity Check on the universe structure, I got several messages that the tables are not in the database structure. I tried the insert table command to see if these tables were visible, and they were not. I logged onto SQL*PLUS as the same user as I logged into BO and ran a DESC command (Oracle 7). The command ran fine, so I know that the permissions are set…
Hi Mike:
I can’t say I have had this happen with Oracle yet but this has happenned quite often with the old Island Resorts Access Database during my training sessions – the designer module starts to suffer from sudden memory loss for no apparent reason! Sometimes (definitly not always) it seems to fix itself by exiting designer and restarting it - other times, I have had to recreate the universe (Yuk!).
May be someone has seen this with Oracle so we can confirm that this is not just a case of ODBC having a bad day!
Regards,
Chander Aggarwal
COMPUEXCEL
The home of BusinessObjects Essentials
WORLD’S FIRST AND ONLY FULL MULTIMEDIA
COMPUTER BASED TRAINING FOR BusinessObjects! Visit us in Orlando!
I too have experienced this. I believe the details of my situation were as follows:
I developed a universe with the connection parameter’s userid set to the tables’ owner.
At deployment time, I changed the connection to another (read_only) userid.
The next time I opened the designer, I recieved the same message you did (ie, tables not in database structure).
I then had to rename all my tables to OWNER.tablename and left the connection parameters using the non-table-owner account, and I am now able to design the universe with the connection parameters using a read_only account.
The key was to rename all my table objects to OWNER.tablename.
In addition, we have synonyms defined for all our tables as:
CREATE PUBLIC SYNONYM tablename FOR owner.tablename; This however, did not seem to permit BO to acknowledge the existence of our tables when we were using an account other then the owner (of course the other account had been granted the appropriate permission to the synonyms/tables).
I hope that helps.
Donald May
MIS Eagle Services
Pratt & Whitney
Ph: (860) 565-5253 Fax: (860) 565-4347 M/S: 117-35
E-mail: maydp@pweh.com
In addition, we have synonyms defined for all our tables as:
CREATE PUBLIC SYNONYM tablename FOR owner.tablename; This however, did not seem to permit BO to acknowledge the existence of our tables…
If you check the documentation you will see that PUBLIC synonyms are not supported by BusObj.
You can stop BusObj checking for the owner by modifying the prm file (Check_Owner_State) but I wouldn’t suggest this as it obviously will then apply for all universes that are deployed.
Regards
Jonathan
Project Leader
Global Medical, Regulatory and Product Strategy (GMRPS) IS
From: May, Donald P. [SMTP:maydp@PWEH.COM] Sent: 19 August 1998 20:27
I too have experienced this. I believe the details of my situation were
as follows:
I developed a universe with the connection parameter’s userid set to the
tables’ owner.
At deployment time, I changed the connection to another (read_only) userid.
The next time I opened the designer, I recieved the same message you did
(ie, tables not in database structure).
I then had to rename all my tables to OWNER.tablename and left the connection parameters using the non-table-owner account, and I am now able to design the universe with the connection parameters using a read_only account.
The key was to rename all my table objects to OWNER.tablename.
In addition, we have synonyms defined for all our tables as:
CREATE PUBLIC SYNONYM tablename FOR owner.tablename; This however, did not seem to permit BO to acknowledge the existence of
our tables when we were using an account other then the owner (of course
the other account had been granted the appropriate permission to the synonyms/tables).
I hope that helps.
Donald May
MIS Eagle Services
Pratt & Whitney
Ph: (860) 565-5253 Fax: (860) 565-4347 M/S: 117-35
E-mail: maydp@pweh.com
Thanks for you input. I guess what puzzles me is that we had visibility of all the tables on Monday. Even today, we have visibility of 75% of the tables. The connection string has not been altered. So, I am baffled at this state of affairs.
I tried changing the Check_Owner_State variable to ‘N’ to no avail. Iwas looking over the documentation, and it says that this variable is Not Used. Do you know from experience that it does work?
Michael,
I tried to use this parameter (BusObj v4.0) and couldn’t see any difference. I ended up changing all my table names to include the owner. This solved the problem for me. To use linked tables, put a copy of the table structure in your area then Insert it into Bus Objects. You can then delete the copy and Bus Obj will still retrieve data, although if you do an Integrity Check, it will report errors on it. Roger
Mike Malone@CONTEXT
08/20/98 07:34 AM
Jonathan,
I tried changing the Check_Owner_State variable to 'N' to no avail. Iwas looking over the documentation, and it says that this variable is Not Used. Do you know from experience that it does work? Thanks,
Michael
In the .prm file in the subdirectory for your database type there is a setting ‘OWNER=Y’. This createss the assumption that the account that you are using to access the tables is the table owner. Change this to ‘OWNER=N’ and all of the tables should appears, as well as the columns.
I too have experienced this. I believe the details of my situation were as follows:
I developed a universe with the connection parameter’s userid set to the tables’ owner.
At deployment time, I changed the connection to another (read_only) userid.
The next time I opened the designer, I recieved the same message you did (ie, tables not in database structure).
I then had to rename all my tables to OWNER.tablename and left the connection parameters using the non-table-owner account, and I am now able to design the universe with the connection parameters using a read_only account.
The key was to rename all my table objects to OWNER.tablename.
In addition, we have synonyms defined for all our tables as:
CREATE PUBLIC SYNONYM tablename FOR owner.tablename; This however, did not seem to permit BO to acknowledge the existence of our tables when we were using an account other then the owner (of course the other account had been granted the appropriate permission to the synonyms/tables).
I hope that helps.
Donald May
MIS Eagle Services
Pratt & Whitney
Ph: (860) 565-5253 Fax: (860) 565-4347 M/S: 117-35
E-mail: maydp@pweh.com
Sorry, as someone else has already pointed out - it is the ‘OWNER’ flag that needs setting.
Regards
Jonathan
Project Leader
Global Medical, Regulatory and Product Stategy IS.
From: mmalone@CONTEXT.COM [SMTP:mmalone@CONTEXT.COM] Sent: 20 August 1998 15:34
Mike Malone@CONTEXT
08/20/98 07:34 AM
Jonathan,
I tried changing the Check_Owner_State variable to ‘N’ to no avail. Iwas
looking over the documentation, and it says that this variable is Not Used.
Do you know from experience that it does work?
I don’t believe the Designer checks for tables that are in the Public Domain when doing an integrity check. One thing you can do is hard-code the Owner name into the table properties. This way the integrity check can find it.
We have a universe which has many tables. Two days ago, when I ran an Integrity Check on the universe structure, I got several messages
that the
tables are not in the database structure. I tried the insert table
command
to see if these tables were visible, and they were not. I logged onto SQL*PLUS as the same user as I logged into BO and ran a DESC command (Oracle 7). The command ran fine, so I know that the permissions are
set…
Hi Mike:
I can’t say I have had this happen with Oracle yet but this has happenned
quite often with the old Island Resorts Access Database during my training
sessions – the designer module starts to suffer from sudden memory loss
for no apparent reason! Sometimes (definitly not always) it seems to fix
itself by exiting designer and restarting it - other times, I have had to
recreate the universe (Yuk!).
May be someone has seen this with Oracle so we can confirm that this is
not just a case of ODBC having a bad day!
We have a universe which has many tables. Two days ago, when I ran an Integrity Check on the universe structure, I got several messages that the tables are not in the database structure. I tried the insert table command to see if these tables were visible, and they were not. I logged onto SQL*PLUS as the same user as I logged into BO and ran a DESC command (Oracle 7). The command ran fine, so I know that the permissions are set correctly. Next, I ran an Integrity Check to parse the objects (Thorough checking). There were no errors, so BO must have found the correct tables and columns for all the objects. Finally, I ran the reporter module and created a report from objects which were tied to the tables which Designer indicated were not in the database structure; these reports ran fine.
I am totally baffled about what happened here. We were able to see these tables two days ago. Has anyone experienced anything like this? If so, how did you fix it?
Michael,
I had this happen and ran the same checks. If you checked your permissions in SQL*PLUS using your login, also check them with the login and password associated with the connection to the database. I found that a DBA had changed the permissions on the login and password associated with the connection to the database.
Theresa
If you look in the documentation relating to the .PRM files, there is a setting you can change so that the universe will always show table structures regardless if the owner is there or not.
Tim
Tim Heuer
PacifiCare Health Systems
(714) 825-5702 - office
(800) 946-4645 pin 1404017 - pager tim.heuer@phs.com
Whenever I get this message it means that there wasn’t a synonym created for the owner.
We have a universe which has many tables. Two days ago, when I ran an Integrity Check on the universe structure, I got several messages that
the
tables are not in the database structure. I tried the insert table
command
to see if these tables were visible, and they were not. I logged onto SQL*PLUS as the same user as I logged into BO and ran a DESC command (Oracle 7). The command ran fine, so I know that the permissions are
set
correctly. Next, I ran an Integrity Check to parse the objects
(Thorough
checking). There were no errors, so BO must have found the correct
tables
and columns for all the objects. Finally, I ran the reporter module and created a report from objects which were tied to the tables which
Designer
indicated were not in the database structure; these reports ran fine.
Reviving this very old, very dead topic. Is this still the only way to get a public synonym structure into Designer? Must I have the physical table structure in the database in order to get the column names visible in Designer? I want to use a synonym that points to a table in a different database so the table structure isn’t available. I changed ‘OWNER=Y’ to ‘OWNER=N’ in my oracle .prm file and I can see the synonym but not the columns. I also read that perhaps creating a private synonym would get me the columns visible. The basic question remains. Is there no way to see public synonym columns in Designer without implementing a workaround? TIA.
(BOB member since 2002-06-11)