Re: Table not visible to other users

Be sure to specify the fully qualified name of the new table when referencing it.. If created by "owner", its name is actually owner.new_table_name or create a synonym called new_table_name for owner.new_table_name and THEN issue the 'grant select to "read" on new_table_name'  

Joe Cosby <joecosby_at_SPAMBLOCKmindspring.com> wrote:

>
>This is probably a painful newbie question (PNQ). I have worked with
>Oracle as a user but am not an expert by any stretch.
>
>I have inherited an Oracle database and I am going to need to make
>some changes to it.
>
>One thing I need to do is add a table. I have three accounts, roles,
>for this database which were set up by the previous admin; "owner",
>"admin", and "read". I set up a Perl script to talk to Oracle and
>create and populate the table, from the "owner" account. No apparent
>problem, the table was created and populated with the correct data.
>(The changes were committed, I re-connected later to verify this.)
>
>The "read" account is the one which actually runs the live
>application. When I try to select from the new table from the "read"
>account, Oracle tells me that the table does not exist.
>
>As far as I know, the two accounts use the same default tablespace, I
>am not sure how to check that. They both see a set of 20 tables used
>to run the application, and these tables are all in the same
>tablespace. The new table is created within that same tablespace.
>
>This is hard to verify because the "read" account also does not see
>the table "user_tables". When I pull up table_space_name from
>user_tables from the "owner" account, the new table shows the same
>tablespace as the other tables.
>
>They are both looking at the same tables, if I make a change to one of
>the tables that they both see, from "owner", the change is visible to
>"read".
>
>I thought this might have something to do with permission levels but I
>granted "select" privilege on the test table to "read", the permission
>was granted and I committed, but the table is still not visible.
>
>This is probably something simple but I am not sure where to start.
>
>Oh and just to add insult to injury, I do not have the password for
>the "dba" account, which apparently is the default highest-permission
>level account on the database.
>
>Any suggestions would be greatly appreciated.
Received on Mon Nov 25 2002 - 12:38:54 CST