Want to get rid of DBLINKS between locations

Question

Hi
We got one challenge to work out, Between location in OWB it creates CONNECTORS. These connectors are nothing but DBLink objects in the database. Basically client does not want this connector to be used in generated code . So we need to suppress this connector somehow. The client feeling that,if it uses dblink it is performance hitch, and moreover we have source and target in the same database
So Can anybody tell me a way to suppress these connectors.
I appreciate your help on this regard
Balaji

Answer 1

Xavier,
This might not possible automatically as it could represent a security breach. One way of doing this is to create an 'on create' DDL trigger on your schema that enqueues a job in the jobs subsystem (you cannot call the grant command directly from the trigger). The job is then executed as soon as possible and explicitly grants the privilege to the user. I have not tried this and don't know if it works, but it might be worth a try.
-- To create a 'on create' trigger in your schema, the code is something like (in this example, the schema is the OE schema):
create or replace trigger on_create
after create
on oe.schema
begin
insert into control_table values (ora_dict_obj_name,'username');
-- ora_dict_obj_name is the name of the created object - this info is available for free from the database;
-- activate the job:
dbms_scheduler.enable('ON_CREATE_GRANT');
end;
-- to create the job schedule:
begin
dbms_scheduler.create_schedule(
schedule_name => 'GRANT_SELECT_SCH',
repeat_interval => 'FREQ=MINUTELY' -- here you can put different frequencies...
end;
-- to create the job:
begin
dbms_scheduler.create_job(
job_name => 'ON_CREATE_GRANT',
schedule_name => 'GRANT_SELECT_SCH',
job_type => 'stored_procedure',
job_action => 'grant_select',
enabled => false
end;
-- the procedure would have to be a dynamic SQL, something like:
create or replace procedure grant_select is
ex_statement varchar2(2000);
begin
-- check if there are rows in the control table
-- if there are no rows exit, if there are rows,
-- for each row in a cursor, select the object name and the user name to create the statement string and run it, something like this:
ex_statement := 'grant select on '||object_name||' to '||user_name;
execute immediate ex_statement;
-- at the end - cleanup by deleting the processed rows in the control table and disable the job:
dbms_scheduler.disable('ON_CREATE_GRANT');
end grant_select;
As mentioned, I did not test this solution and most of it is just pseudocode, but it might be a good starting point.
Regards:
Igor