(1) Create a "private" or "public" DATABASE_LINK (check the syntax
yourself) for the applicable user who will be generating the report. Be
aware of security concerns. If the user must change his password every
few months then the database link will have to be dropped and recreated
as part of the process of updating the password.

(2) Next be aware that this user will have to be granted the applicable
privileges at the remote DB explicitly, on the tables/packages/functions
(etc) it will have to access/use to access the required data.

Here we have a user who access data from a "public" DB link and then we
restrict his privileges severely to ONLY that which he needs to do his
task.
A second user uses a "private" DB link to do replication tasks to keep
the DB's in sync for certain data.

Jeff

-----Original Message-----
From: oracledba-return-134224-JEFFERY.L.SCHRENK=saic.[Email address protected]
[mailto:oracledba-return-134224-JEFFERY.L.SCHRENK=saic.[Email address protected]
On Behalf Of karthik ganesan
Sent: Tuesday, October 31, 2006 1:30 AM
To: LazyDBA Discussion
Subject: LINKING TWO DATABASES - URGENT!!!

Hi all,

I've got two oracle databases residing in two different servers. I like
to link both for generating reports that needs data from both. Please
let me know the procedure to do that and also, will there be any issue
while backing up because of the database link created.

Regards,
karthik





---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


Oracle LazyDBA home page