use untangle firewall to stop script injection

Tom, What is exec print_table ( 'select * from user_db_links' ) I worked around the tnsnames.ora file in various ways but could not succeed. ORA-02085: database link DISPDC1.world connects to ORACLE.WORLD SQL> create table t12 as select * from table t12 as select * from at line 1: Then,as an alternative, I tried to cretae a database link as below:Ģ connect to dewadba identified by dewadba98 SQL> CONNECT - connected to remote database ORA-02019: connection description for remote database not found SQL> CREATE TABLE T12 AS SELECT * FROM TABLE T12 AS SELECT * FROM at line 1: SQL> CONNECT DEWADBA/DEWADBA - Connected to local database My problem description is detailed below: For example I create database link ora8idevĭatabase link select * from do not have to use the connect to and identified by clauses, if I do not, it will use the login and password of the currently connected user to connect to the remote database. PL/SQL Release 8.1.5.0.0 - you have that setup, you log into the database (the local database - the one you want to create the database link in to connect to the OTHER database) and issue the create database link command (see the sql reference manual for complete syntax). Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production Sqlplus the machine the server you want to create the database link ON works - you've gotten the first step done. You need a tnsnames entry in your tnsnames.ora on the server.

Use untangle firewall to stop script injection