Re: Create database link from inside a stored procedure

You know I am not sure I really see an issue with this specific example. I do not believe in allowing tables or indexes to be created on the fly, but this problem is we want to insert data to a remote database and we do not know the database information until we get a request.

So do we submit a create database link request to the dba every time we need to do this or do we use a dba provided package that creates the database link with full Oranet connect information so no tnsnames entry is required, writes an application audit trail, ships the data, and drops the now no longer needed link?

My main issue is will the process work to begin with? In order to reach the remote databases they have to be available to the network of the source db. Now if all targets belong to the company and are on the company network then this is probably not an issue, but if the output has to go accross the Internet then firewalls should stop the messages from ever reaching the remote database to begin with. That is, the database should be behind a firewall and accessed only from application servers (and perhaps from some local IP's). In this kind of setup this process will not work because no Oracle database should ever support direct access from the Internet. The database should always be behind a server.

Just another issue to consider.
-- Mark D Powell -- Received on Thu Mar 30 2006 - 15:00:27 CST