Problem by Replication security!!!

Problem by Replication security!!!

Post by Bostjan Stupic » Wed, 04 Jun 1997 04:00:00



Hello!

I'm working on Oracle Server v7.3 on WinNT.
I have some problems, by protection in replication environment.
Let's say we have the next users:
1. INTERNAL     ... Database Administrator ... SYS
2. SYSTEM       ... What kind of user is that exactly?
3. REPADMIN     ... Replication administrator
4. REPSYS       ... Surrogate Replication administrator (system access)
5. WORK_USER    ... Schema owner
Then I have created the following links from DB1 to DB2:
1. Public database link (without user name and password) owned by SYS
2. Private user link owned by REPSYS
3. Private user link owned by READMIN
4. Private user link owned by WORK_USER

And now the problem ...
When I connect on DB1 as INTERNAL (SYS) I can't access on DB2, because I
have only public link without username and PSW. That is OK.
But when I connect on DB1 as SYSTEM I can access on DB2 ???? That is NOT
OK!!! How can that be, because the user SYSTEM havo no links?

Any Idea?

Bo?tjan ?tupica  /  Ixtlan Consulting d.o.o.  / EMail:

 
 
 

Problem by Replication security!!!

Post by Jurij Mod » Wed, 04 Jun 1997 04:00:00


On 3 Jun 1997 08:22:14 GMT, "Bostjan Stupica"


>I'm working on Oracle Server v7.3 on WinNT.
>I have some problems, by protection in replication environment.
> ..... [SNIP] ....
>Then I have created the following links from DB1 to DB2:
>1. Public database link (without user name and password) owned by SYS
>2. Private user link owned by REPSYS
>3. Private user link owned by READMIN
>4. Private user link owned by WORK_USER

>And now the problem ...
>When I connect on DB1 as INTERNAL (SYS) I can't access on DB2, because I
>have only public link without username and PSW. That is OK.
>But when I connect on DB1 as SYSTEM I can access on DB2 ???? That is NOT
>OK!!! How can that be, because the user SYSTEM havo no links?

>Any Idea?

Obviously your SYS acounts in both databases have different passwords,
while your SYSTEM acounts have not.

If you create db_link without CONNECT TO part of command then then
db_link tries to connect to remote db with username/password of local
user. If such user exists on remote db and have the same password then
connection is succesfull, othervise it is not.

Remember that public db_links are available to all users, so you cant
say your user SYSTEM have no links.

>Bo?tjan ?tupica  /  Ixtlan Consulting d.o.o.  / EMail:


Regards,

============================================================
Jurij Modic                             Republic of Slovenia
tel: +386 61 178 55 14                  Ministry of Finance
fax: +386 61  21 45 84                  Zupanciceva 3

============================================================

 
 
 

1. Problem with merge replication and security.

Hi there.

I'm trying to do a pull subscription on server1 from
server2 but keeps getting security errors all the time.

The snapshotfolder on server2 is a shared folder and you
can access it from server1 but still there is a problem
with security. A pull subscription from server2 to server2
works fine...

These are the errors:

The schema
script '\\THUNDER\C$\Temp\unc\THUNDER_Pharma_Pharma\2001073
1
105418\snapshot.pre' could not be propagated to the
subscriber.  The step failed.

Access is denied.

The process could not read
file '\\THUNDER\C$\Temp\unc\THUNDER_Pharma_Pharma\200107311
05418\snapshot.pre' due to OS error 5.

The schema
script '\\THUNDER\C$\Temp\unc\THUNDER_Pharma_Pharma\2001073
1
105418\snapshot.pre' could not be propagated to the
subscriber.

Any ideas are more then welcome :)

Joachim

2. Sloooooooooow Perfomance.

3. login/security problems preventing merge replication

4. Mac VFP

5. ATTN gurus: replication security problems

6. Workgroup information file missing?

7. Replication security

8. WANTED: Internet technologists

9. SQL Server CE Merge Replication Security

10. Tricky issue - replication/security - any experts?

11. security and replication

12. Replication security