| Problem in copying production [message #133451] |
Fri, 19 August 2005 02:19  |
vgs2005
Messages: 123
Registered: April 2005
|
Senior Member |
|
|
I have a production DB, Prod which has 2 users: ProdMan and ProdEmp. ProdMan created PRodEmp - both have DBA roles.
I have a development DB, Dev which has 2 users: DevMan and DevEmp. DevEmp created DevMan - both have DBA roles.
ProdMan has the same objects/structure as DevMan and ProdEmp has
the same object/structure as DevEmp.
I would like to create users ProdMan_d and ProdEmp_d in Dev. ProdMan_d will have a copy of the objects of ProdMan (in Prod) and ProdEmp_d will have a copy of the objects of ProdEmp (in Prod).
I think there'll be a problem as PUBLIC has been granted a 'SELECT' on all tables. I just want DevMan and DevEmp to see each other's tables -- and ProdMan_d and ProdEmp_d to see each other's tables.. But they're all in same database and tables have PUBLIC access..
Is it possible to resolve this? thanks in advance..
|
|
|
|
| Re: Problem in copying production [message #133457 is a reply to message #133451] |
Fri, 19 August 2005 02:35  |
kugenuma
Messages: 9
Registered: August 2005
Location: Japan
|
Junior Member |
|
|
There is no problem.
If you grant select on specified-schema to public,
everyone can select specified-schema.object.
grant select on scott.emp to public;
conn hr/xx
select * from scott.emp;
--if hr have own emp,just do it.
select * from emp;
|
|
|
|
| Re: Problem in copying production [message #133459 is a reply to message #133457] |
Fri, 19 August 2005 02:46 |
vgs2005
Messages: 123
Registered: April 2005
|
Senior Member |
|
|
How about the synonyms? The synonyms are created like:
create public synonym tabA for DevMan.tabA;
thus, there can be a conflict if the same synonym is created as:
create public synonym tabA for ProdMan_d.tabA;
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
